E-commerce
July 1, 2026
"I received the 'ready for pickup' email, but at the counter they told me my order is not on the list." "Where exactly should I go, to the back of the store or the checkout?" "Can my husband pick it up without me if I have the confirmation on my phone?" Three typical messages when a shop offers online pickup without a dedicated BOPIS app, using a paper list, manual email, and a minimal counter process.
In-store pickup customer support without an app covers ready-for-pickup communication, counter location, ID verification, authorized third parties, holding periods, and counter disputes, distinct from automated Shopify Click & Collect or local delivery.
This guide #431 covers policy INSPU-SUP, flow INSPU-FLOW, and KPI inspu. It complements Click & Collect (#177) with a focus on manual/simple pickup, staff communication, and playbooks without Zapiet or pick-pack apps.
Summary
Why does manual withdrawal generate support tickets?
A manual in-store pickup ticket arises when the customer has ordered online but the store operates with an Excel list, a hand-typed "ready" email, or a counter logbook without real-time Shopify POS sync.
Five typical customer pain points
Ready vs. not ready: email received, package missing from the counter
Counter not found: customer does not know where to go
Third party refused: spouse blocked without a clear policy
Out-of-sync list: order fulfilled on the web, but not on the store list
Retention period: order cancelled at day 7 without reminder
Shopify pickup in store can work without a third-party app if locations, manual fulfillment, and basic email notifications are configured (Shopify, pickup in store 2026). Forrester recalls that 29% of BOPIS users abandoned a pickup order due to lack of clear communication (Forrester, abandon BOPIS). Without an app, the communication gap increases if the INSPU-SUP process is absent.
Angle #431 vs. related content
Click & Collect #177: BOPIS stock sync apps, BOPIS disputes. #431 = minimal pickup without Zapiet, manual list, simple counter.
Availability #271: cross-channel pre-purchase inventory. #431 = post-pickup order, not PDP inventory lookup.
Local delivery #429: home delivery local fleet. #431 = customer travels to the store.
Pickup bot #432: future AI automation for hours and stock. #431 = customer service playbook for agents + sales associates.
Gift order #205: third-party recipient. #431 = ID policy and email receipt at the counter.
DTC Example
Fashion brand, 3 stores, pickup without app, 180 inspu orders/month. Without INSPU-SUP: 28 tickets/month inspu, inspu_not_ready_rate 31%. After playbook: inspu_ticket_rate -49%, inspu_fcr 76%, inspu_csat 4.2/5.
Cost of counter inspu_not_ready
Customer in front of store window + missing order = immediate Google review + refund walk-away. INSPU-SUP ROI: daily sync list + INSPU-STATUS macro reduces manager escalation by 40%.
Shopify BOPIS without third-party app
Shopify notes that 67% of BOPIS customers make additional purchases upon pickup (Shopify, BOPIS 2026). The manual INSPU-SUP process preserves this opportunity if counter communication is clear.
How does manual pickup differ from automated BOPIS #177?
Minimal counter pickup, BOPIS app sync, and local delivery: three distinct support journeys.
Setup matrix → dominant ticket
In-store manual #431: paper list, manual ready email, counter order #
BOPIS #177: Zapiet app, auto SMS, POS scan picked up
Ship to store: warehouse package to store, transfer time
Showroom order: in-store fitting + web order same day
Four INSPU-TYPES
inspu_counter: main checkout counter pickup
inspu_backroom: back store storage, staff appointment
inspu_popup: temporary pop-up, limited hours
inspu_event: trunk show event pickup, name list
Pickup stack without app
Shopify admin fulfill + ready_pickup tag, Google Sheet store list export 2x/day, Klaviyo email template INSPU-READY, support QR counter poster, manual POS mark picked up.
Promise #431
INSPU-SUP policy, INSPU-MAP matrix, 12 inspu_* typologies, INSPU-FLOW flow, INSPU-* macros, inspu_* KPIs.
When to stay without an app
< 50 pickups/month/store, 1-3 locations, team trained on INSPU-FLOW. Beyond this: evaluate app #177 or bot #432, do not skip INSPU-SUP prerequisite.
Which types of inspu_* should be mapped?
Twelve manual in-store pickup ticket typologies for consistent routing.
Twelve inspu scenarios
inspu_not_ready: email ready but package not at the counter
inspu_where_pickup: counter location, floor, PMR accessibility
inspu_hours: pickup hours, exceptional closure
inspu_id_required: ID, email, order # to bring
inspu_third_party: spouse, friend, courier picking up on my behalf
inspu_order_not_found: store cannot find order on the list
inspu_wrong_item: wrong size, reference, missing item
inspu_change_store: change pickup store post-order
inspu_hold_expired: holding period exceeded, cancellation
inspu_manual_list_lag: store list not up to date vs Shopify
inspu_ready_premature: ready email sent by mistake before picking
inspu_chargeback: pickup dispute, customer left without package
Helpdesk tags
inspu, inspu_ready, inspu_comptoir, inspu_litige, inspu_resolved, inspu_escalation. Distinct bopis_, cnc_, local_.
Prioritization
P1: inspu_order_not_found customer on-site, inspu_chargeback. P2: inspu_not_ready, inspu_wrong_item. P3: inspu_hours, inspu_id_required FAQ.
Mining inspu verbatims
90-day export "pickup", "store", "not ready", "counter", "shop". Prioritize macros on top 3 actual typologies per location.
Which INSPU-MAP matrix should be documented per store?
The INSPU-MAP pickup matrix lists counter, hours, deadlines, and policies per location.
INSPU-MAP Columns
location_id: Shopify location name, address
inspu_type: counter, backroom, popup, event
pickup_point: "Checkout 2 back left", PDF map
prep_time: 4 business hours, D+1 if warehouse transfer
hold_days: 7 calendar days before cancellation
id_policy: confirmation email OR ID matching order name
third_party: allowed with email forward, strictly prohibited under own name
contact_comptoir: store phone, not central support only
Example: Lyon counter boutique
location_lyon: inspu_counter, checkout counter 2, prep 4 hrs Mon-Sat, hold 7 days, third_party allowed email PDF, PRM elevator access at the back of the store.
Example: Paris pop-up event
location_popup_marais: inspu_event, pickup at entrance booth, prep D-0 event only, hold 2 days weekend event, id_policy ID + # order mandatory.
Publication /pages/store-pickup
INSPU-MAP FAQ by city: where to collect, what to bring, prep time, storage, authorized third party. Link to INSPU-* macros.
A4 Counter Poster
QR /pages/store-pickup + support phone + "present order # and email". Reduces inspu_where_pickup tickets by 30%.
How to write the INSPU-SUP policy in eight rules?
The INSPU-SUP manual pickup policy governs ready e-mail, counter, and disputes.
Eight INSPU-SUP rules
Lookup Shopify first : fulfillment status, location, tags ready_pickup before reply
Ready e-mail only after pick : INSPU-READY sent when stock physically staged counter
Cross-check manual list : inspu_manual_list_lag → ops sync Sheet same day
Third party per INSPU-MAP : cite id_policy, no arbitrary counter refusal
On-site customer P1 : inspu_order_not_found → manager callback 15 min SLA
Hold expired uphold : inspu_hold_expired refund or extend 1x goodwill gesture documented
Wrong item immediate fix : exchange shelf or refund line, internal quality ticket
No circular referral : salesperson creates ticket with customer, not "call the website"
Ready e-mail governance
inspu_ready_premature : root cause pick before email SOP. Rule 2 checklist 3 points : staged zone, order # label, Shopify fulfill ready.
Manual list sync
Export Shopify unfulfilled pickup location 8 AM + 2 PM → store Google Sheet. Salesperson checks off picked. Lag > 4 h → inspu_manual_list_lag alert ops.
Retention hold D+7
Reminder sequence D+3 D+6 e-mail. D+7 auto cancellation refund if INSPU-MAP hold_days 7. Extend 1x if customer contacts on D+6 P2.
Salesperson Slack template
Store channel #pickup-[city] : order #, staged yes/no, salesperson initials. Support reads thread before INSPU-STATUS reply. Reduce inspu_manual_list_lag confusion.
How to apply the INSPU-FLOW process in eight steps?
The INSPU-FLOW framework structures the manual boutique pickup ticket processing.
Eight steps IL-1 to IL-8
IL-1 Lookup order: order #, pickup location, fulfillment status
IL-2 Classifier inspu_*: section 3 typology
IL-3 Match INSPU-MAP: pickup_point, prep, hold, id_policy, third_party
IL-4 Verify status: Shopify tags, Sheet list, staging photo ops optional
IL-5 Explain: macro INSPU-* grounded IL-4
IL-6 Decide: uphold wait | expedite pick | change store | refund | extend hold
IL-7 Execute: notify Slack store, resend INSPU-READY, Shopify refund, transfer location
IL-8 Document: list_sync_flag, manager_callback, compensation amount
IL-4 inspu_not_ready
If Shopify unfulfilled but INSPU-READY sent → inspu_ready_premature apology + expedite pick IL-7 2 h SLA. If fulfilled ready but counter empty → inspu_manual_list_lag ops + on-site manager 15 min.
IL-6 inspu_third_party
If INSPU-MAP third_party allowed → INSPU-THIRD-01 cite e-mail forward rule. If forbidden → uphold polite suggest buyer present or change to ship home #183.
IL-6 inspu_change_store
Before pick: verify stock new location, transfer fulfillment location Shopify. After pick: deny except manager exception documented.
IL-4 client on site P1
inspu_order_not_found + client_on_site=yes → immediate manager phone + IL-7 expedite pick priority queue.
Which INSPU-* macros and store communication should be configured?
Eight store pickup agent macros and seller communication templates.
INSPU-STATUS-01 (pickup status)
« Order #[X] | Store [City] | Status: [In preparation / Ready]. Counter: [pickup_point]. Hours today: [hours]. Bring [id_policy]. Estimate if not ready: [time]. »
INSPU-READY-01 (ready for pickup email)
« Your order #[X] is ready at [pickup_point], [address]. Hours: [hours]. Bring confirmation email or ID [name]. Kept for [hold_days] days. Map: [link]. »
INSPU-WHERE-01 (where to pick up)
« Pick up at [pickup_point]: [access instructions]. Map: [link map]. Parking: [info]. PRM: [access_notes]. »
INSPU-THIRD-01 (authorized third party)
« Yes, [First Name] can pick up with forwarded PDF confirmation email or ID under the name [Order Name] according to INSPU-MAP. »
INSPU-DELAY-01 (preparation delay)
« Order #[X] is not ready yet. New estimate [date/time]. We will send you INSPU-READY as soon as it is staged at the counter. Sorry for the wait. »
INSPU-HOLD-01 (holding reminder)
« Reminder: order #[X] awaiting pickup until [date D+7]. After this period, automatic cancellation. Pick up at [pickup_point] or contact us at extension 1x. »
Touchpoints without app
Order confirmation: prep_time + pickup_point visible
INSPU-READY email Klaviyo manual trigger or Shopify flow
Counter poster QR + order #
/pages/store-pickup FAQ INSPU-MAP
Store list sheet sync 2x/day Slack reminder
INSPU-LITIGE-01 (counter dispute)
« Case #[ticket] opened. Immediate solution: [exchange/refund]. Counter reference: [X]. Manager will contact you within 2 hours if needed. »
Which third-party, gift, and deferred list cases should be processed?
Special inspu cases require separate INSPU-MAP extensions and SLAs.
Gift order #205
Buyer vs recipient pickup: INSPU-MAP third_party + gift message. Recipient needs e-mail forward or buyer auth phone support. Link gift order (#205).
Sheet lag list inspu_manual_list_lag
Shopify shows ready, Sheet missing: ops add row + call store within 30 min. Root cause: missed 2 p.m. export. Prevent with automated Shopify → Sheet Zap hourly peak.
Store change inspu_change_store
Before pick: IL-7 transfer location if stock OK. Link order modifications.
Ship to store delay
Warehouse to store parcel: prep_time D+1-D+2 in INSPU-MAP. INSPU-DELAY-01 not INSPU-READY until parcel scanned at store.
Pop-up event inspu_event
Trunk show nominal list: inspu_order_not_found check event roster Excel separate Sheet. Temp staff trained INSPU-WHERE-01 15 min briefing.
Click & Collect upgrade path #177
If volume > 80 inspu/month/store: evaluate migration to BOPIS app. INSPU-SUP macros remain the handoff base. Link Click & Collect (#177).
Partial wrong item #368
inspu_wrong_item partial refund or immediate exchange in-store. Link partial refund (#368).
PMR access pickup_point
INSPU-MAP access_notes PMR elevator ramp. INSPU-WHERE-01 proactive reduce inspu_where_pickup store calls.
Which KPIs should be measured?
The manual in-store pickup support KPIs drive ready accuracy and counter FCR.
Eight key metrics
inspu_ticket_rate: inspu tickets / inspu orders
inspu_not_ready_rate: not_ready confirmed / inspu orders
inspu_ready_premature_rate: ready email before staged / ready emails
inspu_fcr: resolved first contact / inspu tickets
inspu_sur_place_sla: order_not_found on site < 15 min / P1
inspu_list_lag_rate: manual list lag tickets / inspu orders
inspu_no_show_rate: hold expired annul / inspu orders
inspu_csat: satisfaction tag inspu resolved
DTC Benchmark
inspu_not_ready_rate < 12 % post INSPU-SUP, inspu_fcr > 72 %, sur_place_sla > 92 %, no_show < 8 %.
Dashboard by location
INSPU-TYPE breakdown, top typologies, list sync misses, manager callbacks count.
Ops alert
inspu_manual_list_lag > 5 tickets/week location X: audit Sheet export + 30 min seller training.
Order-to-ready ops KPI
Track order placed → INSPU-READY sent vs INSPU-MAP prep_time promise. Correlate with inspu_not_ready_rate.
Which anti-patterns should be avoided during a manual withdrawal?
Ten in-store pickup support anti-patterns to ban.
1. INSPU-READY before physical staging
Rule 2 checklist 3 points. Premature ready = top inspu_not_ready cause.
2. Circular referral counter ↔ web
Rule 8 clerk creates ticket. Customer on-site not blocked.
3. Third party arbitrary refuse
INSPU-MAP third_party policy quote. No ad-hoc clerk decision.
4. Sheet list stale > 24 h
Sync 2x/day minimum. inspu_manual_list_lag alert.
5. On-site P2 queue
Rule 5 P1 15 min manager. Customer in front of showcase is urgent.
6. Confusing BOPIS #177
Auto SMS app ≠ manual INSPU-READY process. Route distinct macros.
7. No /pages/store-pickup
Self-service where/id gap. Public FAQ INSPU-MAP.
8. Hold expired without callback D+3 D+6
INSPU-HOLD sequence mandatory. Cancellation surprise = chargeback.
9. Wrong item no immediate fix
Rule 7 counter exchange/refund. No "come back tomorrow" default.
10. Pickup point vague "in store"
INSPU-MAP pickup_point precise. PDF map linked INSPU-WHERE-01.
11. Gift pickup without auth recipient
#205 flow: buyer auth or e-mail forward before releasing parcel.
12. POS picked up not marked
Clerk hands over parcel without scanning → double pickup fraud risk. 5 min POS training.
How does Qstomy help with manual in-store pickup?
Qstomy on Shopify: INSPU-FLOW order lookup, INSPU-MAP pickup_point hours cite, INSPU-STATUS-01 auto, third_party policy explain, on-site handoff P1 manager pre-filled fields.
Qstomy inspu capabilities
inspu_order_lookup: IL-1 location fulfillment status
inspu_map_explain: pickup_point, id_policy, hold_days
inspu_status_template: INSPU-STATUS-01 auto
inspu_third_policy: INSPU-THIRD-01 cite
inspu_handoff_sur_place: P1 manager queue fields
inspu_route_bopis: app BOPIS #177 if detected setup
Pipeline #431 → #432
#431 SAV agents counter disputes. #432 future bot pickup hours stock. Shared INSPU-MAP.
Encrypted DTC Scenario
Mode 3 shops 180 inspu/month, 28 baseline tickets.
After INSPU-SUP + Qstomy: inspu_ticket_rate -47%, inspu_fcr 78%, inspu_sur_place_sla 94%, inspu_csat 4.3/5.
Explore customer support and request a demo.
Bot preview #432
Intents inspu_hours, inspu_status feed future pickup bot. INSPU-SUP human prerequisite counter disputes.
What is the checklist for deploying INSPU-SUP?
INSPU-SUP Checklist (12 steps)
Inventory INSPU-TYPE and active Shopify pickup locations
Document INSPU-MAP pickup_point, prep, hold, id per location
Draft INSPU-SUP policy 8 rules + ready email checklist
Publish /pages/store-pickup FAQ + counter QR poster
Template Klaviyo INSPU-READY-01 + INSPU-HOLD reminders D+3 D+6
Google Sheet store list sync 8 am + 2 pm + Slack reminder
Create INSPU-* helpdesk macros
Train sales staff 45 min on INSPU-FLOW + POS mark picked up
Counter-support RACI: no circular referral
Tags inspu_* + dashboard KPI section 9 per location
P1 on-site manager phone displayed at the counter
Sync INSPU-MAP → bot #432 future corpus
In brief
#431 = manual pickup without app, completes BOPIS #177
INSPU-MAP: counter → prep → hold → id → third party
INSPU-FLOW: lookup → verify list → status/dispute
Ready email after staging: not before physical pick
KPI inspu_not_ready_rate: target < 12%
FAQ
Difference with Click & Collect #177?
#177 BOPIS apps sync SMS auto. #431 minimal pickup, manual list, counter email.
What to bring for pickup?
INSPU-MAP id_policy: confirmation email OR ID with order name. INSPU-THIRD-01 if third party.
Email says ready but not at the counter?
inspu_not_ready or inspu_ready_premature: IL-4 verify, expedite pick 2 hrs or inspu_manual_list_lag sync.
Change pickup store?
Before pick: inspu_change_store if stock OK. After pick: deny except manager exception.
Order not picked up D+7?
inspu_hold_expired: auto-cancel refund per INSPU-MAP. 1x extension if contacted D+6.
Take it further
This week: publish INSPU-MAP /pages/store-pickup, deploy Sheet sync 2x/day, create INSPU-STATUS-01 and INSPU-READY-01 macros, train sales staff on the 3-point ready checklist.
Share this guide #431 with stores and support: an identified counter on the help page is worth a customer leaving with their bag; a premature ready email is worth an unhappy line in front of the storefront.
Switch to a BOPIS app later?
Volume > 80/month/store: migrate to #177. INSPU-MAP remains the base for counter policies.
Enzo
July 1, 2026
