Guides
3PL Warehouse Management Software Checklist
A 3PL has many clients on one floor, and that changes what you need from warehouse management software. A twelve point checklist to take to every demo.
Cargohold
Whether Cargohold fits a 3PL depends on how the 3PL runs: a custom build tends to suit 3PLs whose billing, client rules and dock handoffs are specific to them, and buying usually wins when the work is standard. We stick to what is on Cargohold's public pages, link every one, and say plainly when you are better off buying something else.
Cargohold is a platform for warehouses, freight and fleets, built to order. The Cargohold site describes one system in which a single record moves through every module, so nobody re-types it.
For a 3PL the relevant parts are warehouse management, inventory, billing, a client portal, and yard and dock. The page for 3PLs and warehouses describes storage, cross dock, transload and fulfillment on one record per client, with billing that follows the work.
This is what the public pages say, one module at a time.
Warehouse management. The warehouse management page lists receiving on a scanner with lot, expiry and serial, and photos for anything over, short or damaged. It describes blind receiving for deliveries with no advance notice, and directed putaway that respects temperature zones, hazmat segregation and client space. It also lists several picking methods, pack stations that scan every item, and cycle counts with variance approval before stock changes. The scanner app keeps working when the Wi-Fi drops.
Inventory. The inventory page describes items and balances kept per client, warehouse, location, lot and serial. Statuses include available, hold and damaged, and an immutable ledger sits behind every balance. Adjustments need a reason code, and approval above a threshold you set.
3PL billing. The billing page describes rate cards for storage, handling, value-added work, accessorials and minimums. Billable events are raised from the ledger and task records, and each one traces back to its source. Billing runs per client and period, with a preview, an approval step, invoices and credit notes. A leakage check lists work that was done with no matching charge.
Client portal. The client portal page describes a dashboard for each client showing stock, orders, shipments and invoices, scoped to that client's own data. An invoice opens to the billing detail behind it.
Two of our other pieces go into the reasoning: what to look for in a 3PL system and why generic software forces workarounds.
This is where Cargohold differs most from a subscription product. It is not a login you sign up for. It is built for your operation.
According to the pricing page, the model is a one-time custom build, no per-seat, per-truck or per-client fees. You own the code and the data. The system runs on your own server, which Microsive sets up in your name.
The pages describe these steps:
We have left out price and timing on purpose. Ask Microsive for both, and for what happens after handover, and get the answers in writing.
Cargohold deserves a serious look if several of these are true:
Here is a hypothetical case. A 3PL has a dozen clients, each on a different rate card, and its monthly invoice takes two people two days to assemble from exports. The pain sits in billing and client reporting, which is the problem the billing and portal pages are written for.
Plenty of 3PLs should not build anything. Cargohold's build vs buy guide says buying wins when your operation is close to how a product expects a warehouse to run. The own your WMS guide says buying is the better path when your process already fits standard software and you would rather not run a server.
In plain terms, buy a subscription product if:
If that list sounds like you, we would rather you picked a subscription product than took a build you will not use well. A mismatched build is bad for you and bad for us.
Do this on paper, with no vendor in the room.
If the leftovers are small, buy. If the leftovers are how you run the business, a build deserves a conversation. The build vs buy guide suggests the same method.
You can see the platform or read the pricing page before deciding whether to talk to anyone.
That depends on how your 3PL runs, and this page does not rank products. It describes what Cargohold does, who it suits and when a subscription product is the better buy.
Buy when the work is standard and a demo matches it without gaps, when you need to be live very soon, when you are still working out your process, when nobody wants responsibility for a server, when nobody can describe how the work runs, or when you are very small with few clients.
According to its public pages, it covers warehouse management, inventory, billing, a client portal, and yard and dock on one record per client. This page lists what each module describes and links the source.
One with real edges in its process, where every standard demo ends with someone saying they would do that part in a spreadsheet. It also helps to expect more clients, want to own the system and data, have a person who knows how the operation runs, and be comfortable with someone looking after a server.
List ten things your current system makes people do by hand. For each, decide whether it is normal 3PL work or a quirk of your business. Ask any product you consider to show all ten in a demo with your own example, then count what is left. Small leftovers mean buy. If the leftovers are how you run the business, a build deserves a conversation.
From Cargohold's public pages. The page sticks to what they state and links each of them.