A multi-tenant 3PL warehouse keeps each customer inventory, users, and settings fully separated while still letting the operator roll every number up into one portfolio view. Shipider does this by default: separation is the baseline, and aggregation happens on demand when you actually want the wider picture.
If you run a third-party logistics operation, you are really running many small warehouses inside one building. Each customer has their own stock, their own order flow, and their own idea of what "done" looks like. The software you use has to respect that boundary at all times, then let you step back and see the whole book of business when a decision calls for it. This article walks through how that works in practice: isolation as the default, roll-ups when you want them, billing that matches the model, and the supporting pieces that hold it together.
Isolation by default: the whole promise of a 3PL platform
For a 3PL, isolation is not a feature you switch on. It is the entire reason the platform earns trust. One customer should never see another customer inventory, orders, or reports, and there should be no way to stumble into that data by accident. In Shipider every query is scoped to the tenant, so the separation is enforced at the data layer rather than being something an operator has to remember to apply.
That scoping shows up in a few concrete ways:
- Data isolation. Inventory, orders, pallets, and reports belong to a single tenant and are only ever returned within that tenant. A query run for one customer cannot reach another customer records.
- Per-company users. Each customer can have their own logins with their own permissions. A user attached to one company sees that company and nothing else.
- Per-company settings. Preferences, workflow choices, and configuration live at the company level, so one customer setup never bleeds into the next.
- Branding hooks per tenant. Where a customer wants their own look on what they see, the branding is scoped to that company rather than shared across the whole platform.
The practical payoff is calm. When a customer asks who can see their data, the answer is short and true: only them and the operator team you assign. You are not stitching that guarantee together with careful naming conventions or a shared spreadsheet that everyone hopes nobody sorts the wrong way. The boundary is built in, which is exactly what a warehouse that grew up on Excel needs when it starts taking on outside clients.
Roll-ups when you want them
Isolation would be limiting on its own. As the operator you still need to see how the whole building is performing, because that is how you plan labor, spot a customer who is growing fast, and notice one who has gone quiet. Shipider handles this by keeping the tenant boundary intact while letting you aggregate across all of your customers when you choose to.
The portfolio view rolls up the numbers that matter across every tenant:
- Volume. How much is moving across all customers, so you can read the shape of the week rather than guessing.
- Utilization. How full the space is across the operation, which feeds both space planning and the conversation about taking on new work.
- Activity. What is actually happening across tenants, so a slow patch or a surge is visible before it becomes a surprise.
From that portfolio view you drop into a single customer detail whenever a question gets specific. One customer wants to know why an order is sitting, or you want to check the utilization behind one account before you renew. The aggregate view answers the "how is the business doing" question, and the drill-down answers the "what about this one customer" question, without you ever leaving the same platform or breaking the isolation that the customer relies on.
Billing that matches the model
A 3PL earns money per customer and per unit of work, so the software bill should follow the same logic. Shipider uses usage-based pricing: you are billed on the operational work that runs through the platform, not on how many people log in. That fits the economics of the business you are actually running.
Two things fall out of that choice that make a real difference to a growing operation:
- No per-seat tax to pass on. Adding a checker, a night-shift picker, or a customer login does not raise the bill. You can give people the access they need without turning every new account into a cost decision.
- No pallet caps. You are not pushed into a higher tier the moment a customer sends more stock than a plan allows. Growth in volume is the thing you want, and the pricing does not punish it.
Because the charge tracks operational work, it lines up naturally with how you invoice your own customers. When a customer is busy, the platform cost for that work moves with the revenue it generates, rather than sitting as a fixed line you have to spread across everyone. You can see the full breakdown on the pricing page.
The pieces that make it work
Isolation, roll-ups, and matching billing are the frame. A few supporting pieces keep the operation honest and connected day to day.
Per-tenant events and scoped API keys
Most 3PL customers have their own systems that want to know when something happens: an order picked, a pallet received, a shipment out the door. Shipider fires webhooks per tenant and issues scoped API keys, so each customer integration only ever touches that customer data. You can wire a customer into their own stack without opening a door to anyone else. There is more on how the events and the interface fit together in our piece on webhooks and the API.
Evidence per customer
When a customer questions a count or a condition, you want proof, not a memory. Shipider keeps pallet-level traceability scoped to each customer, so the history of a pallet stays inside that tenant and is there when a dispute comes up. That record is what turns "we think it shipped" into "here is exactly what happened." We go deeper on this in pallet-level traceability.
A second check on every order
Handling other people stock raises the cost of a mistake. A maker-checker workflow puts a second set of eyes on each order before it is treated as final, so the person doing the work and the person confirming it are not the same. That catches the small errors that would otherwise reach a customer, and it gives you a clean answer when someone asks how the order was verified. The full pattern is covered in our write-up on the maker-checker workflow.
Single shared list vs true multi-tenant
Plenty of warehouses start by running every customer through one shared list and a column that says who owns what. It works until it does not. The table below lines up that approach against a true multi-tenant platform on the points that decide whether a 3PL can grow without fear.
| Capability | Single shared list | True multi-tenant (Shipider) |
|---|---|---|
| Data isolation | A filter you hope nobody removes; one wrong sort exposes another customer | Enforced at the query level; a customer cannot see another customer data |
| Per-customer view | Manual filtering, easy to get wrong | Each customer scoped by default, with their own users and settings |
| Portfolio roll-up | Rebuilt by hand, often in a separate spreadsheet | Volume, utilization, and activity aggregated on demand, then drill into one customer |
| Per-tenant events | One shared feed or nothing; risky to connect a customer | Webhooks and scoped API keys per tenant |
| Billing fit | Seat counts and tier caps that fight your growth | Usage-based on operational work; no per-seat tax, no pallet caps |
The shared list is fine when you have one or two customers and everyone in the building knows each other. The moment you take on real volume, the gap between "we filter carefully" and "the system enforces it" becomes the difference between a confident sales conversation and a nervous one. If you want to see how this maps to a full operation, the 3PL solution page lays it out.
Putting it together
Running a multi-tenant 3PL comes down to three habits the software should hold for you. Keep every customer separate without anyone having to think about it. Let the operator see the whole book of business and then zoom into one account when a question is specific. Bill in a way that grows with the work rather than taxing the team and the stock. Add per-tenant events, evidence you can stand behind, and a second check on every order, and you have an operation that can take on new customers without adding new anxiety.
FAQ
How does Shipider keep one customer from seeing another customer data?
Every query is scoped to the tenant, so data is only ever returned within the customer it belongs to. Users, settings, and branding hooks are per company as well, which means the separation is built into the platform rather than depending on someone applying a filter correctly.
Can I still see performance across all of my customers at once?
Yes. Shipider rolls up volume, utilization, and activity across every tenant into a portfolio view, and you can drop into a single customer detail whenever you need to answer a specific question. Isolation stays intact while you look at the aggregate.
Why usage-based pricing instead of per-seat?
A 3PL earns per customer and per unit of work, so the bill should track the same thing. Usage-based pricing means you are charged on operational work rather than logins, with no per-seat tax to pass on and no pallet caps that push you into a higher tier as volume grows. The pricing page has the details.
Can each customer connect their own systems safely?
Yes. Shipider fires webhooks per tenant and issues scoped API keys, so a customer integration only ever reaches that customer data. You can connect one customer to their own stack without exposing anyone else.
What happens when a customer disputes an order or a count?
Pallet-level traceability is kept per customer, so the history of a pallet is available as evidence when a question comes up. A maker-checker workflow also puts a second check on every order before it is final, which reduces the errors that lead to disputes in the first place.
Ready to run each customer separately and still see the whole picture? Create your Shipider account and set up your first tenants.
Related reading: E-commerce Fulfillment WMS Playbook: Matching Shipider to Your DTC Stack
Related reading: Small Warehouse WMS Playbook: How to Get Off Excel in a Week