Awaiting receive
0Hub area
Hub operations
The hub experience is being shaped as a scan-first console with visible exceptions, not as a generic warehouse app. The point is quick, trustworthy cross-dock handling.
Buildable orders
0Ready parcels
0Exceptions
0Receive first, then trust
Inbound manifests need to be accepted in a controlled desk before any pouch scan or parcel build becomes trustworthy.
Scan is the exception hinge
Seal integrity and actual weight should branch into clean exceptions immediately, not leak into later parcel confusion.
Parcel build is a visible merge
When multiple seller pouches converge into one buyer parcel, the hub should make that consolidation legible.
Dispatch closes the operational promise
Carrier, service, tracking, and shipping cost belong together at dispatch so the parcel story stays coherent.
Inbound board
Receive shipment manifests before scanning pouches.
No rows available yet.
Pouch scan desk
Scan, weigh, and branch into exceptions without leaving the console.
- No pouch activity yetRecent pouch scans and exceptions will collect here.
Parcel build and dispatch
Consolidate received pouches into buyer-ready outbound parcels.
No rows available yet.
Operational pressure
This is the fast scan operators need before drilling into any single receive, scan, or dispatch action.
- 0 shipment(s) waiting to be receivedReceiving is the first trust checkpoint. If this queue grows, downstream parcel timing becomes harder to trust.
- 0 pouch(es) ready for scanScan is where seal integrity, weight reality, and exception branching should stay visible.
- 0 order(s) can be consolidatedThe hub desk should make build readiness obvious so staff are not forced to infer it from raw pouch state.
- 0 parcel(s) are ready to dispatchDispatch should feel like the final deliberate handoff, with carrier, service, and cost all visible at once.