BOPIS Chaos Control by Scheduling a Dedicated Curbside Runner

Treat the curbside runner as a real role

BOPIS volume turns chaotic when curbside work is treated as a shared task. When everyone owns it, no one owns it. Associates get interrupted mid pick. Customers wait outside while staff search for bags. The service desk gets clogged. Managers spend their time dispatching instead of leading.

A dedicated curbside runner during peak hours fixes the operating model. It creates a clear handoff. Pickers pick. Service desk verifies. Runner delivers. The store stays organized and the customer gets a consistent experience.

This post explains how to identify peak hours, size runner coverage, set clear boundaries, and launch the role without creating a new layer of confusion.

Start with data that reflects pickup reality

Order placement timestamps do not equal pickup arrival times. Many customers place orders in the morning and pick up after work. Others place and pick up within an hour. If you staff based on placement alone, you will miss peaks.

Use pickup ready notifications and actual pickup check in timestamps if you have them. If not, use curbside arrival logs or manual counts for two weeks.

Data points that matter

• Curbside check in time by day of week
• Average items per order and percent of bulky items
• Percent of orders with substitutions or missing items
• Average time from check in to handoff
• Number of parking spots and walking distance to the door

This data tells you when a runner is needed and what slows them down.

Build a simple peak hour heat map

You do not need a fancy dashboard. A basic table works.

A simple approach

• For each day type, count curbside check ins per half hour
• Identify the top three peak blocks
• Confirm if peaks shift by season or by promotion cycle
• Separate weekday patterns from weekend patterns

Once you see peaks, you can schedule the runner role like you schedule a register lane.

Separate pickup demand from store traffic demand

Peak curbside hours can overlap with peak in store traffic, but not always. When they do overlap, the store feels the pain more because everyone is busy.

Planning rule

• If curbside peak overlaps with in store peak, runner coverage must be protected, not borrowed

Borrowing the runner for other tasks collapses the system at the worst time.

Define the curbside runner job so the handoff is clean

The runner role must have clear boundaries. Otherwise it becomes a catch all task list.

Runner responsibilities

• Monitor curbside check ins and queue
• Verify order number and customer identity per policy
• Retrieve staged orders from the correct zone
• Deliver to the vehicle using a consistent path
• Handle bulky items with safe lifting methods
• Capture completion in the system

Runner responsibilities should not include picking unless you are short staffed and you explicitly choose that model. Mixing picking and running usually creates late orders because the runner is away from the curb.

Define handoffs between picking, staging, and runner work

A clean handoff prevents searching and rework.

A simple handoff flow

• Picker completes the pick and confirms accuracy
• Order is bagged and labeled in the staging area
• Stager places the order in a defined zone and updates location
• Runner retrieves from the zone and completes handoff to customer

If you do not have a stager role, the picker can stage. The important part is that the location update is done correctly.

Standardize staging zones so the runner moves fast

Staging is where time is lost. The runner cannot move fast if the staging area is messy.

Staging zone standards

• Separate ambient, chilled, and frozen
• Separate large and bulky from small bags
• Use clear location labels that match the system
• Keep a short path from staging to curbside exit
• Keep a small exception zone for holds and problem orders

The runner should not be deciding where to look. They should be executing a repeatable route.

Size runner coverage using work content, not feelings

Runner staffing depends on how long each handoff takes. Measure it.

Components of runner time

• Time to read check in and confirm order number
• Walk time from curb to staging and back
• Retrieval time in staging
• Load time at vehicle
• Exception time for missing bags, substitutions, or identity checks

A common pattern in many stores is that walk time dominates. If staging is far from curbside, you may need more than one runner even with moderate volume.

Use a practical coverage rule for peak blocks

A simple sizing rule is useful even if it is not perfect.

A starting rule

• If average handoff time is four minutes and you expect more than ten curbside check ins per hour, one runner will struggle without help
• If handoff time is six minutes and you expect more than eight check ins per hour, add support or a second runner
• If bulky items are common, add extra minutes to handoff time and plan coverage accordingly

Then validate by tracking wait times for a week and adjusting.

Decide on a two runner model for heavy peaks

Two runners can be more efficient than one if they split the work properly.

Two runner split options

• One runner handles arrivals and small orders, one runner handles bulky and special handling
• One runner retrieves while the other loads and confirms completion
• One runner covers curbside while the other covers store pickup counter during peak

Pick one model and stick with it. Switching models mid shift creates confusion.

Scheduling templates that work in real stores

Templates reduce decision load for managers and create stable expectations for staff.

Weekday template for lunch pickup and after work pickup

Many stores see two weekday peaks.

Template approach

• Runner coverage in the lunch block for a limited window
• Runner coverage in the after work block with protected time
• Light coverage outside peaks with a backup plan for spikes

If you cannot staff two peak blocks, staff the bigger one and fix staging so the runner can move faster.

Weekend template focused on extended peaks

Weekends often have a longer peak rather than two distinct peaks.

Template approach

• Two runner coverage for the highest volume block
• One runner coverage for the shoulder hours
• Clear break coverage plan so the role never goes unmanned

Break coverage is a common failure. If the runner goes on break and no one is assigned, wait times spike and the team panics.

Holiday and promotion template with surge capacity

Surges need a pre planned trigger.

Surge triggers

• Queue exceeds a defined count
• Average wait time exceeds a defined target
• A wave of ready notifications indicates high pickup volume

Surge response options

• Assign a second runner for a limited block
• Assign a loader helper to speed bulky handoffs
• Temporarily pause non urgent tasks in staging to clear backlog

Surge plans should be written and practiced, not invented in the moment.

Process standards that keep the runner fast and safe

Speed is mostly process, not hustle.

Use a queue method that prevents missed arrivals

The runner needs a consistent way to track who is waiting.

Queue practices

• Work first in first out unless a policy exception applies
• Confirm the vehicle description if the system supports it
• Use a visible board or device list if multiple arrivals occur at once
• Close the loop in the system immediately after handoff

Missed arrivals usually come from poor queue control, not from slow walking.

Reduce exceptions by tightening picking and staging accuracy

Every exception costs minutes and creates stress.

Exception reduction practices

• Use a final bag count check before staging
• Label every bag clearly with order identifier
• Separate substitution and missing item notes so the runner is not discovering problems at the curb
• Hold problem orders in the exception zone and notify the customer before they arrive when possible

The runner should not be troubleshooting in the parking lot.

Set safe handling rules for bulky orders

Bulky orders create injury risk and slow service if handled poorly.

Safe handling practices

• Use carts designed for weight and stability
• Use a two person lift rule for defined items
• Stage bulky items closest to the curb exit
• Train runners on loading method to protect backs and shoulders

Safety is part of service. Injuries create staffing gaps that make curbside worse.

Protect the runner role from being pulled away

The runner role collapses when managers treat it as spare labor.

Protection rules that work

• During peak blocks, the runner does not stock shelves or run register
• During peak blocks, the runner does not pick orders unless a defined emergency occurs
• If the store is short staffed, reduce the pickup promise, not the runner coverage

If you pull the runner away, you are choosing longer waits and more complaints. Make that choice explicit so the store stops doing it by accident.

Prevent burnout and turnover in the runner position

Runner work can be physically demanding and socially stressful. Treat it like a rotation role, not a permanent penalty.

Burnout prevention practices

• Rotate runner duty across trained staff
• Keep shift length reasonable for high volume days
• Provide water and planned breaks
• Recognize that weather affects fatigue and pace
• Give the runner a backup person during heavy peaks

If you ignore burnout, you will lose the people who are best at the role.

What to track so the system improves

Track measures that connect to customer experience and labor efficiency.

Core service measures

• Average wait time from check in to handoff
• Percent of pickups within the target time
• Abandon or cancel events linked to pickup experience
• Customer complaints tied to curbside

Operational measures

• Orders staged with correct location on first attempt
• Exception rate per hundred orders
• Runner handoffs per hour during peak blocks
• Minutes lost to searching for staged orders

Use these measures to fix process and staffing, not to blame individuals.

A fourteen day launch plan

Days one to three measure and define the role

Actions

• Collect curbside check in counts by half hour
• Measure average handoff time and top delay reasons
• Define runner responsibilities and boundaries
• Define staging zone standards and label method

Deliverable

• A written runner role and a basic peak block schedule

Days four to seven set staging and queue standards

Actions

• Clean staging area and set zones by temperature and size
• Train pickers and stagers on location updates
• Train runner on queue method and safety rules
• Run the first peak block with dedicated coverage

Deliverable

• Reduced searching and clearer handoffs

Days eight to fourteen adjust staffing and stabilize

Actions

• Compare planned coverage to actual wait times
• Add a second runner for the heaviest block if needed
• Set break coverage so runner role is always covered
• Publish a rotation plan to reduce burnout

Deliverable

• Stable peak coverage and consistent service

Quick checklist for each peak block

Before the block

• Confirm runner assigned and backup assigned
• Confirm staging zones are clean and labeled
• Confirm carts and supplies are ready
• Confirm queue method is active

During the block

• Work the queue consistently
• Close the loop in the system after each handoff
• Escalate exceptions quickly to the defined owner
• Keep bulky items on the fast path

After the block

• Clear staging backlog
• Record top delay reason for the block
• Reset supplies and carts
• Confirm the next coverage handoff

BOPIS curbside feels chaotic when the store treats it as a side task. A dedicated curbside runner during peak hours turns it into a controllable operation with clean handoffs, faster service, and less stress for the team.