Dependency Risks
Most catalog failures are actually dependency failures with a missing proof packet.
This lane maps blocker sources to required evidence, owner lanes, readiness, and the impact area if the dependency stays unresolved.
| Blocker | Required Evidence | Owner | Readiness |
|---|---|---|---|
| Marketplace feed mapping incomplete Channel feed sync Marketplace visibility | Mapped field proof, feed preview, and channel acceptance note | Catalog Ops | red |
| Storefront component fallback not approved PDP rendering Product detail rendering | Fallback screenshot proof and component contract signoff | Storefront Engineering | yellow |
| Search index rebuild not scheduled Search / discovery Facet discoverability | Index rebuild job confirmation and validation query results | Search Platform | yellow |
| Campaign audience rules lagging price-window logic Ad and CRM targeting Paid and lifecycle targeting | Audience rule diff, QA sample set, and campaign relaunch note | Growth Systems | red |
Dependency Blockers
Where catalog release recovery is likely to stall.
DR-21 · Catalog Ops
Field exists in source data, but downstream channel mapping is still incomplete.
Channel feed sync · Marketplace visibilityDR-29 · Storefront Engineering
The UI fallback exists, but release proof has not yet been signed off.
PDP rendering · Product detail renderingDR-34 · Search Platform
Facet configuration is ready, but the index rebuild still lacks an execution window.
Search / discovery · Facet discoverabilityDR-41 · Growth Systems
Audience logic still reflects the old price-window model.
Ad and CRM targeting · Paid and lifecycle targeting