E-commerce
1 juillet 2026
« La couleur est-elle fidèle aux photos ? » « C'est plutôt mat ou satiné ? » « Quelle différence entre bleu nuit et noir ? » Trois questions pré-achat où le client hésite sans réponse grounded, puis ouvre un ticket post-réception ou abandonne le panier.
Un chatbot IA couleur matière rendu e-commerce ne remplace pas COLOR-FLOW agents (#449). Il lit COLOR-MAP, cite finish_note et lighting_disclaimer, compare coloris proches, envoie real_photo_url et route échange coloris stock vérifié, puis handoff post-réception vers #449.
Ce guide #450 couvre intents bot_color_*, flow COLOR-BOT et KPI color_bot. Distinct du SAV couleur (#449) et de bot validation perso (#418) : ici, cas d'usage IA aide au choix : couleur, matière et rendu visuel pré-achat.
Sommaire
Pourquoi un bot couleur réduit-il les retours motif teinte ?
Un ticket couleur évitable naît quand le client commande sans finish_note, disclaimer éclairage ou comparaison coloris avant achat.
Cinq déclencheurs tickets color botifiables
Pre fidelity : couleur fidèle photos ?
Finish ask : mat, satin, brillant, grain
Compare variants : navy vs midnight vs black
Material ask : composition, toucher, entretien
Lighting context : rendu lumière naturelle
Digital Applied estime qu'environ 45 % des retours mode et déco viennent de taille, fit ou écart couleur/description, souvent corrigeables en amont (Digital Applied, returns playbook 2026). Kn8 rappelle qu'un agent storefront vérifie le catalogue live avant recommandation, contrairement à un chatbot statique (Kn8, agents e-commerce 2026). Shopify permet images et swatches par variant_id couleur (Shopify, variantes 2026).
Angle #450 vs contenus voisins
SAV color #449 : COLOR-FLOW retour échange execute. Le #450 = bot tier 1 pre-purchase fidelity compare.
Bot perso #418 : couleur fil broderie validation. Le #450 = coloris catalogue pas sur-mesure.
Wrong item #186 : picking error. Le #450 = attentes rendu pas fulfillment.
Blocs PDP : FAQ statique fiche. Le #450 = conversation contextuelle variant.
Analyse retours : dashboard motifs. Le #450 = deflect amont tickets color.
Exemple DTC déco textile
Top 15 coloris pastel 380 sessions PDP/semaine, 34 % retours motif couleur baseline #449. Après COLOR-BOT : color_bot_resolution 86 %, color_bot_ticket_delta -47 %, color_bot_pre_deflect 31 %, color_bot_csat 4,5/5.
Variant gate CB-2
Verify product handle + selected color variant_id before COLOR-BOT. Material question without color context → bot_color_material_cite product level first.
Jewelry finish density
Plated gold rose gold : highest bot_color_finish_cite volume. Pre-load COLOR-MAP macro photos CB-6.
Seasonal launch pre-scale
New color collection : preload T1 T3 and COLOR-MAP extended disclaimer before launch day bot traffic spike.
Deco textile lot variation
bot_color_pre_fidelity cites supplier_batch metafield if color_lot_variation flag in COLOR-MAP. Sets realistic expectation pre-buy.
En quoi COLOR-BOT diffère-t-il de COLOR-FLOW #449 et bot #418 ?
Bot couleur matière, playbook agents color et bot validation perso : trois couches sur COLOR-MAP partagée #449.
Matrice bot color → rôle
#450 COLOR-BOT : pre fidelity, finish cite, compare variants, real photo, exchange deeplink pre-buy
#449 COLOR-FLOW : post-réception hue disappointment, return execute, defect QA
#418 VALID-FLOW : couleur fil gravure personnalisation confirm
#186 wrong : variant expédiée ≠ commandée
Router upstream
« Couleur fidèle », « mat ou brillant », « différence navy black », « composition coton », « photo réelle » → COLOR-BOT. « Reçu plus foncé déçu retour », « tache teinture » → handoff #449 CB-7. « Couleur broderie fil » → bot_color_route_418. Order mismatch color → bot_color_route_186.
Données COLOR-BOT
COLOR-MAP JSON #449 finish_note lighting_disclaimer real_photo_url, Shopify variant images swatch, material metafield product, alternate color variant inventory CB-4.
Promesse #450
Policy COLOR-BOT, 12 intents bot_color_*, flow CB-1 à CB-8, guardrails no exact color guarantee, KPI color_bot_*.
Pre-purchase not post-return
#450 primary job = convert informed buyer. #449 primary job = resolve disappointed receiver.
bot_color_route_186 gate
Order line variant_id ≠ client claim shipped color : immediate handoff wrong item not COLOR-PRE macro.
Quels intents bot_color_* configurer ?
Douze intents bot couleur matière rendu couvrent tier 1 pré-achat et routing.
Douze intents bot_color
bot_color_swatch_lookup : product + color → variant_id CB-2
bot_color_pre_fidelity : fidélité photos grounded disclaimer
bot_color_finish_cite : finish_note mat satin brillant
bot_color_compare_variants : navy midnight black side by side
bot_color_lighting_disclaimer : studio vs naturel standard copy
bot_color_real_photo : real_photo_url unretouched send
bot_color_material_cite : composition care from product metafield
bot_color_alternate_suggest : alternate coloris in stock CB-4
bot_color_add_cart_deeplink : /cart/add variant_id color chosen
bot_color_return_policy_cite : return_tier summary pre-buy only
bot_color_handoff_449 : post-order hue defect disappointment
bot_color_route_418 : personalization thread color
Tags session
color_bot, color_bot_pre, color_bot_compare, color_bot_resolved, color_bot_handoff_449, color_bot_route418. Distinct color_agent, perso_valid.
Triggers T1-T5
T1 : PDP swatch select + dwell 10 s « Questions couleur » chip. T2 : keyword couleur fidèle matière brillant navy. T3 : swatch hover hesitation proactive. T4 : collection page color filter context. T5 : cart line color property review pre-checkout.
Intent priority
bot_color_swatch_lookup before bot_color_compare_variants. Never compare without CB-2 variant context.
P1 P2 intent routing
P1 : bot_color_pre_fidelity, bot_color_handoff_449. P2 : bot_color_compare, bot_color_finish. P3 : bot_color_material FAQ.
Comment appliquer le flow COLOR-BOT en huit étapes ?
Le flow COLOR-BOT guide aide choix couleur grounded COLOR-MAP #449.
Huit étapes CB-1 à CB-8
CB-1 Accueil : « Je vous aide sur la couleur et le rendu de ce produit. »
CB-2 Lookup variant : product handle + color label → variant_id
CB-3 Classifier intent : bot_color_* section 3
CB-4 Read COLOR-MAP : finish_note, lighting_disclaimer, real_photo, return_tier
CB-5 Read catalog : variant images, material metafield, alternate colors inventory
CB-6 Respond : fidelity | finish | compare | material | real photo
CB-7 CTA : add cart deeplink | alternate color | /pages/color-accuracy | handoff
CB-8 Clore/log : color_bot_action, variant_color, pre_deflect, converted
CB-6 bot_color_pre_fidelity
COLOR-PRE-01 template from #449 : finish_note + lighting_disclaimer + real_photo_url link + bot_color_return_policy_cite one line.
CB-6 compare branch
bot_color_compare_variants : cite COLOR-COMPARE-01 navy midnight black with swatch URLs from CB-5 variant images.
CB-6 material branch
bot_color_material_cite : product metafield composition + finish_note. No invent fiber percentages.
CB-7 alternate suggest
Client hésite coloris : bot_color_alternate_suggest in-stock siblings + bot_color_add_cart_deeplink if accepts.
CB-8 pre_deflect log
Log session COLOR-PRE sent → purchase 7 j → no color return 30 j. Dashboard color_bot_pre_deflect.
CB-7 /pages/color-accuracy fork
Deep FAQ link for clients wanting full policy read. Bot summarizes then CTA page not wall of text.
CB-6 lighting branch standalone
Client asks lumière only : bot_color_lighting_disclaimer full COLOR-LIGHT-01 copy from #449 plus link real_photo_url practical comparison tip.
Quelle policy COLOR-BOT documenter ?
La policy bot couleur matière COLOR-BOT reprend COLOR-SUP #449 avec garde-fous IA pré-achat.
Huit règles COLOR-BOT
COLOR-MAP only : finish disclaimer return_tier from JSON #449
Catalog grounded CB-5 : material images from metafield API not LLM
No exact color guarantee : lighting_disclaimer always CB-6 fidelity
No agent opinion color : cite COLOR-MAP not « moi je trouve »
Compare max 3 variants : sibling coloris same product only
Alternate verify stock CB-5 : qty > 0 before deeplink
Max 8 turns color flow : puis add cart CTA or handoff #449
Post-order handoff #449 : bot never execute return label refund
Corpus RAG sources
/pages/color-accuracy, COLOR-MAP #449, COLOR-PRE-01 COLOR-COMPARE-01 templates section 7 #449, product material metafields.
Distinct #418 perso
Catalog swatch = COLOR-BOT. Line item broderie fil = bot_color_route_418 immediately.
Revue mensuelle bot color
Audit : exact match guarantee language, invented material %, compare wrong product, post-order return promise.
COLOR-SUP prérequis gate
No COLOR-BOT prod until #449 COLOR-SUP published and /pages/color-accuracy live.
Quels guardrails protègent fidélité et matière ?
La matrice bot color autorisé vs interdit protège attentes client et conversion.
Actions autorisées bot
Cite finish_note lighting_disclaimer from COLOR-MAP
Compare up to 3 sibling color variants
Send real_photo_url if exists CB-4
Cite material metafield composition care
Suggest alternate coloris in stock
Return_tier summary pre-buy cite only
Add cart deeplink chosen variant
Handoff post-order #449 pre-filled
Actions interdites bot
Guarantee exact screen match
Invent material composition percentages
Blame client monitor aggressively
Execute return refund post-order
Compare cross-product colors
Route catalog color to #418 perso
Anti-hallucination catalog
Template fidelity : « [Coloris] : [finish_note]. [lighting_disclaimer]. » from COLOR-MAP JSON. Voir prévention hallucinations.
Empathy without admission
Pre-buy : inform not apologize brand fault. Post-order disappointment → handoff #449 COLOR-EMPATHY-01 agents.
Leather grain disclaimer
Natural leather : bot_color_material_cite grain unique per hide from COLOR-MAP extension. No two identical.
Comment brancher COLOR-MAP #449 et Shopify variant data ?
L'intégration bot couleur matière combine COLOR-MAP, variant images et metafields produit.
Champs read COLOR-BOT
product_id : handle from PDP context
color_variants[] : label, variant_id, image_url, inventory_qty
selected_variant_id : from CB-2 swatch match
finish_note : COLOR-MAP per variant or product
lighting_disclaimer : COLOR-MAP standard or extended pastel
real_photo_url : unretouched stock image or null
material_metafield : composition care instructions
Shopify product metafields custom.material_composition (Shopify, metafields 2026).
PDP context T1
Pass selected swatch + product handle CB-2 pre-fill. Highest color_bot_pre_deflect conversion rate.
Variant image gallery CB-5
bot_color_compare_variants uses variant-specific image URLs not parent default only.
Integration Qstomy
Voir intégration Shopify + COLOR-MAP RAG sync #449.
Order context post-pay
If order_id detected + hue disappointment keywords → bot_color_handoff_449 skip pre macros.
Swatch hex metafield CB-4
Optional hex_swatch COLOR-MAP enriches bot_color_compare_variants visual cite alongside image URLs.
Quels triggers PDP, swatch et UX pour COLOR-BOT ?
Le déploiement UX COLOR-BOT intercepte hésitation couleur avant abandon.
Cinq placements widget
PDP swatch T1 : « Question sur cette couleur ? » chip after select
Finish note expand T2 : « En savoir plus matière » opens bot
Compare hover T3 : « Navy ou Black ? » proactive on dual swatch dwell
Cart color review T4 : recap finish disclaimer pre-pay
/pages/color-accuracy T5 : FAQ link opens bot context
Proactive message CB-1
« [Vert d'eau] : [finish_note]. Variation légère possible selon écran : [lighting_disclaimer one line]. Photo réelle ou comparer un autre coloris ? »
Pastel collection launch
Pre-load T1 T3 on new pastel SKUs with extended lighting_disclaimer before launch support spike.
Mobile swatch UX
Swatch tap opens bot drawer not dead end. Critical mobile conversion mode coloris.
Video 360 link CB-7
If product video metafield exists : bot_color_pre_fidelity includes video URL natural + studio light.
A/B T1 proactive vs passive
50 % PDP color chip vs none 4 semaines min 600 sessions per hero coloris. Measure color_bot_pre_deflect lift.
T4 cart recap mobile
Cart drawer one-line finish_note before pay reduces color_finish_surprise post-reception on mobile majority traffic.
Finish note inline PDP sync
Merch metafield finish_note visible under swatch complements T1 bot chip. Dual channel reduces color_finish_surprise tickets 20-30 % pilots.
Quels KPI color bot mesurer ?
Les KPI bot couleur matière lient deflection pré-achat, conversion et retours amont.
Huit métriques clés
color_bot_resolution_rate : résolu sans handoff / sessions color_bot
color_bot_ticket_delta : baisse tickets #449 vs baseline
color_bot_pre_deflect : achats post COLOR-PRE sans retour couleur 30 j
color_bot_compare_engagement : compare sessions / swatch dwell T3
color_bot_add_cart_rate : deeplink click / sessions resolved pre
color_bot_handoff_449_rate : post-order routed agents
color_bot_real_photo_click : real_photo_url opens / offers
color_bot_csat : satisfaction tag color_bot resolved
Benchmark DTC mode déco
color_bot_resolution 84-90 %, color_bot_ticket_delta -42-52 %, color_bot_pre_deflect 26-34 %, color_bot_add_cart_rate 38-48 %, color_bot_csat > 4,3/5.
Dashboard mensuel
Trigger T1-T5 breakdown, top coloris by sessions, compare vs fidelity intent split, handoff 449 rate, SKU color return correlation.
Croisement analyse retours
Measure color return rate delta on SKUs with COLOR-BOT T1 active vs control. Align analyse retours motif couleur.
SKU pilot color return correlation
Track color return rate 30 j pre vs post COLOR-BOT on top 10 pastel SKUs. Target -25 % minimum pilot cohort.
Quels anti-patterns éviter sur bot couleur matière ?
Douze anti-patterns bot couleur rendu à bannir.
1. Exact match guarantee
Règle 3 lighting_disclaimer mandatory. Legal and return dispute risk.
2. Invent material composition
Règle 2 CB-5 metafield only. Hallucination fiber %.
3. Post-order return execute bot
Règle 8 handoff #449. Bot pre-buy only.
4. Blame monitor pre-buy
Inform disclaimer not lecture client screen.
5. Skip COLOR-MAP #449
Deploy bot before finish_note documented.
6. Compare cross-product
Règle 5 sibling variants same PDP only.
7. Route catalog to #418
Swatch ≠ broderie fil. bot_color_route_418 disambiguation.
8. Agent opinion color
Règle 4 COLOR-MAP cite only.
9. Ignore real_photo_url null
Offer variant images CB-5 fallback not « pas de photo ».
10. No alternate when hesitating
bot_color_alternate_suggest missed conversion opportunity.
11. Generic « voir fiche produit »
COLOR-PRE-01 grounded beats defer.
12. Confondre wrong item #186
Pre-buy fidelity ≠ order mismatch. Route bot_color_route_186 if order context.
13. Deploy before COLOR-MAP
Erreur : bot live without #449 finish_note published. Hallucination and policy drift guaranteed.
Comment Qstomy automatise couleur et matière ?
Qstomy sur Shopify exécute COLOR-BOT : CB-2 swatch lookup, CB-4 COLOR-MAP read, bot_color_pre_fidelity, bot_color_compare_variants, bot_color_material_cite, real_photo send, alternate color deeplink, handoff #449 post-réception champs CB-4 pré-remplis.
Capacités bot_color Qstomy
bot_color_map_rag : finish disclaimer return_tier
bot_color_pre_template : COLOR-PRE-01 auto PDP
bot_color_compare_engine : 3 variant side by side
bot_color_material_read : metafield composition
bot_color_cart_deeplink : variant add in-chat
bot_color_handoff_449 : post-order ticket pre-fill
Pipeline #449 → #450
#449 COLOR-SUP COLOR-MAP prérequis. #450 bot tier 1 deflect 85 %+ color pre-purchase. Shared policy post-réception agents.
Scénario DTC chiffré
Déco textile pastel, 89 tickets color/mois baseline #449, color_fcr 59 %.
Après COLOR-BOT Qstomy T1 swatch chip : color_bot_resolution 87 %, color_bot_ticket_delta -48 %, color_bot_pre_deflect 32 %, color_return_rate SKU pilot -29 %, color_bot_csat 4,6/5.
Explorez support client et demander une démo.
Continuity merch CF-8
CB-8 sessions flagged high compare intent feed conversations → PDP photo updates.
Weekly color_bot transcript audit
Scan guarantee exact match phrases count zero. Material % invent count zero. Handoff 449 rate stable post-order.
RAG corpus color bot
Feed COLOR-MAP + 40 transcripts CB-8 anonymisés for intent bot_color tuning. Revue trimestrielle avec ops #449.
Quelle checklist pour déployer COLOR-BOT ?
Checklist COLOR-BOT (12 étapes)
Valider COLOR-SUP #449 + COLOR-MAP /pages/color-accuracy
Export COLOR-MAP JSON + material metafields product
Configurer 12 intents bot_color_* section 3
Implémenter flow CB-1 à CB-8 + swatch gate CB-2
Deploy T1 PDP swatch chip + T3 compare proactive
Guardrails no exact guarantee + material metafield only
Router pre-buy vs post-order handoff #449 disambiguation
Router perso #418 vs catalog color bot_color_route_418
Tests staging 8 scénarios : fidelity, finish, compare, material, alternate deeplink, post-order handoff, perso route, wrong 186
Dashboard KPI color_bot_pre_deflect mensuel
A/B T1 proactive 4 semaines hero coloris
RAG sync COLOR-MAP on policy change
En bref
#450 = bot couleur matière pré-achat, pas SAV #449 ni perso #418
COLOR-BOT : fidelity finish compare material deeplink
COLOR-MAP #449 : finish disclaimer real_photo grounded
No exact guarantee : lighting_disclaimer always
KPI color_bot_pre_deflect : cible > 28 %
FAQ
Bot vs agents #449 ?
#449 post-réception retour échange defect execute. #450 bot tier 1 pré-achat fidelity compare.
Différence bot #418 ?
#418 couleur fil personnalisation. #450 coloris catalogue swatch.
Couleur fidèle garantie ?
Non. bot_color_lighting_disclaimer + finish_note COLOR-MAP, jamais match exact promis.
Client déçu post-réception ?
bot_color_handoff_449 ticket pré-rempli agents COLOR-DISCLAIMER-01.
Quels triggers PDP ?
T1 swatch chip, T3 compare dwell, T4 cart color recap pre-pay.
Aller plus loin
Cette semaine : validez COLOR-MAP #449, configurez intents bot_color_*, déployez T1 chip swatch PDP, testez CB-6 compare navy/black grounded images, connectez material metafields CB-5, lancez dashboard color_bot_pre_deflect.
Partagez ce guide #450 avec merchandising et support : un bot qui cite finish_note avant achat vaut dix retours « pas la même couleur », une promesse match exact vaut cent litiges et zéro confiance swatch.
Go-live test matrix
8 scenarios sign-off : pre fidelity pastel, compare navy black, material cite, real photo send, alternate deeplink, post-order handoff, perso route 418, order mismatch 186.
Document CB-8 logs color_bot_action per scenario before production traffic enable.
Enzo
1 juillet 2026
