Order picking and fulfillment workflows for supermarkets
Coordinate picking, substitutions, fulfillment control, and exception handling so online grocery demand can scale without operational drift.
Store execution
Support pick flows that match the physical store, labor model, and peak-order reality of supermarket operations.
Exception control
Handle substitutions, unavailable items, and fulfillment errors with clearer workflows instead of manual improvisation.
Order visibility
Keep order status, readiness, and handoff decisions visible to store, support, and delivery teams.
Where fulfillment pages need to create confidence
- Faster picking without breaking service quality
- Cleaner substitution control during demand spikes
- Better order readiness for dispatch and delivery teams
- Less manual coordination between digital and store operations
Store picking is warehouse work in a building designed for shoppers
A supermarket floor is laid out to move customers past promotions, not to move a picker through forty order lines on the shortest path. Aisles are shared with shoppers, stock moves between backroom and shelf during trading hours, and the same square metre serves two conflicting purposes at once. Fulfilment software written for distribution centres assumes fixed slot locations, stable stock, and nobody standing in the way. None of that holds in a trading store. Picking workflows have to be built around the store as it actually operates: variable layouts, part-time staff, shared aisles, and a shelf that a customer emptied ten minutes ago.
What a pick run actually costs
The cost of an online grocery order is dominated by the minutes between accepting it and staging it. Travel between zones, backtracking for a missed line, waiting at the scale for a weighed product, and stopping to contact a customer about a substitution all land in the same labour budget. Two stores running identical order volumes can differ sharply in cost per order purely on how their runs are sequenced and batched. Rydel treats the pick run as the unit of work to optimise: what gets grouped, in what order, by whom, and which decisions the picker makes on their feet versus which the system settles in advance.
How a pick run is built
Orders are grouped into runs by delivery window, zone, and order profile, then sequenced against the store's own layout so the floor is walked once rather than repeatedly. Chilled and frozen lines sit late in the run to limit time out of temperature. Heavy and fragile items are ordered so the trolley loads sensibly. The picker receives a sequence rather than a shopping list, and each line carries its location, quantity, accepted substitution rules, and whether the item needs weighing or an age check. The intent is to move decisions out of the aisle, where they are slowest and most error-prone.
Substitutions are a customer conversation, not an exception
In grocery an out-of-stock line is normal; the response is what decides whether the customer orders again. Rydel treats substitution as a rules-driven decision made at the moment of picking. Acceptable alternatives are defined per product and per category, price-protection rules decide who absorbs a difference, and the shopper's own preferences carry through from checkout. When a substitution needs approval the request reaches the customer while the picker is still in the aisle, not after the van has left. Every substitution is recorded against the order, so the pattern shows up in reporting instead of disappearing into the shift.
Weighed items, fresh dates, and what generic systems get wrong
Grocery fulfilment carries product types that general order management does not model. A weighed item has no final price until it is picked. Fresh produce has a date code that determines whether it is acceptable for a delivery two days out. Alcohol and blades need an age check at the door rather than at checkout. Multi-buy promotions have to survive a substitution without quietly changing what the customer pays. These details decide whether a rollout succeeds or generates weeks of manual correction, and they belong in the fulfilment layer rather than in a spreadsheet the store manager maintains privately.
Staging and the handoff to delivery
A picked order is not a finished order. It has to be consolidated across ambient, chilled, and frozen, staged where the driver can find it, and marked ready in a way dispatch can trust. Where staging is informal, delay accumulates at the loading door: drivers wait for orders that were finished but not located, or leave with part of an order while the remaining crate waits for a later run. Rydel keeps staging location, container count, and readiness state on the order itself, so dispatch plans against the real state of the store rather than an assumption about it.
What happens when the store is under pressure
Every fulfilment operation works at ten orders an hour. The design question is what happens at peak, when a promotion lands, or when two pickers call in sick. Capacity has to be visible before slots are sold rather than discovered on the day. Runs need re-sequencing when a picker drops out mid-shift. Orders that cannot be completed need a defined path — partial fulfilment, rebooking, or refund — that support staff can execute without escalating to a manager. A fulfilment system earns its place on the worst trading day of the year, not the average one.
What to measure
Four numbers describe the health of supermarket fulfilment: units picked per hour, substitution rate by category, perfect-order rate (delivered complete, on time, with no correction afterwards), and cost per order including the labour spent on exceptions. Read by store and by shift, they separate a process problem from a local one — a substitution rate that spikes in one store on one shift is a stock or training issue, not a platform issue. Rydel reports these from the same order records the pickers create, so operational and commercial numbers reconcile instead of being argued over monthly.
Where fulfilment sits in the wider platform
Picking depends on everything either side of it: on inventory accurate enough to be worth picking against, on a storefront that promised something the store can actually deliver, and on dispatch knowing when an order is genuinely ready. Rydel runs fulfilment against the same catalogue, stock, and order records as order management, inventory control, and delivery operations. That is why a substitution made in the aisle appears in the customer's account, on the delivery note, and in the analytics without anyone re-keying it into a second system.
Frequently asked questions
Does Rydel support picking from the shop floor as well as a dedicated fulfilment area?
Yes. Runs are sequenced against whichever layout the store uses, so the same workflow covers in-store picking, a backroom fulfilment area, or a dedicated dark store. Stores in the same chain can run different models without separate configurations of the order flow.
How are weighed items handled when the final price is not known in advance?
The picker records the actual weight at the point of picking and the order total updates before payment is settled, so the customer is charged for what was picked rather than an estimate that has to be corrected later.
Can customers approve substitutions before the order leaves the store?
Yes. Where a substitution falls outside the pre-agreed rules, the approval request goes to the customer while the picker is still in the aisle. Customers can also set standing preferences at checkout so common cases resolve without contact.
What happens to an order that cannot be completed?
It follows a defined exception path rather than an ad-hoc decision: partial fulfilment with the missing lines credited, a rebooked slot, or a cancellation. The chosen path is recorded on the order so support and reporting both see the same outcome.
How long does it take to set up picking for a new store?
The main input is the store's layout and zone structure, which determines pick sequencing. Chains that have already defined those standards centrally can open a store against them; the setup is configuration rather than a fresh implementation.
Turn supermarket fulfillment into a controlled workflow
Map picking, substitutions, and handoff logic into one order-management layer built for digital grocery execution.
Smart operations. Better visibility. Real growth.
Office
Borochov 16, Petah Tikva
© 2026. All rights reserved. Powered By Ryware
