One supply chain execution platform, from customer order to freight invoice
Kargentra runs order management, transportation, warehouse and yard, the control tower, freight finance, governed AI and every partner portal on one operational record. Start with transport or the warehouse on its own, and every module you add reads the same facts instead of re-keying them.
One record, nine stages, every party
Most logistics estates pass files between an order system, a warehouse system, a transport system, carrier websites and a finance tool, and reconcile the differences by hand. Kargentra keeps one operational record that each stage advances. The owning module changes as the work moves; the record does not.
- Applications
- 8 role-built apps on one identity
- Lifecycle
- 9 order-to-delivery stages
- Deployment
- 3 shapes from one tenant
- 01
Order intake
Owned by Order ManagementOrder: requested
Works it: Customer · ERP · EDI
- 02
Order acceptance
Owned by Order ManagementOrder: committed
Works it: Customer service
- 03
Warehouse fulfilment
Owned by WMS · YardShipment: warehouse ready
Works it: Supplier · floor
- 04
Transport planning
Owned by TMSLoad plan: confirmed
Works it: Planner
- 05
Carrier sourcing
Owned by TMSTender: awarded
Works it: Carrier
- 06
Dispatch release
Owned by TMSTrip: released
Works it: Dispatcher
- 07
Delivery execution
Owned by Control TowerTrip: ETA vs actual
Works it: Driver
- 08
Delivery completion
Owned by Driver AppPOD: evidence complete
Works it: Customer
- 09
Billing readiness
Owned by FinanceShipment: billing ready
Works it: Finance
Thirteen modules on one operational record
Every module below reads and writes the same record. Pick the ones your operation needs today; the rest are a configuration change away, not a migration.
Plan and execute
The operational core, from accepted order to delivered goods.
- OMSOrder ManagementMulti-channel intake, deterministic validation, availability-to-promise, holds and changes, and fulfilment routed to native or external legs.Learn more
- TMSTransportation ManagementPlanning with an optimiser, carrier and fleet sourcing, routing guides, dispatch release, live execution and the close to Finance.Learn more
- WMSWarehouse ManagementScan-first receiving, inspection, putaway, slotting, wave or continuous picking, cartonisation, kitting and multi-client ownership.Learn more
- YMSYard ManagementAppointments, gate checks against what was expected, dock assignment, service, release holds and dwell from recorded times.Learn more
See and decide
Where people find what needs them, and get help deciding.
- Control TowerControl Tower & Live TrackingEvery queue that needs a person, source-labelled tracking, delivery risk against the commitment and governed exception recovery.Learn more
- Ask KargentraAsk KargentraAn always-on context layer on every screen that explains with citations and proposes next steps a named person approves.Learn more
- CollaborationCollaboration CenterConversations, requests and escalations anchored to the order, shipment, trip, purchase order, invoice or dispute they concern.Learn more
Bill and configure
Money facts with provenance, and configuration without code.
- FinanceFreight Finance & BillingCommercial facts per shipment, billing readiness, freight audit, disputes in both directions and invoices built from Finance-ready facts.Learn more
- AdminAdministration & ConfigurationPackages, Process Composer, Configuration Studio with Effective Preview, onboarding readiness, people and roles, and data activation.Learn more
Portals and apps
Every outside party works on the same record, scoped to what is theirs.
- CarrierCarrier Network & PortalQuote requests, tenders, bookings, resource nomination, delivery evidence, declared capacity and disputes for carriers.Learn more
- CustomerCustomer PortalOrders, promises, shipments, documents, returns, charges, invoices and line disputes, scoped to each customer account.Learn more
- SupplierSupplier PortalPurchase order responses, advance shipping notices, dock appointment requests and answers to receipt discrepancies.Learn more
- DriverDriver AppAssignments, release acknowledgement, stops, delivery attempts, photo and signature proof, and a queue that works offline.Learn more
Compose the platform; do not re-platform the business
The same tenant can run transport only, the warehouse only, or the whole connected estate. What a tenant buys, which modules are switched on and who owns each stage are one availability decision, so the API, the preview and the navigation always agree.
TMS only
Run transport on its own. Orders arrive from your ERP, EDI 204 or the API; planning, sourcing, dispatch, tracking and the delivery-to-finance close run in Kargentra.
- Warehouse readiness read from your existing system
- Driver App and Carrier Portal included in the flow
WMS only
Run the warehouse on its own. Orders come from an external ERP or OMS, and outbound shipments are handed to your existing transport process with their readiness stated.
- Scan-first execution and multi-client ownership
- Supplier Portal tied to receipt truth
Full connected
Order, warehouse, yard, transport, portals, driver app and finance on one record, so every hand-off between teams is a state change rather than a file.
- One audit trail from order to invoice
- Order Management also runs standalone beside an ERP
Decide who runs each stage, and see the effect before it goes live
For each of the nine order-to-delivery stages, a tenant administrator chooses who runs it: Kargentra, an external system connected through governed exchange, an external system updated by hand, or not applicable. Drafts are compared with the live route, and a new version applies to new orders. One availability decision then drives what the API permits, what Effective Preview shows and what each person’s navigation offers.
- An externally owned stage refuses local writes instead of marking itself complete
- Effective Preview for a chosen person shows products, route, forms, policies and screens
- Distinct states for not in subscription, not switched on and run outside Kargentra
- Every change versioned, previewed and recorded in change history
The foundation under every module
Shared services that every application uses in the same way, so security, evidence and integration behave identically whether the person is a planner, a supplier or a driver.
Identity and single sign-on
Named people sign in once through a standards-based OpenID Connect realm across Operations, Tenant Admin, every portal, the warehouse handheld and the Driver App, then choose the workspace they are acting in.
Multi-tenancy with row-level security
Tenant-owned tables run under forced Postgres row-level security beneath application authorisation. Another tenant’s record reads as not found, so its existence is never disclosed.
Roles and permissions
Every API operation names its permission in the contract. Roles are versioned, membership is governed, and My Access explains what a person can do and which role grants it.
Audit evidence
Business and administrative actions land in a tenant-scoped, hash-chained audit record with actor, membership and correlation id. Access to document content is audited as well.
Events and webhooks
Lifecycle events publish to versioned event contracts. External systems receive signed webhooks with delivery health, retries and a governed replay for exhausted deliveries.
Connector Hub
Store a sealed credential, test, discover, map with versioned approval, switch on and inspect every exchange attempt, for ERP, e-commerce, carrier, telematics, finance and more.
Documents and evidence
Documents and proof sit in S3-compatible object storage, versioned with supersession and served through short-lived signed links. An evidence policy decides what completes a record.
Offline sync
The Driver App queues actions without signal and reconciles them in order when it returns. Conflicts, such as a reassignment made meanwhile, come back to the driver to answer again.
Observability and privacy-first diagnostics
Every request carries a correlation id and every failure is classified into one of ten named classes. Diagnostics work from metadata, with no switch that reveals payloads to anyone.
Theming and languages
Tenants apply their theme and languages in the operations workspace, the customer portal and the driver app, including right-to-left scripts, and each person’s light or dark appearance follows them from portal to portal.
Precise words, enforced in the product
Logistics software often lets one status mean three things. Kargentra keeps these distinctions as separate facts in the data, the API and the screens, which is why its figures can be trusted.
| Kept apart | What it means in practice |
|---|---|
| OrderShipmentLoad planTrip | A customer’s demand, the goods moving to one destination, what travels together and the vehicle run that carries it are four records. Splitting or combining one never corrupts another. |
| RequestedProposedCommittedETAActual | Five different times. On-time performance is measured against the commitment using actuals, never against an estimate that quietly moved. |
| PlannedObservedAuthoritative | A plan is intent, an observation is one source’s report and the authoritative milestone is what the record accepts. A position never changes trip status on its own. |
| AssignmentReadinessReleaseExecution | Naming a driver does not make a trip ready, and a ready trip has not been released. Each step is its own governed act with its own owner. |
| ArrivalDelivery attemptProof of deliveryCompletion | Being at the door is not delivering, and submitted proof is not accepted proof. A failed attempt leads to recovery, not to completion. |
| Evidence completeBilling ready | A delivery can hold every document and still be blocked from billing by an open exception or a missing rate. |
| ExpectedReceivedAvailableAllocated | Warehouse quantities are never collapsed into one number, so promises are made only against stock that is really free. |
| Warehouse readyDispatch ready | Staged goods are ready for transport. The trip may still be waiting for a driver, documents or release. |
| EntitlementPermissionRecord scopeWorkflow stateUI visibility | What the tenant bought, what a person may do, which records they may reach, what the record allows now and what the screen shows are checked separately. |
| AI proposalAuthoritative action | Ask Kargentra explains and proposes. Only a person with the permission approves, through the governed action, and the approval is audited. |
From your scenario to a running operation, in four steps
- 01
A working session on your scenario
Bring a real lane, a site and a recent exception. We run it through Kargentra live on real screens and show where each step lands on the record.
- 02
A tailored pilot, if it fits
If Kargentra fits, we invite you to discuss a pilot tailored to your operation: what it would cover, which of your data it would use and what it would have to prove.
- 03
A phased rollout by module
Start with the module that removes today’s largest problem, set the process route for stages you keep elsewhere, then add the next module on the same record.
- 04
Run and improve
Onboarding readiness, manager health and change history show what is working. Configuration changes are previewed, versioned and audited rather than hard-coded.
Platform questions
What is a supply chain execution platform?
A supply chain execution platform runs the operational work between a customer order and an issued invoice: order management, warehouse and yard execution, transport planning and dispatch, tracking, exceptions, and the commercial close. Kargentra adds the partner portals, a driver app and governed AI on the same record, so execution and billing share one set of facts instead of being reconciled between separate products.
How do OMS, TMS and WMS share data in Kargentra?
They do not exchange copies; they work on one operational record. An accepted order forms shipments, the warehouse marks them ready for load or blocked, transport plans loads and trips from them, and delivery evidence and charges attach to the same shipment. Each module writes only through governed commands, so a hand-off between teams is a state change with an audit record, not a file transfer.
Is Kargentra multi-tenant?
Yes. Each customer is a tenant on a shared platform, and its data is isolated at two levels: application authorisation checks entitlement, permission and record scope on every request, and the database enforces forced row-level security beneath it as a last line of defence. A record belonging to another tenant reads as not found, so even its existence is not disclosed.
Can processes be configured without code?
Yes. Tenant administrators use Process Composer to choose who runs each of nine order-to-delivery stages, and Configuration Studio to manage fields, forms, workflows, operating policies, integrations and AI defaults through templates. Every change can be previewed for a specific person and role before it is applied, is versioned, and appears in change history. Configuration changes runtime behaviour, not just screens.
Can we start with one module and add others later?
Yes. Transportation Management and Warehouse Management each run on their own, and Order Management can run beside an existing ERP. Each connects to the systems you already have, and the Process Composer records which stages stay external. When you add a module, it reads the same record rather than importing history, and the stage simply changes owner from an external system to Kargentra.
How does Ask Kargentra use the platform’s data?
Ask Kargentra sits on an always-on context layer that knows which record and screen a person is looking at, and it can only read what that person is permitted to see. It explains with citations to record facts, states how fresh they are, and proposes a next step. Nothing changes until a person with the right permission approves the governed action.
Bring one lane and one exception
We will run them through Kargentra live, on real screens, and show you where each step lands on the record.