Order Fulfilment Software: What It Does & When You Need a Right-Sized System
Order fulfilment software manages the journey from order received to parcel delivered, across stock, picking, packing and dispatch. This guide explains the core functions, who genuinely needs a full platform, and the right-sized owned alternative for firms outgrowing spreadsheets and disconnected tools.
Order fulfilment software manages the work between an order arriving and a parcel reaching the customer: allocating stock, directing picking and packing, booking carriers, printing labels, sending tracking and handling anything that comes back. It may be one product or several connected tools, but the aim is the same: every order should carry one status, one stock reservation and one record of what was sent.
The practical problem is that most growing businesses buy fulfilment tools one step at a time. A courier portal prints labels, a spreadsheet drives the pick list, the webstore holds stock and returns sit in an inbox. Each tool works on its own, yet staff spend the day copying data between them, and errors appear at the joins. This guide explains what to expect from each part of the software, how to test it and when a full platform is worth the cost.

Fulfilment software should tell the picker what to collect and record what actually left the shelf. Illustrative photograph, not an OpsMavix project.
Image credit: Tiger Lily, Pexels License. No edits.
Key Takeaways
- Order fulfilment software covers allocation, picking, packing, dispatch, carrier labels, tracking and returns.
- Allocation rules decide who gets stock when supply is short; write them down before choosing software.
- Labels and tracking should be generated from order data, never retyped from a screen.
- Returns need their own statuses so uninspected stock is not sold again.
- Many businesses need configuration or integration, not a full platform; complexity decides, not turnover.
- Test every option with the same week of real orders, including the awkward ones.
In this guide:
- 1. Understand What Order Fulfilment Software Covers
- 2. Map the Journey From Order Receipt to Delivery
- 3. Set Allocation Rules the System Can Enforce
- 4. Check the Picking and Packing Controls
- 5. Connect Carrier Labels and Tracking
- 6. Treat Returns as Part of Fulfilment
- 7. Decide Who Needs a Full Platform
- 8. Compare Costs and Run a Pilot
- Frequently Asked Questions
- How OpsMavix Can Help
1. Understand What Order Fulfilment Software Covers
One job, several product labels
“Order fulfilment software” is a buyer’s description rather than a single product category. Vendors sell overlapping tools under different names, and the same capability can appear in more than one of them.
| Product label | Usual centre of gravity | Fulfilment steps it often covers |
|---|---|---|
| Shipping or label software | Carrier booking and labels | Dispatch, labels, tracking, sometimes returns labels |
| Order management system (OMS) | Orders from many channels | Capture, allocation, routing, status updates |
| Warehouse management system (WMS) | Physical stock inside a building | Receiving, locations, picking, packing, dispatch |
| 3PL platform | Stock held for several clients | Client orders, warehouse tasks, client billing |
| ERP | Finance and operations in one data model | Sales orders, stock, purchasing, invoicing, sometimes warehouse |
If you want the definitions in more depth, see what an order management system is and warehouse management system functions. This guide focuses on buying: which capabilities matter and how to test them.
Start from the outcome, not the label
Write down the result you need, for example “every order dispatched on the promised day, with the correct items and tracking sent to the channel”. Then check which steps currently stop that happening. The answer tells you which part of the software matters most, regardless of what the product calls itself.
2. Map the Journey From Order Receipt to Delivery
List each step with the record it creates
Fulfilment software is only as good as the records it keeps at each step. The table below is a buyer’s checklist: for each step, what the software should do and what you should ask to see demonstrated.
| Step | What the software should do | What to ask to see |
|---|---|---|
| Order receipt | Import orders from every channel into one queue with the channel reference kept | A marketplace order and a phone order arriving in the same list |
| Release | Hold orders that fail payment, credit or address checks | A held order with a visible reason and owner |
| Allocation | Reserve stock against released order lines | Two orders competing for the last unit |
| Picking | Produce pick lists from allocated orders only | A short pick recorded as an exception |
| Packing | Confirm items, parcel count and weight | A scan of the wrong item being rejected |
| Dispatch | Book the carrier and print the label from order data | A label created without retyping the address |
| Tracking | Write the tracking number back to the order and the channel | The channel showing the order as dispatched |
| Returns | Authorise, receive, inspect and resolve returned items | A return held out of sellable stock until inspected |
For a step-by-step view of how the statuses connect, our ecommerce order management process flow maps each handoff. Here the question is narrower: which of these steps does your current set-up fail, and does a candidate system fix it?
Mark where data is retyped
Walk one order through your operation and note each time someone copies information from one screen to another. Those points are where wrong addresses, wrong quantities and missed dispatches begin, and they are usually the first thing new software should remove.
3. Set Allocation Rules the System Can Enforce
Separate physical stock from promised stock
Allocation reserves units for a specific order. Without it, every channel sees the same physical units as available and two customers can buy the last one. Good software keeps on-hand, allocated and available quantities as separate figures and updates channels from the available figure. Our guide to preventing overselling covers the channel side of this.
Write the priority rule before the demo
When stock is short, someone has to decide who gets it. If the rule lives only in a supervisor’s head, the software cannot apply it. Common rules include:
- Oldest released order first.
- Premium or next-day services before standard services.
- Trade customers with agreed allocations before marketplace orders.
- Complete orders before partial shipments, where the customer will not accept part delivery.
Hypothetical allocation example
Assume one SKU has 30 units available and four released orders want it. The business ships next-day orders first, then oldest first.
| Order | Service | Received | Units wanted | Units allocated | Remaining stock |
|---|---|---|---|---|---|
| A | Next day | 10:40 | 6 | 6 | 24 |
| B | Standard | 09:15 | 12 | 12 | 12 |
| C | Standard | 09:50 | 10 | 10 | 2 |
| D | Standard | 11:05 | 5 | 2 or 0 | 0 or 2 |
Orders A, B and C need 6 + 12 + 10 = 28 units, leaving 30 - 28 = 2. Order D wants 5. If partial shipment is allowed, it receives 2 units and 3 go on backorder; if not, it waits with 0 allocated and the 2 units stay available. The software should let you choose and should show the decision on the order. For handling the shortfall, see backorder management.
Multi-location routing
If stock sits in more than one warehouse, shop or 3PL, allocation also chooses the location. Ask how the system decides: nearest site, site with full stock, or a fixed preference. Our multi-location inventory management guide explains where this becomes difficult.
4. Check the Picking and Packing Controls
Picking methods the software should support
| Method | How it works | Where it fits |
|---|---|---|
| Single-order picking | One picker collects one order at a time | Low volume or large, mixed orders |
| Batch picking | One trip collects several orders, sorted afterwards | Many small orders with common SKUs |
| Zone picking | Pickers own areas and orders pass between them | Larger buildings with distinct product areas |
| Wave picking | Orders released in groups, often by carrier collection time | Fixed courier cut-offs and higher volume |
Most small operations need only the first two. Ask whether the system supports the method you use today and whether changing method is a setting or a project. Our warehouse picking solution guide compares the methods in more detail.
Packing checks worth paying for
- Scan each item against the order line so a wrong SKU is rejected at the bench.
- Confirm quantities, including multi-packs and bundles.
- Capture parcel count and weight where the carrier service needs them.
- Print the delivery note and any required documents at the same time as the label.
- Record who packed the order, so issues can be traced and training targeted.
Plan for exceptions at the bench
Ask what happens when an item is missing, damaged or the wrong size box is needed. The packer should be able to move the order into a named exception status without paper notes. If the only option is to cancel and recreate the order, the software will produce workarounds within a week.

The label and tracking number should come from the order record, not from retyping. Illustrative photograph, not an OpsMavix project.
Image credit: Kampus Production, Pexels License. No edits.
5. Connect Carrier Labels and Tracking
Know what your carriers already provide
Carriers often supply their own tools. Royal Mail, for example, describes Click & Drop as its primary shipping solution, able to integrate with major marketplaces and web stores and to create postage labels for home, office and commercial printers. A carrier tool can be enough if you use one carrier and one or two channels. The difficulty begins with several carriers, mixed services and orders from systems the carrier tool does not connect to.
What to check in a label and tracking integration
| Requirement | Why it matters | Question to ask |
|---|---|---|
| Service selection rules | Weight, size and promise date decide the service | Can rules choose the service automatically, with manual override? |
| Address validation | Bad addresses cause failed deliveries | Where are address problems flagged, and before or after packing? |
| Label printing | Labels must match printers and formats in use | Which label sizes and printers are supported in the demo set-up? |
| Tracking write-back | Customers and channels need the number | Is tracking sent back to every channel automatically? |
| Failed booking handling | Carrier systems reject some requests | Where does a failed booking appear and who sees it? |
| International parcels | Customs data is required outside the UK | Which product data fields feed customs information? |
International shipping rules change, so confirm customs data requirements with your carrier and current GOV.UK guidance rather than relying on a software default.
Hypothetical time saving from label integration
Assume a business dispatches 400 parcels a week and currently copies each address from the webstore into a courier portal. Integration removes 1.5 minutes per parcel, and staff time costs £14 an hour.
- Time saved: 400 × 1.5 = 600 minutes a week, which is 600 ÷ 60 = 10 hours.
- Weekly value: 10 × £14 = £140.
- Yearly value over 52 weeks: £140 × 52 = £7,280.
These figures are hypothetical. Measure your own minutes per parcel before using a calculation like this to justify spending, and include fewer wrong addresses as a separate, unquantified benefit unless you have your own error data.
6. Treat Returns as Part of Fulfilment
Give returns their own statuses
A return should move through requested, authorised, received, inspected and resolved. Inspection decides whether an item goes back to sellable stock, to a seconds location or to write-off. Until then it should not count as available. Software that adds a return straight back to stock on arrival can sell a damaged item to the next customer.
Build the legal timings into the workflow
For most UK online consumer sales of goods, the Consumer Contracts Regulations 2013 set a cancellation period ending 14 days after the goods come into the consumer’s physical possession. The consumer must send the goods back within 14 days of telling the trader they are cancelling. Where the trader has not offered to collect them, the refund is due within 14 days of receiving the goods back or, if earlier, of the consumer supplying evidence of sending them. Exceptions apply, so confirm the rules for your products. The software should show each open return against its refund deadline, not only against inspection.
Hypothetical returns workload
Assume 1,200 orders a month and a hypothetical return rate of 6%. That is 1,200 × 0.06 = 72 returns. If 75% pass inspection, 72 × 0.75 = 54 units go back to sellable stock and 72 - 54 = 18 need another outcome. Without separate statuses, all 72 can appear as sellable the moment they are booked in. Our returns management guide covers the reverse flow in full.
7. Decide Who Needs a Full Platform
Signals that a full platform fits
A full fulfilment platform or WMS earns its cost when complexity is real and lasting:
- Several warehouses, shops or 3PLs where orders must be routed between sites.
- High volume with fixed carrier cut-offs that need wave or zone picking.
- Large numbers of SKUs held in managed bin locations.
- Many channels and carriers, each with its own rules.
- A team that will own configuration and keep the system maintained.
If you hold stock for other businesses, the requirements change again; see 3PL inventory management software.
Signals that a lighter approach fits
- One building, a few hundred SKUs and one or two carriers.
- The main pain sits in one or two steps, such as stock sync or label creation.
- Most platform modules would be switched off.
- The team cannot support a long implementation alongside daily work.
Compare the approaches
| Approach | Where it fits | Limitations to check |
|---|---|---|
| Configure current tools | The webstore or carrier tool already has the needed feature | Edition limits, permissions and reporting |
| Connect existing tools | Each tool works but handoffs fail | Sync frequency, error visibility and who fixes failures |
| Packaged fulfilment software | Standard flows with common channels and carriers | Fit with your exceptions, bundles and returns; pricing as volume grows |
| Focused custom application | A specific gap packaged tools handle poorly | Scope, support, maintenance and integration effort |
| Full ERP, packaged or custom | Fulfilment tied closely to purchasing, production and finance | Implementation scope, data migration and internal capacity |
Packaged software is often quicker to start with and brings tested carrier and channel connections. A custom application or ERP earns its place when your rules repeatedly fall outside what configuration supports, or when fulfilment must share data with processes a packaged tool does not cover. Size alone does not decide; a small business can have complicated trade rules, and a large one can run a simple flow well.
8. Compare Costs and Run a Pilot
Compare total cost over the same period
Licence or build price is only part of the cost. Include set-up, integrations, data migration, training, support, internal staff time and how pricing changes with order volume or users.
Hypothetical three-year comparison
The figures below are hypothetical and show the method, not real quotes.
| Cost item | Packaged subscription | Focused custom application |
|---|---|---|
| Set-up or build | £6,000 | £24,000 |
| Monthly fee or support | £400 | £250 |
| Monthly cost over 36 months | £400 × 36 = £14,400 | £250 × 36 = £9,000 |
| Three-year total | £6,000 + £14,400 = £20,400 | £24,000 + £9,000 = £33,000 |
On these numbers the subscription is £33,000 - £20,400 = £12,600 cheaper over three years. The answer changes if order volume pushes the subscription into a higher tier, if extra modules are needed, or if the packaged tool cannot handle a rule and staff work around it by hand. Price each option against your own volume and requirements; neither model is always cheaper.
Run the same scenario with every supplier
Choose one recent week of real orders, including a short pick, a failed address, a multi-parcel order and a return. Ask each supplier to process the same set and mark each requirement as demonstrated, configurable, requiring development or unsupported.
Pilot acceptance checklist
- Orders from every channel arrive in one queue with their channel references.
- Allocation follows the written priority rule, including partial shipments.
- Pick lists contain only released, allocated orders.
- Packing rejects a wrong item and records the packer.
- Labels print from order data for each carrier and service in use.
- Tracking numbers reach the order and the sales channel.
- Returns stay out of sellable stock until inspected.
- Open returns show their refund deadline.
- Failed bookings and sync errors appear in a list with an owner.
- Data can be exported if you later change system.
After the pilot, expand step by step and keep a weekly review of exceptions so the system is maintained rather than worked around.
Frequently Asked Questions
What does order fulfilment software do?
It manages the steps from order receipt to delivery: allocating stock, directing picking and packing, booking carriers, printing labels, sending tracking and handling returns, with each order keeping one status throughout.
Is order fulfilment software the same as a WMS?
Not exactly. A WMS manages physical stock and tasks inside a warehouse. Fulfilment software may include WMS features, but it can also be an OMS, shipping tool or ERP module, depending on where your work is concentrated.
Do small businesses need order fulfilment software?
Many need some of it. A single-channel shop may manage with its webstore and carrier tool. Once several channels share stock, or labels and tracking are retyped by hand, connected fulfilment features usually pay for themselves in fewer errors.
Can a carrier’s own tool be enough?
Sometimes. Carrier tools can import orders and print labels, which may cover a business using one carrier and supported channels. They rarely manage allocation, picking controls or returns inspection, so check those separately.
How should returns be handled in fulfilment software?
As their own flow with authorised, received, inspected and resolved statuses. Uninspected returns should not count as available stock, and each open return should show its refund deadline.
How long does implementation take?
It depends on channels, carriers, data quality, integrations and testing. Ask suppliers for milestones, responsibilities and acceptance criteria based on your scope rather than a general estimate.
What should I prepare before speaking to suppliers?
A written map of your current steps, your allocation rules, a list of carriers and services, one week of real orders including exceptions, and the reports you need each day.
Can OpsMavix build order fulfilment software?
Yes. OpsMavix can build focused applications or a full custom ERP, and can configure or integrate suitable existing tools where those approaches fit the requirements.
How OpsMavix Can Help
OpsMavix can map how orders move from receipt to delivery across your channels, warehouse and carriers, then define the system scope needed to remove retyping and make every order traceable.
That may involve configuring the tools you already use, connecting channels and carriers, introducing ecommerce inventory automation, adding an inventory automation system, building a wholesale order management system for trade orders or developing a full custom ERP.
Contact OpsMavix with one recent week of dispatched orders, the records behind them and the handoff that creates the most rework. We can use that evidence to define requirements and a practical pilot.
Getting value from OpsMavix? Add us as a preferred source on Google — you'll see more of our operations content in your AI Overviews, AI Mode and Search.