Storefront + Demand
STBM
Inventory + Supply
Stock Flow
Customer Care
Follow-Up
Finance + Controls
Margin Guard
Retail operations vertical
Storefront, inventory, replenishment, and customer follow-through as one loop.
Retail teams need a page that feels operational: demand, stock, order exceptions, procurement, and customer care share one platform story.
Vertical operating story
Same cinematic system, configured for this vertical.
Customer promises and inventory posture share one context.
Open
Customer promises and inventory posture share one context.
Retail operations can connect sales signals, replenishment, fulfillment, and service follow-up without shifting tools.
Open retail workspace
The same published package serves root and preview retail hosts.
Open
The same published package serves root and preview retail hosts.
Host aliases choose the retail page through manifest routing rather than edge-specific pages.
Retail can grow by pack, not fork.
Open
Retail can grow by pack, not fork.
Future store, procurement, and inventory details should land as DB-backed configuration over shared primitives.
Built from one platform story
The page, workflow, and workspace entry stay connected.
Composed icon recipe
Open
Composed icon recipe
The hero uses shared icon-composer parts over one reusable app-card stage, so each vertical reads as a configured expression of the same platform.
One publication inventory
Open
One publication inventory
The platform page and vertical pages share one publication path, while each vertical keeps its own audience, route, and operating language.