WMS Dashboard
The Warpspeed WMS dashboard is the operator surface of ShipOS. It is what your account manager uses, what our pickers and putaway team check between waves, and what your CFO opens on the first of the month. Everything below is real functionality, not a marketing mockup.
TL;DR
A warehouse management system without a usable dashboard is a database with a lock on the door. Most third-party WMS products were built before the modern web design language and they show it. Brands that work with us routinely describe their previous portal as a 1998 ERP screen with a fresh logo. We took a different approach. The dashboard is treated as a first-class product, with its own designers, performance budget, and accessibility checklist.
The result is a screen that loads in under two seconds on a fresh login, renders a useful summary in the first viewport without scrolling, and respects the brand owner who only has five minutes between meetings to check on yesterday's shipments. It is also the same screen our supervisors use to manage a wave at 3pm with 40 carts running across the floor. Both audiences need to trust the same numbers.
Section 01
The default landing view for a brand owner role surfaces the metrics that actually move the business. Each tile shows the current value, a 7-day or 28-day comparison, and a sparkline. Click through gets you to the underlying order list with the same filter applied.
Default KPI tiles in the Warpspeed dashboard
| Metric | Definition | Default goal |
|---|---|---|
| SLA attainment | Percent of orders shipped within the contracted cutoff | 99.0% rolling 7-day |
| OTIF (on-time, in-full) | Percent of B2B orders delivered on the requested date with full quantity | 98.0% rolling 30-day |
| Order cycle time | Median minutes from order release to label printed | Under 4 hours for D2C, under 24 hours for B2B |
| Units per labor hour | Pick units divided by clocked-in pick hours | Set per facility based on layout |
| Inventory accuracy | Cycle count variance over total counts in the period | 99.5% rolling 30-day |
| Exception rate | Orders that triggered any exception type, as a share of total | Under 2.0% rolling 7-day |
SLA and OTIF are the two metrics most commonly mishandled across the industry. Many 3PLs report SLA against the time the label was generated, not the time the carrier scanned the package. We use the carrier scan timestamp by default because it is the only one a customer experiences. OTIF in our tile counts a partial fill as a miss, which is the convention used by most major retailers in their vendor scorecards[1]. If a brand prefers the looser definition, the tile can be configured per account, but the default is strict.
Section 02
Inventory in ShipOS lives in three layers. Physical position is tracked at the bin level so the WMS can hand a picker the shortest path. Logical availability handles channel reservations, kit components, and safety stock. Financial inventory captures lot, expiration, and FIFO order so finance teams can value on-hand stock at the correct landed cost.
The dashboard surface for inventory shows a searchable table with on-hand, available, committed, in-transit, and reserved by channel for every SKU. A row click opens a detail drawer with bin-level positions, recent receipts, lot and expiration breakdown, and a 90-day movement chart. For brands selling on more than one channel, the reservation breakdown is the most-used view. Marketing campaigns that move volume to a single SKU can drain the buffer faster than replenishment can react, and the dashboard makes that situation visible before it becomes a stockout.
Inventory fields shown on the SKU detail drawer
| Field | Description |
|---|---|
| On hand | Physical units present in the facility |
| Committed | Units allocated to released orders not yet picked |
| Available | On hand minus committed minus safety stock |
| Reserved by channel | Units locked to a specific sales channel |
| In transit | Units on inbound POs with confirmed ETAs |
| Lot detail | Lot code, expiration, supplier, and inbound PO reference |
| Bin positions | Active bin assignments with quantity in each |
| Movement history | Receipts, picks, adjustments, transfers, and counts |
“Inventory is not a number, it is a reservation system with a physical anchor.”
Industry research has consistently linked inventory accuracy to fulfillment performance and customer retention[2]. A brand that trusts the number on the dashboard will sell against it. A brand that does not will keep extra safety stock, which raises holding cost and slows working capital. Getting the inventory layer right is the single most valuable investment a WMS can make.
Section 03
The order board is the home screen for ops and customer service teams. It renders all orders in a configurable kanban or table view, segmented by status. Statuses follow the standard lifecycle: received, validated, allocated, released, picked, packed, manifested, in transit, delivered, exception. Each transition is logged with the user, system, or webhook that triggered it.
Order board filter chips shipped by default
| Filter | Use case |
|---|---|
| SLA tier | Separate same-day, next-day, and standard ship cutoffs |
| Channel | Shopify, Amazon, BigCommerce, manual entry, EDI |
| Carrier and service level | UPS Ground, USPS Priority, FedEx Home, DHL eCommerce |
| Destination zone | Filter to a single carrier zone for transit analysis |
| Exception type | Address invalid, payment hold, inventory short, carrier label fail |
| Hold reason | Customer hold, fraud review, restricted item, missing docs |
Orders showing as exceptions get pulled into a dedicated queue with an owner and an SLA timer. The queue prevents the most common 3PL failure mode: an exception falls into a status nobody owns, sits there for two days, and only surfaces when the brand emails about a chargeback. With a queue and a timer, the next-action and the responsible person are always explicit.
Section 04
Every exception in ShipOS is an object with a type, an owner, an SLA, a status, a root-cause tag, and an audit trail. The dashboard shows them in a queue ordered by remaining SLA time. Standard types include address validation failures, carrier label rejections, inventory short picks, payment holds, and customer requested holds. Custom types can be added for brand-specific cases like serial number captures or hazmat compliance forms.
When an exception is resolved, the user picks a root-cause tag from a controlled vocabulary. Those tags feed the exception analytics tile and the weekly account review. The discipline pays off over months, because patterns that are invisible at order one are obvious at order ten thousand. The brand learns that 60% of address failures come from a single Amazon storefront collecting unverified addresses, or that label rejections spike on Mondays after a carrier rate update.
Section 05
A finance lead does not need to see the slot map. A picker does not need a P&L. ShipOS ships with six default role profiles, each with a customized landing view and a permission set scoped to that role. Brands can also create custom roles for vendors, auditors, or third-party logistics consultants who need scoped read-only access for a specific window of time.
Default role profiles
| Role | Default view | Permissions |
|---|---|---|
| Brand owner | KPI summary plus 7-day order trend | Read everything in their account, manage users, configure rules |
| Operations lead | Live wave board and exception queue | Full operational read and write, no billing |
| Customer service agent | Order lookup with full status timeline | Read orders, post notes, request reships within a daily limit |
| Finance lead | P&L, freight spend, invoice history | Read financial reports, no operational write |
| Picker or putaway | Mobile task list | Scan and update only the active task |
| Read-only auditor | Configurable scoped view | Read access expires automatically after a set window |
Every action is logged with a user identifier, timestamp, and IP address. The audit log is exportable, which matters for SOC 2 evidence collection and for internal investigations when a number on a report does not match an expected outcome. This is table stakes for software in a finance-adjacent workflow but it is genuinely rare in 3PL portals.
Section 06
The dashboard ships with a performance budget. Initial paint should land in under one second on a typical broadband connection, full interactivity in under two seconds. Those numbers are not aspirational, they are enforced by build- time checks. A new feature that pushes the bundle past the budget gets blocked in code review.
Inventory and order events propagate to the dashboard through a websocket channel with a target latency under one minute end-to-end. When the websocket drops, the client falls back to polling at a five-second interval. The user never sees the failure unless they look at the connection icon in the corner.
Section 07
A picker spends their entire shift on a handheld scanner, not a desktop. The dashboard ships a mobile experience that respects that. Tasks are presented as large tap targets. Scanner input is captured with no user action required. Barcode parsing handles the major retail and pharma symbologies including GS1-128 with embedded lot and expiration data.
Every floor action emits an event. Pickers see their own throughput in the corner of the screen, gamified just enough to encourage healthy pace without crossing into surveillance. The same throughput data feeds the labor planning view that supervisors use to balance workloads across waves.
“The picker who scans the box is the user. Everyone else is a stakeholder.”
See it in action
Drop us your latest order export and a SKU list. We will build a sandbox tenant and screen-share the dashboard against your data, no slide deck required.