CEDX Shipping · Commerce & Retail
CEDX Shipping is the dispatch console: shipments, labels and live trackers across carriers and four origins — with slip probability on the in-flight parcels, scan age in hours, and the gap between best quote and paid priced to the cent.
The rate-leak card does not say shipping costs more than expected. It says $605.64 over best quote, and that zone-5 ground parcels are paying a median $4 above best. The fix starts with the number.
Runs on demo data. Northline DC East is the software's demo network, not a customer.
What it is
320 shipments with destination, origin, carrier, service, zone, cost, status and tracking on the row — a $210 freight row to Atlanta reads next to a $6.39 economy parcel, and nobody has to open either to know what it cost.
278 labels linked to their shipments: 233 printed as active postage, 35 waiting in the pack queue, and zero pre-label gates blocking. Voided and refunded are states on the row — a refunded freight label at $44.52 is accounted money, not a mystery.
156 active trackers with last scan, ETA, scan age, hours-past-ETA, slip percentage and carrier on the row. The worst sit at 92% and 98% slip with the cause named — a customs hold, a weather delay, a parcel held at address.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/shipping.
01 — Overview
The cards read 320 shipments, $13K of postage and insurance month-to-date, 100% on-time delivered SLA, 36 exceptions, 39 in-flight parcels at 50%+ slip risk, and $605.64 of rate leak. The chart annotates the month: a carrier rate-card refresh, a six-hour sorter outage at DC-W, a negotiated ground reduction.
02 — Shipments
Search by ship number, city, tracking or order, then filter to in transit, delivered, exception, labelled or draft. The columns keep carrier, service, zone and cost visible so a rate question is answered from the table.
03 — Labels
The label ledger ties each label to its shipment, carrier, service and origin with cost on the row. The pack queue counts what is ready to print; the refunded column accounts for what came back.
04 — Tracking
The tracking board sorts the network's worry: out-for-delivery today (38), stale scans past 24 hours (67), and exceptions needing action (36) — each with scan age and slip probability so the oldest block gets cleared first.
Who runs it
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
Clears the 35-label ready queue and prints against the shipment, not from memory.
ready to print · 35
Watches the stale-scan board — 67 trackers without a fresh scan in 24 hours — before the phone rings.
stale ≥24h · 67
Owns the rate card: zone-5 ground at a median $4 over best is a renegotiation with a number on it.
rate leak · $605.64The 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
A shipment is quoted against the rate card before a label exists — 17 sit in rated — and the leak card remembers what was paid instead.
Labels print from the pack queue — 35 ready, 233 printed — with voided and refunded as accounted states, not missing money.
Every in-flight parcel carries ETA, scan age and slip probability; 67 went stale past 24 hours in the seed, each one aged in hours.
Exceptions arrive coded — address, weather, refused, damage — and aged, so the oldest block is the one somebody clears first.
One record
The four origins on this board are the stock network's sites, and the fulfilments these labels post against come from the order queue. Same demo seed, same numbers.
The ship queue in Orders releases the fulfilments these labels post against — both consoles run on the same 320-row demo seed.
CEDX InventoryDC-E, DC-W, HQ-F and the 3PL node are Inventory's sites; both consoles carry the Northline DC East demo workspace.
CEDX WarehouseThe pack queue feeding these labels is the pick-and-pack floor Warehouse runs upstream.
CEDX StoreStore's fulfilment-rate card — 51% closed fulfil share — is the storefront-side view of this dispatch board.
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 carriers, your origins
Shipping 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/shipping. It runs on demo data, origins and all.
Paid minus best quote, summed — $605.64 month-to-date in the seed — with the worst cluster named on the alert: zone-5 ground parcels paying a median $4 over the best quote.
A tracker with no fresh carrier scan in 24 hours or more. The seed has 67 of them, each aged in hours on the row, because a silent parcel is the one that becomes a support ticket.
The demo uses coded carriers across five service levels, economy through freight. This page deliberately makes no claim about specific carrier integrations — that is a pilot conversation, not a screenshot.
Delivered shipments against their SLA, as the card states. It does not cover the 156 still in flight — those carry slip probability instead, 39 of them at 50% or higher in the seed.
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. Rate leak is a card on the first screen.