Dispatch · Dispatch Board
Keep custody visible at every handover.
Support cannot answer where an order is when a carrier handover exists only in calls or a courier portal.
This is a capability inside Lightning Pharos, not a separate product.
Scan a package handover to a named carrier.
01 · What ships
The complete working surface.
Getting the order out of the door with a custody trail.
- 01
Handover to a courier or aggregator recorded as a custody event, with a timestamp and a named actor
- 02
Daily manifests with sign-off
- 03
Custody status and silence-window exceptions
- 04
Adapter refresh and a Shopify handover event where configured
02 · Connected work
One action. One history. More than one team.
Pharos keeps the source action and the records it affects on one inspectable event path.
- 01 / 03
Source action
Scan a package handover to a named carrier.
- 02 / 03
Governed event
Each custody change receives an actor, time and shipment status.
- 03 / 03
Connected result
The manifest, custody status and silence-window exceptions follow one trace.
03 · What it needs
Ready inside every Pharos workspace.
No additional module is required before this capability can be switched on.
04 · Where it stops
The boundary is part of the product.
There is no pick-and-pack workflow or return-to-stock flow. Courier and Shopify providers are not yet claimed as live-verified integrations.
Bring your exact workflow to a walkthrough and we will show where Pharos fits and where it does not.