Platform
Thirteen surfaces, one graph.
ATLAS is not a set of dashboards over a warehouse of copied data. Each module reads the same records, so opening an entity always leads somewhere real.
- Entities modelled
- 45+
- From city to carrier bill
- Warehouses
- 23
- 193 zones · 5.8K bins
- Carriers
- 32
- 115 service levels
- SKUs
- 672
- 4.3K stock positions
- Tracking events
- 28.3K
- Across every consignment
Modules
Every operational surface.
Executive control tower
Active and delayed consignments, SLA breaches, warehouse status, inventory alerts, fleet deployment, carrier performance, delivery success, transit time, shipping cost and the live exception queue.
ExploreOrder management
Order book with search, faceted filters and URL-shareable views. Every order opens onto its customer, items, warehouse, fulfilments, shipments, payment, merged timeline and returns.
Warehouse management
Sites, zones, bins, inventory, inbound, receiving, putaway, picking, packing, dispatch, transfers and cycle counts — per site and across the estate.
ExploreInventory
SKU, product, variant, warehouse, zone and bin with available, reserved, incoming and reorder point. Health is derived at read time: healthy, low, critical, out of stock or overstock.
Transportation
Shipments, carriers, service levels, lane rate cards, routes, dispatch, capacity, delivery windows, tracking history and a live exception board.
ExploreFleet and driver operations
Drivers, vehicles, vehicle types, capacity, utilisation, assignments, maintenance and driver performance measured from actual route work.
Last-mile delivery
Today’s routes, stops, driver assignments, ETAs, delivery status, failed deliveries, rescheduling, cash on delivery and proof of delivery, on a deterministic schematic map.
ExploreProcurement and suppliers
Suppliers, purchase orders, inbound shipments, supplier scorecards, realised lead times, receiving and quality checks.
Returns and reverse logistics
Request, approval, pickup, reverse carrier, warehouse inspection, disposition — restock, repair, dispose, return to supplier or liquidate — and refund.
Customer 360 and CRM
Profile, orders, shipments, deliveries, returns, support, CRM activity, notes and SLA history, with a health score derived from all of it.
Finance and billing
Shipping spend, carrier cost, cost per shipment, revenue, margin, invoices, COD, refunds and carrier bill reconciliation. Money in integer minor units.
Integrations
A catalogue of conceptual data flows to CRM, commerce, payment, carrier, mapping, ERP and messaging systems, each with an explicit scope list.
Platform administration
Users, the nine-role matrix, the theme registry and its token contract, live data-integrity invariants and the audit trail.
Architecture
Derived, not stored.
Statuses that are a pure function of other fields are never persisted. Inventory health comes from on-hand, reservations, quarantine and open purchase orders. A return's stage is read off its timestamps. SLA outcome compares delivery against the promise.
- One deterministic generator builds the whole graph from fixed seeds
- Derivation lives in a separate layer that every surface shares
- List state — search, facets, sort, pagination — is URL state, so views are shareable
- Tables scroll inside their own container; the document never scrolls sideways
- Charts are hand-built SVG that read theme tokens, with a hidden data table for assistive tech
- The map is a projection of the dataset’s own coordinates, with no external tiles
What is deliberately out of scope
So the template stays honest about what it is.
Authentication
There is no sign-in. Role switching changes navigation and visibility only; a production build must enforce the matrix server-side.
Write paths
Nothing in the console mutates the dataset. Every screen is a read model over the generated graph.
Live integrations
No external service is contacted. Integration entries describe flows and scopes, not connections.
Real cartography
The map is a schematic projection, not survey-grade geography or routing.
Media storage
Proof-of-delivery signatures are drawn from a seed; no images are uploaded or stored.
The fastest way to judge it is to use it.
Open the console, switch role and theme, and follow a single consignment from the exception queue to its proof of delivery.