Curbside Pickup That Actually Works: A POS Setup Guide
Make curbside a profit channel instead of a parking-lot headache: order-ahead flows, arrival alerts, runner handoffs, and substitution rules that keep cars moving and food hot.
The NoPOS developer relations team writes practical guides for building on the NoPOS REST API — from first smoke test to production POS.
Curbside promised convenience, but too many stores run it as organized chaos: runners wandering the lot, cold food, and a phone ringing off the hook with "I'm here." The fix is mostly POS setup, not more staff. Get the flow right and curbside turns into your highest-margin channel.
Take the order ahead, not at the curb
Curbside only works when the order, payment, and pickup details are captured before the car arrives. Offer order-ahead with prepaid checkout as the default, and collect the vehicle description and a callback number at checkout. Pay-at-pickup should be the exception — every curbside payment taken at the car costs you three minutes and a runner's full attention.
Alert the kitchen the moment the customer is en route
The biggest curbside failure is timing: food fired too early goes cold, fired too late keeps cars idling. Give customers an "I'm on my way" button that fires the ticket with a promised window, then an "I've arrived" tap that pages the runner with the stall number. Your POS should show curbside tickets on their own rail, sorted by promised time, not buried in the dine-in queue.
Give runners a handoff checklist, not a memory test
Each curbside handoff should show the runner exactly what verification is needed: order number, customer name, stall, bag count, and any age-restricted items needing ID. Require a one-tap confirm at the car so dispatch knows the order left the building. Track average curb-to-car time per shift — when it creeps past five minutes, you have a staging problem, not a people problem.
Set substitution and refund rules before you need them
Out-of-stock items kill curbside satisfaction when the runner has to negotiate at the window. Let customers pre-authorize substitutions at checkout ("substitute similar item" vs "refund the item"), and empower runners to issue the refund on the spot from a mobile device. Log every substitution — patterns reveal which items need deeper par levels for the pickup rush.
Design the lot like a drive-thru
Number your pickup stalls clearly, keep them closest to the door the runners use, and put the stall map inside the runner's view so nobody memorizes numbers. Separate curbside staging from delivery-driver pickup so runners stop competing for the same bags. Walk the route yourself with two full bags on a rainy day; every door, curb, and puddle you hit is friction your staff hits a hundred times a week.
Build from the current contract
Open the gateway for OpenAPI, Swagger, AGENTS.md, llms.txt, and the first X-API-Key smoke test.
More from NoPOS Blog
Cash Discounting & Surcharging: Cover Card Fees Without Breaking the Rules
A practical guide to offsetting card processing fees on NoPOS: cash-discount vs surcharge vs dual pricing, receipt disclosure rules that keep you compliant, and how to configure each model per location.
Best PracticesChargebacks and Fraud Prevention Without Slowing the Line
A practical guide to cutting chargebacks and payment fraud on NoPOS: EMV and tokenized taps that shift liability, AVS and CVV rules that block card testing, and receipt-level evidence that wins representments without slowing checkout.