WMS · Freight · Client billing · Channel intelligence
One system for the whole logistics operation.
Warehouse, freight, client billing and channel demand in one database — with an AI layer that reads across all of it.
- 556
- Documented API paths
- 250+
- Write endpoints proven guarded by a test
- 7
- Sales-channel connectors
- 9
- Actions requiring a second person
- EN · 繁中
- Languages held at parity by a test
Run the operation
Receive, put away, allocate, pick, pack, ship, return. Every stock change passes one movement chokepoint, so a count or a recall traces back to the movement that caused it.
Bill the client
Work performed becomes a priced billable event and an invoice. Storage, handling, value-added services and freight — per client, in their currency.
Read the demand
Channel sell-through sits in the same database, so reorder points, stockout alerts and plain-language questions are answered from the ledger rather than guessed.
Every name below is a working screen.
Inbound
- Purchase orders
- Receiving
- Directed putaway
- Cross-dock
- Dock scheduling
- Yard
- Suppliers
Inventory
- Balances
- Lots & expiry
- Serial units
- FEFO & recall
- Holds
- Cycle counting
- Damage & QC
- GS1 identity
- Transfers
- Slotting
Outbound
- Waves
- Waveless streaming
- RF worklist
- Batch picking
- Pick-to-light
- Put wall
- Cartonization
- Pack verify
- Backorders
- Kitting
Freight & after
- Rate shopping
- Labels & manifests
- SSCC
- LTL & FTL
- Load planning
- Bills of lading
- Tracking pages
- Returns portal
Intelligence
- Control tower
- Alerts
- Demand → Buy
- Forecasting
- Ask AI
- Per-shop channel intel
- Executive digest
Platform
- Multi-client 3PL
- Client portal
- Billing & wallets
- Labour standards
- Multi-site
- RFID
- Printing
- Data imports
- Audit
Built to be audited.
An append-only audit ledger
SHA-256 chained entry to entry, update and delete refused, re-verifiable through the API.
One authorisation chokepoint
A test walks the route registry and fails the build on any unguarded endpoint.
A second person, by identity
Nine actions need a different human being. Self-approval is refused before roles are considered.
Tenant isolation, jobs included
The isolation tests cover background tasks — where cross-tenant bugs actually hide.
What this is not
No SOC 2 or ISO attestation, and nothing here implies one. Not built: EDI 940 and AS2. Two enterprise commerce connectors read fine, but their write paths are simulator-tested, pending a client sandbox. One carrier's label purchase runs against production; its rate, track and cancel calls await account verification.
It talks to what you already run.
Sales channels
Seven connectors — hosted storefronts, open-source carts, enterprise commerce suites and regional marketplaces.
3PL and WMS
Four warehouse and fulfilment platforms, plus a compatibility façade for the one you are leaving.
Carriers
Three global parcel carriers, plus universal multi-carrier tracking.
EDI
850 · 856 · 945 · 810 · 997, over SFTP or a filesystem inbox
Your own code
601 documented API paths, plus a façade that speaks your incumbent's API so what you have already written keeps working.
Switching systems is the risk, so it is engineered.
- 01
Keep your integration
Point the base URL at the compatibility façade and swap the auth header.
- 02
Mirror
Both systems hold the same data. The incumbent stays authoritative; nothing is at stake.
- 03
Parallel run
The flip stays locked until every record type matches at 99% for three consecutive runs.
- 04
Governed flip
A typed confirmation against a readiness gate, written to the audit ledger. Then billing dual-runs.
See it on real data.
A guided demo on a seeded tenant, run by someone who can answer the awkward questions.