E-commerce
1 juillet 2026
« Mon conjoint attend ma validation, le chatbot ne sait pas où cliquer. » « Je suis invité en lecture seule, comment ajouter un article ? » « Qui peut payer le panier partagé ? » Trois messages où un co-achat bloqué faute de self-service ouvre un ticket alors que SHCART-MAP, les rôles RBAC et le statut approval contiennent déjà la réponse.
Un chatbot IA paniers partagés e-commerce ne remplace pas SHCART-FLOW agents (#443). Il lit SHCART-MAP, cite rôle et approval_status grounded, renvoie invite dans resend limit, nudge approbateur, explique checkout_role et route B2B conflit privacy vers #443.
Ce guide #444 couvre intents bot_shcart_*, flow SHCART-BOT et KPI shcart_bot. Distinct du SAV panier partagé (#443) et du bot save (#438) : ici, cas d'usage IA co-achat : inviter, valider et finaliser une commande collaborative.
Sommaire
Pourquoi un bot panier partagé réduit-il les tickets co-achat ?
Un ticket panier partagé évitable naît quand un participant ne comprend pas son rôle, le statut approval ou qui peut checkout avant d'écrire au support.
Cinq déclencheurs tickets shcart botifiables
Invite perdue : collaborateur cherche lien invitation
Permission refusée : viewer veut éditer
Approval bloqué : approbateur n'a pas validé
Checkout ambigu : qui clique payer
Conflit édition : modifications écrasées, refresh
Baymard estime que 18 à 24 % des achats DTC impliquent une seconde personne consultée avant paiement (Baymard, checkout 2026). Tidio note qu'un bot tier 1 permissions et approval réduit tickets collaboratifs agents de 50 à 62 % vs FAQ statique (Tidio, chat stats 2026). Gorgias documente les assistants shopping multi-intent post-panier (Gorgias, assistant 2026).
Angle #444 vs contenus voisins
SAV shcart #443 : SHCART-FLOW invite role change B2B execute. Le #444 = bot tier 1 permissions approval checkout explain.
Bot save #438 : restore fork solo SCART-MAP. Le #444 = co-édition live multi-participants.
Save #437 : panier enregistré TTL solo. Le #444 = shared_cart_id collaboratif.
Cadeau groupe #433 : split payeurs post-commande. Le #444 = pré-checkout co-achat.
Checkout #292 : paiement in-checkout. Le #444 = amont permissions approval gate.
Exemple DTC
Mobilier 180 shared carts/mois, 34 tickets baseline #443. Après SHCART-BOT : shcart_bot_resolution 85 %, shcart_bot_ticket_delta -54 %, shcart_approval_nudge_success 71 %, shcart_bot_csat 4,4/5.
Shared cart gate
SHB-2 verify shared_cart_id + participant email before SHCART-BOT macros. No shared_cart_id → route SCART-BOT #438 or #437 solo save.
Peak co-achat Noël rentrée
Famille validation panier cadeaux spike : scale approver nudge T5 et bot capacity pre-peak Black Friday.
En quoi SHCART-BOT diffère-t-il de SHCART-FLOW #443 et SCART-BOT #438 ?
Bot co-achat, playbook agents shcart et bot save solo : trois couches sur SHCART-MAP partagée #443.
Matrice bot shcart → rôle
#444 SHCART-BOT : role explain, approval status cite, invite resend, checkout guide, conflict policy, approver nudge
#443 SHCART-FLOW : role change ops, privacy P1, B2B PO, owner transfer, remove contributor execute
#438 SCART-BOT : restore save token fork solo
#433 group gift : post-order split pay
Router upstream
« Panier partagé », « valider panier conjoint », « invitation collaboratif », « qui paie », « approbation en attente », « lecture seule modifier » → SHCART-BOT. « Changer rôle ops », « fuite adresse owner », « équipe B2B devis PO », « retirer contributeur execute » → handoff #443 SHB-7. « Panier enregistré solo » sans shared_cart_id → #438 SCART-BOT.
Données SHCART-BOT
SHCART-MAP JSON #443, shared cart app API collaborators[], approval_status, roles, checkout_role, invite_ttl, conflict_resolution, resend_count, cart lines total read-only.
Promesse #444
Policy SHCART-BOT, 12 intents bot_shcart_*, flow SHB-1 à SHB-8, guardrails no approval bypass, KPI shcart_bot_*.
Co-achat vs fork save
Client veut copie solo pas co-edit → bot_shcart_route_scart438 fork #438 not shcart invite macros.
Contributor list bot scope
shcart_contributor_list : bot explains owner pays all, contributors add lines only. bot_shcart_role_explain editor vs owner checkout.
Quels intents bot_shcart_* configurer ?
Douze intents bot paniers partagés couvrent tier 1 co-achat et routing litige.
Douze intents bot_shcart
bot_shcart_lookup : shared_cart_id + participant email verify
bot_shcart_role_explain : viewer editor approver owner cite
bot_shcart_invite_resend : resend within invite limit
bot_shcart_approval_status : pending approved rejected grounded
bot_shcart_approver_nudge : relance approbateur pending
bot_shcart_checkout_guide : checkout_role who can pay
bot_shcart_permission_denied : viewer edit blocked explain
bot_shcart_conflict_explain : conflict_resolution policy cite
bot_shcart_guest_join_guide : magic link steps guest_join
bot_shcart_cart_summary : N lines total read-only all roles
bot_shcart_handoff_443 : B2B privacy role change complex
bot_shcart_route_scart438 : solo save fork no shared_cart_id
Tags session
shcart_bot, shcart_bot_approval, shcart_bot_resolved, shcart_bot_handoff_443, shcart_bot_route438. Distinct scart_bot, shcart_agent.
Triggers T1-T5
T1 : shared cart page widget « Aide co-achat ». T2 : keyword panier partagé/collaboratif/valider conjoint. T3 : /pages/shared-cart bot embed. T4 : invite email deep link ?intent=bot_shcart_guest_join. T5 : proactive approval pending 48 h Klaviyo segment approver nudge bot.
Intent priority
bot_shcart_lookup before bot_shcart_checkout_guide. Never checkout URL if approval_required pending règle 3.
Intent routing priority table
P1 : bot_shcart_approval_status, bot_shcart_checkout_guide. P2 : bot_shcart_permission_denied, bot_shcart_conflict_explain. P3 : bot_shcart_guest_join_guide FAQ.
Comment appliquer le flow SHCART-BOT en huit étapes ?
Le flow SHCART-BOT guide co-achat grounded SHCART-MAP #443 et app API.
Huit étapes SHB-1 à SHB-8
SHB-1 Accueil : « Je vous aide sur le panier partagé : rôles, validation, paiement. »
SHB-2 Auth lookup : shared_cart_id + participant email or invite token
SHB-3 Classifier intent : bot_shcart_* section 3
SHB-4 Match SHCART-MAP : roles, approval, checkout, ttl, conflict
SHB-5 Read cart data : collaborators, approval_status, lines total, resend_count
SHB-6 Respond : role | approval | checkout | invite | conflict templates
SHB-7 CTA : invite_url | approve link | checkout_url if gate green | /pages/shared-cart
SHB-8 Clore/handoff : B2B privacy role ops → #443 SH-6
SHB-5 approval_pending flow
If approval_status pending → bot_shcart_approval_status cite approver masked + bot_shcart_approver_nudge resend if under limit. No checkout_url SHB-7 règle 3.
SHB-6 permission_denied
Role viewer + edit attempt → bot_shcart_permission_denied + bot_shcart_role_explain + suggest owner upgrade or bot_shcart_route_scart438 fork.
SHB-6 checkout_guide
If approval approved + checkout_role owner_only → bot_shcart_checkout_guide owner email masked must pay. If approver_after_gate → cite gate green then owner checkout.
SHB-6 conflict_explain
Pull audit last_write timestamp SHB-5. bot_shcart_conflict_explain cite conflict_resolution + bot_shcart_cart_summary current state.
SHB-2 no shared cart
Zero shared_cart_id save token only → bot_shcart_route_scart438 explain difference co-achat vs save solo.
SHB-8 session log
Log shared_cart_id_hash, participant_role, approval_status, shcart_bot_action, nudge_sent Y/N. Dashboard KPI section 9.
SHB-7 gate green checkout URL
Only inject checkout_url when approval_status approved AND participant matches checkout_role. Log gate check SHB-8 audit.
Quelle policy SHCART-BOT documenter ?
La policy bot panier partagé SHCART-BOT reprend SHCART-SUP #443 avec garde-fous IA.
Huit règles SHCART-BOT
SHCART-MAP only : roles approval checkout from JSON #443
App API grounded : SHB-5 approval_status collaborators, pas LLM invent
No approval bypass : no checkout_url if approval_required pending
Resend invite within limit : 3x per invitee per 24 h SHCART-SUP règle 4
No role change bot : upgrade editor ops → handoff #443 SHB-7
No PII leak : viewer cart summary no owner address payment
Conflict policy cite : conflict_resolution SHCART-MAP not guess
Max 8 turns shcart flow : puis /pages/shared-cart or handoff #443
Corpus RAG sources
/pages/shared-cart, SHCART-MAP #443, SHCART-SUP #443, macros SHCART-ROLE SHCART-APPROVE from #443 section 7.
Approver nudge limit
bot_shcart_approver_nudge max 2 per cart per 24 h. Beyond → handoff #443 owner options.
Revue mensuelle bot shcart
Audit 20 transcripts : zero checkout bypass pending, zero role change bot, zero PII leak viewer, handoff timely B2B.
Sync webhook approval
App approval event → invalidate bot session cache. Next message cites fresh approved status within 30 s SLA.
Quels guardrails protègent approval et permissions ?
La matrice bot shcart autorisé vs interdit protège approval gate et confidentialité.
Actions autorisées bot
Lookup shared_cart_id + participant verify SHB-2
Explain role viewer editor approver owner
Cite approval_status pending approved rejected
Resend invite within limit
Nudge approver email within nudge limit
Guide checkout_role who pays after gate green
Explain conflict_resolution refresh lock
Cart summary lines total read-only
Actions interdites bot
Checkout URL if approval pending
Change collaborator role without ops
Reveal owner payment address to viewer
Approve or reject cart as bot impersonating approver
Invent approval_status hallucination
Remove contributor execute
Anti-hallucination approval
Template : « Statut validation : [API approval_status]. [Approver masqué] depuis [date API]. » Voir prévention hallucinations.
Approver impersonation block
Bot never clicks approve API. Direct approver to email CTA one-click mobile only.
CNIL collaborator scope
Participant email lookup legitimate co-achat. Log SHB-8 hash. No store collaborator PII post-session.
Viewer cart summary scope
bot_shcart_cart_summary : SKU qty line total only. No shipping address payment method owner contact.
Comment brancher SHCART-MAP #443 et app Shared Cart ?
L'intégration bot panier partagé combine SHCART-MAP, shared cart API et invite resend.
Champs read SHCART-BOT
shared_cart_id : UUID or app cart id
participant_email : match collaborators[] role
participant_role : owner editor viewer approver
approval_status : pending approved rejected null
approver_email_hash : masked display
checkout_role : owner_only any_editor approver_after_gate
resend_count_24h : invite and nudge counters
Apps Shopify Shared Cart exposent REST webhooks collaborators et approval events (Shopify App Store, shared cart 2026).
SHB-2 invite token join
Deep link invite token maps participant before email typed. Highest shcart_bot_auth_success join rate.
Approval webhook sync
Real-time approval_status update RAG cache. Bot cite fresh state post-approver click under 30 s.
Integration Qstomy
Voir intégration Shopify + SHCART-MAP RAG sync on policy update #443.
OOS price notify bot
If cart line inventory change webhook → proactive bot_shcart_cart_summary delta all collaborators optional T5.
Route post-approval checkout fail
Gate green but payment error → reroute checkout bot #292 not shcart permission macros.
Multi-collaborator list masked
SHB-5 returns collaborator count and roles summary without full email list PII. Owner session may see full list app UI.
Quels triggers UX et touchpoints pour SHCART-BOT ?
Le déploiement UX SHCART-BOT maximise co-achat self-service pre-ticket.
Cinq placements widget
Shared cart page T1 : « Aide co-achat » chip SHB-1
/pages/shared-cart T3 : bot embed FAQ + live lookup
Invite email T4 : deep link bot guest join guide
Approval pending badge T1 : « En attente ? Discuter » opens bot
Proactive T5 48 h : approver nudge segment + owner status bot
Structured lookup SHB-2
Fields shared_cart_id or invite token + email. Pre-fill cart id from URL param shared cart page.
Role badge + bot chip
UI « Vous êtes : Viewer » + chip « Pourquoi je ne peux pas modifier ? » auto bot_shcart_permission_denied.
Approver mobile CTA parity
Bot cite same approve reject URLs as email template #443. Reduces mobile approver stuck.
Cart page fork disambiguation
Modal share co-achat vs save #437 : bot opening question « Co-achat live ou copie solo ? » routes SHCART vs SCART.
B2B team cart handoff chip
shcart_team_b2b detected → bot_shcart_handoff_443 + équipe vente CTA after 2 turns.
A/B approver nudge copy
Variant A rappel vs B urgence event date : measure shcart_approval_nudge_success 4 semaines approval_gate cohort.
Quels KPI shcart bot mesurer ?
Les KPI bot paniers partagés lient deflection, approval nudge et conversion co-achat.
Huit métriques clés
shcart_bot_resolution_rate : résolu sans handoff / sessions shcart_bot
shcart_bot_ticket_delta : baisse tickets #443 vs baseline
shcart_approval_nudge_success : approved within 24 h post nudge / nudges sent
shcart_bot_invite_resend_rate : resends / invite intents
shcart_bot_checkout_guide_rate : checkout completed post bot guide / guide sessions
shcart_bot_handoff_443_rate : B2B privacy role ops routed
shcart_bot_route438_rate : misroute save solo corrected
shcart_bot_csat : satisfaction tag shcart_bot resolved
Benchmark DTC
shcart_bot_resolution 82-88 %, shcart_bot_ticket_delta -48-58 %, approval_nudge_success 65-75 %, shcart_bot_csat > 4,2/5, handoff_443 < 14 %.
Dashboard mensuel
Intent breakdown, approval pending bot vs email nudge, permission_denied resolution, conflict explain sessions, shared_to_order post bot.
Audit approval bypass
Transcript scan checkout_url before approval approved count zero. Violation P1 same day.
T1 shared cart page attach rate
Track widget open on collaborative cart sessions. Target T1 attach > 25 % reduces permission tickets.
Permission denied resolution funnel
Track bot_shcart_permission_denied → fork #438 vs owner upgrade request. Optimize UX role badge copy monthly.
Quels anti-patterns éviter sur bot panier partagé ?
Douze anti-patterns bot panier partagé à bannir.
1. Checkout link pending approval
Règle 3 no bypass. Budget dispute chargeback risk.
2. Confondre save #438
SHB-2 shared_cart_id gate. SCART macros wrong flow.
3. Role upgrade bot
Règle 5 handoff #443. Owner grant only ops.
4. Bot approves cart
Never impersonate approver API click.
5. PII owner to viewer
Règle 6 cart summary items only.
6. Invent approval status
Règle 2 API grounded. « Probablement validé » interdit.
7. Resend invite illimité
Règle 4 spam approver collaborator.
8. Ignore conflict policy
Règle 7 cite SHCART-MAP conflict_resolution.
9. Group gift #433 pre-checkout
Split pay post-order ≠ shcart approval bot scope.
10. Deploy bot before SHCART-SUP
#443 SHCART-MAP prérequis. Bot sans policy = wrong role answers.
11. No T1 shared cart widget
Highest intent moment missed on collaborative cart page.
12. SHCART-MAP stale RAG
checkout_role change without reindex = wrong bot_shcart_checkout_guide.
13. Bot remplace approver email
Erreur : disable approver email rely bot nudge only. Email CTA one-click reste canal primaire conversion.
Comment Qstomy automatise le co-achat panier partagé ?
Qstomy sur Shopify exécute SHCART-BOT : SHB-2 lookup participant, bot_shcart_role_explain SHCART-MAP, bot_shcart_approval_status API, approver nudge within limit, bot_shcart_checkout_guide post gate green, handoff #443 B2B privacy champs pré-remplis.
Capacités bot_shcart Qstomy
bot_shcart_lookup : SHB-2 shared cart verify
bot_shcart_approval_read : status approver masked
bot_shcart_invite_resend : limit check resend
bot_shcart_approver_nudge : Klaviyo trigger
bot_shcart_checkout_template : SHCART-CHECKOUT style
bot_shcart_handoff_ticket : #443 ops pre-fill
Pipeline #443 → #444
#443 SHCART-SUP SHCART-MAP prérequis. #444 bot tier 1 deflect 85 %+ permission approval. Shared policy human B2B privacy.
Scénario DTC chiffré
180 shared carts/mois, 34 tickets baseline #443, SHCART-MAP publiée.
Après SHCART-BOT Qstomy : shcart_bot_resolution 86 %, shcart_bot_ticket_delta -55 %, shcart_approval_nudge_success 73 %, shcart_bot_csat 4,5/5.
Explorez support client et demander une démo.
Continuity reroute
Post checkout success → order lookup GORD-BOT #442 if guest. One brand conversation.
Corpus entraînement shcart
Feed SHCART-MAP + 40 transcripts SHB-8 anonymisés pour intent bot_shcart tuning. Revue trimestrielle avec équipe #443.
Quelle checklist pour déployer SHCART-BOT ?
Checklist SHCART-BOT (12 étapes)
Publier SHCART-MAP #443 + /pages/shared-cart
Documenter policy SHCART-BOT 8 règles
Configurer 12 intents bot_shcart_* section 3
Implémenter flow SHB-1 à SHB-8 shared cart API
Deploy T1 shared cart page + T3 FAQ widget
Invite email T4 deep link + guest join guide
Guardrails no approval bypass + no role change bot
Approver nudge limit + handoff #443 template
Router shcart vs scart438 vs group433 disambiguation
Tags shcart_bot_* + dashboard KPI section 9
Tests staging 8 scénarios approval pending, role viewer, checkout owner, conflict, handoff B2B
RAG sync SHCART-MAP on policy change
En bref
#444 = bot co-achat, pas SAV agents #443
SHCART-BOT : rôle approval checkout invite nudge
No bypass approval : checkout après gate vert
Handoff #443 : B2B privacy role change ops
KPI shcart_bot_resolution : cible > 85 %
FAQ
Bot vs agents #443 ?
#443 exécute role change B2B privacy. #444 bot tier 1 explain nudge resend.
Différence bot save #438 ?
#438 restore fork solo. #444 co-achat live shared_cart_id.
Approbateur ne répond pas ?
bot_shcart_approver_nudge limit 2x/24h puis handoff #443.
Viewer veut modifier ?
bot_shcart_permission_denied + owner upgrade or fork #438.
Qui paie ?
bot_shcart_checkout_guide checkout_role SHCART-MAP après approval.
Aller plus loin
Cette semaine : validez SHCART-MAP #443, configurez intents bot_shcart_*, déployez widget T1 page panier partagé, testez SHB-5 approval pending no checkout URL, lancez dashboard shcart_bot_resolution.
Partagez ce guide #444 avec product et support : un bot co-achat qui cite le bon rôle vaut dix validations conjointes, un lien checkout avant approbation vaut une dispute budget et cinq chargebacks.
Formation ops bot shcart
Module 1 : SHB-2 gate shared vs save. Module 2 : approval bypass audit. Module 3 : handoff #443 champs. Go-live sign-off support lead.
Enzo
1 juillet 2026
