E-commerce
July 1, 2026
"My postal code is only 8 km away, why is there no local delivery at checkout?" "The delivery driver was supposed to arrive between 6 PM and 8 PM, but nobody rang." "I have a delivery photo of a drop-off in front of a building that isn't mine." Three messages where a poorly framed local delivery website generates disputes, negative reviews, and chargebacks, whereas the radius, timeslot, and proof of delivery (POD) should have been visible right from the purchase stage.
The local delivery e-commerce customer support covers zone eligibility, same-day or next-day time windows, driver contact, photo/signature POD, unattended parcels left without instructions, and compensation, distinct from national carriers, general carrier slots, or in-store pickup.
This guide #429 covers policy LOCAL-SUP, flow LOCAL-FLOW, and local KPIs. The first content dedicated to hyperlocal delivery. Distinct from carrier slots (#427) and Click & Collect (#177): here is the customer service playbook for home delivery in local zones, private fleets, or local couriers.
Summary
Why do local delivery ticket prices increase after checkout?
A local delivery ticket relates to an order delivered from a warehouse, store, or dark store near the customer, promising a short lead time, time slot, or internal fleet, outside the standard Colissimo/Chronopost network.
Five typical customer pain points
Rejected zone: Zip code close by but outside checkout radius
Missed window: Courier outside promised same-day window
No-show courier: Slot passed, package not received
Disputed POD: Delivery photo at wrong address or blurry
Courier contact: Reaching courier en route, access instructions
Shopify allows local delivery via Settings > Shipping and delivery, delivery radius or zip codes, flat rate and slots (Shopify, local delivery 2026). Onfleet estimates that 44-58% of local last-mile delivery disputes concern missed time slots or insufficient POD when the customer did not receive live SMS tracking (Onfleet, last-mile 2026).
Angle #429 vs related content
Time slot #427: SLOT-FLOW carrier national scheduled. #429 = local fleet 5-25 km radius, same-day store delivery.
Express #338: cut-off vitesse national. #429 = hyperlocal neighborhood warehouse, not a remote hub.
Click & Collect #177: retrait magasin client. #429 = home delivery from the same local stock.
Perishables: chaîne froid SAV. #429 = cross-functional view of local delivery for all products + local fresh.
Local Bot #430: future pre-purchase zip code eligibility. #429 = agent CS playbook.
DTC Example
Fine grocery Paris + florist Lyon, 410 local orders/month. Without LOCAL-SUP: 52 local tickets/month, local_window_missed_rate 22%. After playbook: local_ticket_rate -47%, local_pod_dispute_rate -38%, local_csat 4.3/5.
Cost of local_driver_no_show
1 untreated P1 fresh no-show = full refund + stock loss + local customer churn. LOCAL-SUP ROI: same day redelivery + POD audit recovers 35-45% of contestable disputes.
Convert over 2,000 customers on average per month with Qstomy.
The world’s 1st Shopify AI dedicated to customer conversion
Empowering 200+ e-commerce merchants
How does local delivery differ from national delivery and pickup?
Hyperlocal home delivery, national carrier slot, and in-store pickup: three distinct logistic promises.
Promise matrix → dominant ticket
Local delivery #429: radius zone, same-day, courier, POD
Delivery slot #427: Colissimo carrier scheduled window
Express #338: tomorrow national hub, no precise hour choice
Click & Collect #177: customer travels, no courier
Four LOCAL-TYPE
local_same_day: order before noon cut-off, afternoon delivery
local_next_day: D+1 zone 10-20 km
local_fresh: grocery/meat, 2-hour window, cold chain mandatory
local_oversize: floral, workshop furniture, 2-person handoff
Local delivery stack
Shopify local delivery zones, Onfleet/Bringg/Stuart/Uber Direct apps, own bike/van fleet, WMS pick from store or micro-fulfillment. Support reads local_zone, local_window, driver_id, pod_photo_url, pod_signature.
Promise #429
LOCAL-SUP policy, LOCAL-MAP matrix, 12 local_* typologies, LOCAL-FLOW flow, LOCAL-* macros, local_* KPIs.
Own fleet vs API courier
Own fleet: driver direct contact with ops. Stuart/Uber Direct: API tracking + POD webhook. LOCAL-MAP local_fleet field for agent LL-4 lookup path.
Which local_* typologies should be mapped?
Twelve local delivery ticket typologies for consistent routing.
Twelve local scenarios
local_zone_not_eligible: nearby postal code but outside checkout radius
local_window_missed: delivery outside promised same-day window
local_driver_no_show: time slot passed, package missing
local_pod_missing: delivered status without photo or signature
local_pod_dispute: customer denies receipt, photo contested
local_address_wrong: driver wrong building, floor
local_modify_request: change time slot, access notes, phone
local_driver_contact: reach driver currently en route
local_fresh_violation: fresh product warm or outside cold window
local_left_unsafe: package left without compliant instructions
local_fee_dispute: contested local surcharge at checkout
local_chargeback: dispute threat POD or no-show
Helpdesk tags
local, local_missed, local_pod, local_redelivery, local_resolved, local_escalation. Distinct slot_, express_miss, cnc_pickup, wismo.
Prioritization
P1: local_driver_no_show today fresh, local_fresh_violation, local_chargeback. P2: local_pod_dispute, local_modify_request before dispatch. P3: local_zone_not_eligible FAQ, local_fee_dispute.
Local verbatim mining
90 days export "local delivery", "driver", "proof of delivery photo", "same day", "did not show up". Prioritize macros on top 3 actual store typologies.
Which LOCAL-MAP matrix should be documented?
The LOCAL-MAP local delivery matrix lists zones, schedules, fees, and POD.
LOCAL-MAP Columns
local_zone: radius km, postal code list, districts
local_type: same_day, next_day, fresh, oversize
cut_off: order cutoff time for same-day (e.g., 11:30 AM)
window_options: 12 PM - 2 PM, 6 PM - 8 PM, 2-hour slots
local_fee: flat rate €4.90, free > €50
local_fleet: own van, Stuart API, Uber Direct
pod_required: photo + signature, photo only, signature
safe_place_policy: allowed, prohibited, with checkout consent
missed_policy: same-day redelivery, refund fee, full fresh
Local_fresh Grocery Example
local_fresh_paris15: 8 km radius, 10 AM cutoff, 12 PM - 2 PM window Mon-Sat. Mandatory photo POD. Missed fresh → full refund + P1 priority redelivery.
Local_same_day Florist Example
local_same_day_lyon: postal codes 69001-69009, 2 PM cutoff, 5 PM - 8 PM delivery. Safe_place prohibited without presence. Missed → free redelivery next morning 1x.
Publication /pages/local-delivery
LOCAL-MAP FAQ: postal code zones, same-day cutoff, modifying driver instructions, what to do if missed, POD. Link to LOCAL-* macros.
Radius vs Postal Code list
Shopify local delivery supports km radius or explicit postal codes. Document both in LOCAL-MAP: "9 km" customer may be eligible for 10 km radius but excluded by postal code list edge case.
How to write the LOCAL-SUP policy in eight rules?
The LOCAL-SUP local delivery policy governs the zone, POD, redelivery, and compensation.
Eight LOCAL-SUP rules
Lookup local delivery first: order shipping method local, local_zone metafield before reply
POD before dispute close: retrieve pod_photo_url, signature, GPS timestamp LL-4
Window missed verified: driver app delivered_at vs local_window before compensation
Redelivery same day priority: local_driver_no_show today → ops redispatch if stock fresh
Fresh P1: local_fresh_violation → full refund or redelivery same day cold chain
No zone promise if ineligible: local_zone_not_eligible = explain radius, do not make up
Safe place uphold policy: local_left_unsafe only if checkout consent + POD shows safe_place
Driver contact via ops: local_driver_contact route dispatcher, no personal driver number to customer
Compensation matrix missed
Local fee refund if window missed confirmed. Fresh violation → full refund. Standard missed 1 h late → local fee refund + 10 € store credit manager gesture LTV > 150 €.
POD dispute resolution
Photo shows wrong building → redelivery + refund. Photo clear correct address client denies → uphold POD + carrier/driver ops review. Blurry POD → redelivery free 1x gesture.
Modify before dispatch
If not picked + before cut-off window: LOCAL-MODIFY-OK-01 access notes, phone, timeslot. If dispatched → LOCAL-MODIFY-DENY-01 driver contact ops only.
How to apply the LOCAL-FLOW flow in eight steps?
The LOCAL-FLOW framework structures local delivery ticket processing.
Eight steps LL-1 to LL-8
LL-1 Lookup order: shipping method local, local_window, fulfillment location
LL-2 Classifier local_*: typology section 3
LL-3 Match LOCAL-MAP: zone, type, cut_off, pod_required, missed_policy
LL-4 Verify delivery data: TMS driver status, pod_photo, GPS, delivered_at
LL-5 Expliquer: macro LOCAL-* grounded LL-4
LL-6 Décider: uphold POD | redelivery | refund fee | full refund fresh | ops callback
LL-7 Exécuter: redispatch TMS, Shopify partial/full refund, driver debrief
LL-8 Documenter: pod_reviewed, redelivery_id, compensation amount, driver_id
LL-4 local_pod_dispute
Pull pod_photo_url + GPS pin. Compare address geocode order vs POD metadata. Wrong pin → LL-6 redelivery + refund local fee. Match + clear photo → LL-6 uphold polite cite POD.
LL-4 local_driver_no_show
Window end passed + status not delivered → LL-6 redelivery same day P1 or refund if fresh expired. Supervisor callback 2 h SLA.
LL-6 local_driver_contact
If en_route status → ops dispatcher SMS driver relay instructions. Bot/agent never share driver personal mobile direct client per rule 8.
LL-4 local_zone_not_eligible
Verify CP vs LOCAL-MAP radius. If borderline 9.5 km radius 10 km → escalate ops exception 1x gesture documented. Else LOCAL-ZONE-01 explain + standard shipping offer.
Which LOCAL-* macros and touchpoints should be configured?
Eight local delivery agent macros and self-service touchpoints.
LOCAL-CONFIRM-01 (local delivery confirmed)
"Local delivery on [day] [window] to [address]. Same-day cut-off: [time]. Delivery driver instructions: [notes]. Live tracking: [tracking link]. Order #[X]."
LOCAL-MODIFY-OK-01 (instructions updated)
"Delivery driver notes updated: [digicode/intercom]. Contact phone: [phone]. Time slot unchanged [window]."
LOCAL-MODIFY-DENY-01 (modification impossible)
"Delivery driver already on the way / package picked. Contact us urgently: [phone ops]. Tracking reference: [link]."
LOCAL-MISSED-01 (missed window)
"We confirm delivery outside of window [window]. Local fee refund of [X] € within 5-10 days. New delivery [date window] scheduled #[redelivery_id]."
LOCAL-POD-01 (proof of delivery shared)
"Here is the delivery photo from [datetime] at [GPS address]. If this is not your home, reply within 24 hours for redelivery."
LOCAL-ZONE-01 (out of zone)
"Your postal code [code]: outside current local delivery radius ([radius] km / zones: [link]). Standard delivery [ETA] available."
Touchpoints
Checkout: zone map + cut-off visible before payment
Confirmation email: local_window + tracking link above the fold
In-transit SMS: live tracking link + 15 min ETA
/pages/local-delivery FAQ LOCAL-MAP
Post-delivery: auto email POD photo if delivered
LOCAL-FRESH-P1 (local fresh violation)
"Fresh product delivered outside window or lukewarm: full refund initiated. Do not consume. Priority shipping if stock and window available."
Which Fresh, POD dispute, and driver en route cases should be processed?
Special local cases require LOCAL-MAP extensions and separate SLAs.
Fresh products local_fresh
local_fresh_violation: cooler bag + 2 hr max window. Lukewarm or missed → refund full P1. Link perishables.
POD dispute wrong building
GPS pin 200 m off order address → driver error confirmed. Redelivery + refund + driver debrief LL-8. Not friendly fraud if POD metadata clear.
Safe place local_left_unsafe
Checkout checkbox safe_place consent required. No consent + left doorstep → free redelivery. Link damaged package if rain damage.
Address + zone conflict #183
Address change may exit local_zone. Re-check LOCAL-MAP new postcode or switch to standard shipping. Link address change (#183).
Click & Collect fallback #177
local_zone_not_eligible borderline: offer Click & Collect same store if stock. Link Click & Collect (#177).
National slot vs local same-day
Customer confuses carrier SLOT #427 and local same-day: route separate macros. Local = neighborhood fleet. Slot = Colissimo scheduled window.
Partial refund gesture #368
Minor delay 30 min inside window: PART-REF store credit vs full missed path. Link partial refund (#368).
Which local KPIs should be measured?
The local delivery support KPIs drive window SLA and POD quality.
Eight key metrics
local_ticket_rate: local tickets / local orders
local_window_missed_rate: window missed confirmed / local orders
local_on_time_rate: delivered within window / local orders
local_pod_dispute_rate: pod disputes / local delivered
local_redelivery_rate: redeliveries / local no-show missed
local_fresh_incident_rate: fresh violations / local_fresh orders
local_fee_refund_rate: fee refunds / local_window_missed
local_csat: satisfaction tag local resolved
DTC Benchmark
local_window_missed_rate < 10 % post LOCAL-SUP, on_time > 88 %, pod_dispute < 4 %, local_csat > 4.1/5.
Weekly Dashboard
LOCAL-TYPE breakdown, zone district highest missed, driver performance scorecard, POD quality blur rate.
Ops alert
local_window_missed_rate > 18 % zone X week: audit cut-off capacity + fleet dispatch TMS.
POD quality ops KPI
Track pod_photo readable rate / deliveries. Driver coaching if blur > 12 % fleet.
Which anti-patterns should be avoided in local delivery?
Ten local delivery support anti-patterns to ban.
1. Closing disputes without a POD lookup
LL-4 mandatory. local_pod_dispute without photo = process failure.
2. Giving out driver's personal number
Rule 8 ops dispatcher relay. Privacy + safety.
3. Confusing slot #427
Colissimo slot ≠ local same-day fleet. Use distinct router macros.
4. Safe place without checkout consent
Rule 7 uphold. local_left_unsafe redelivery if no checkbox.
5. Treating missed fresh deliveries as standard
Rule 5 P1 full refund. Not local fee only.
6. Promised zone outside of LOCAL-MAP
Rule 6 LOCAL-ZONE-01 honest. No "we will make an exception" without ops doc.
7. No on-the-way tracking SMS
local_driver_no_show preventable. SMS ETA 15 min reduces no-show by 25% historically.
8. Upholding disputes with blurry PODs
Blurry photo → redelivery gesture. Clear wrong address → driver error.
9. Conflating Click & Collect #177
Store pickup ≠ home delivery driver. Customer "I am coming to collect" → #177 not #429.
10. Missing /pages/local-delivery
Self-service zone gap. FAQ LOCAL-MAP public checkout trust.
11. Address change without zone re-check
#183 sync mandatory. New postal code may exit local_zone mid-order.
12. Wismo only without citing local_window
"Where is my package?" local today → LOCAL-CONFIRM-01 + live tracking, not generic WISMO.
How does Qstomy help with local delivery?
Qstomy on Shopify: LOCAL-FLOW order lookup, LOCAL-MAP zone window explain, LOCAL-CONFIRM-01 resend, POD link share, missed policy cite, handoff redelivery ops pre-filled fields.
Qstomy local capabilities
local_order_lookup: LL-1 local_window type zone
local_map_explain: cut_off, fee, pod_required
local_status_read: LL-4 driver POD GPS
local_confirm_template: LOCAL-CONFIRM-01 auto
local_pod_share: LOCAL-POD-01 link
local_handoff_redelivery: LL-7 fields ops P1
Pipeline #429 → #430
#429 CS agents POD redelivery. #430 future bot local eligibility pre-purchase postal code. Shared LOCAL-MAP.
Quantified DTC Scenario
410 local orders/month, 52 baseline tickets.
After LOCAL-SUP + Qstomy: local_ticket_rate -45%, local_on_time 90%, local_pod_dispute_rate 3.2%, local_csat 4.4/5.
Explore customer support and request a demo.
Bot preview #430
Intents local_zone, local_cutoff feed future bot eligibility. LOCAL-SUP human prerequisite POD disputes.
What is the checklist for deploying LOCAL-SUP?
LOCAL-SUP Checklist (12 steps)
Inventory LOCAL-TYPE and active Shopify radius/ZIP code zones
Document LOCAL-MAP cut_off, windows, fees, pod, missed per type
Draft policy LOCAL-SUP 8 rules
Publish /pages/local-delivery FAQ + checkout zone map visible
Confirmation email local_window + SMS on-the-way tracking
TMS POD photo GPS webhook configured Onfleet/Stuart
Create LOCAL-* helpdesk macros
Train agents LOCAL-FLOW 45 min (LL-4 POD review, fresh P1)
Process redispatch same day + driver debrief LL-8
Sync #183 address change → local_zone re-check workflow
Tags local_* + dashboard KPI section 9
Sync LOCAL-MAP → bot #430 future corpus
Summary
#429 = hyperlocal local delivery, not slot #427 nor C&C #177
LOCAL-MAP: zone → cut-off → window → POD → missed
LOCAL-FLOW: lookup → POD verify → redelivery/compensate
POD before close dispute: photo GPS signature LL-4
KPI local_window_missed_rate: target < 10%
FAQ
Difference from slot #427?
#427 national carrier Colissimo window. #429 same-day local fleet within store radius.
Difference from Click & Collect #177?
#177 customer picks up in store. #429 driver delivers to doorstep in nearby zone.
Parcel not received but drop-off photo exists?
LOCAL-POD-01 share GPS photo. Wrong address → redelivery. Clear correct → uphold review.
Modify driver instructions?
LOCAL-MODIFY-OK-01 if not picked. LOCAL-MODIFY-DENY-01 if on the way, ops relay.
My ZIP code is outside the local zone?
LOCAL-ZONE-01 explain radius + standard shipping. Exception ops documented 1x borderline gesture.
Go further
This week: publish LOCAL-MAP /pages/local-delivery, configure POD webhook TMS, create macros LOCAL-CONFIRM-01 and LOCAL-POD-01, train agents LL-4 POD verify + fresh P1 queue.
Share this guide #429 with ops and support: a clear zone at checkout is worth a customer ordering locally, a blurry POD is worth a neighborhood dispute that costs ten times the average cart value.
Enzo
July 1, 2026
