E-commerce
July 1, 2026
"M is greyed out, do you have L?" "My size 38 disappeared at checkout." "Let me know when S is back in stock." Three messages where a single-size variant stockout blocks the purchase, even though SIZE-MAP, Shopify inventory, and adjacency already contain the answer.
An e-commerce size stockout AI chatbot does not replace SIZE-FLOW agents (#447). It reads SIZE-MAP, checks variant_id inventory, lists available sizes, suggests grounded adjacency, activates variant alerts, and rebuilds alternate carts, then routes post-order exchanges to #447.
This guide #448 covers intents bot_size_*, flow SIZE-BOT, and KPI size_bot. Distinct from size customer service (#447) and the SKU alternatives bot (#245): here, we focus on the AI partial stockout use case: adjacent size, variant alert, and conversion.
Summary
Why does an out-of-stock-by-size bot reduce fashion support tickets?
An avoidable OOS size ticket arises when the customer cannot find an adjacent size, variant alert, or alternate cart before writing to support.
Five botifiable size ticket triggers
Size grey-out: my size greyed out on PDP
Adjacent ask: Is L available if M is OOS?
Notify variant: M-only alert, not product
Checkout lost: size OOS at payment
Available list: which sizes are left?
In footwear mode, 60 to 75% of stock tickets concern an isolated size variant (Opensend, stockout 2026). Zipchat estimates that a variant-aware assistant recovers 35 to 50% of sales lost to OOS sizes via adjacency + alert (Zipchat, OOS assistant 2026). Denser insists on a live variant_id inventory query before making a recommendation (Denser, sync stock 2026).
Angle #448 vs related content
CS size #447: SIZE-FLOW exchange oversell execute. #448 = tier 1 bot adjacent notify cart rebuild.
Bot alternatives #245: cross-product substitutes SKU full. #448 = same product, different size, not dress vs jacket.
Stockout #87: all variants OOS. #448 = parent live, size-only.
Alerts #48: marketing widget setup. #448 = in-chat variant alert.
Size guide: morphological fit advice. #448 = stock variant route fit separately.
DTC footwear example
Bestseller 420 PDP sessions/week M OOS, 68% stock size-only tickets baseline #447. After SIZE-BOT: size_bot_resolution 84%, size_bot_ticket_delta -49%, size_bot_adjacent_accept 32%, size_bot_csat 4.4/5.
Variant gate SB-2
Verify product handle + requested size variant_id before SIZE-BOT. All variants zero → bot_size_route_full87 not adjacent macros.
Peak BFCM M/L depletion
Scale SIZE-BOT T1 T5 capacity and SB-4 API monitoring pre-Black Friday hot size wave.
Marketplace size lag T4
Google Shopping size available, site not: bot cites live inventory SB-4, not stale feed. Route display error #447 if persistent sync fault.
How does SIZE-BOT differ from SIZE-FLOW #447 and bot #245?
Bot size OOS, playbook agents size and bot alternatives SKU: three layers on shared SIZE-MAP #447.
Bot size matrix → role
#448 SIZE-BOT: variant inventory, adjacent suggest, available list, notify variant, cart rebuild deeplink
#447 SIZE-FLOW: post-order exchange, oversell compensation, marketplace lag ops
#245 OOS bot: cross-product substitute primary secondary OOS-MAP
#87 global: full SKU discontinued post-order cancel
Upstream router
"My size M out of stock", "size 38 unavailable", "other size available", "greyed out", "alert my size" → SIZE-BOT. "Oversell order exchange", "compensation display error" → handoff #447 SB-7. "Product entirely sold out alternative" all sizes zero → bot_size_route_oos245 or #87.
SIZE-BOT data
SIZE-MAP JSON #447 adjacency_grid notify_scope, Shopify variant inventory API all sizes qty, restock_metafield per variant, size chart URL, cart add variant_id deeplink.
Promise #448
SIZE-BOT policy, 12 intents bot_size_*, flow SB-1 to SB-8, guardrails no fit guarantee, KPI size_bot_*.
Same product not substitute
#448 adjacent L same SKU. #245 different product when all sizes OOS or different need category.
Kids size adjacency
Age sizes 8-10-12: adjacency_grid by age not letter in SIZE-MAP kids extension bot reads same SB-5.
Which bot_size_* intents should be configured?
Twelve out-of-stock by size bot intents cover tier 1 variant OOS and routing.
Twelve bot_size intents
bot_size_lookup : product + size → variant_id SB-2
bot_size_oos_confirm : requested size qty 0 grounded
bot_size_available_list : in-stock sizes list API
bot_size_adjacent_suggest : adjacency_grid SIZE-MAP cite
bot_size_notify_variant : variant_id alert signup steps
bot_size_restock_cite : restock_metafield or alert only
bot_size_add_cart_deeplink : /cart/add variant_id adjacent
bot_size_cart_rebuild : checkout lost alternate variant
bot_size_chart_route : fit question → size guide URL
bot_size_handoff_447 : post-order exchange oversell
bot_size_route_full87 : all variants OOS global
bot_size_route_oos245 : cross-product substitute need
Session tags
size_bot, size_bot_adjacent, size_bot_notify, size_bot_resolved, size_bot_handoff_447, size_bot_route245. Distinct oos_bot, size_agent.
Triggers T1-T5
T1 : PDP size selector grey-out click "Size help". T2 : keyword size M out of stock shoe size unavailable. T3 : cart line variant OOS inline chip. T4 : checkout error variant-specific deep link bot. T5 : proactive dwell 15 s on OOS size selector.
Intent priority
bot_size_lookup before bot_size_adjacent_suggest. Never adjacent without SB-4 inventory verify target qty > 0.
Intent routing P1 P2
P1 : bot_size_cart_rebuild, bot_size_oos_confirm. P2 : bot_size_adjacent, bot_size_notify. P3 : bot_size_chart_route FAQ.
How to apply the SIZE-BOT flow in eight steps?
The SIZE-BOT flow guides grounded out-of-stock variant mapping SIZE-MAP #447 and Shopify API.
Eight steps SB-1 to SB-8
SB-1 Greeting: "I am checking available sizes for this product."
SB-2 Lookup variant: product handle + size label → variant_id
SB-3 Classifier intent: bot_size_* section 3
SB-4 Read inventory: all variants qty, requested, adjacent targets
SB-5 Match SIZE-MAP: adjacency_grid, notify_scope, restock_metafield
SB-6 Respond: oos confirm | available list | adjacent | notify | cart rebuild
SB-7 CTA: add cart deeplink | notify toggle | size chart | handoff
SB-8 Close/log: size_bot_action, variant_oos, variant_suggested, converted
SB-4 size_oos_single flow
Requested qty 0, siblings > 0 → bot_size_oos_confirm + bot_size_available_list + bot_size_adjacent_suggest + bot_size_notify_variant offer.
SB-6 adjacent branch
Apply adjacency_grid. Cite adjacent in stock with size chart disclaimer. bot_size_add_cart_deeplink if client accepts.
SB-6 cart_rebuild
size_cart_checkout_lost : bot_size_cart_rebuild alternate variant cart URL + notify requested size option.
SB-4 all variants zero
→ bot_size_route_full87 or bot_size_route_oos245 if client wants different product substitute.
SB-6 fit overlap
Client asks "Will L fit me?" → bot_size_chart_route size guide first, then adjacent stock if still interested.
SB-8 conversion log
Log adjacent_click notify_subscribed cart_rebuild_success. Dashboard size_bot_adjacent_accept.
SB-7 notify vs adjacent fork
Client chooses branch: bot logs size_bot_action adjacent vs notify for funnel dashboard split.
SB-6 size_run_popular_gone
M L OOS S XL available: bot_size_available_list full in-stock run, adjacent suggest S then XL per adjacency_grid, no promise M date unless restock_metafield.
Which SIZE-BOT policy should be documented?
The SIZE-BOT out-of-stock size policy incorporates SIZE-SUP #447 with AI safety guards.
Eight SIZE-BOT rules
SIZE-MAP only: adjacency notify from JSON #447
Variant API grounded: SB-4 qty before any size cite
Notify variant_id only: notify_scope not product blast
No restock date invent: restock_metafield or alert SB-6
No fit guarantee: adjacent + size chart link disclaimer
Adjacent verify stock: target variant qty > 0 SB-4 before deeplink
Max 2 adjacent suggest: adjacency_grid order first two in stock
Max 8 turns size flow: then notify CTA or handoff #447
Corpus RAG sources
/pages/size-availability, SIZE-MAP #447, SIZE-SUP #447, SIZE-OOS-01 SIZE-ADJ-01 templates section 7 #447.
Distinct #245 substitute
Bot never cross-product substitute on size-only unless bot_size_route_oos245 all sizes zero client confirms.
Monthly bot size review
Audit: wrong available list, fit guarantee language, product notify not variant, stale inventory cite.
SIZE-SUP prerequisite gate
No SIZE-BOT prod until #447 SIZE-SUP published and agents trained handoff fields SB-8.
Which guardrails protect adjacency and inventory?
The allowed vs forbidden bot size matrix protects conversion and variant accuracy.
Allowed bot actions
Confirm specific size OOS grounded
List in-stock sizes from API
Suggest adjacent per adjacency_grid in stock
Variant notify signup inline
Cart rebuild alternate variant deeplink
Route size chart for fit questions
Restock metafield cite if exists
Handoff post-order #447
Forbidden bot actions
Guarantee adjacent fit "L = M"
Invent available sizes hallucination
Notify product not variant_id
Adjacent without SB-4 stock verify
Cross-product substitute on size-only default
Order exchange execute bot
Anti-hallucination inventory
Template: "Size [M]: out of stock. Available: [S, L, XL]" from API JSON. See hallucination prevention.
Webhook stale prevention
Re-query variant inventory before bot_size_add_cart_deeplink click send. Cache max 60 s SB-4.
Plus-size adjacent sensitivity
Neutral language bot_size_available_list no body commentary. SIZE-BOT rule 5 fit disclaimer only.
How do I connect SIZE-MAP #447 and the Shopify variant API?
The out-of-stock bot integration combines SIZE-MAP, variant inventory, and the notify app.
SIZE-BOT read fields
product_id: handle or id from PDP context
variants[]: size option value, variant_id, inventory_quantity
requested_variant_id: from SB-2 size label match
adjacent_targets[]: from adjacency_grid SIZE-MAP
restock_date: variant metafield or null
size_chart_url: product or global guide
Shopify Admin API inventory_levels per variant_id (Shopify, InventoryLevel 2026).
PDP context T1
Pass selected size + product handle to bot SB-2 pre-fill. Highest size_bot_adjacent_accept rate.
Notify Klaviyo variant
bot_size_notify_variant triggers variant_id event not product. Parity #447 notify_scope.
Qstomy Integration
See Shopify integration + SIZE-MAP RAG sync #447.
Cart webhook T3
Line variant qty → 0 mid-session → proactive bot_size_cart_rebuild chip on cart page.
Route full OOS #245
All variants zero + client rejects wait → bot_size_route_oos245 cross-product if OOS-MAP configured.
Inventory webhook SB-4 refresh
Shopify inventory_levels/update invalidates cache within 60 s. Adjacent deeplink always fresh qty.
What PDP, cart, and UX triggers for SIZE-BOT?
The UX SIZE-BOT deployment intercepts before greyed-out size bounce.
Five widget placements
PDP grey size T1: "This size is unavailable" chip
Click add OOS size T2: immediate bot_size_oos_confirm
Cart variant OOS T3: "Try [L]" inline chip
Checkout error T4: variant name + bot session
Dwell T5 15 s: proactive on OOS selector
Proactive message SB-1
"Size [M] temporarily unavailable. Sizes in stock: [list]. Neighboring size [L] or back in stock alert [M]?"
Footwear half-size
adjacency_grid ±0.5: bot cites 38.5 → 39 → 38 order per SIZE-MAP footwear vertical.
Size chart fork
Button "Size guide" parallel bot_size_chart_route. Stock bot handles availability not fit advice.
Mobile size selector
Grey-out tap opens bot drawer not dead end. Critical mobile conversion footwear.
BFCM hot sizes
Pre-load T1 T5 on hero SKU M/L before peak. Scale SB-4 API rate limit monitoring.
A/B proactive T5 copy
Variant A list available vs B adjacent first: measure size_bot_adjacent_accept 4 weeks M OOS cohort.
Checkout error T4 template
"Your size [M] is no longer available. Remaining sizes: [list]. Try [L] or alert [M]?" Deep link opens bot session pre-filled variant context.
Which bot size KPIs should be measured?
The size bot out-of-stock KPIs link deflection, adjacent conversion and notify quality.
Eight key metrics
size_bot_resolution_rate: resolved without handoff / size_bot sessions
size_bot_ticket_delta: drop in #447 tickets vs baseline
size_bot_adjacent_accept: add cart deeplink click / adjacent suggests
size_bot_notify_signup: variant notify / notify offers
size_bot_cart_rebuild_rate: checkout lost recovered / cart OOS events
size_bot_handoff_447_rate: post-order routed agents
size_bot_notify_to_order_7d: orders within 7 days post notify
size_bot_csat: satisfaction tag size_bot resolved
DTC fashion benchmark
size_bot_resolution 82-88 %, size_bot_ticket_delta -45-55 %, size_bot_adjacent_accept 28-36 %, notify_to_order_7d 15-22 %, size_bot_csat > 4.2/5.
Monthly dashboard
Trigger T1-T5 breakdown, top variant OOS by sessions, adjacent vs notify choice, route245 rate all sizes zero.
A/B PDP OOS
50 % T1 widget vs none 4 weeks min 800 sessions per SKU hero. Measure size_bot_adjacent_accept lift.
Fit language audit
Transcript scan guarantee fit phrases count zero. SIZE-BOT rule 5 violation P2.
T3 cart chip conversion
Track cart OOS chip click → deeplink success. Target size_bot_cart_rebuild_rate > 40 % cart OOS events.
What anti-patterns should be avoided on size stock bots?
Twelve out-of-stock size bot anti-patterns to ban.
1. Cross-product on size-only
#245 substitute when L same product in stock. Wrong recovery path.
2. Product notify not variant
Rule 3 notify_scope. Spam all size restocks.
3. Fit guarantee adjacent
Rule 5 disclaimer size chart always.
4. Invent size list
Rule 2 SB-4 API only.
5. Skip SIZE-MAP #447
Deploy bot before adjacency_grid documented.
6. Global #87 macro on partial
"Out of stock" when L XL available. Conversion killer.
7. Adjacent without stock verify
Rule 6 deeplink fail checkout frustration.
8. Restock date invent
Rule 4 metafield or alert only.
9. Exchange execute bot
Post-order → handoff #447 not bot order edit.
10. Ignore cart rebuild T3
Checkout lost highest intent missed on cart page.
11. Stale inventory cache
60 s max re-query before deeplink.
12. Confondre fit guide
bot_size_chart_route not stock invent for morphology.
13. Bot replaces PDP notify widget
Error: bot only no PDP grey notify CTA. Multi-channel complement not replace.
How does Qstomy automate out-of-stock tracking by size?
Qstomy on Shopify runs SIZE-BOT: SB-2 variant lookup, SB-4 inventory read, bot_size_available_list, bot_size_adjacent_suggest SIZE-MAP, bot_size_notify_variant, cart rebuild deeplink, handoff #447 post-order pre-filled SB-4 fields.
Qstomy bot_size capabilities
bot_size_variant_lookup: SB-2 SB-4 all sizes
bot_size_adjacent_template: adjacency_grid auto
bot_size_notify_trigger: variant_id Klaviyo
bot_size_cart_deeplink: alternate variant add
bot_size_route_full87: all zero → global
bot_size_handoff_ticket: #447 exchange pre-fill
Pipeline #447 → #448
#447 SIZE-SUP SIZE-MAP prerequisite. #448 bot tier 1 deflect 85 %+ size-only. Shared policy human post-order.
Calculated DTC scenario
Footwear bestseller M OOS 420 sessions/week, 68% stock tickets size-only baseline #447.
After Qstomy SIZE-BOT: size_bot_resolution 85%, size_bot_ticket_delta -50%, size_bot_adjacent_accept 34%, size_bot_csat 4.5/5.
Explore customer support and request a demo.
Continuity #245
All sizes zero same session → bot offers bot_size_route_oos245 cross-product substitute seamless handoff.
Size bot training corpus
Feed SIZE-MAP + 40 anonymized SB-8 transcripts intent bot_size tuning. Quarterly review #447 ops.
Weekly size_bot review
Ops review top 5 variant OOS by sessions, adjacent accept rate, handoff 447 rate, transcript fit guarantee scan zero tolerance.
What is the checklist for deploying SIZE-BOT?
SIZE-BOT Checklist (12 steps)
Validate SIZE-SUP #447 + SIZE-MAP /pages/size-availability
Export SIZE-MAP adjacency_grid JSON + variant API read
Configure 12 intents bot_size_* section 3
Implement flow SB-1 to SB-8 + variant gate SB-2
Deploy T1 PDP grey size + T3 cart OOS chip
Guardrails no fit guarantee + variant notify only
Cart deeplink re-query inventory before send
Router size-only vs full87 vs oos245 disambiguation
Staging tests 8 scenarios M OOS L available, cart rebuild, notify, all zero, fit route
Handoff #447 template post-order
Monthly size_bot KPI Dashboard
RAG sync SIZE-MAP on policy change
In brief
#448 = OOS size bot, not customer service #447 nor substitute SKU #245
SIZE-BOT: inventory adjacent notify cart rebuild
Same product: adjacent size not cross-product default
Alert variant_id: not product global
KPI size_bot_adjacent_accept: target > 30 %
FAQ
Bot vs agents #447?
#447 exchange oversell compensation execute. #448 bot tier 1 adjacent notify cart.
Difference bot #245?
#245 cross-product substitute SKU full. #448 same product other size.
Which size to suggest?
adjacency_grid SIZE-MAP + SB-4 in-stock verify + size chart link.
Alert my size?
bot_size_notify_variant variant_id scope inline or PDP CTA.
All sizes out of stock?
bot_size_route_full87 or bot_size_route_oos245 substitute.
Go further
Size guide
This week: validate SIZE-MAP #447, configure intents bot_size_*, deploy T1 greyed-out size chip PDP, test SB-4 adjacent deeplink inventory re-query, connect notify variant_id Klaviyo, launch dashboard size_bot_adjacent_accept.
Share this guide #448 with merchandising and product: a bot that quotes sizes in stock is worth ten lost sales on greyed out options, a global product alert is worth a hundred irrelevant emails and zero conversion for size M.
Go-live test matrix
8 scenarios sign-off: M OOS L stock adjacent deeplink, notify variant, cart rebuild, all zero route245, fit route chart, handoff post-order, stale cache block.
Enzo
July 1, 2026
