Monitor Product Readiness
Once Product Readiness has been configured, you can monitor readiness scores directly from the Product Grid and Product Edit Form to understand which products are ready for publication and which still require attention.
Monitor readiness in the Product Grid
The Product Grid provides an overview of readiness across many products, making it easy to identify products that still require work.
- Open the Products page.
- Add the Readiness column if it is not already displayed.
- Review each product's readiness score.
- Filter or sort products to prioritise your enrichment work.
Products may have multiple readiness scores if more than one Readiness Configuration applies.
Review a product's readiness
Open a product to see exactly why it is or is not ready.
- Open a product.
- Select the required Channel and Locale.
- Review the Readiness panel.
- Expand the unmet requirements.
- Update the product information until all requirements have been satisfied.
Understand readiness results
| Result | Meaning |
|---|---|
| 100% | The product satisfies every applicable requirement. |
| 1–99% | One or more requirements still need attention. |
| 0% | No applicable requirements have been met. |
| N/A | No requirements apply to the selected product. |
Improve product readiness
To improve a product's readiness score:
- Complete missing attribute values.
- Correct invalid values.
- Ensure products belong to the correct categories or groups.
- Complete any required reference entity associations.
- Verify channel-specific and locale-specific content.
Readiness scores update automatically after products or Readiness Configurations are modified.
Filter products by readiness
Use Product Grid filters to focus on products requiring attention.
For example, you can:
- Find products below 100% readiness.
- Find products that are fully ready.
- Filter products using a specific Readiness Configuration.
Use Product Readiness outside the PIM
Product Readiness results can be retrieved through the Akeneo REST API, included in product exports, and used to trigger external processes through the Akeneo Event Platform.
These capabilities let you connect readiness results to syndication, publishing, reporting, workflow, and other external systems.
Retrieve readiness results with the REST API
Readiness results are available on the standard product and product model REST API endpoints through the with_readiness query parameter.
| Value | Returned information |
|---|---|
scores_only |
Returns the aggregated score and the scores for each applicable channel and locale. |
detailed |
Returns readiness scores and the unmet requirements associated with each result. |
API request examples
GET /api/rest/v1/products?with_readiness=scores_onlyGET /api/rest/v1/products-uuid?with_readiness=detailedGET /api/rest/v1/product-models?with_readiness=detailed
Use scores_only when you only need to know whether products are ready. Use detailed when the receiving system also needs to understand why products are not ready.
Filter products by readiness
You can filter products and product models according to their readiness results.
This allows an external system to retrieve only the products relevant to its process. For example, you could retrieve:
- Products that have reached 100% readiness
- Products below a specified readiness score
- Products matching a score for a specific configuration
- Products matching several readiness conditions using AND or OR logic
A syndication process can use these filters to retrieve only products that meet the required publishing conditions.
See the dedicated Readiness API documentation for the complete response structure and filtering syntax.
Export products by readiness
Readiness conditions can also be used when selecting products for an export.
Add readiness filters to a product or product model export profile when you need to export products based on whether they meet a particular business goal.
For example, you can configure an export to include:
- Only products that are fully ready
- Products that still require enrichment
- Products evaluated by a particular Readiness Configuration
- Products matching several readiness conditions
Readiness filters determine which products are included in the export. The attributes and other product information included in the generated file are still controlled by the export profile.
React to readiness changes with the Event Platform
The Akeneo Event Platform publishes an event when a product or product model crosses the readiness threshold.
External systems can subscribe to these events and automatically start a follow-up action. For example, a subscriber could begin syndication as soon as a product becomes ready.
Available readiness events
| Event type | When it is published |
|---|---|
com.akeneo.pim.v1.product.became-ready |
A product moves from below 100% to 100% readiness. |
com.akeneo.pim.v1.product.became-not-ready |
A product that was at 100% drops below 100%. |
com.akeneo.pim.v1.product-model.became-ready |
A product model moves from below 100% to 100% readiness. |
com.akeneo.pim.v1.product-model.became-not-ready |
A product model that was at 100% drops below 100%. |
Information included in an event
Each event identifies the affected item and the publishing contexts whose readiness state changed.
- Product events include the product UUID and identifier.
- Product model events include the product model code.
- Events include the exact channel and locale combinations on which the state changed.
Subscribers can use this information to act only on the product and context concerned.
Events are published only when readiness crosses the 100% threshold. They are not published after every readiness calculation.
What can trigger a readiness event?
A readiness state can change after:
- A product or product model is created
- Product information is updated
- A classification or association used by a requirement changes
- A Readiness Configuration is updated
Updating a configuration may affect many products at once. Each product that crosses the readiness threshold can produce an event.
Consider the potential event volume before making significant changes to a configuration used by a large product selection.
See the dedicated Readiness Event documentation for complete payload examples and subscription details.
Choose the right integration method
| Method | Best used for |
|---|---|
| REST API | Retrieving the current readiness state on demand. |
| Product export | Producing scheduled or manually generated files containing a selected set of products. |
| Event Platform | Reacting automatically when a product becomes ready or is no longer ready. |
Example integration flow
- A user completes the missing product information in the PIM.
- The Readiness Engine recalculates the product's score.
- The product reaches 100% readiness for a channel and locale.
- The Event Platform publishes a
became-readyevent. - An external system receives the event.
- The system retrieves the latest product information through the REST API.
- The product is published or syndicated to the appropriate destination.
Frequently asked questions
Why does the same product have several readiness scores?
A product can be evaluated by multiple Readiness Configurations. Each configuration produces its own readiness score.
Why is the score N/A?
None of the configuration's requirements apply to the selected product, so no readiness score can be calculated.
Why hasn't my score updated?
Readiness is recalculated automatically after products or configurations change. Large updates may take time to process.
Can I manually recalculate readiness?
No. Readiness calculations are managed automatically by Akeneo.
Can readiness differ between channels and locales?
Yes. Each channel and locale combination is evaluated independently, so a product may be ready in one context but not another.