E-commerce
July 1, 2026
"The bot gave me a dead link after the instore scan." "The AI promises -15% while the poster said -10%." "Chatbot confirms pop-up attribution without checking my order." Three failures where a miscalibrated QR code bot invents a promo or off-map URL.
An AI chatbot QR code journey does not replace QR agents (#577). It reads QR-MAP, cites destination_url discount_code cart_prefill, offers session recovery saved cart and handoff attribution exception to humans.
This guide #578 covers intents bot_qr_*, flow QRbot and KPI qr_bot. Partner bot of the QR playbook (#577). New omnichannel AI use case: continue purchase post-scan explain promo without issuing discount or confirming attribution without UTM.
Summary
Why automate the QR code journey with a bot?
"My cart is empty after scanning", "the QR doesn't work", and "does my order count for the pop-up?" skyrocket during retail events. A calibrated bot looks up the QR-MAP, sends the correct destination_url, cites the channel promo, and offers a resume cart without improvising displayed discounts.
What the bot solves (tier 1)
Scan fail redirect: destination_url map if QR is 404
Cart resume: cart_prefill saved cart link
Promo channel citation: discount_code status conditions map
Attribution check: order UTM store_event_id if order_ref
QR validity: valid_from_until map citation
McKinsey estimates that 73% of consumers use multiple channels before purchasing, but the offline-online gap creates tickets if the QR journey is not documented (McKinsey, omnichannel 2026). The bot intercepts bot_qr_scan_help before agents invent promos.
QRbot vs QR #577, BOPIS #177, live #557, AMBbot #576 and promo #111
Five pieces of content, five distinct offline-online journeys.
Quick matrix
#578 QRbot: tier 1 bot scan resume promo attrib
Click & Collect #177: in-store pickup BOPIS distinct
Live #557: code session live replay
AMBbot #576: influencer code distinct attribution
Pipeline: bot scan resume promo cite → #577 attribution exception reissue marketing. Immediate BOPIS → #177 reroute.
Which bot_qr_* intents should be configured?
Eight QR journey bot intents mapped to typologies #577.
Eight bot_qr intents
bot_qr_scan_help : QR fail wrong landing redirect map URL
bot_qr_cart_resume : cart_prefill saved cart session lost
bot_qr_promo_status : discount_code status conditions map
bot_qr_attribution : order UTM store_event_id verify
bot_qr_validity : valid_from_until active or expired QR
bot_qr_product_info : cart_prefill_skus PDP map cite
bot_qr_stock_info : stock online vs offline handoff if mismatch
bot_qr_handoff : expired reissue attribution exception → #577
Tier 1 auto : scan_help, cart_resume, promo_status, validity, product_info if qr_id or UTM detect + QR-MAP + guardrails.
bot_qr_handoff, stock mismatch, attribution dispute → agents #577 payload qr_id order_ref store_event_id.
How do I consume QR-MAP #577?
The bot reads QR-MAP #577: qr_id, destination_url, channel_type, store_event_id, utm_params, discount_code, valid_from_until, cart_prefill_skus.
Lookup grounded
QR lookup: qr_id or utm_content → QR-MAP row
URL verify: destination_url live HTTP check
Shopify Discount API: discount_code status conditions
Order UTM API: Shopify order attribution if order_ref
DEEP-LINK-GROUNDED-BOT: cart_prefill from map only
ATTRIBUTION-VERIFY-BOT: confirm UTM store_event_id API only
Anti-hallucination alignment (#123): Promo URL = QR-MAP or Shopify API only.
QRBOT-SUP policy in six rules
Six bot rules safe QR code journey.
QR-MAP-GROUNDED: URL promo attribution from map only
NO-PROMO-ISSUE-BOT: bot does not issue or replace channel promo
ATTRIBUTION-VERIFY-BOT: confirm UTM attribution API before yes
DEEP-LINK-GROUNDED-BOT: cart_prefill destination_url map only
SESSION-RESUME-BOT: saved cart link map before blame client
BOPIS-LIVE-REROUTE-BOT: in-store pickup → #177, live code → #557
Flow QRbot QBB-1 to QBB-8
Eight-step bot flow for QR code path.
QBB-1 Classify: bot_qr_* intent detect
QBB-2 QR collect: qr_id photo UTM order_ref email
QBB-3 QR-MAP: destination promo channel store_event
QBB-4 URL verify: destination live discount active
QBB-5 Guardrail: NO-PROMO ATTRIBUTION-VERIFY SESSION-RESUME
QBB-6 Respond: TPL-QRbot grounded map
QBB-7 Handoff: expired reissue attrib dispute → #577
QBB-8 Log: intent qr_id tag qr_bot store_event_id
Example TPL-QRbot-SCAN
“QR [qr_id] [store_event_id]: correct link [destination_url map]. Products [cart_prefill_skus]. Promo [discount_code] if eligible. Valid [valid_from_until]. [If scan fail: click this link.] [If expired: handoff agent.]”
TPL-QRbot templates and touchpoints
Four essential templates.
TPL-QRbot-SCAN
QR [qr_id]: [destination_url map]. Products [cart_prefill_skus]. [If 404: direct link above.] Channel [channel_type store_event_id].
TPL-QRbot-RESUME
QR cart recovery [qr_id]: [saved_cart_url or destination_url + cart_prefill]. Promo [discount_code] included if valid. Valid [valid_until].
TPL-QRbot-PROMO
Channel promo [discount_code]: [Shopify status: valid / expired / conditions]. Discount [discount_value map]. Min [min_spend]. Exclusions [exclusions]. Enter at checkout or via [destination_url].
TPL-QRbot-HANDOFF
Request [expired / reissue / dispute attribution] forwarded to agent. QR [qr_id]. Order [order_ref]. Store [store_event_id]. SLA [handoff_sla].
Touchpoints
Post-scan landing embed: bot_qr_cart_resume widget
404 QR fallback page: bot_qr_scan_help entry
Checkout promo error: bot_qr_promo_status chip
Post-purchase chat: bot_qr_attribution order_ref
Edge cases and reroutes
Five cases outside tier 1 standard QR bot.
Expired QR reissue: NO-PROMO-ISSUE-BOT handoff #577 marketing ops
Attribution dispute: ATTRIBUTION-VERIFY handoff #577 QR-ATTR-01
In-store pickup BOPIS: BOPIS-LIVE-REROUTE #177
Live event code: live #557 distinct session code
Post-QR order tracking: WISMO tracking bot
Bot never issues promo: reissue expired attribution dispute → agents #577 marketing ops.
Essential qr_bot KPIs
Five QRbot steering metrics.
qr_bot_scan_deflect: scan_help resolved without agent
qr_bot_cart_resume_rate: cart_resume → checkout started
qr_bot_promo_deflect: promo_status resolved without handoff
qr_bot_handoff_rate: expired reissue attrib / total qr bot
qr_bot_hallucination_rate: promo URL out of audit map
Target: qr_bot_scan_deflect higher than 65% retail event with QR-MAP sync pre-event mobile test.
QRbot anti-patterns
Five common QR bot errors.
Invented URL: QR-MAP-GROUNDED destination only
Validated poster promo: cite discount_code map not poster oral
Attribution without UTM: ATTRIBUTION-VERIFY-BOT order API
Blaming customer for empty cart: SESSION-RESUME-BOT cart_prefill first
BOPIS Confusion: BOPIS-LIVE-REROUTE #177
QRbot with Qstomy
Qstomy on Shopify: detect bot_qr intent, QR-MAP RAG grounded, Shopify discount verify, order UTM lookup, saved cart resume link, handoff #577 expired attribution payload qr_id.
Pipeline: #578 bot scan resume promo → #577 execute marketing escalate.
Explore AI support and request a demo.
Checklist, FAQ and going further
QRbot Checklist (8 steps)
Sync QR-MAP #577: RAG bot + UTM detect
Policy QRBOT-SUP: 6 NO-PROMO-ISSUE-BOT rules
8 intents bot_qr_*: flow QBB-1 to QBB-8
4 templates TPL-QRbot-*: SCAN RESUME PROMO HANDOFF
Post-scan embed: bot_qr_cart_resume widget landing
404 fallback page: bot_qr_scan_help entry
Red team 10 prompts: issued promo invented URL attribution confirmed
Dashboard KPI: qr_bot_* section 9
FAQ
Difference #577?
#577 = agents attribution reissue promo escalate. #578 = bot tier 1 scan resume promo handoff.
Bot creates a promo?
No. NO-PROMO-ISSUE-BOT. Handoff #577 marketing.
Empty cart post-scan?
TPL-QRbot-RESUME cart_prefill saved cart link map.
Attribution pop-up confirmed?
Only if order UTM store_event_id verify API.
Going further
This week: index active QR-MAP in RAG, embed bot post-scan landing, red team promo display non-mapped.
Enzo
July 1, 2026
