Choosing 3PL software for small business usually starts with a problem rather than a product. A small 3PL should move to dedicated software once spreadsheets can no longer tell you, quickly and reliably, what stock each client holds, what each client owes and who moved what last week. For an operator with a handful of clients and one site, that point often arrives sooner than expected. This guide sets out the warning signs, what a first system must do, what it costs, how go-live works and what to ask before you sign anything.
What software do small 3PLs use?
Many small 3PLs start with spreadsheets and an accounting package, and some add an ecommerce or ERP module once they take on online retailers. Dedicated 3PL software usually follows when client count, billing disputes or daily volume make the spreadsheet a business risk rather than a convenience.
In practice, most small operators sit in one of three positions:
- Spreadsheets and paper: Cheap and familiar, but the data sits with whoever built the file, and nothing is checked at the point of pick.
- General business software: Useful for invoicing and orders, but usually built for a single business holding its own stock, not for several clients sharing one building.
- Purpose-built 3PL software: Designed around multiple clients, per-client rules and charging, with scanning on the floor and a record of every movement.
If you want the wider market picture before you narrow the list, our guide to 3PL software providers covers the field. This article is about the decision a small operator faces first, which is whether the current setup can still do the job.
When should a small 3PL move off spreadsheets?
A small 3PL should move off spreadsheets when it can no longer answer client stock, billing and traceability questions from a single source of truth. If a question takes an hour of digging, or only one person knows where the answer lives, the spreadsheet has already become a risk.
The table below links the symptoms most small operators recognise to their likely cause, and to what you should look for in a replacement.
| What you notice | Likely cause | What to look for in software |
|---|---|---|
| Clients phone or email for stock levels | Stock data is not visible to the client | A client view of their own stock |
| Month-end invoices take days to build | Chargeable work is recorded by hand and re-keyed | Charges captured from warehouse transactions |
| Pickers reach the wrong bay and nobody notices until a client complains | Locations are not checked at the point of pick | A scan that stops the pick if the location is wrong |
| You cannot say who moved a pallet last Tuesday | No time-stamped record of each action | A full audit trail by user, time and location |
| Every new client needs a new spreadsheet | One set of rules is shared across all clients | Per-client settings for workflows and charges |
The third row is the one that surprises people most. On a paper pick list, one person picks and a second checks the pallet before it leaves, so a single correct despatch can take two people’s time. A scan at the location and at the product removes most of that check, but only if the system refuses to continue when the scan does not match the task. Clarus’s handheld flow works that way: if a picker scans the wrong location, the device says so and shows the location the task expects, so the mistake is caught at the bay rather than at the customer.
Be honest about the limits too. Scanning cannot stop someone taking a box from the pallet next to the one they scanned. Good software narrows the error window; it does not remove the need for supervision on the floor.
What must a first 3PL system do?
A first system for a small 3PL must keep each client’s stock separate, show clients their own position, charge for work from the record rather than from memory, and give you a trail you can defend. Everything else is secondary until those four are working.
Must-haves
- Multi-client stock separation: Each client’s stock, reports and rules sit within one warehouse without mixing. Ask the vendor to show two clients with different workflows running side by side.
- A client portal: Clients should be able to see their stock and orders without ringing you. Clarus’s client access feature is built for this. The reason it matters is simple: every query your team answers by phone is time not spent on picking.
- Billing from the record: Storage, handling and despatch charges should come from transactions in the system. The client billing page sets out how Clarus approaches per-client charges. Invoices also have to meet VAT record rules, which GOV.UK sets out in its guidance on charging, reclaiming and recording VAT. Whatever you buy, ask how a charge gets created and who can change it.
- Carrier labels and shipping: If you despatch parcels, the system needs to print labels and record tracking against the right order. Clarus has an integration page for Royal Mail, and pages for a range of other carriers. Check yours is on the list before the demo, not after.
- Marketplace and webshop connections: Small 3PLs often take on clients who sell through Shopify or eBay. Each connection should bring orders in automatically rather than through a CSV upload each morning.
- A record of every movement: Every receipt, move, pick and hold should show who did it and when. Without that, a stock discrepancy becomes an argument.
Nice-to-haves, depending on your clients
- Expiry and rotation rules: If your clients hold food or other dated goods, check how rotation works. In Clarus, FIFO follows the date the stock record was created, down to the millisecond. Expiry-based picking is configured separately, so ask the vendor to show you both before you rely on either. The stock rotation page covers the options.
- Barcode data: Most UK retail and wholesale stock carries GS1 barcodes, and GS1 UK sets the standards those codes follow. Ask how the system reads the identifiers on your clients’ labels, because a label the system cannot parse is a receiving delay on every pallet.
- Cross-docking: If you move stock straight through without storing it, check whether the system can receive a pallet and despatch it in one flow, and whether you can charge for that handling separately.
What a small 3PL should not expect
Some gaps are common across the category, and it is better to find them in the demo than in the first month. Clarus does not have a returns module, so returns are handled as a manual process today. It also does not monitor temperatures. Temperature-controlled work can be recorded through checks you set up as fields, but a person still does the checking. If a client needs continuous temperature logging, ask for a clear answer on that before you commit.
If you handle food for clients, the bar is higher. BRCGS standards expect complete traceability records, so check how batch and lot details are captured from receipt through to despatch, not just whether the fields exist.
What does 3PL software cost?
Clarus plans start from £1,000 a month. That figure is the starting point for a comparison, not the whole cost. A system that is cheap to licence but takes a year to go live can cost more in staff time than a dearer one that is running in twelve weeks.
Many vendors in this market quote on application, so compare offers on the same basis. Ask each one for a written quote that covers the licence, implementation, training, any integrations you need and any data migration. A small 3PL should also count the cost of the current setup honestly. Two people checking picks by hand, or a day of month-end re-keying, is a running cost that never appears on a software invoice. The Clarus pricing page has the current details.
How long does 3PL software take to go live?
A standard Clarus implementation goes live in around 12 weeks, provided both sides give the project proper support. Mathew Buttar, who spent years as a warehouse and operations manager before taking on Clarus go-lives on site, puts it plainly: “12 weeks is a good standard because you need to allow people time.” Complex projects with many clients, heavy use of features and high volumes can run much longer, sometimes up to two years.
The time goes on people more than software. Mathew’s approach is to start with basics: setting up super users, populating the system with master data, and testing whether it works for each client’s way of operating before anything goes live. He suggests appointing at least two super users from your own team, because they become the people who understand why the system is set up the way it is. Testing is manual. The people who will use the system check each step, including any interface files, and sign off the User Acceptance Testing schedule before go-live.
On phasing, he is direct: phased rollouts drain capacity, and a big bang go-live is fine if you have time for full UAT. For a small operator with one site, a single cutover after thorough testing is often the simpler route, but that depends on how many clients you move at once.
The wider sector is also worth watching. UKWA, the UK trade body for warehousing, publishes work on where the sector is heading, and Logistics UK represents businesses across the wider logistics sector. The ONS business counts show how many transport and storage businesses operate in the UK each year, which helps you judge whether your market is growing around you.
What should you ask in a demo?
The demo is where a small 3PL can separate a system that fits from one that only looks good. Ask the vendor to show the specific task you do every week, not a standard tour. These questions will expose most of the gaps quickly:
- Show me two clients with different billing rules in the same warehouse, and how each one’s charges are calculated.
- Show me a pick where the wrong location is scanned. What does the picker see, and what does the supervisor see afterwards?
- Who can see a client’s stock, and can I stop a client seeing another client’s data?
- When stock goes on hold, who placed the hold, who released it and why, and where can I see that history?
- How do you handle returns today, and what is the manual process I would run?
- Which of my carriers and marketplaces are already connected, and which would need custom work?
- What does your standard project need from my team in weeks one to four?
- Can I speak to a customer who runs a site about my size?
Ask for the answers in writing where it matters. A demo is a sales meeting, and a vague answer about returns or temperature control is easier to correct before you sign than after.
If you want to see how this would work for your own clients, our guide to the best WMS for 3PLs sets out the wider requirements. Two Clarus customer stories are worth reading if you run a small operation: St John’s Hall Storage and Tap’in 3PL.
Speak to a warehouse expert
If you’re evaluating your options and want to see how a purpose-built WMS works in practice, Clarus is worth a conversation. We work with 3PLs and distributors across the UK to implement warehouse management software that fits the way you operate, not the other way around.
Get in touch with our team to talk through your requirements.
How we compared this
This guide draws on Clarus’s own implementation experience, as recorded in internal interviews with the team that runs go-lives, and on the UK government, trade body and standards sources linked in the references. Checked November 2026. We have not benchmarked other vendors’ products or prices, and several do not publish them. Clarus is our own product, so treat the comparison of options as a starting point and verify it against each vendor’s written answers.