Outbound
From the wave to the trailer door
Sales orders, waves, pick jobs, pack stations, manifests and delivery routes. Fulfilment is a governed pipeline, not a pick list exported to a handheld.
Wave 14 · pick jobs
A-pick
31 / 42
B-bulk
12 / 28
Pack 2
9 / 16
Next job · PJ-10492 · 14 lines · short-aisle · offered to RF-17
What it covers
- Waves and pick jobs — Release work from rules. Pick jobs break into tasks and lines the RF can execute without a supervisor rewriting the plan.
- Pack stations — Cartonisation, packaging types and station workflows so the pack bench is part of the WMS, not a side PC.
- Carriers and manifests — Rate shop, freight documents, carrier manifests and SSCC where partners require them.
- Routes and exceptions — Multi-stop delivery routes and an exceptions board so short picks and holds do not vanish into chat.
The fulfilment pipeline
Orders enter from the partner API, files or the client portal. Waves group work. Pick jobs go to RF. Pack closes the carton. Manifests close the carrier. Routes close the journey.
- Sales orders and allocation
- Wave planning and the wave scheduler
- Pick job, task and line hierarchy
- Pack stations and packaging types
- Shipments, manifests and delivery routes
- Outbound exceptions
Shipping maturity in the same product
Cartonisation, EDI 856, AS2, return labels and load verification are warehouse problems. Pathfinder treats them as outbound capability — not a bolt-on TMS you integrate after go-live.
Shown on a dedicated environment
Tell us about the warehouse. We arrange a demonstration on a Pathfinder instance — not a public login from this website.