320 orders in the queue. 47 of them scored critical.
CEDX Orders is the order-management console: fulfilments, returns and refunds on one ledger, with an exception score on every order, automation rules previewed before anyone turns them on, and a do-this-next queue that prices the fix.
The risk board does not say some orders are late. It says one order carries a 99 score against $35K, and that clearing the top ten exceptions is worth $169K. The queue sorts itself.
orders.cedxsystems.com — live build
Runs on demo data. Northline Outfitters is the software's demo workspace, not a customer.
320 orders in the workspace124 open fulfilments, 140 logged
$483K in exception value58 orders with high scores, 47 critical
90 returns, 80 refundsone ledger, money back included
What it is
Score, route, ship, close — with the work shown.
Automation rules, previewed before they run
Four rules sit on the fulfilments screen with would-have-applied counters computed on this week's queue: items four or more to ground economy (62 orders), multi-line with partial stock routed by DC load (27), express or past-SLA to the priority pick lane (54), wholesale to freight-quote review (37). One is live.
Counters computed on the real queue, not a sample
Combine hints merge three-shipment customers into one
Ship queue: 124 open, 36 past SLA, 35 partial
orders — screen-2
Returns are a queue, not a folder
90 RMAs with reason, status, amount and age on every row — wrong size, damaged, late delivery, changed mind — and 47 still open across transit and received. Restocked is a state the warehouse closes, not a hope.
Reasons and statuses as filter chips
Needs-restock and damaged get their own tabs
Gross RMA amount $8.2K, on the card
orders — screen-3
Refunds reconcile to the processor
80 refunds with method, reason and status on the row — card, wallet, store credit, bank; cancel, goodwill, not as described. Twenty-three sit pending with the processor, and a $4.1K card cancel sits in failed, visible rather than vanished.
Completed $11K, pending 23, on the cards
Failed and reversed are first-class states
Filtered total $119K across 80 rows
orders — screen-4
Product tour
Four screens, captured from the running build.
Not a mockup and not a concept deck. This is what opens at /app/orders.
orders.cedxsystems.com
01 — Overview
The OMS brief, with the risk priced
The cards read 320 orders, 124 open fulfilments, $483K of exception value across 58 high-score orders, $186K of late-ship exposure, 47 critical exceptions and 47 open returns. Below them, the do-this-next queue prices the day: clear the top ten critical exceptions for $169K at impact 9, effort 3, confidence 0.86 — or add two hours of overtime at the Denver DC tonight.
OMS health 40: fulfil, critical, late-ship, returns
Exception board: scores to 99, exposure to $35K a row
02 — Fulfillments
The ship queue, with a robot that shows its work
The queue works by location — Denver DC, wholesale cage, Portland store, Austin store — with a freight order aged 68 hours at the top. Above it, the rules engine prints its counters, and the combine hints price the saving: four customers with three open shipments each, mergeable to one with the label-and-pick saving estimated.
Automation preview: would have applied to 62, 27, 54, 37 orders
Combine groups carry an estimated saving per group
Location chips match the fulfilment sites
03 — Returns
Ninety RMAs, forty-seven open
The returns ledger ties every RMA to its order and customer, with reason and amount on the row. Damaged goods in transit read next to wrong-size restocks, and the disposition queue counts what is still waiting: 47.
RMA, order, customer, reason, status, amount per row
Opened date and age visible in the table
Open queue: transit plus received, 47 rows
04 — Refunds
Eighty refunds, twenty-three with the processor
The money-back side of the ledger: every refund carries amount, method, reason and status. Pending, reversed, failed and completed are all on the table — including the $4.1K card cancel that failed and stayed visible.
Methods: card, wallet, store credit, bank
Reasons: cancel, goodwill, not as described, sizing
Status column never blanks a failure
Who runs it
Three roles work the queue.
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
Fulfilment ops
Works the ship queue by location — 124 open, 36 past SLA — and merges the combine groups before the pick starts.
ship queue · 124
Dispatch
Takes the priority pick lane the rules badge for them — 54 orders this week — and clears the 68-hour freight row first.
past SLA · 36
Order operations
Owns the exception board: 47 critical, the do-this-next queue, and the overtime call when it arrives priced at impact 8.
critical · 47
The shape of it
What the demo order book actually looks like.
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.
320orders in the workspace+8.1% on the card
$483Kexception value58 orders with high scores
$186Klate-ship exposure73 orders with breach probability at or above 55%
47critical exceptionsand 47 open returns awaiting disposition
Orders by channelshare of seed · from the Overview board
Online48
POS22
Marketplace18
Wholesale12
Fulfilment progress140 fulfilments logged against 320 orders
An order's life, in the order it actually happens.
01
Score
Every order takes an exception score as it lands — 58 score high and 47 critical in the seed — with the dollar exposure attached to the score.
02
Route
Automation rules preview their effect before anyone turns them on: ground economy would have caught 62 orders this week, and the counter says so.
03
Ship
The queue works by location and promise date: 124 open, 36 past SLA, 35 partial — with combine hints merging three-shipment customers into one parcel.
04
Close
Returns restock or write off, refunds complete or reverse, and the ledger stays open until disposition — 47 RMAs were still waiting in the seed.
One record
The order is the record the estate already keeps.
Orders links back to the catalog from its own console, and its channel taxonomy matches the sales board's. The record underneath is shared, not synced.
Finding this out on the third call is worse for you than reading it here, and worse for us.
Orders is not generally available. What opens today is the live build running on demo data — Northline Outfitters is the software's demo workspace, not a customer.
We have no named customers to show you, so this page shows none. The buyers, customers and order rows in the captures are the demo seed.
Exception scores and late-ship probabilities are the demo model's output on demo data. They are not a claim about your order book.
The automation-rule counters are previews computed on the demo queue — the screen says would have applied, and one rule is live. A person turns rules on; we do not claim the bot's decisions are certified.
Freight-quote review on wholesale orders is workflow routing, not a carrier rate claim. No audit or compliance certification has been issued; the security page carries what we can evidence.
Yes. Every screenshot is a capture of the running build and you can open the same build at /app/orders. It runs on demo data, which the workspace banner makes plain.
What is an exception score?
A per-order risk score, visible on the board — 99 on the worst rows — with the dollar exposure next to it. The queue sorts by it, which is how 320 orders become a 47-row work list.
What does the late-ship forecast do?
Flags orders whose breach probability passes 55% — 73 orders worth $186K in the seed — before the promise breaks rather than after, so the fix is a routing change or an overtime call, not an apology.
Do the automation rules act on their own?
The demo shows them as previews with would-have-applied counters and a toggle per rule; one is live. A person turns a rule on after seeing what it would have done to this week's queue.
How do returns and refunds relate?
Two tabs of the same ledger. The RMA tracks the goods — received, restocked, written off — and the refund tracks the money — pending, completed, reversed, failed — and both stay open until disposition.
Is CEDX Orders audited or certified?
No certification has been issued. What we can evidence about hosting, encryption, tenant isolation and production access is written up on the security page.
The queue already knows which orders matter.
Live build, demo data, no card. The exception board is the first screen.
