Plentrove
Supply chain control tower
DC → store → DTC: network nodes, ATP-style inventory, transfer orders, TMS shipments from checkout, and ASN receiving with variance. Writes require admin; sellers may adjust stock for their SKUs.
North star
Dashboard intelligence
docs/NORTH_STAR_DASHBOARDS.md
Supply chain uses the identical North star intelligence layer as partner and ops dashboards—one L1–L9 stack for execution and readiness across the network.
Related consoles · same intelligence layer
Platform ops
Admin L1–L9 + posture + § D.
Messaging § D (ops)
Open ops, then production tab.
Merchant hub
Same L1–L9 north star; merchant→retailer lane.
Retailer hub
Same L1–L9 north star; bridges merchant and shopper.
Shopper hub
Same L1–L9 north star; retailer→shopper lane.
Logistics dispatch
L1–L9 + session hint.
Live data loops (L1–L9)
Session probes for L1–L9 (identity, catalog, listings, orders, workspace, ops API, payments, RA embed, UPM embed). Production readiness follows in this card when shown.
Network handoff
Retail Auctus ↔ Plentrove
Retail Auctus keeps listing velocity, seller onboarding, and attributed-sale proof on its product. Plentrove keeps the enterprise shell aligned: this North star strip, marketplace routes, and the live Retail Auctus embed so operators and partners see one coherent posture.
Retail Auctus embed (L8): checking…
- The L8 chip above reflects the live embed contract: Plentrove must load Retail Auctus on RA’s hostname, never this app’s origin.
- When Retail Auctus delegates a contact action from the embed, Plentrove receives it through the same intake as the site contact form (brief on-page confirmation).
- Merchants: Retail Auctus–tagged paid orders surface in Sales insights when buyers use RA-tracked shop entry points.
Production readiness
Supply chain environment posture
Evaluating automated production readiness and L1–L9 dashboard loops for this environment.
Current blockers
No automated blockers from the health bundle or public catalog right now. Complete manual verification (messaging, attachments, role smoke) before declaring full production.
Operator next actions
- Loading /api/health/bundle, identity, commerce orders, admin dashboard, embed URLs, and public catalog…