3PL software for every client, warehouse and invoice
Kargentra is 3PL software that runs many clients’ stock, orders and freight in one tenant without one client ever seeing another. It makes the client a dimension of every item, balance and order, gives each client a portal scoped to its own records, and charges warehouse services, storage and transport from the work your teams actually recorded.
What gets in the way today
One SKU, two owners
Two clients ship the same product with the same barcode. Without owner-scoped identity, warehouses fall back on prefixes, duplicate item masters or separate databases, and every workaround becomes a stock error waiting to happen.
Client visibility by spreadsheet
Clients email for stock and order status, and account managers paste exports into replies. Each client sees a slightly different version of the truth, and every answer costs someone an hour.
Billing rebuilt at month end
Storage, handling, kitting and freight charges are reconstructed from logs and memory. Charges without evidence turn into disputes, and margin is only known weeks after the work was done.
Every client wants different rules
Receipt tolerances, expiry rules, labels and release limits differ by client. Without configuration, each new contract means custom code or a supervisor who remembers the exceptions.
Onboarding a client is a project
Every new client brings item data, open orders and an ERP to connect. Loads are run by hand, mappings live in someone’s head, and nobody can say with confidence when the client is ready to go live.
Floor exceptions without an owner
Short receipts, damaged pallets and pick exceptions are noted on paper and resolved whenever someone remembers. The client hears about the problem from its own customer before it hears from you.
How Kargentra changes the work
The client is a data dimension
The client is part of the identity of every item, balance, demand line and handling unit. Two clients can both stock product code 4471 under the same barcode in one building, and every scan still resolves to the right owner, because separation comes from the data model and permissions rather than naming conventions.
- Owner-scoped SKU and barcode identity
- Client workload visible in warehouse analytics
- Client account chosen on every client-owned order
Client rules and onboarding without code
Each client inherits a starter operating profile and overrides only what its contract needs, previewed per facility or client before saving. New clients arrive through an activation project: import, profile, map, validate and reconcile to Ready for Pilot.
- Stale previews are refused rather than applied
- Client systems connected through Connector Hub, EDI 204 and signed webhooks
Scan-first floor work
One queue of real warehouse work on phone, tablet or desktop. A scan opens an inbound, an item, a pallet, a bin or an outbound order, and the operator acts in place with their permissions shown on screen.
- Three-way match: ordered, expected, received
- Wave, batch, cluster, zone or continuous picking
- Cartonisation from verified dimensions
Value-added services as evidence
Kit and bundle recipes consume exact components and produce traceable output stock. Every service performed is recorded as an event with its lineage, so it can be charged and defended.
A portal scoped to each client
Clients see only their own orders, shipments, inbound receipts, documents, charges and invoices. People who work across several accounts choose the account they are acting for, and every list reconciles with its headline count.
Billing from recorded work
Each client’s month adds up from recorded events: pallets stored, cartons picked, kits built and loads delivered. A commercial engagement gathers that client’s warehouse and transport work into one job, storage is checked against counted units before a period is frozen, and invoices draw only on facts already handed to Finance.
- One margin position per client engagement, kept per currency
- Warehouse-only jobs reach Finance without an artificial shipment
- Client freight routed, dispatched and closed on the same record
Receive against what the supplier declared
The handheld inbound queue shows each expected notice with its declared quantities, lots and handling units. Operators receive by scan, and any shortage, excess, wrong item or damage is recorded against the line rather than corrected silently.
- Received goods stay restricted until inspection passes and a hold is released
- Cross-dock sends matched receipts straight to picked outbound demand
- Each operator sees their own standing, so unavailable actions are named, not hidden
Stock by client, lot, expiry and disposition
Inventory 360 answers what a client owns, where it is and whether it can be used. Lot and expiry drive first-expired, first-out allocation, and quarantine or damage keeps stock out of available until someone with the permission releases it.
- On hand, available, allocated and held kept as separate numbers
- Cycle counts with counted against expected and governed corrections
- Printable pallet labels a thermal printer reads directly
Invoices your clients can check line by line
Invoices are built from Finance-ready facts: shipments, warehouse engagements, closed storage periods and agreed dispute adjustments. A client can dispute a single line from the portal with evidence, and an agreed increase becomes a supplemental invoice rather than an edit to an issued document.
- Issued invoices are immutable and corrected only by credit or supplemental documents
- Each correction is traced back to its source
- Clients never see buy cost, margin or another client’s charges
The modules that matter most here
- Warehouse ManagementMulti-client ownership, client policies, scan-first execution, kitting and the handoff to transport, all on one stock model.Explore WMS
- Customer PortalEach client sees its own orders, shipments, inbound, documents, charges and invoices, and disputes a line with evidence.Explore Customer
- Freight Finance & BillingCommercial engagements, warehouse service charging, storage period close, invoice generation and disputes from recorded work.Explore Finance
- Transportation ManagementPlans, sources, dispatches and tracks client freight when it leaves the building, on the same record.Explore TMS
- Order ManagementReceives client orders from portals, APIs, ERP connectors and EDI, and promises against the client’s own stock.Explore OMS
- Administration & ConfigurationActivation projects, operating profiles, process routes and roles let you onboard each client without custom code.Explore Admin
Third-Party Logistics (3PL): frequently asked questions
What is 3PL software?
3PL software runs warehouse and transport work on behalf of many clients at once. It needs everything a single-company system has, plus client ownership on every record, per-client rules, client-facing visibility and billing for services performed. Kargentra combines warehouse, transport, a client portal and finance on one record, so the work a client is billed for is the work your floor actually recorded.
Can each 3PL client see only its own data?
Yes. Ownership is a dimension on items, balances, demand and handling units, and portal access is scoped to the client account. A client sees its own orders, shipments, inbound receipts, documents, charges and invoices, and never another client’s records, buy costs or margins. Underneath, tenant data runs under forced row-level security in the database as a last line of defence.
How does 3PL billing work in Kargentra?
Billing follows the work. Handling, kitting and other warehouse services each leave a recorded event against the client, and a commercial engagement collects them with that client’s transport as one job. Storage is billed by period: before a period is frozen you see the counted units and the resulting charge, so a wrong count is fixed before it reaches the client. Invoices are then generated from those Finance-ready facts, approved and issued with no amounts typed by hand.
Can two clients store the same SKU or barcode?
Yes. Because ownership is part of the identity of items, balances and handling units, two clients can hold the same product code or barcode in the same facility. Scans resolve to the owner in context, allocations respect ownership, and reports split workload and stock by client without prefixes or duplicate item masters.
Can we connect to each client’s ERP or order system?
Yes. Client systems can send orders machine to machine under their own identity and receive signed webhooks as orders progress. Connector Hub manages each connection with a sealed credential, a connection test, versioned field mappings and an exchange history with governed replay. Inbound EDI X12 204 load tenders are validated and kept as evidence before they become orders.
Does Kargentra handle kitting and value-added services?
Yes. Kit and bundle recipes define the exact components consumed and the output produced, and each run records transformation evidence with full lineage. Because every service performed is an event on the record, it feeds warehouse service charging directly, so a client can see what was done, when and from which components.
Further reading
- Guide · 9 min readOMS vs WMS vs TMS: what each system doesOrder, warehouse and transportation management compared: what each system owns, where they hand off and how to choose the right mix.
- Guide · 9 min readFreight audit and billing readiness, explainedThe freight audit process step by step, why delivery evidence decides billing readiness, common invoice errors and how disputes are resolved.
- Guide · 9 min readElectronic proof of delivery (ePOD): a practical guideWhat electronic proof of delivery should capture, how offline capture works and why arrival, a delivery attempt and accepted POD are different.
See Kargentra run your operation
A working session on your lanes, your sites and your hand-offs: order to invoice, on one record.