Product analytics reports whether products are ready for POS, Kiosk, Display, and Online use. Catalog governance currently creates and tracks review-only multi-store rollout requests; it does not copy, publish, or activate a product in a target store.
Diagnose channel blockers
Open Product analytics and select Refresh. Review fully launch-ready products, products with blockers, active products, total catalog size, the Launch watchlist, Channel action map, and Products needing attention. Open a blocked product and correct the first reported reason, then refresh the snapshot.
Use Export readiness CSV when owners or implementation teams need a dated review list. The export reflects the current readiness snapshot, not future activation and not provider delivery. Sales trend by product is explicitly unavailable until POS order data is linked to the catalog; use Menu mix report for available sales evidence instead.
Create a rollout review request
- Open Catalog governance.
- Search and select one Source product.
- Review the Source readiness snapshot for POS, Kiosk, Display, and Online blockers.
- Choose one or more Target stores and add a useful Rollout note.
- Select Create propagation request.
Each new request enters pending review. A blocked source can still be recorded for review, so creating the request is not evidence that the product is safe to publish. The target store must validate its local category, pricing, tax, availability, inventory, modifier, and channel requirements separately.
Understand the review-only status board
Use Rollout status board and Propagation queue to filter by status, store, product, or note. This page can update records among pending review, missing, overdue, and not participating. Ready and active are legacy or domain-service statuses and are not selectable from this review-only queue.
Changing the row status does not perform a POS-safe propagation, create a target-store product, or activate a menu. It records rollout tracking and audit evidence only. Do not tell a store that a product is live based on the queue status.
Verify real target-store availability
After local implementation is completed through an authorized product workflow, sign into the target store context and verify the product record, category, price, tax, modifiers, inventory mapping, availability, and intended channel flags. Place a controlled test order on every intended channel. Keep the governance request and note as coordination evidence, not as the activation mechanism.