Administration
Production Administration Console
Operator-facing control surface for Channel X. Keep onboarding, role access, attribution, catalog visibility, and commerce diagnostics moving from setup into live execution.
Overview
Administration workspace tuned for Channel X operator flow.
Loading workspaces…
North star
Dashboard intelligence
docs/NORTH_STAR_DASHBOARDS.md
The North star is one intelligence layer for the whole network: the same L1–L9 function operators see here is what merchant→retailer and retailer→shopper consoles use—so capability and capacity stay aligned on functional, achievement-oriented surfaces.
Sign in: /login · /cx-ops/login · local dev http://localhost:3004
Related consoles · same intelligence layer
Messaging § D
Exit criteria deck (anchor).
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.
Supply chain tower
L1–L9 + operator posture.
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 ↔ Channel X
Retail Auctus keeps listing velocity, seller onboarding, and attributed-sale proof on its product. Channel X 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: Channel X must load Retail Auctus on RA’s hostname, never this app’s origin.
- When Retail Auctus delegates a contact action from the embed, Channel X 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.
Active tab command deck
Overview command deck
Run the top-level operator loop here: review network alerts, confirm rollout posture, and check whether merchants, retailers, shoppers, and revenue signals are moving coherently.
Alerts
0
High-signal items the operator team should review first.
Merchants
0
Merchant records currently visible to ops for readiness and account review.
Attributed sales
0
Latest production-facing revenue signals available in this environment.
Transportation
Control tower
Transportation queue and admin actions are managed from this Ops control tower.
