What happens when retailers do not adapt fraud controls for curbside pickup and click-and-collect orders?

Why This Matters for Security Teams

Friction appears fastest at the fraud review layer, where rules built for parcel shipping are reused for pickup and handoff flows that do not produce the same evidence. curbside pickup and click-and-collect compress the moment of transfer, so the control problem shifts from carrier tracking to proving possession, authorisation, and fulfilment integrity. When retailers keep older assumptions, fraud losses are rarely dramatic in a single event, but they become persistent through chargebacks, duplicate claims, and weak dispute files.

Retailers also need to treat the pickup channel as a different evidence environment, not just a different fulfilment option. The decision quality depends on whether the business can tie the order to a specific handoff event, a validated customer or proxy, and a timestamped record of completion. CIS Controls v8 is useful here because it reinforces that account handling, audit logging, and data protection are operational controls, not back-office paperwork.

In practice, many retailers discover the gap only after a spike in "item not received" disputes shows that the old delivery evidence model no longer matches how the sale actually completed.

How It Works in Practice

fraud controls for curbside pickup and click-and-collect work best when they follow the handoff, not just the order. A parcel delivery flow typically depends on carrier scans, shipping labels, and a last-mile status update. Pickup flows need different signals: order release, arrival confirmation, who collected the order, what was handed over, and whether the handoff was tied to a verified identity, vehicle, code, or barcode. Without those signals, investigators are left with partial logs and a weak chain of custody.

At a minimum, retailers should align control points to the moments where fraud can occur:

• order placement, to catch unusual velocity, payment mismatch, or account takeover patterns;
• order release, to ensure the item is not staged too early or handed over on stale approval;
• pickup confirmation, to record the exact person, device, code, or proxy used at collection;
• exception handling, to document substitutions, split fulfilment, cancellations, and store overrides.

That evidence should be easy to retrieve during disputes, because chargeback defense depends on proving completion, not merely showing that the order was prepared. Stores also need tighter internal controls at the counter or curb, since social engineering, rushed staff decisions, and informal workarounds can undermine the strongest policy on paper. CIS Controls v8 also maps well to this operational reality because logging, access control, and secure handling of customer data all support the evidentiary trail.

These controls tend to break down when fulfillment rules differ by store, because inconsistent handoff steps create gaps that fraud teams cannot reconstruct after the fact.

Common Variations and Edge Cases

Tighter pickup controls often increase checkout friction and store labour overhead, so retailers have to balance fraud reduction against speed at the curb. Not every order needs the same level of verification, and best practice is evolving toward risk-based controls rather than a single rigid workflow for all pickup transactions.

High-value items, high-risk geographies, account changes, or repeated "not received" claims usually justify stronger verification than routine low-risk pickups. By contrast, forcing the same heavy process on every order can push legitimate customers into abandonment or slow store operations enough to create new business losses. The practical challenge is deciding where stronger proof is worth the delay.

Mixed-channel commerce also creates edge cases such as proxy pickup, family collection, split orders, and substitutions, each of which can weaken a simplistic yes-or-no receipt model. Retailers need policies that say what counts as sufficient evidence for each of those cases and who can override them. When the evidence model is too narrow, the business can still lose disputes even when the customer actually collected the item.

Practitioners should expect fraud patterns to shift toward ambiguity, not obvious theft, because the channel itself makes completion harder to prove.

Risk and Threat Considerations

Fraud exposure rises when pickup and click-and-collect orders are defended with shipping-era controls, because the strongest abuse path is often not theft at the door but a claim that the handoff never occurred. That creates a control weakness in dispute resolution, evidence retention, and store-level verification, especially where multiple staff members can release the same order.

Failure mechanism: An attacker, or sometimes a dishonest customer, exploits weak handoff evidence by collecting an order under a looser process, then disputing receipt after the fact. If the retailer cannot prove who collected the item, when it left store custody, and what confirmation was captured, the dispute process defaults toward loss.

Impact: Chargebacks increase, fraud investigations become harder to close, and stores may absorb unrecovered losses even when the physical item did leave inventory. Over time, the retailer also loses confidence in channel-level reporting because order completion, handoff, and dispute outcomes no longer align.

Practitioner Guidance

What to prioritise: Treat pickup proof as a control requirement, not an operational convenience. The first priority is to make sure every order type has a defined evidence standard, because a control that cannot survive a dispute is incomplete for fraud purposes.

What to verify: Confirm that the store can produce a defensible record of pickup, including timestamp, collector confirmation, order status, and any exception or override. If those records are not retrievable quickly, the control is not yet ready for chargeback defense.

Decision rule: If an order can be handed over without a matching proof record, escalate it for tighter verification or redesign the pickup flow. Do not rely on post-incident recollection from staff when the transaction itself should have produced the evidence.

Practitioner takeaway: The real test is whether the retailer can prove fulfilment after the customer disputes it, because in mixed delivery models fraud control and evidence control are the same problem.

Related resources from NHI Mgmt Group

• How should retailers adapt fraud controls when AI-assisted search becomes a major purchase path?
• How should retailers prepare fraud controls for the holiday peak season without blocking too many good orders?
• How should retailers adapt fraud controls for a longer peak shopping event like Prime Day?
• What happens when retailers expand into direct-to-consumer without mature fraud controls?