UT Studio · Template 23
One operating system for the whole supply chain.
ATLAS connects the customer to the doorstep: CRM, orders, procurement, inventory, warehouse operations, fulfilment, transportation, fleet, last-mile delivery, proof of delivery, returns, refunds and finance — all reading from one dataset, with every metric derived rather than stored.
No sign-up, no external calls. The console runs on a deterministic demo network you can explore end to end.
Live demo network
Every figure below is computed from the same dataset the console renders.
- Hub
- Served city
- Lane
- Orders
- 3.8K
- 11K order lines
- Shipments
- 3.8K
- 28.3K tracking events
- On-time delivery
- 92.8%
- avg transit 1d 16h
- Cost per shipment
- ₹1,738
- 3.0% of revenue
- Network
- 23 sites
- 32 carriers · 164 drivers
Thirteen connected surfaces
Not a dashboard. An operating system.
Each module is a real workspace with its own density, filters and detail records — and every one of them opens onto the others. An order leads to its fulfilment, its consignment, its route, its stop, its proof of delivery, its return and its invoice.
Executive control tower
Network position in one view: active and delayed consignments, SLA breaches, warehouse status, inventory alerts, fleet deployment, carrier performance and cost — all derived from the same records.
ExploreOrder management
The order book with SLA state, allocation, fulfilment, shipments, payment, a merged timeline and any returns raised against it.
ExploreWarehouse management
Sites, zones, bins, inbound, receiving, putaway, picking, packing, dispatch, transfers and cycle counts, per site and across the estate.
ExploreTransportation
Carriers, service levels, lane rate cards, consignment tracking, capacity and a live exception queue that shows only work still in play.
ExploreLast-mile delivery
Today’s routes and stops on a deterministic schematic map, with delivery windows, failed deliveries, cash collection and proof of delivery.
ExploreProcurement
Suppliers scored on OTIF, realised lead time, fill rate and receiving defects, with purchase orders, inbound flow and quality checks.
ExploreReverse logistics
Request, approval, pickup, reverse carrier, warehouse inspection, disposition and refund — every stage derived from the record’s own timestamps.
ExploreCustomer 360 and CRM
One account view across orders, shipments, deliveries, returns, support, CRM activity, SLA history and receivables, with a health score built from all of it.
ExploreFinance and analytics
Revenue, cost of goods, freight cost, margin, refunds, receivables ageing, COD and carrier bill reconciliation — money in integer minor units throughout.
ExploreOne graph
Everything is connected, because it is the same data.
ATLAS models the supply chain as a single relational graph. There is no analytics copy and no per-screen fixture, so a number can never disagree with itself between two screens.
- Every shipment belongs to an order; every order belongs to a customer
- Every shipment carries a carrier, a service level and a rate card lane
- Every delivery stop belongs to a route with a driver and a vehicle
- Every inventory row resolves to a warehouse, zone, bin and SKU
- Every return line references the original order item
- Money is an integer count of minor units, everywhere
These are not claims — they are invariants evaluated live on the Data Integrity screen and asserted by the test suite from the same definitions.
The domain chain
How one record leads to the next.
- 1CustomerAccount, segment, contracted SLA and credit terms
- 2OrderChannel, priority, promised date, payment intent
- 3FulfilmentAllocation to a site, wave, pick, pack, dispatch
- 4ShipmentCarrier, service level, rated freight, scan history
- 5Route and stopDriver, vehicle, sequence, delivery window
- 6Proof of deliverySignature, OTP, photo or safe drop
- 7ReturnPickup, inspection, disposition, restock
- 8Refund and invoiceSettlement, billing, margin
Six real themes
Theming that changes more than colour.
A theme in ATLAS sets semantic tokens only. Switching one changes palette, type family and scale, density, borders, radius, elevation, chart palette, map palette, table rhythm and navigation weight — with no component-level overrides anywhere.
Control
Cool slate and signal blue with compact tables, built for long shifts on the exception feed.
Fleet
High-contrast industrial styling with hazard amber and squared corners for dispatch screens.
Cargo
Warm paper surfaces and container orange with generous spacing for customer-facing work.
Supply
A calm teal planning grid for inventory, procurement and replenishment.
Terminal
Monospaced, zero-radius and hairline-ruled for maximum density.
Enterprise
Corporate navy with a serif display face and layered elevation for reporting.
Use the swatch control in the header to switch theme and light or dark on any page, including this one.
Questions
What this is, and what it is not.
- Is ATLAS a hosted product or a template?
- ATLAS is a commercial front-end template from UT Studio. It ships a complete, connected demo dataset and every operational surface, ready to be wired to your own services.
- Does the demo call real carrier or payment APIs?
- No. Every integration in the Integration Center is a conceptual data flow with a documented scope list. The template makes no external network calls at all.
- How is the demo data generated?
- From a fixed seed at runtime. The whole graph — customers, orders, warehouses, shipments, routes, returns and invoices — is rebuilt deterministically, so every build and screenshot matches.
- What does the map use?
- A deterministic SVG projection of the dataset’s own coordinates. Google Maps and Mapbox appear as the production-grade replacements you would swap in.
Open the console and follow one order all the way through.
Start at the control tower, pick an exception, open its consignment, jump to the route, the stop and the proof of delivery, then look at the invoice it lands on.