What a 3PL client portal should show you about inventory states, order holds, inbound receiving and billing detail, and how to test a warehouse portal before you sign.
Once your inventory moves into a third-party logistics (3PL) warehouse, you lose the ability to walk the aisles and see it for yourself. What you see instead is whatever the warehouse's systems choose to show you, usually through a client portal connected to its warehouse management system (WMS).
That portal is how you answer everyday questions: how many units are on hand, which orders are stuck, what arrived on last week's container, and why this month's invoice looks the way it does. A good portal makes those answers self-serve. A thin one turns every question into an email thread.
This article lays out what a 3PL client portal should let you see, grouped into inventory, orders, and billing, and how to test a portal before you commit to a provider.
Sales conversations focus on the warehouse floor: equipment, space, labor. But after onboarding, your day-to-day relationship with a 3PL runs mostly through software. If the portal can't show you something, you either wait for someone to look it up or you work without it. Over months, that gap shows up as slower decisions on reordering, slower answers to customers, and harder invoice reviews.
Inventory is the first thing most brands check, and the area where vague numbers cause the most trouble. A useful portal should separate inventory into states rather than show one total:
Beyond the snapshot, look for inventory history: a SKU-level record of receipts, shipments, adjustments, and cycle-count corrections. When a count changes unexpectedly, the history is how you find out why. If your products have lot codes or expiry dates, the portal should show quantities by lot as well.

For orders, the key question is "where is it, and if it's stuck, why?" A portal should show each order's status through the warehouse, for example received, on hold, released, picked, packed, and shipped, along with the tracking number once a label is created.
The most useful feature here is hold and exception reasons. An order marked "on hold" with no explanation is almost as unhelpful as no status at all. Reasons such as unmapped SKU, insufficient stock, address issue, or awaiting instructions tell you exactly what to fix.
How orders and inventory reach the portal in the first place depends on the integrations between the WMS, your store, your marketplaces, and carriers. Our guide to warehouse system integrations explains how those connections fit together.
Inbound shipments are where many discrepancies start. A portal should let you create or view advance shipping notices, then compare expected versus received quantities by SKU once the shipment is processed. Notes on damage, shortages, or overages at receiving, ideally with photos, save long back-and-forth conversations later.
Invoices are where trust between a brand and a 3PL is often tested. The portal should let you trace each charge back to the activity that caused it:
| Charge type | Detail you should be able to see |
|---|---|
| Pick and pack | Which orders and how many units per order |
| Storage | Which units or locations, and for what period |
| Receiving | Which inbound shipments and how they were counted |
| Packaging | Which materials were used on which orders |
| Special projects | What was done, when, and under which request |
| Postage | Label cost per shipment |
If you're not yet sure how each line on a 3PL invoice is built, our line-by-line breakdown of 3PL fulfillment costs is a useful companion to this checklist.
Even the best dashboard won't answer every question. Check whether you can export inventory, order, and billing data to a spreadsheet, and whether reports can be filtered by date range, SKU, and channel. Export access means you can reconcile against your own systems instead of relying entirely on screenshots.
A warehouse partner's technology is part of the service you're buying. To see how IDCEA approaches warehouse software, visit our warehouse technology page.