3PL software for a small 3PL: what you need first

You have a lease or a corner of someone else's building, one or two clients lined up, and a decision about software. Everyone you ask has an opinion, and most of the opinions come from people with bigger operations than yours.

This guide is written for the small or new 3PL. It sorts what you need into three stages: before your first client ships, during your first few months, and later. The point is to avoid paying for, or building around, things you will not touch for a year.

Stage one: before the first order ships

At this point you need software that does four things reliably. Nothing else matters yet.

1. Know what you have and where it is. Every item received gets recorded against a client and a location. Counts must be right, because your client will compare them with their own books.

2. Keep clients apart. Client A's stock must never be picked for Client B's order. If software lets you assign stock only by SKU name, check what happens when two clients both sell a "blue large T-shirt".

3. Receive and ship with a paper trail. When goods arrive, you can say who counted, when, and what was damaged. When they leave, you can say what went out and where.

4. Record what you did for billing. You do not need a full billing engine on day one. You do need a record of storage, receiving, picks and extras by client, so that your first invoice is not a reconstruction from memory.

If a tool gives you these four, it can run a small warehouse. If it gives you a hundred other features and misses one of these four, it will cost you.

A day one test

Before committing, run a small pretend client through whatever you are considering:

1. Create a client and three SKUs, one of which has a size variant.
2. Receive two pallets, with one carton short.
3. Put one pallet in a pick location and one in reserve.
4. Enter five orders, one with two items, one with a bad address.
5. Pick, pack and ship them.
6. Look at the stock figures, then at what you would bill.

If any step needs a workaround you cannot explain to a staff member in two minutes, note it. You are not looking for perfection. You are looking for surprises, while it is cheap to find them.

Stage two: the first few months

Once real work is running, other needs show up. These are the ones that usually arrive first.

Client visibility. Clients start emailing for stock counts. At some point it is cheaper to give them a login than to answer. You do not need a portal before your first order, but you will want one soon.

Storefront connections. If your clients sell through online stores, orders will arrive from them. Importing by file may be fine for a while. Direct connections save time once volume rises.

Shipping labels. You will want labels printed from the order, with tracking sent back to the client's store.

Returns. A returned parcel is a small puzzle: whose is it, is it sellable, what do you tell the client? Have a place to record each answer.

Billing detail. Your hand-made first invoices will show where the gaps are. Common ones: extras done on the floor but not logged, and storage counted inconsistently.

More than one user. Staff need their own logins, with different permissions. A shared password makes it impossible to see who did what.

Stage three: later

These matter as you grow. Do not let anyone talk you into buying them now unless you have an actual use for them.

• Wave or batch picking across many orders.
• Advanced slotting and replenishment rules.
• EDI with retailers.
• Multiple warehouses.
• Labor tracking and performance reporting.
• Large-scale API access.

None of these is bad. They solve problems that you may not have yet. Write them in a "later" list and review it every six months.

Three hypothetical small 3PLs

These are made-up examples to show how needs differ.

The apparel specialist. Two clients, both with sizes and colors. Their trouble is variants: many SKUs, small quantities. The system must handle variant barcodes cleanly, and returns matter a lot.

The bulk stockist. One client with pallets of heavy goods, few orders a day. Storage billing is the main revenue. The system must count pallets and bill by pallet per day or month without friction. Pick speed barely matters.

The kit packer. Several clients with subscription boxes. Each order is assembled from several items on a schedule. Kitting and batch handling matter far more than for the others.

Same label, "small 3PL". Three different first systems. Your first job is to describe your own work, in a paragraph, before you look at any product.

Questions to ask any vendor or builder

• What is the price based on, and what happens to it when I add a client?
• Can I try my day one test before signing?
• What do I get if I leave: can I export my data, in what form, how quickly?
• Who sets it up and how long does it take?
• What does support cover, and what is extra?

Keep the answers in writing. Memory is a poor contract.

When to revisit

Look again at your software when:

• You cannot answer a client's stock question in a few minutes.
• You spend a day each month fixing billing.
• You turn away a client because your system cannot do something they need.
• A new hire needs more than a day to learn the basics.

None of these means you chose wrong. They mean you grew.

Next step

Write one paragraph describing what you will store, how it arrives, and how it leaves. Then run the day one test above against whichever options you are considering. Come back to this list in three months and see which stage two items have turned up.