Oryx: Feature sets

Edit on GitHub

A feature set is a group of related features that can be added to an Oryx application with a single reference. Feature sets simplify the process of setting up an application by reducing the amount of boilerplate code required to configure and initialize the application.

There are two types of feature sets: domain and application feature sets.

Domain feature sets

A domain feature set is an aggregation of the features related to a certain functionality or domain. For example, the product feature set exposes all available product features. This includes components and the associated business logic.

Application feature sets

An application feature set is an aggregation of the features related to a certain business model, such as B2C, B2B, marketplace, or fulfillment. Such feature sets are usually bigger and can include features from different domain feature sets.

Application feature sets can be seen as demo apps, because one such set lets you quickly set up a project without developing. However, a standard feature set might be too opinionated for your production application, which is why you might want to extend an existing set or create your own. For more details about creating feature sets, see Create feature sets.

Available application feature sets

Oryx includes predefined feature sets that cover common use cases for web applications. The application feature sets are provided in the presets package. The following feature sets are available:

  • b2cFeatures: features commonly used in B2C applications.
  • fulfillmentFeatures: features used in PWAs, used for picking products for fulfillment.

Static experience data

Feature sets contain static experience data. Experience data includes the structure and layout of the components of an application. Feature sets provide all the static pages data that is required for the application experiences. For example, the b2cFeatures feature set comes with the following static data:

  • Home page
  • Search page
  • Category page
  • Product Details page
  • Cart page
  • Checkout page
  • Login page

Application feature sets reuse each other’s pages and introduce their own.

Static experience data is provided using the ExperienceStaticData injection token. Although feature sets provide standard experience data, you can provide your own using the same mechanism:

const app = appBuilder()
    providers: [
        provide: ExperienceStaticData,
        useValue: [header, footer, ...pages],

Here’s an example of static experience data for the Login page:

export const loginPage = {
  type: "Page",
  meta: {
    title: "Login Page",
    route: "/login",
    description: "Login Page Description",
  options: {
    data: {
      rules: [{ layout: "flex", padding: "30px 0" }],
  components: [
      type: "oryx-auth-login",
      options: {
        data: {
          rules: [{ width: "50%", margin: "auto" }],

To better understand the data structure, see Compositions.

By utilizing the static experience data provided in Oryx presets, you can easily set up the overall structure and layout of your application, including common sections like the header and footer, without having to write the code from scratch.


The labs package provides experimental features that are not designed for production environments. Experimental features may evolve into standard feature sets over time, but this is not guaranteed. You can use a labs feature set in your demos, POCs, or local development.

Create feature sets

In addition to the provided feature sets, you can create custom sets tailored to your business requirements. To create a custom set, create an array of feature objects that implement the AppFeature interface and pass it to the withFeature() method of the appBuilder() object. Example:

import { appBuilder } from "@spryker-oryx/core";
import {
} from "/docs/scos/dev/front-end-development/202404.0/oryx/my-features";

const customFeatures = [customFeature1, customFeature2];

const app = appBuilder().withFeature(customFeatures).create();