Most in-store pickup guides focus on the technology: which platform integrations you need, what your POS should support, how to configure the order management system. The technology matters, but it's not where most operations fail. Operations fail in the physical layout of the counter, the staffing model, and the handoff procedures. This guide focuses on those.
This is the guide I wish I had when we were doing the initial store assessments for our early pilot locations. Some of what's here is obvious in retrospect but wasn't obvious when we were looking at the counter floor for the first time.
Physical Layout: Zones Before Technology
Before you install any software, walk your pickup counter and draw zone boundaries. A zone is a distinct physical area where a courier or customer waits for their order. Most counters have between three and six natural zones based on their physical geography: the curbside lane, the interior counter, adjacent parking slots, the side entrance if there is one.
Why does zone definition matter before technology? Because every software decision downstream depends on it. When you configure dispatch sequencing, you're assigning orders to zones. When you train couriers, you're training them to go to Zone B not "the counter near the entrance on the left." When you measure wait time, you're measuring it by zone. Vague zone definitions produce vague operations.
Three things to get right when drawing zone boundaries. First, make sure zones don't overlap physically. If Zone A couriers and Zone B couriers can both approach the same counter window, you have a congestion point that no software will solve. Second, confirm that each zone has a clear visual signal for couriers: a posted sign, a painted marking, a specific physical feature. Couriers shouldn't have to ask which zone they're at. Third, think about capacity: how many vehicles can queue in each zone without blocking traffic? That number is the hard upper bound on simultaneous dispatches per zone.
Staffing Logic: The Right Ratios
The most common staffing mistake in pickup operations is treating all counter staff as interchangeable. In practice, pickup counter roles divide into three functions that require different skills and benefit from different staffing coverage:
Picking staff move through the store floor or warehouse to assemble orders. Their throughput is constrained by pick distance and SKU complexity. For a standard grocery or home goods store, a typical picking rate is 8 to 12 orders per hour per picker. If your peak incoming rate exceeds that, you need more pickers, not a better dispatch system.
Dispatch staff handle the counter: confirming bags, assigning couriers, managing the queue display, handling exceptions. During peak, one experienced dispatch staff member can handle about 15 to 18 routine orders per hour with good tooling. Without tooling, that ceiling is closer to 10 to 12 before decision quality starts degrading.
Float staff cover both roles and handle counter overflow. A counter with two dedicated dispatch staff and one float staff member can handle a 25-order-per-hour peak reliably. Trying to manage a 25-order peak with a single dispatcher and no float is where most lunch-hour congestion events start.
Handoff Procedure: The Documented Version Matters
Most pickup operations have an implicit handoff procedure: staff know roughly what to do because they've been shown by a more experienced colleague. The problem with implicit procedures is that they don't survive staff turnover, shift changes, or high-pressure moments.
The documented handoff procedure for a courier pickup should cover five steps: order confirmation (how does the dispatcher confirm the courier's assignment against the dispatch system?), bag location (which staging slot or zone position?), identity verification (which fields from the order does the courier need to confirm?), departure confirmation (what does the dispatcher do in the system to mark the order dispatched?), and exception path (what does the dispatcher do if the bag isn't where it should be, or the courier doesn't match the assignment?).
The exception path is the one most often missing from implicit procedures. Staff know what to do when everything goes right. What happens when a courier shows up for an order that's been reassigned to a different courier? When a bag is missing? When the order confirmation shows a different zone than where the courier is standing? A written procedure for those cases prevents the 3-minute paralysis that happens when staff encounter them for the first time under pressure.
Shift Handoff: The Often-Neglected Transition
The shift handoff, the moment when an outgoing team hands over to an incoming team, is a consistent source of pickup operation failures. The outgoing shift knows the state of the active queue, which orders are in exception, which couriers have been confirmed. The incoming shift doesn't. The first 15 minutes of any shift run worse than the last 15 minutes of the previous one, and if the handoff is informal, that gap is larger.
A minimal shift handoff takes 5 minutes and covers three things: current active queue depth (how many orders are pending and in what status), active exceptions (which orders are in a non-standard state and why), and any system issues (POS timing problems, courier platform outage, zone configuration changes). The dispatch system should display this information prominently; the verbal handoff should confirm and add context. Without it, the incoming shift is navigating a queue that has pre-existing state they don't understand.
Measuring What Matters
Pickup operations teams tend to measure what's easiest to measure: order volume, average wait time. Those are useful numbers, but two metrics are more actionable for diagnosing where your operation is losing time.
Courier retention rate: the percentage of courier arrivals that result in a same-visit pickup. A courier who arrives and leaves without picking up represents 100% waste of that courier arrival. If your retention rate is below 80%, you have either a queue sequencing problem (assigning couriers to orders that aren't ready) or a courier-communication problem (couriers not knowing which zone to go to). Tracking this number by zone and by time window tells you which.
Exception rate per shift: the number of orders per shift that require non-standard handling. A high exception rate, above 10% of orders in a peak window, signals an upstream problem: unclear order status updates from the POS, a picking accuracy issue, or a courier platform assignment mismatch. The exceptions themselves are symptoms. The exception rate is the signal.
Getting your physical layout, staffing ratios, and handoff procedures right before deploying dispatch software gives the software a foundation to work with. The stores that see the strongest results from automated sequencing are those that already have their operational basics in order. The sequencing layer removes the dispatch bottleneck. If the bottleneck is picking throughput or courier retention, the sequencing layer improves the margins but doesn't fix the root cause.