Order Fulfillment Software for B2B & B2C Warehouses
Order fulfillment software that plans waves against carrier cutoffs, customer windows, dock doors and labour — choosing single-order, batch, cluster or zone picking per wave, and surfacing promise-date exceptions while there is still time to act.
Schematic
Order lifecycle and its exceptions
The happy path, and the three places orders actually leave it.
Order fulfillment that schedules the work, not just prints it
MileSoft Order Fulfillment turns an order pool with promise dates and carrier assignments into waves that can actually finish in time. Wave generation respects carrier cutoffs, customer delivery windows, dock assignments and labour capacity, and each wave's picking strategy — single-order, batch, cluster or zone — is chosen from its own order mix rather than set once for the building.
A pick-path optimiser sequences each tour, a labour model reports when a wave will finish rather than only how many pick hours it contains, and outbound is staged in load sequence for the dock door the load will leave from. Business-to-business and consumer orders run in the same engine on separate wave streams, partitioned by how much latency each order can tolerate.
Carrier integration covers manifesting, GS1 SSCC labelling and tracking. Returns create an authorisation record routed to restock, refurbish or dispose, and inspected stock returns to the same warehouse record rather than a separate returns database. Promise-date exceptions surface at wave time, while the cheaper responses are still available.
Order fulfillment software
A pick-list printer is not an order fulfillment engine
Printing today's orders in a sensible sequence is formatting. Deciding what travels together, and whether it can make the carrier, is scheduling.
Underneath the pick list are the decisions that matter: which orders should travel together, by which picking strategy, and whether the result can be picked, packed and staged before a carrier that will not wait. A system that does not make them leaves them to whoever releases the work. A wave is a batch, and a batch is a commitment: grouping makes picking efficient and also makes each order wait.
| Constraint | Source | Consequence of ignoring it |
|---|---|---|
| Carrier cutoff | The carrier's schedule | The load ships tomorrow |
| Customer window | The order's promise | A delivery outside the agreed window |
| Dock assignment | The dock plan | Output staged at the wrong door and re-sorted |
| Labour capacity | The shift roster | A wave that cannot finish in the time available |
The dock constraint is the one most often left out, and it fails visibly: correct picking whose output reaches staging in an order nobody can load, so it is sorted again at the door. Wave release is coordinated with loading dock door availability so outbound is staged in load sequence. And a perfect wave plan against a wrong stock position produces a perfectly sequenced failed pick — which is why inventory tracking accuracy sits upstream of everything here.
Wave planning
Wave planning: choosing a wave size instead of inheriting one
Bigger waves spread travel across more orders — and make every order wait longer.
work per order = tour travel ÷ orders in wave + handling per order · flow time = half the wave fill time + the wave's own duration
Travel dominates picking time, and a tour visiting more faces grows sublinearly — so the first few orders added to a batch deliver most of the saving and the twentieth very little, while flow time rises linearly.
Worked example: 90 orders an hour, 4 lines each
With 0.4 minutes of handling per line and measured tours of 22, 34, 44 and 58 minutes for waves of 5, 15, 30 and 60 orders, work per order falls from 6.0 to 3.9, 3.1 and 2.6 minutes. Flow time at 15 orders is about 39 minutes; at 60 it is about 78.
Going from 5 to 15 orders saves 2.1 minutes of work per order for 12 more minutes of flow — clearly worth it. Going from 15 to 60 saves another 1.3 minutes and doubles flow time. A facility waving at 60 because its previous system did is paying 39 minutes of latency for a third of the saving it had already banked. Every input is in your own pick history.
Batch, cluster and zone picking
Single-order, batch, cluster and zone picking are one trade, not a maturity ladder
Each strategy moves work out of travel and into something else. The order mix decides which is cheapest.
Single-order
One tour per order. Wins when latency matters more than efficiency — the time-critical case.
Batch
One tour plus a sort per line picked. Wins when multi-unit orders share faces, because the tour barely grows as orders are added.
Zone
The slowest zone's tour plus a consolidation step per order. Wins on very large counts of one- or two-line orders.
Cluster
A slightly longer tour with a lighter sort into carts. Often the answer for the case the usual heuristic does not name: many orders, each with many lines spread across zones.
The engine selects a strategy per wave from the actual order mix, so two waves in the same shift can pick differently.
Zone picking and labour
Why a zone-picked wave finishes when its slowest zone does
Total labour and completion time are different quantities, and a cutoff is missed on the second.
completion time = worst zone's work ÷ that zone's pickers + consolidation
A picker in zone A cannot pick zone C's lines without becoming a zone C picker, so idle capacity elsewhere does not help. In batch picking every picker draws from one pool and imbalance self-corrects; in zone picking it persists until someone reassigns.
Worked example: total labour fits, the wave still misses
620 minutes of work across four zones, twelve pickers at three per zone, 25 minutes of consolidation, 140 minutes to cutoff. With zone A at 300 minutes, completion is 100 + 25 = 125 — inside. When the mix shifts so zone A carries 420 minutes, total labour still fits easily, but completion is 140 + 25 = 165: the wave misses by 25 minutes while zones C and D stand idle.
Rebalance to today's mix — six pickers in A, three in B, two in C, one in D — and completion is 95 minutes. Same twelve people, same work, forty minutes inside the deadline instead of twenty-five outside it. Balancing should follow the wave, not the roster.
B2B, B2C and returns
B2B and B2C fulfillment in one engine, but not in one wave
The two profiles want opposite wave sizes.
Business-to-business orders are pallet-level, bulk and scheduled; consumer orders are unit-level, time-sensitive and carrier-integrated. The wholesale order can absorb hours of latency and benefits from large batches; the consumer order cannot. Mixing them in one wave gives each the other's optimum. The right architecture is one engine with concurrent wave streams, partitioned by what an order can tolerate rather than by channel — a rush wholesale order belongs with the fast stream, and a standing consumer subscription with the slow one.
Returns generate an authorisation record with putaway routed by reason — restock, refurbish or dispose — and inspected stock becomes available in the same warehouse record. There is no separate returns database, because a return living outside the main record is stock that exists physically and not systemically. Carrier integration covers manifesting, labelling to GS1 SSCC and tracking.
Promise-date exceptions
What surfacing an exception two hours earlier is actually worth
MileSoft's product material puts promise-date exceptions at wave time, two to four hours before they would surface at the dock. The hours are not the value.
The value of early detection is the difference between the cheapest response still possible at wave time and the cheapest one left at the dock. It depends on the responses a facility can actually execute, not on the hours.
Worked example: a shortage on a 40-unit line
Responses: substitute (20 min, cost 15), expedite from reserve (75 min, 40), split the shipment (30 min, 120), re-promise (10 min, 200), ship short (0 min, 480). At wave time, 150 minutes out, the cheapest is substitution at 15. At the dock, 12 minutes out, only re-promising and shipping short remain, and the cheapest is 200. Early detection is worth 185 per exception — about 5,550 a week at 30 exceptions.
Remove the substitution policy and split authority, and the value falls to 160. A facility that can only re-promise or ship short gets zero: the exception arrives two hours earlier and changes nothing. Define the response set — substitution rules, split authority, expedite budget, re-promising policy — before deployment.
Evaluating fulfillment software
Eight questions to put to any order fulfillment software
Each is answerable by demonstration — including by us.
| # | Dimension | Ask the vendor to demonstrate |
|---|---|---|
| D1 | Wave size reasoned | What sets wave size — a target order cycle time, or a default? |
| D2 | Strategy per wave | Do two waves in the same shift ever use different pick strategies? |
| D3 | Deadline feasibility | Does the system refuse to release a wave that cannot finish before the cutoff? |
| D4 | Makespan not labour | Does it report a wave's completion time, or only its total pick hours? |
| D5 | Balance to the wave | Is zone staffing set from today's order mix, or from the roster? |
| D6 | Urgency partition | Can a rush wholesale order join a fast wave, or is it batched by channel? |
| D7 | Dock-aware staging | Is outbound staged in load sequence, or sorted at the door? |
| D8 | Exception with response | When a promise failure surfaces, does the system offer the actions still available? |
D3 separates planning from printing. A system that releases a wave which cannot finish in the time remaining is formatting, and the deadline is being managed by whoever notices.
On evidence: no published outcome is attributed to this module. And on accuracy claims generally in this category, ask for the denominator: 99.9% of lines at five lines per order is roughly 99.5% of orders, and customers experience orders. MileSoft's return model assumes a 15% labour gain on 12 pick-and-pack staff; that gain can only come from better-formed waves reducing travel, so it is largest where a facility picks order by order today and smallest where it already batches well.
Standards referenced: ISO/IEC 19987 and 19988, GS1 SSCC and General Specifications, ISO/IEC 15459-1, ISO 22400-2, IEC 62264-3, Incoterms 2020. Derivations are in the order fulfilment method paper.
Features
Key Features
Built-in capabilities that set our software apart
Constraint-aware wave planning
carrier cutoffs, customer windows, dock assignments and labour capacity
Strategy per wave
single-order, batch, cluster or zone picking chosen from each wave's order mix
Pick-path optimisation
tour sequencing inside each wave
Completion-time labour model
zone staffing balanced to the wave, with makespan reported against the cutoff
B2B and B2C wave streams
one engine, partitioned by urgency rather than channel
Carrier integration
manifesting, GS1 SSCC labels and tracking, with outbound staged in load sequence
Returns in the same record
authorisation and putaway by reason: restock, refurbish or dispose
Benefits
Key Benefits
What your team gains from adopting our platform
Testimonials
What Our Clients Say
Trusted by industry leaders across manufacturing, HVAC, and logistics.
"The software features, such as real-time monitoring and alerts, have proved invaluable in optimizing machine operations. MileSoft team's professionalism, technical expertise, and dedication to meeting our requirements have been impressive."
FAQ
Order Fulfillment Software — FAQs
Answers to the most common questions about this product. Need more? Book a demo or reach out via Contact.
What is wave planning, and do we need it?
Which pick strategy suits our order profile?
Can we run B2B and B2C in the same system?
Does it handle returns?
How does it connect to our dock and carrier systems?
Explore More
Related Products
Complementary tools teams often pair with this solution
Related Reading
Go deeper
Explore the long-form story behind this product.
A Wave Is a Batch, and a Batch Is a Deadline: Strategy Selection, the Travel-Latency Trade, and the Recovery Window
Architecture, Computational Methods, and a Modelled Scenario for MileSoft Order Fulfillment
Read the paperRead the full Order Fulfillment Software for B2B & B2C Warehouses deep-dive
Read articleSee how MileSoft delivers in Warehouse
Read case studySee your savings in under a minute
Estimate the time and cost this tool could give back — free, instant, no sign-up.
Plot your own wave-size curve before you buy anything
Share a week of pick history. We will chart work per order against order flow time by wave size, and show where a zone wave would miss its cutoff.