The Route Nobody Walks
Every bin location in our system can be given a pick sequence. The field is on the create form and the edit form, it is validated, it is stored, and it comes back on the item screen. Nothing in the product has ever sorted anything by it. For a warehouse where the walk is the cost, that is not a missing feature — it is a field that reads as a promise.
Ask any warehouse manager between Rotterdam and Venlo what their largest controllable cost is and you will get the same answer: walking. Not storage, not systems, not even labour in the abstract — the distance a picker covers between the first line of an order and the last.
It is the cost that responds best to software, too, because the fix is arithmetic rather than capital. Number your locations in the order somebody physically walks them, sort every pick list by that number, and the same order takes fewer steps. No conveyor, no robot, no new building.
Our system lets you record that number. It has never used it.
What is actually there
A location in our warehouse model is genuinely detailed. It belongs to a warehouse, it has a code and a name, and it carries a storage role plus a full physical address inside the building: zone, aisle, bay, shelf, bin. It also carries a pick sequence — an integer, validated between 1 and 999,999, on both the create and the edit screen, stored on the location and returned wherever the item's locations are listed.
A person filling that form in would reasonably conclude that the number does something. It is the only field on the screen whose name describes an operation rather than a place.
It does not do anything. There is no ordering by it anywhere in the application. There is no pick list document, no wave, no route, no batch pick and no sequence-aware display. The number is stored faithfully and read by nothing that would act on it.
A field you can fill in is a promise. This one has been taking data since it shipped and has never spent any of it.
The sixth field of exactly this shape
We keep finding these, and the pattern is worth naming because it is more useful to you than any single instance. A column exists. It is fillable, validated, and rendered on a form. Nothing reads it. The system behaves identically whether it is populated or empty.
Inert fields found in our own product, and what each one looks like it promises
locations.pick_sequence
Looks like: pick lists are ordered by your walking route. Actually: nothing sorts by it.
locations.capacity
Looks like: a bin can be full and the system will say so. Actually: no putaway check and no utilisation view. Covered in The Shelf That Cannot Be Full.
Count plan frequency
Looks like: a plan marked monthly generates a monthly count. Actually: nothing schedules from it. Covered in The Monthly That Never Comes.
items.fefo_policy
Looks like: rotation can be set per item. Actually: dead column — but oldest-expiry-first is enforced unconditionally anyway, so the behaviour is better than the field suggests.
Approval value thresholds
Looks like: an order over a value routes differently. Actually: stored by the engine and consumed by nothing.
The location address itself
Zone, aisle, bay, shelf and bin are stored, displayed and searchable, and they do exactly what they appear to do.
The last row is not padding. Most of the location model works; the inert field is the exception, which is precisely why it is convincing.
Why this matters more in the Netherlands than almost anywhere
Two reasons, and neither is about the software.
The first is that Dutch logistics operates at a density where walking distance is a line on a rate card. A great deal of the warehousing here is third-party — you are picking somebody else's goods for a fee per line or per order, and your margin is the gap between that fee and the minutes it takes. A system that cannot order a pick route is not costing you a nice-to-have; it is costing you the variable you sell.
The second is labour. Picking is done by people who may be with you for a season, in a market where those people are scarce and expensive. Route order is the single largest determinant of how quickly a new picker becomes productive, because a sequenced list is self-teaching and an unsequenced one requires knowing the building.
What you can actually do with what exists
-
Encode the route into the location code, not the pick sequence
The code is a string and it is displayed everywhere the location is. If you name your bins so that alphabetical order is walking order — A-01-01-A, A-01-01-B, A-01-02-A — then every list that sorts by code is, accidentally, a route. This is the whole workaround and it is genuinely effective.
-
Get the zoning right before go-live, because the code is hard to change later
Renaming a bin after six months of movement history means every historical record refers to a code that no longer describes where the goods were. Decide the scheme once. It is worth a day of arguing.
-
Use storage roles to separate the fast pick face from bulk
The storage role on a location is real and it is respected in the interface. A separate fast-moving zone, physically short to walk, is the intervention that beats sequencing anyway.
-
Do not populate pick sequence and expect it to work
Fill it in if you want a record of your intended route for the day you have a system that reads it. Do not build a process on it, and do not let a supervisor believe a list is sequenced because the field is filled.
The single most valuable thing in this post
If you are evaluating any warehouse system, ask to see a printed or on-screen pick list for a five-line order across four aisles, and ask what determines the order of the lines. It is a two-minute test and it separates a warehouse management system from an inventory system with location fields. We are an inventory system with location fields, and this is us saying so before you find out.
What AWRA OpsHub does today
- Multi-warehouse stock with a full location hierarchy — zone, aisle, bay, shelf, bin — plus a code, a name and a storage role on every location.
- Stock held per item per location, with batch tracking, allocation ordered oldest-expiry-first, and hold and disposition states on a location row.
- Movement history on every unit, including transfers between warehouses and the receipt at the other end.
- Barcode scanning against items and locations, and mobile capture that survives losing signal.
What it does not do
- Any pick list document. There is no picking wave, no batch pick, no route and no pick confirmation step.
- Ordering by pick sequence. The field is stored, validated and displayed, and nothing in the product sorts by it.
- Putaway logic. Nothing suggests a location for an incoming pallet, and nothing checks a bin's capacity — see The Shelf That Cannot Be Full.
- Slotting analysis. There is no report ranking locations by pick frequency, so the data to design a route exists in movement history but nothing surfaces it.
Not ours, by choice
- This is an inventory system, not a warehouse management system, and the distinction is real rather than marketing. If picking productivity is your operating margin, you need the other category of product and we would say so on a call.
- The location-code workaround is genuinely used and genuinely works. It is not a substitute for sequencing; it is a way of getting sequencing for free from a field that already sorts.
- Nothing here is Dutch. It applies to any dense pick operation; the Netherlands is where our reader is most likely to be running one.
What is not built for the Netherlands today can still be built for you
Anything described above as not built is a statement about what ships in the standard product today — not a limit on what AWRA OpsHub can do in the Netherlands. Kenya's eTIMS integration and its maintained payroll engine exist because Kenyan clients needed them and commissioned them; neither appeared by itself. The same door is open here. If the buyer's number on the document, and something that checks it is real, a bank or mobile money feed, a statutory return format, a rule your own operation needs that the standard one does not have, or a link to a system you already run is what stands between you and a decision, tell us and we will scope it as a build — written spec, timeline and price — before you commit to anything.
Four builds, and the first one is far smaller than the three behind it
Put the particulars on the printed invoice. Your VAT identification number, your customer's, and their address are all stored today and none of the three reaches the document — so the first build is a template and a query rather than a schema change, and it removes most of the reason a Dutch cross-border invoice would fail on inspection. Then a reverse-charge treatment that survives being saved, with the legend printed from the line's own state instead of typed into a notes box by hand, and a validation failure for treatments the resolver does not recognise rather than the silent fall-through to the standard rate it does today. Then validation of a counterparty VAT number at the point it is entered, against VIES, because the zero rate on an intra-Community supply is conditional on that number being valid and we currently accept any string. Only then a btw-aangifte and an opgaaf ICP assembled from the result — quoted last because an ICP listing is a per-customer total keyed to VAT numbers, and it cannot be built until those numbers are on the transactions in a form a query can read. A Peppol access point for business-to-government invoicing is a separate build and a present one, since that mandate has been live since January 2019.
Banks and payments
SEPA credit transfers and direct debits, iDEAL collection, and bank statement feeds wired into the Payments Register, so money in and out reconciles against the documents that authorised it rather than being re-keyed from a bank screen.
The operational work, which is what most commissions actually are
An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.
Payroll and statutory returns
A Dutch payroll engine with loonheffing computed on live employee records, pension administration and submission on each pay run. None of it exists today; labour cost attribution to projects and cost centres does.
Systems you already run
The accounting package, CRM, online store or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. No roadmap slide, and no pretending in a demo that something exists when it does not.
Tell us what you need integratedFive questions that tell you what a warehouse module really is
Show me a pick list for a multi-line order, and tell me what orders the lines.
A good answer sounds like
A sequence field, a zone path, or a route algorithm — named, and visible on screen.
What it actually means
If the lines come back in item order or in order-entry order, there is no routing, whatever the location model looks like.
Which fields on a location change system behaviour, and which are descriptive?
A good answer sounds like
A short list of the former and a longer list of the latter.
What it actually means
Every vendor has descriptive fields. The ones that answer this question honestly are telling you where the machinery is.
What happens when a bin is full?
A good answer sounds like
A warning, a suggested alternative, or an explicit "nothing".
What it actually means
Ours is nothing. A hard refusal would be worse — goods that have arrived have to go somewhere.
Can you rank my locations by pick frequency?
A good answer sounds like
Yes, from movement history, as a report.
What it actually means
This is the input to slotting. If it cannot be produced, the system cannot help you improve the layout even manually.
How many people are picking against one document at once?
A good answer sounds like
A clear answer about concurrency and confirmation.
What it actually means
Systems without a pick document have no answer to this, which is fine at low volume and dangerous at high volume.
The verdict
Do not buy this expecting a routed pick. Buy it for accurate multi-location stock, batch control and traceable movement, encode your walking order into the location codes on day one, and keep the pick sequence field empty so that nobody downstream mistakes it for a working control. If routed picking is the reason you are shopping, this is the wrong category of product and we would rather you knew now.
Talk to us about a location scheme
The coding scheme is the decision that is expensive to change and free to get right. If you are laying out a building or migrating one, we will go through it with you before anything is loaded.
Get the scheme reviewedFrequently asked questions
If pick sequence does nothing, why is it on the form?
It was built as part of the location model in anticipation of picking work that has not been done. That is an explanation rather than a defence — a validated field on a live form is read by users as a working control, which is why we are publishing this rather than quietly leaving it there.
Will sorting by location code really give me a route?
It will if, and only if, your codes are assigned in walking order. That is a naming discipline rather than a feature, and it breaks the first time somebody adds a bin out of sequence — so leave gaps in the numbering, the way street numbering does.
Could you build routed picking for us?
A pick document with a route, confirmation and concurrency is a substantial build rather than a setting, and it would sit on top of a location model that already holds everything it needs. Describe the operation and we will come back with a written scope, a timeline and a cost before you commit.
