Decision tables and event triggers
Pick source, pick work, pick job, pick release, validation, automation and notifications are rule-driven. Change the operation without waiting for a release.
Warehouse management for 3PL and distribution
Pathfinder WMS gives operators enterprise inbound, dock, inventory and fulfilment — without a two-year implementation. Rules-driven, RF-native, and built for dedicated customer environments.
Open receipts
18
4 at QC
Pick jobs
126
Wave 14 live
Doors busy
9 / 12
Yard 23 trailers
Labour vs plan
97%
Shift B
Inbound vs outbound · today
Activity
The gap
Distribution and 3PL operations need ASN-level inbound, wave picking, yard control, carrier manifests and a real integration layer. Most products force a choice between a lightweight WMS that cannot scale and an enterprise suite that arrives late and over-configured.
| Lightweight WMS | Pathfinder | Enterprise suite | |
|---|---|---|---|
| Inbound & dock | Basic goods-in | POs, ASNs, QC, yard in one product | Deep — after a programme |
| How you get it | Public cloud tenant | Dedicated environments, issued URL | PMO and 12–24 months |
| When it fits | Simple, single-client, low change | 3PL and DC that have outgrown mid-market | Global network already committed |
Capabilities
On the floor
See ASNs, discrepancies, QC holds and unexpected receipts in one place. Receive by HU or SSCC, govern blind receipts, and keep suppliers honest.
| Document | Supplier | Location | Status |
|---|---|---|---|
| ASN-8821 | Acme Foods | Dock 4 | Receiving |
| ASN-8820 | Northline | Dock 2 | QC hold |
| PO-19044 | Blind | Yard | Unexpected |
| ASN-8814 | Helix | Putaway | Complete |
Intelligence
Pathfinder is intelligent because the warehouse is configurable and the next unit of work is governed — not because a chatbot sits on the dashboard.
Pick source, pick work, pick job, pick release, validation, automation and notifications are rule-driven. Change the operation without waiting for a release.
Putaway, pick and replenishment share a governed “what work next” spine, with an audit trail. Future agents plug into the same contract; they are not bolted on as a parallel product.
Velocity classes, slotting recommendations that become transfer tasks, and staffing plans against backlog using engineered labour standards — not guesswork.
How you run it
Pathfinder is not a public app you log into from a marketing site. Each customer receives managed environments, SSO if you need it, and white-label branding for operators and the client portal.
Separate environments for each customer, promoted through a controlled release path. The warehouse URL is issued to you — it is not listed here.
JWT sessions in the product, with OIDC/SSO for Entra, Okta or a generic provider when the operation requires it.
Company name and logo on the operator login, header and client portal. Stock owners see their world, not a generic SaaS shell.
RF devices, users and portal seats are entitled centrally so contracts, operations and the floor stay aligned.
Systems we connect
Pathfinder does not publish a wall of vendor logos we have not certified. We connect the hosts you already run via API, files and AS2.
REST with idempotency keys and granular permissions. Docs ship inside the customer environment — not on this website.
Stable-file intake, blob retention, run timelines, and outbound file delivery the warehouse can diagnose.
Trading-partner AS2 for EDI-style interchange, including outbound 856-class messages where the operation requires them.
A governed outbound message outbox with delivery, retry and activity — not a fire-and-forget script.
OIDC SSO for Microsoft Entra ID, Okta, or a generic issuer. Pathfinder support sign-in can require TOTP MFA.
Connect the systems you already run through the API and files. We do not sell a catalogue of paid point connectors.
Tell us about the warehouse. We arrange a demonstration on a Pathfinder instance — not a public login from this website.