Article
How a 3PL warehouse works in Lift: clients, depots and bins

A 3PL warehouse holds other people's stock. That one fact shapes everything else: every unit on every shelf belongs to a client, every order is for a client, and every charge goes on a client's invoice. A warehouse system that thinks only in products and locations leaves your team to keep track of whose stock is whose, usually in their heads or on a spreadsheet beside the system.
OpenBoxes Lift builds the client into the structure of the warehouse itself. This article explains how: the client, the depot, the bins, and the one rule that holds them together. The client names below are invented examples.
The client#
In Lift, a client is a business you store goods for. Each client has their own products, stock, orders, rate card and invoices.
You add a client from Clients in the portal sidebar with New client, and you fill in three things:
- Client name, the name your team knows them by, for example Northwind Traders.
- Client code, 2 to 8 letters or digits starting with a letter, for example
NWT. - Bins, how many storage bins to create for them, from 1 to 200.
Choose the code with care. It cannot be changed later, because it becomes part of every code Lift creates for that client in OpenBoxes.
What Lift creates in OpenBoxes#
Your Lift instance is OpenBoxes, so a client has to exist in OpenBoxes for your team to receive, pick and ship for it. Lift does that setup for you, one step at a time:
- An organization for the client, coded
LIFT-NWT. - A depot that holds only this client's stock,
LIFT-NWT-DEPOT. - The bins inside that depot:
LIFT-NWT-B001,LIFT-NWT-B002and so on. - A parcel location, where the client's outbound parcels are sent from.
- An inbound origin, where deliveries to the client's depot arrive from.
- Your team's access to the new depot.
You can leave the page while it works, and setup carries on. The client shows Setting up and then Active. If a step stops partway, the client shows Setup stopped, and Retry setup on its page picks up from there.
The client's page then lists what was created under In OpenBoxes: the organization code, the depot, the parcel location, inbound deliveries, the bins and the SKUs. It is also where you import the client's SKUs and manage their kits.
The one rule: one client per bin#
Every bin belongs to exactly one client. Each client gets their own depot, and the bins inside it are theirs alone. A bin is never shared between two clients, and one client's stock never sits in another client's depot.
This sounds like a constraint, and it is, on purpose. It is what makes the rest of the system simple:
- Stock counts are right per client. When Lift reads what is in a bin, it already knows whose stock it is, because the bin can only belong to one client.
- Orders cannot pick the wrong client's stock. An order for Northwind is filled from Northwind's depot.
- Storage charges follow the bins. If you bill storage per bin per day, a bin holding a client's stock is a bin you can charge that client for, with no apportioning between clients. Client Billing explains the count.
If you are used to a mixed-stock warehouse, where any SKU can go in any open slot, this is the main habit to change. Plan bins per client. When a client grows, they need more bins of their own, not a share of someone else's.
Products, coded by client#
Each client's products are loaded from a CSV of their SKUs. In OpenBoxes, each product is coded <client code>-<SKU>. Northwind's MUG-01 becomes NWT-MUG-01, and if Harbor Supply also sells a MUG-01, theirs becomes HBS-MUG-01. Two clients can use the same SKU without ever clashing.
When you import, the file also says whether each product is lot controlled. That is set once, when the product is first imported, and it cannot be changed after the product exists in OpenBoxes. Decide it per product before the first import, especially for anything with an expiry date or a batch number a manufacturer could recall.
How the pieces fit at work#
Once a client is set up, the structure carries through every step:
- Receiving. An ASN for a client becomes an inbound movement into that client's depot, and your team puts the stock away into that client's bins.
- Orders. Every order belongs to one client, and it ships from that client's parcel location.
- Packing. The pack station checks every scanned item against the order, so a product from the wrong client is refused like any other wrong item.
- Billing. Each client's work and storage are counted against that client's rate card, and Lift drafts one invoice per client each month.
When a client leaves#
Archiving a client runs the setup in reverse. Lift turns off the client's access, parcel location, bins, depot and organization in OpenBoxes. Nothing is deleted: the records and their history stay in OpenBoxes.
Archiving cannot be undone in the portal, so archive a client only once their stock has left your warehouse.
Trying it#
The best way to see the structure is to set up one test client of your own before your first real client: a client named after your business, with a handful of bins and three or four SKUs. Once you have added it, look at the client's page under In OpenBoxes, then open OpenBoxes and find the depot and bins Lift made. Clients, Depots and Bins in the docs has every field and status, and the 3PL page has an overview of the rest of the flow. The pricing page has the 3PL plans.
Want a 30-minute setup call? Ask in the support chat and we'll set a time.
Keep reading
- GuideLocations
- On the siteOpenBoxes Lift for 3PL warehouses
- What's newWhat shipped in October 2026

