Product Readiness is in beta. It is available for evaluation and early use, but its features, configuration options, and API contracts are still evolving and may change or be removed before general availability. We recommend against relying on it for business-critical workflows until the full release.

A Readiness Configuration defines which products or product models to evaluate, the channels and locales concerned, and the requirements those entities must meet.

You can create separate configurations for different retailers, markets, campaigns, compliance checks, or other business goals.

Before you start

To open the Readiness Configuration list, your role needs permission to view Readiness configurations. To create, edit, duplicate, or delete a configuration, your role also needs permission to edit Readiness configurations.

Administrators manage these permissions from System > Roles. Permissions for the Readiness External API are managed separately.

Create a Readiness Configuration

1. Go to Settings > Readiness.
2. Click Create.
3. Enter a unique code and at least one clear label.
4. Choose the entity levels to evaluate: products, product models, or all levels.
5. Define the product selection.
6. Select the applicable channels and locales.
7. Configure one-step locale fallbacks if needed.
8. Add the requirements the selected entities must meet.
9. Choose whether the configuration remains a draft or is enabled, then save it.

Draft configurations are not evaluated and do not produce scores. Enabling a configuration starts background calculation for the products and product models in its selection. When an enabled configuration changes, updated scores may take time to appear.

Define the entity levels and product selection

The entity level determines whether the configuration evaluates products, product models, or both.

The product selection determines which entities are evaluated. You can target entities using conditions on family, category, group, status, attribute values, and other supported product-selection fields.

Combine conditions with AND or OR logic when necessary. Keep the selection easy to explain because the same entity can match several Readiness Configurations and receive separate scores from each one.

Entities outside the product selection are not evaluated by the configuration.

Select channels and locales

Select the channels and locales for which readiness should be calculated. Each selected channel and locale combination receives its own result.

A product can therefore be ready for one publishing context and not ready for another.

Requirements are evaluated in every selected context. They are not scoped individually to specific channels or locales. For scopable or localizable attributes, Readiness automatically evaluates the value that corresponds to the channel and locale currently being scored.

Configure locale fallbacks

A locale fallback tells Readiness to evaluate another locale when the value for the evaluated locale is empty.

For example, you can configure fr_CA to fall back to fr_FR.

Fallbacks support one step only. A chain such as fr_CA → fr_FR → fr_BE is not supported.

Use a fallback only when content from the fallback locale is acceptable for the target market.

Define readiness requirements

A Readiness Configuration can contain up to 25 individual requirements. Each applicable top-level requirement has the same weight in the score.

Add a requirement

1. Open the configuration's requirements section.
2. Click Add requirement.
3. Select an attribute or supported system field.
4. Select an available operator.
5. Enter or select the expected value when required.
6. Under Applies on, keep All channels or select one or more channels where the requirement should be evaluated.
7. Save the requirement.

The available operators depend on the selected field type.

Group requirements

Use a requirement group when several checks should count as one top-level requirement:

• An AND group passes when every applicable child requirement passes.
• An OR group passes when at least one applicable child requirement passes.

The group counts as one top-level requirement in the score, regardless of the number of children it contains.

Non-applicable requirements

An attribute requirement is skipped when the attribute does not belong to the product's family. For a product model, the requirement is still evaluated when the attribute is defined at a lower level. 

Skipped requirements do not lower the score. If every top-level requirement is skipped, the result is N/A.

Choose which channels each requirement applies to

By default, every top-level requirement applies to all channels selected in the Readiness Configuration.

To limit a requirement to specific channels:

1. Go to the Define readiness requirements section.
2. Open the Applies on menu for the requirement.
3. Keep All channels, or select the channels where the requirement should be evaluated.

For a requirement group, channel applicability is configured on the group. All requirements inside the group follow the channel selection defined for that group.

Manage Readiness Configurations

Edit a configuration

Open a configuration, make the required changes, and save. Changes to an enabled configuration can trigger background recomputation for many products and product models.

Duplicate a configuration

From the Readiness Configuration list, use the duplicate action when you need a similar selection or requirement set for another business goal. Give the copy a unique code and review every setting before enabling it.

Delete a configuration

Deleting a configuration removes its associated scores without changing the products or product models themselves. This action cannot be undone.

Import and export Readiness Configurations

Configuration import and export use the PIM's standard Imports and Exports areas. They are not actions on the Readiness Configuration list.

• Use a Readiness configuration export job to generate a YAML file containing configuration definitions. Scores are not included.
• Use a Readiness configuration import job to create or update configurations from YAML.

The destination PIM must contain every referenced channel, locale, attribute, option, category, group, currency, and other required entity.

Configuration best practices

• Create one configuration for each clear publishing or business goal.
• Use drafts while a configuration is incomplete or under review.
• Keep product selections focused and easy to explain.
• Use requirement groups only when the children form one business rule.
• Review locale fallbacks with your localisation teams.
• Check the affected entity count before saving a broad change.
• Export configurations before extensive edits or environment migrations.

Next steps

• Monitoring Product Readiness.
• Product Readiness permissions & access.
• Product Readiness FAQ.