CEDX Store · Commerce & Retail
CEDX Store is the trading console for the whole operation — online, the register, the marketplace, wholesale and the assistant channel — gross sales, open fulfilment and contribution margin on the same row, with the SKUs dragging margin named on a board.
The margin-risk board does not say sales are up. It says one pant is selling at -37.9% net, and which promo code did it. That is the conversation a store console should start.
Runs on demo data. Northline Outfitters is the software's demo workspace, not a customer.
What it is
The Orders tab holds 420 orders with payment and fulfilment state on every row, filterable by channel — online, POS, marketplace, wholesale, assistant — and by state, from unfulfilled to restocked. A 23-item wholesale row at $1.4K pending sits next to a $152.38 online order already fulfilled.
The Products tab lists 340 products with price, stock, promo depth and 30-day units in the row — so a SKU at stock 0 with a 15% promo still running is visible as a problem, not discovered at month end. Inventory value stands at $2.81M at cost.
The Customers tab knows the 180 buyers as segments — new, repeat, VIP, at-risk, wholesale — with orders, lifetime value, channel and last order per row. The top wholesale account shows 49 orders and $107K LTV.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/store.
01 — Overview
Six cards carry the period: $206K gross sales, 420 orders, 207 open fulfil, 36.4% contribution margin against the 28% target, 51% fulfilment rate, and $159K of margin at risk across 85 SKUs. The alerts arrive root-caused: the SUMMER20 code is at 92% of its usage cap with high margin drag, and 142 SKUs sit at or below reorder point.
02 — Orders
Tabs cut the table to all orders, open fulfil, paid or SLA risk; chips stack channel and fulfilment state on top. The rows tell the story plainly — a refunded online order already restocked, a wholesale order pending with 23 items.
03 — Customers
180 customers with segment chips across the top and LTV on the row. The wholesale segment dominates the demo view — rows of 20 to 49 orders each — and the list sorts by lifetime value instead of alphabet.
04 — Products
340 products, 300 active, 160 on promo. Price, stock, promo depth, channel and 30-day units share the row, so the bestseller at 1,540 units and the stocked-out pant at zero are visible in the same glance.
Who runs it
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
Owns the trading brief: gross sales, channel mix and the margin-at-risk board read before the next promo calendar goes out.
margin at risk · $159K
Works the open-fulfil queue and the SLA-risk tab — 207 orders in the demo view — before the carrier cutoff, not after.
open fulfil · 207
Watches promo depth against stock: 160 products on promo, and the ones selling below their margin target already named on the board.
on promo · 160The shape of it
Every figure below is legible in the captures above. Nothing here is a projection of your estate — it is the state of the demo data.
How it runs
Orders land from five channels into one table — online, the register, the marketplace, wholesale and assistant checkout — payment and fulfilment state on the row.
The open-fulfil count and the SLA-risk tab say what to touch first; 207 orders were open in the demo view, with the oldest wholesale rows aged by items and payment state.
The Overview prices the damage as it happens: contribution margin against target, margin at risk in dollars, and the SKUs and promo codes causing it named on the board.
142 SKUs sat at or below reorder point, and the Products table shows stock next to promo depth — so the buy and the discount get argued about together.
One record
Store's captures and its siblings' show the same demo workspace — Northline Outfitters — and the same channel taxonomy. That shared record is the point of the estate.
The four channels on the Orders board — online, POS, marketplace, wholesale — are the same taxonomy Store's donut reports gross sales against, with returns and refunds carried there.
CEDX POSThe register slice of Store's channel mix is the POS floor: tickets, tenders and shifts roll up into the same trading brief.
CEDX CatalogThe 340 products with price, stock and promo depth are the rows Catalog keeps complete and channel-ready.
CEDX InventoryThe 142 SKUs at or below reorder point are where the sales board meets the stock network's reorder logic.
Limits
Finding this out on the third call is worse for you than reading it here, and worse for us.
Start
Open it right now
Your channels, your catalogue
Store with the rest of it
Questions
Yes. Every screenshot is a capture of the running build and you can open the same build at /app/store. It runs on demo data, which the workspace banner makes plain rather than hiding in a disclaimer.
From the demo seed. The sales-by-channel donut and the order table are two views of the same 420 demo orders — nothing on the page is a projection or an industry benchmark.
The dollar value of sales running on SKUs priced under their margin target — $159K across 85 SKUs in the demo view — with the worst rows named on the board along with the net percentage and the promo code involved.
No, and the page does not claim that. The console you see is the trading layer behind the channels — orders, customers, products, discounts and margin — not a storefront editor.
The share of fulfilments closed in the view — 51% in the demo seed — with the open 207 broken out as unfulfilled plus partial, so the queue size is a number and not a mood.
No certification has been issued. What we can evidence about hosting, encryption, tenant isolation and production access is written up on the security page.
Live build, demo data, no card. The margin-risk board is on the first screen.