E-commerce
June 28, 2026
"It says in stock on Google but out of stock on your site." "My size M sold out while I was paying." "When is the product coming back?" Out of stock questions generate frustration, negative reviews, and chargebacks when poorly handled.
Opensend estimates that 69% of online shoppers abandon if the item is unavailable, and that stockouts represent about 20% of cart abandonments (Opensend, stockout statistics 2026).
This guide #106 covers out-of-stock customer support: responding, compensating, alternatives, and realistic lead times. Distinct from back-in-stock alerts (#48): this is about the daily support workflow, not just alert conversion.
Summary
Why do disruptions generate so many support tickets?
Out-of-stock product inquiries in e-commerce affect pre-purchase conversion and post-order satisfaction with a high emotional toll.
Measurable customer support impact
Volume: 5-15% of tickets depending on fashion and tech verticals.
Frustration: the customer has invested time and purchase intent.
Negative reviews: "fake stock advertising" is common on marketplaces.
Chargebacks: canceled order poorly explained post-payment.
Opportunity: a well-proposed alternative = a saved sale.
Five touchpoints
Pre-purchase PDP (available? when is it back?), checkout (variant disappears), post-order (cancellation email), waiting for restock (date? alert?), peak demand (BFCM, drop, influencer). AlixPartners via Omnisend: 66% of customers buy from a competitor if a product is unavailable (Omnisend, back-in-stock 2026). A dry "out of stock, goodbye" template = a lost customer. A structured response with an alternative + alert recovers a significant share of sales.
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
Which disruption scenarios should be treated differently?
Adapting the out of stock support to the type of situation avoids unsuited generic responses.
Eight distinct scenarios
Total SKU stockout: zero units remaining, all variants.
Variant stockout: size M out, L available.
Post-order stockout: sold but inventory sync error.
Temporary stockout: restocking in 7-14 days known.
Definitive stockout: end of line, discontinued.
Supplier stockout: dropship supplier OOS.
Flash overselling: BFCM, limited drop, influencer story.
Displayed vs. actual stock: marketplace lag or Google Shopping.
Ticket prioritization
Paid post-order > pre-purchase VIP customer > curiosity question. Tag Gorgias `stockout_urgent` if the order is affected. Pre-order never launched vs. sold out: separate support messages. Partial order: ship available items + refund OOS item or hold full order depending on policy.
See prioritize tickets (#26), dropshipping (#96), order modification.
Which customer questions should be prepared in advance?
Mapping customer out-of-stock questions feeds macros, bot, and help center.
Pre-purchase (top 6)
When will the product be back in stock?
Can I be notified when it is available?
Do you have a similar alternative?
Why was it marked as in stock yesterday?
Can I pre-order?
Will size X be back?
Post-order (top 6)
My order is cancelled, why?
Refund or wait for restocking?
Can I receive a different product?
Refund processing time after stock cancellation?
Is a promotional compensation code possible?
Partial order: when will the rest ship?
Draft a canned response sheet per cluster in the knowledge base (#102). Urgent OOS gift: alternative + gift wrap. B2B MOQ: contact account manager. See pre-purchase questions, B2B support.
How to communicate out-of-stock status on the PDP and checkout?
OOS (out-of-stock) communication on the PDP reduces upstream tickets if it is honest and actionable.
Product detail page best practices
Real-time inventory: Shopify inventory sync, no 24-hour delay.
Clear badge: "Temporarily Out of Stock" or "Back Soon", no active Buy button.
Restock date: if known "Estimated back March 15", otherwise alert only.
Alert button: "Notify me when back" near the variant selector.
Visible alternatives: "You may also like" section on the OOS page.
OutOfStock Schema: Google Shopping accurate, pause OOS SKU feed.
Checkout and transparency
OOS variant at checkout: clear message, suggest another size/color, no cryptic error. Process page "How do we handle stockouts": refund, alert, lead times. "Cart reserved for 15 min": customer understands why OOS if they return later. EcomHint: keep URL live (200) during temporary stockouts, no SEO-destructive redirect.
See back-in-stock alerts (#48), contextual recommendations, help page.
How do you manage a stockout after an order has been paid for?
The cancelled stock order support requires responsiveness, empathy, and clear options.
Urgent post-OOS workflow
Proactive email within 24 hours: stockout + options, do not wait for a customer ticket.
Option A: full refund (5-10 business days bank processing).
Option B: product alternative of equal value or explained upgrade.
Option C: wait for restocking, documented Date X.
Option D: store credit +10% goodwill gesture if it is the brand's mistake.
Customer reply window of 48 hours before auto-action according to policy.
Communication and SLA
Sincere apology + brief explanation (overselling, sync issues) without blaming the customer. Tag `stockout_post_order`: FRT 2 hours, resolution 24 hours (SLA support (#101)). Proactive email before chargeback. Gift order: contact buyer and recipient if email is known.
See store credit vs refund, loyalty complaints (#94), chargebacks.
How to offer alternatives that save the sale?
Well-proposed out-of-stock alternatives convert frustration into an immediate or deferred purchase.
Valid alternative criteria
Same use case: equivalent function, no off-topic products.
Similar price: ±15% or explained benefit upgrade.
Confirmed stock: verify availability before suggesting.
Chat visual: PDP link + inline photo.
Browse history: personalize if Shopify data is available.
Typical agent script
"Model X is out of stock until [date or email alert]. In the meantime, [Y] offers [similar benefit] and is available. Would you like the link?" 10% alternative code: manager approval required if margins are tight.
Internal sheet per hero SKU: 2 merchandising-validated alternatives + 1-line pitch. Tag ticket `alternative_converted` to measure effectiveness. Baymard recommends strong cross-selling on unavailable product pages, especially discontinued products (EcomHint, out of stock 2026). See bundle choice (#97), comparison page.
How to manage restocking, alerts, and pre-orders on the support side?
Customer restock questions demand transparency: never invent a date.
Restock date rules
Known date: PDP window + support + bot metafield.
Unknown date: "We will alert you by email", not "soon".
Restock delay: proactive email update to waitlist.
Restock cancellation: notify + alternative + refund waitlist.
Alerts and pre-orders
Sign up customer for specific variant alert, not overall product: conversion +40% vs global product alert (US Tech Automations). Notification within 15 min post-restock: ~25% conversion; 4 h delay reduces conversion by ~60%. 48% of buyers accept back-in-stock alert opt-in (Opensend). Pre-order: clear shipping window, cancellation possible, no charge before shipment.
STOQ, Klaviyo, Shopify apps: 1-click capture PDP or bot. Explicit GDPR opt-in. See alerts (#48), pre-order communication.
What bot scripts and intents for breakup/cancellation?
Standardizing the out-of-stock support scripts aligns the human and bot teams.
Recommended Gorgias Macros
STOCK-001 pre-purchase OOS: date or alert + alternative.
STOCK-002 post-order cancel: apology + 4 options.
STOCK-003 restock: timeframe + alert signup.
STOCK-004 variant OOS: other size/color available.
STOCK-005 end of line: alternative, no return date.
STOCK-006 compensation: goodwill code if brand error.
Tier 0-1 bot intents
product_out_of_stock (status + alert + alternative), variant_unavailable (suggest variants), order_cancelled_stock (refund/substitute/wait options), restock_when (date or alert flow), alternative_product (2 SKUs). Bot uncertain about restock date: handoff to human, never a made-up date. Escalation: order > €200 OOS post-order → senior agent + pre-approved 15% gesture.
See support templates, answers database (#102), tagging, VIP escalation.
How to handle out-of-stock situations in dropshipping, marketplaces, and during peak periods?
External stockouts require a specific process and pre-loaded macros.
Dropshipping and marketplace
Post-order OOS supplier: cancellation + fast refund or alternative supplier SKU. Amazon/Etsy sync lag: honor or cancel + compensation based on channel policy. How about Instagram "out of stock?": public response + DM alert link.
BFCM, drops and influencer
Anticipate stockout help center, pre-loaded STOCK macros, bot intents, email template cancel stock. Site banner post-story stockout + proactive alternative bot. Flash terms: no rain check communicated on PDP reduces tickets. BFCM post-mortem: top SKU OOS, recommended qty N+1, CSAT stockout tickets.
Ops loop: support feedback → merchandising reorder or discontinue. See BFCM preparation, centralize marketplace, subscription support.
How to prevent tickets via stock sync and coordination?
Reduce preventive out-of-stock tickets through ops and support-merchandising coordination.
Inventory sync
Shopify POS + online: unified real-time inventory.
Dropship apps: hourly minimum sync.
Marketplace feeds: auto-pause OOS SKUs.
Cart hold: stock reservation for 10-15 min at checkout.
Internal low stock alerts: ops before zero customers.
Weekly coordination
15 min support-ops: top 3 out-of-stock SKU tickets, confirmed PO dates. Monthly meeting: top 10 SKUs → reorder or discontinue. Discontinued SKUs: update PDP + bot corpus (#103) on the same day. KPI: stockout tickets / orders, alternative conversion offered, stockout CSAT.
See Shopify integration, clean bot corpus (#103), conversation insights.
How does Qstomy handle out-of-stock questions?
Qstomy automates out-of-stock chatbot responses: real-time status, restock, alternatives, alerts, connected to Shopify.
Key capabilities
Stock lookup variant: Shopify real-time availability.
Metafield restock date: displays if configured, otherwise shows alert.
Back-in-stock signup: captures email inline in chat → Klaviyo.
Alternative recommend: 2 products from the same collection.
Order cancel flow: post-order OOS options.
Proactive PDP OOS: visitor trigger for unavailable variant.
DTC Business Case
Fashion brand with 140 orders/day, 11% out-of-stock tickets, stockout CSAT 3.4, 22% alternatives manually accepted.
Deployment of Qstomy OOS intents + alternatives + Klaviyo sync alert. 9-week results: out-of-stock tickets −34%, bot alternatives accepted 41%, alert signup +28% vs PDP button alone, stockout CSAT 3.4 → 4.1, post-order cancel resolution time −52%. Emotional handoff with context + pre-loaded alternatives.
Explore AI support, reducing tickets with AI, bot-to-human handoff, or request a demo.
Which operational playbooks should be launched this week?
Playbook 1: top 5 out-of-stock SKUs + macro
Export Gorgias `stockout` tags for 90 days. List the top 5 SKUs. For each: 2 merchandising-approved alternatives + macro STOCK-001 or 004.
Playbook 2: post-order cancel test
Simulate an order of a hero SKU that is OOS post-pay (staging or test order). Time the proactive email, clear options, and ticket FRT. Goal: 24-hour resolution.
Playbook 3: PDP audit 10 hero SKUs
Force OOS variant in staging: badge visible? Variant alert button? Alternatives showing? Google feed paused?
Playbook 4: bot intents OOS
Test 10 questions: "size M available?", "when back in stock?", "why was my order canceled?". Bot suggests alert + alternative, never a made-up date.
Playbook 5: sync sync audit
Verify inventory sync Shopify ↔ marketplace ↔ dropship app. Pause feed for OOS SKUs. Slack #stock-alerts: support notifies merch in real time.
Useful links
Zero stock does not mean zero support: this is the moment when your customer service proves its value by turning disappointment into loyal anticipation or an alternative sale.
Enzo
June 28, 2026
