A Readiness Configuration defines which products you want to evaluate, the publishing contexts concerned, and the requirements those products must meet.

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

Before you start

To create or manage Readiness Configurations, your role must include the appropriate Product Readiness permissions.

An administrator can manage access from System → Roles by opening a role and reviewing its Readiness permissions.

Create a Readiness Configuration

1. Go to Settings → Readiness.
2. Click Create.
3. Enter a unique code and a clear label for the configuration.
4. Define the products covered by the configuration.
5. Select the applicable channels and locales.
6. Add the requirements products must meet.
7. Review and save the configuration.

After you save the configuration, Akeneo evaluates the relevant products in the background and calculates their readiness scores.

Define the product selection

The product selection determines which products and product models are evaluated by the configuration.

Use selection conditions to target only the products associated with the configuration's business goal. For example, you could select:

• Products in particular categories
• Products belonging to selected families
• Products with particular attribute values
• Products associated with specific groups
• Products matching several combined conditions

Products that do not match the selection are not evaluated by that configuration.

Combine selection conditions

When adding several selection conditions, review the logic carefully to ensure the configuration targets the intended products.

A configuration may overlap with another configuration. This means the same product can have several readiness scores when it is evaluated for different business goals.

Select channels and locales

Select the channels and locales for which readiness should be calculated.

Each applicable channel and locale combination receives its own result. A product can therefore be ready for one publishing context but not ready for another.

For example, a product could be:

• Ready for the ecommerce channel in English
• Not ready for the ecommerce channel in French
• Ready for a print channel with different content requirements

Scope requirements

Requirements can be limited to particular channels or locales.

This is useful when a requirement applies only in a certain context. For example:

• A marketplace description may be required only for the ecommerce channel.
• Legal text may be required only for a particular locale.
• A channel-specific price may need to fall within an expected range.

Configure locale fallbacks

A locale fallback lets a readiness requirement use the value from another locale when the primary locale does not contain a value.

This can be useful when several markets share content or when a local translation is optional.

When configuring a fallback:

1. Select the locale being evaluated.
2. Select the locale that should provide the fallback value.
3. Review the fallback order when more than one fallback is available.

Define readiness requirements

Requirements describe the conditions a product must meet to be considered ready.

A Readiness Configuration can contain up to 25 requirements. Each applicable requirement contributes equally to the final readiness score.

Add a requirement

1. Open the configuration's requirements section.
2. Click Add requirement.
3. Select the attribute or system field to evaluate.
4. Select the condition the product must meet.
5. Enter or select the expected value, when required.
6. Limit the requirement to particular channels or locales if necessary.
7. Save the requirement.

Supported requirement types

Requirements can evaluate product attributes and system fields, including:

Group requirements

Use a requirement group when several checks should be treated as one requirement in the readiness score.

• Use AND when every sub-requirement in the group must pass.
• Use OR when at least one sub-requirement in the group must pass.

The entire group counts as a single requirement when the score is calculated.

For example, you could create an OR group that passes when a product contains either:

• A product image uploaded directly to the PIM, or
• A valid externally hosted image

Non-applicable requirements

A requirement may not apply to every selected product. For example, an attribute requirement does not apply when the attribute is not part of the product's family.

Non-applicable requirements are skipped and removed from the score calculation. They do not lower the product's score.

If none of the requirements apply to a product, its score is displayed as N/A.

Manage Readiness Configurations

From Settings → Readiness, you can review and manage your existing configurations.

Edit a configuration

1. Open the configuration you want to update.
2. Change its product selection, contexts, fallbacks, or requirements.
3. Save your changes.

Akeneo then evaluates the affected products again in the background.

Duplicate a configuration

Duplicate an existing configuration when you need a similar set of requirements for another channel, locale, retailer, or business goal.

After duplication, update the new configuration's code, label, product selection, contexts, and requirements before using it.

Delete a configuration

Delete a configuration only when it is no longer required.

Deleting it removes the associated readiness results from the affected products. This action does not delete or change the products themselves.

Import and export Readiness Configurations

Use import and export operations to back up configurations, move them between PIM environments, or manage several configurations more efficiently.

Export configurations

1. Open the Readiness Configuration list.
2. Select the export action.
3. Choose the configurations you want to export.
4. Run the export and download the generated file.

Import configurations

1. Open the Readiness Configuration list.
2. Select the import action.
3. Upload the configuration file.
4. Review any validation messages.
5. Confirm the import.

Configuration best practices

• Create one configuration for each clear publishing or business goal.
• Use labels that help users understand what the score represents.
• Keep product selections focused and easy to explain.
• Avoid adding requirements that do not help users make a publishing decision.
• Use requirement groups when several alternative values can satisfy the same business need.
• Review locale fallbacks with your localisation teams.
• Export configurations before making extensive changes.
• Test new configurations on a limited product selection before applying them broadly.

Next steps

• Monitor readiness scores in the Product Grid.
• Review unmet requirements from the Product Edit Form.
• Filter and export products based on their readiness scores.