E-commerce
1 juillet 2026
« La M est grisée, avez-vous la L ? » « Ma pointure 38 a disparu au paiement. » « Prévenez-moi quand la S revient. » Trois messages où une rupture variante taille seule bloque l'achat alors que SIZE-MAP, l'inventaire Shopify et l'adjacence contiennent déjà la réponse.
Un chatbot IA rupture par taille e-commerce ne remplace pas SIZE-FLOW agents (#447). Il lit SIZE-MAP, vérifie variant_id inventory, cite tailles disponibles, suggère adjacence grounded, active alerte variante et rebuild cart alternate, puis route échange post-order vers #447.
Ce guide #448 couvre intents bot_size_*, flow SIZE-BOT et KPI size_bot. Distinct du SAV taille (#447) et du bot alternatives SKU (#245) : ici, cas d'usage IA rupture partielle : taille adjacente, alerte variante et conversion.
Sommaire
Pourquoi un bot rupture par taille réduit-il les tickets mode ?
Un ticket size OOS évitable naît quand le client ne trouve pas taille adjacente, alerte variante ou panier alternate avant d'écrire au support.
Cinq déclencheurs tickets size botifiables
Size grey-out : ma taille grisée PDP
Adjacent ask : L disponible si M OOS ?
Notify variant : alerte M only not product
Checkout lost : taille OOS au paiement
Available list : quelles tailles restent ?
En mode footwear, 60 à 75 % des tickets stock concernent une variante taille isolée (Opensend, rupture 2026). Zipchat estime qu'un assistant variant-aware récupère 35 à 50 % des ventes perdues sur taille OOS via adjacence + alerte (Zipchat, OOS assistant 2026). Denser insiste sur query inventaire variant_id live avant recommandation (Denser, sync stock 2026).
Angle #448 vs contenus voisins
SAV size #447 : SIZE-FLOW exchange oversell execute. Le #448 = bot tier 1 adjacent notify cart rebuild.
Bot alternatives #245 : substituts cross-product SKU full. Le #448 = même produit autre taille pas robe vs veste.
Rupture #87 : toutes variantes OOS. Le #448 = parent live size-only.
Alertes #48 : widget marketing setup. Le #448 = alerte variant in-chat.
Guide tailles : fit conseil morphologie. Le #448 = stock variant route fit separately.
Exemple DTC footwear
Bestseller 420 sessions PDP/semaine M OOS, 68 % stock tickets size-only baseline #447. Après 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 dispo site non : bot cite live inventory SB-4 not feed stale. Route display error #447 if persistent sync fault.
En quoi SIZE-BOT diffère-t-il de SIZE-FLOW #447 et bot #245 ?
Bot size OOS, playbook agents size et bot alternatives SKU : trois couches sur SIZE-MAP partagée #447.
Matrice bot size → rôle
#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
Router upstream
« Ma taille M rupture », « pointure 38 indispo », « autre taille dispo », « grisé », « alerte ma taille » → SIZE-BOT. « Échange commande oversell », « compensation display error » → handoff #447 SB-7. « Produit entièrement épuisé alternative » all sizes zero → bot_size_route_oos245 or #87.
Données SIZE-BOT
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.
Promesse #448
Policy SIZE-BOT, 12 intents bot_size_*, flow SB-1 à 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.
Quels intents bot_size_* configurer ?
Douze intents bot rupture par taille couvrent tier 1 variant OOS et routing.
Douze intents bot_size
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
Tags session
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 « Aide taille ». T2 : keyword taille M rupture pointure indispo. 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.
Comment appliquer le flow SIZE-BOT en huit étapes ?
Le flow SIZE-BOT guide rupture variante grounded SIZE-MAP #447 et Shopify API.
Huit étapes SB-1 à SB-8
SB-1 Accueil : « Je vérifie les tailles disponibles pour ce produit. »
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 Clore/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 « L me va ? » → 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 dispo : bot_size_available_list full in-stock run, adjacent suggest S then XL per adjacency_grid, no promise M date unless restock_metafield.
Quelle policy SIZE-BOT documenter ?
La policy bot rupture taille SIZE-BOT reprend SIZE-SUP #447 avec garde-fous IA.
Huit règles SIZE-BOT
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 : puis 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.
Revue mensuelle bot size
Audit : wrong available list, fit guarantee language, product notify not variant, stale inventory cite.
SIZE-SUP prérequis gate
No SIZE-BOT prod until #447 SIZE-SUP published and agents trained handoff fields SB-8.
Quels guardrails protègent adjacence et inventaire ?
La matrice bot size autorisé vs interdit protège conversion et exactitude variant.
Actions autorisées bot
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
Actions interdites bot
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 : « Taille [M] : rupture. Disponibles : [S, L, XL] » from API JSON. Voir prévention hallucinations.
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 règle 5 fit disclaimer only.
Comment brancher SIZE-MAP #447 et Shopify variant API ?
L'intégration bot rupture taille combine SIZE-MAP, variant inventory et notify app.
Champs read SIZE-BOT
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.
Integration Qstomy
Voir intégration Shopify + 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.
Quels triggers PDP, panier et UX pour SIZE-BOT ?
Le déploiement UX SIZE-BOT intercepte avant bounce taille grisée.
Cinq placements widget
PDP grey size T1 : « Cette taille est indisponible » chip
Click add OOS size T2 : immediate bot_size_oos_confirm
Cart variant OOS T3 : « Essayer [L] » inline chip
Checkout error T4 : variant name + bot session
Dwell T5 15 s : proactive on OOS selector
Proactive message SB-1
« Taille [M] momentanément indisponible. Tailles en stock : [list]. Taille voisine [L] ou alerte retour [M] ? »
Footwear half-size
adjacency_grid ±0.5 : bot cites 38.5 → 39 → 38 order per SIZE-MAP footwear vertical.
Size chart fork
Button « Guide des tailles » 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 semaines M OOS cohort.
Checkout error T4 template
« Votre taille [M] n'est plus disponible. Tailles restantes : [list]. Essayer [L] ou alerte [M] ? » Deep link opens bot session pre-filled variant context.
Quels KPI size bot mesurer ?
Les KPI bot rupture par taille lient deflection, adjacent conversion et notify quality.
Huit métriques clés
size_bot_resolution_rate : résolu sans handoff / sessions size_bot
size_bot_ticket_delta : baisse tickets #447 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 j post notify
size_bot_csat : satisfaction tag size_bot resolved
Benchmark DTC mode
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.
Dashboard mensuel
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 semaines min 800 sessions per SKU hero. Measure size_bot_adjacent_accept lift.
Audit fit language
Transcript scan guarantee fit phrases count zero. SIZE-BOT règle 5 violation P2.
T3 cart chip conversion
Track cart OOS chip click → deeplink success. Target size_bot_cart_rebuild_rate > 40 % cart OOS events.
Quels anti-patterns éviter sur bot rupture taille ?
Douze anti-patterns bot rupture taille à bannir.
1. Cross-product on size-only
#245 substitute when L same product in stock. Wrong recovery path.
2. Product notify not variant
Règle 3 notify_scope. Spam all size restocks.
3. Fit guarantee adjacent
Règle 5 disclaimer size chart always.
4. Invent size list
Règle 2 SB-4 API only.
5. Skip SIZE-MAP #447
Deploy bot before adjacency_grid documented.
6. Global #87 macro on partial
« Produit épuisé » when L XL available. Conversion killer.
7. Adjacent without stock verify
Règle 6 deeplink fail checkout frustration.
8. Restock date invent
Règle 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
Erreur : bot only no PDP grey notify CTA. Multi-canal complement not replace.
Comment Qstomy automatise la rupture par taille ?
Qstomy sur Shopify exécute 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 champs SB-4 pré-remplis.
Capacités bot_size Qstomy
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 prérequis. #448 bot tier 1 deflect 85 %+ size-only. Shared policy human post-order.
Scénario DTC chiffré
Footwear bestseller M OOS 420 sessions/week, 68 % stock tickets size-only baseline #447.
Après SIZE-BOT Qstomy : size_bot_resolution 85 %, size_bot_ticket_delta -50 %, size_bot_adjacent_accept 34 %, size_bot_csat 4,5/5.
Explorez support client et demander une démo.
Continuity #245
All sizes zero same session → bot offers bot_size_route_oos245 cross-product substitute seamless handoff.
Corpus entraînement size bot
Feed SIZE-MAP + 40 transcripts SB-8 anonymisés intent bot_size tuning. Revue trimestrielle #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.
Quelle checklist pour déployer SIZE-BOT ?
Checklist SIZE-BOT (12 étapes)
Valider SIZE-SUP #447 + SIZE-MAP /pages/size-availability
Export SIZE-MAP adjacency_grid JSON + variant API read
Configurer 12 intents bot_size_* section 3
Implémenter flow SB-1 à 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
Tests staging 8 scénarios M OOS L dispo, cart rebuild, notify, all zero, fit route
Handoff #447 template post-order
Dashboard KPI size_bot mensuel
RAG sync SIZE-MAP on policy change
En bref
#448 = bot taille OOS, pas SAV #447 ni substitut SKU #245
SIZE-BOT : inventory adjacent notify cart rebuild
Même produit : taille voisine pas cross-product default
Alerte variant_id : not product global
KPI size_bot_adjacent_accept : cible > 30 %
FAQ
Bot vs agents #447 ?
#447 exchange oversell compensation execute. #448 bot tier 1 adjacent notify cart.
Différence bot #245 ?
#245 cross-product substitute SKU full. #448 same product other size.
Quelle taille proposer ?
adjacency_grid SIZE-MAP + SB-4 in-stock verify + size chart link.
Alerte ma taille ?
bot_size_notify_variant variant_id scope inline or PDP CTA.
Toutes tailles épuisées ?
bot_size_route_full87 or bot_size_route_oos245 substitute.
Aller plus loin
Guide des tailles
Cette semaine : validez SIZE-MAP #447, configurez intents bot_size_*, déployez T1 chip taille grisée PDP, testez SB-4 adjacent deeplink inventory re-query, connectez notify variant_id Klaviyo, lancez dashboard size_bot_adjacent_accept.
Partagez ce guide #448 avec merchandising et product : un bot qui cite les tailles en stock vaut dix ventes perdues sur grisé, une alerte produit global vaut cent e-mails irrelevantes et zéro conversion taille 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
1 juillet 2026
