E-commerce
July 1, 2026
"The bot confirms an in-store reservation even though the POS hasn't held the item." "The AI sends a BOPIS link instead of the online checkout after a try-on." "Chatbot quotes an invented online price outside of map." Three failures where a poorly calibrated store-to-online bot promises a hold, confuses store pickup #177, or invents price parity.
An AI chatbot for store-to-online e-commerce journeys does not replace INSTTRY agents (#739). It reads INSTTRY-MAP, quotes try_reservation_policy_copy online_checkout_path_copy, looks up stock variant web, and hands off hold price exception to store associates.
This guide #740 covers intents bot_insttry_*, flow INSTTRYbot, and KPI insttry_bot. Companion bot of the INSTTRY playbook (#739). Omnichannel AI use case: guide try-on stock to final purchase without promised holds or BOPIS confusion.
Summary
Why automate the in-store to online journey with a bot?
“How to order after trying on?”, “is my size available online?” and “reserve for 24 hours” arrive post-boutique visit, counter QR code, or store email. A calibrated bot references INSTTRY-MAP reservation checkout price path without confirming hold or routing BOPIS #177.
What the bot resolves tier 1 store to online
Journey explanation: online_checkout_path_copy RESERVE-CITE map
Web stock variant: STOCK-CITE lookup after trying on map
Price parity: price_match_policy_copy PRICE-CITE map
Associate code: associate_referral_code_flag checkout map
Store hours try-on: store_hours_tryon_copy proactive map
McKinsey points out that offline-to-online retail journeys demand stock and checkout consistency (McKinsey, omnichannel 2026). Without a grounded bot, AI promises reservation or confuses try-then-buy and Click & Collect.
INSTTRYbot vs INSTTRY #739, omni bot #272, BOPIS bot and AVAIL #271
Six contents, six distinct omnichannel flows.
Quick Matrix
#740 INSTTRYbot: tier 1 bot stock reservation checkout handoff journey
#739 INSTTRY: agents hold reservation price exception store ops
Omni bot #272: store stock pick-up return general distinct try-then-buy
BOPIS bot #177: online post-purchase pick-up distinct try-on then web checkout
AVAIL #271: cross-channel pre-purchase stock distinct post-fitting map
QR scan #590: fallback store scan distinct final purchase journey
Pipeline: #740 bot stock trial final purchase tier 1 → #739 agents hold reservation price exception store ops.
Which bot_insttry_* intents should be configured?
Eight bot intents for the online store journey mapped to insttry_* typologies #739.
Eight bot_insttry intents
bot_insttry_parcours : online_checkout_path_copy journey explain map
bot_insttry_reservation : try_reservation_policy_copy RESERVE-CITE handoff
bot_insttry_variant : variant_sync_note STOCK-CITE lookup map
bot_insttry_checkout : online_checkout_path_copy deep link send map
bot_insttry_price : price_match_policy_copy PRICE-CITE map
bot_insttry_associate : associate_referral_code_flag checkout map
bot_insttry_oos : insttry_oos alternatives AVAIL271 reroute map
bot_insttry_handoff : hold price exception store → #739
Tier 1 auto: journey, variant, checkout, price if INSTTRY-MAP active + NO-RESERVE-PROMISE guardrails.
bot_insttry_handoff hold reservation price exception → agents #739 payload store sku variant intent.
How should INSTTRY-MAP #739 be consumed?
The bot reads INSTTRY-MAP #739: insttry_program_id, eligible_skus, store_locations, try_reservation_policy_copy, stock_hold_duration_hours, online_checkout_path_copy, price_match_policy_copy, associate_referral_code_flag, variant_sync_note, store_hours_tryon_copy, customer_communication_copy.
Lookup grounded
RESERVE-CITE-BOT: try_reservation_policy_copy cite map verbatim
STOCK-CITE-BOT: variant online availability API lookup map
PRICE-CITE-BOT: price_match_policy_copy cite if discrepancy map
NO-RESERVE-PROMISE-BOT: no hold confirmed bot handoff #739 POS ops
BOPIS177-REROUTE-BOT: post-purchase pickup → #177 C&C distinct try-then-buy
AVAIL271-REROUTE-BOT: pre-purchase stock → #271 AVAIL distinct post-try-on
INSTTRY739-HANDOFF-BOT: hold price exception → #739 agents IT-7
Alignment anti-hallucination (#123): reservation price checkout = INSTTRY-MAP whitelist only.
INSTTRYBOT-SUP policy in six rules
Six bot rules for online store journey owner.
INSTTRY-MAP-GROUNDED-BOT : price reservation journey from map only
RESERVE-CITE-BOT : try_reservation_policy_copy citated without promised hold
NO-RESERVE-PROMISE-BOT : no confirmed hold bot handoff #739 POS ops
STOCK-CITE-BOT : variant availability lookup before checkout link
PRICE-CITE-BOT : price_match_policy_copy citated map only
BOPIS177-REROUTE-BOT : BOPIS collection → pickup bot distinct try-then-buy online
Flow INSTTRYbot ITB-1 to ITB-8
Eight-step store journey bot flow online.
ITB-1 Classify : bot_insttry_* intent detect QR counter email post-visit widget
ITB-2 Collect : store_location sku variant fitting question
ITB-3 INSTTRY-MAP : reservation checkout price associate hours variant
ITB-4 Location lookup : store_locations insttry_flag inventory API verify
ITB-5 Guardrail : RESERVE STOCK PRICE NO-RESERVE BOPIS177 HANDOFF
ITB-6 Respond : TPL-INSTTRYbot grounded customer_communication_copy
ITB-7 Handoff or close : hold price exception store #739 payload
ITB-8 Log : intent insttry_program_id tag insttry_bot reserve_cited checkout_sent handoff Y/N
Example TPL-INSTTRYbot-JOURNEY
« [store_location map] : tried [variant map]. Order online: [online_checkout_path_copy map.] Reservation [stock_hold_duration_hours map] h : [try_reservation_policy_copy map.] RESERVE-CITE-BOT NO-RESERVE-PROMISE-BOT. »
TPL-INSTTRYbot templates and touchpoints
Four essential templates.
TPL-INSTTRYbot-PARCOURS
Store [store_location map] : [online_checkout_path_copy map.] [try_reservation_policy_copy map.] [store_hours_tryon_copy map.] RESERVE-CITE-BOT.
TPL-INSTTRYbot-CHECKOUT
Your [variant map] : web stock [STOCK-CITE-BOT lookup map.] Checkout link : [online_checkout_path_copy map.] [associate_referral_code_flag map if active.]
TPL-INSTTRYbot-PRICE
Web checkout price : [price_match_policy_copy map.] PRICE-CITE-BOT. I cannot confirm beyond the official policy map.
TPL-INSTTRYbot-HANDOFF
Request [hold reservation / price exception / store] forwarded to team. Summary [store_location sku variant intent]. INSTTRY739-HANDOFF-BOT.
Touchpoints
QR store counter poster : bot_insttry_parcours proactive entry
Post-store visit email : bot_insttry_checkout deep link send
Keyword reserve tried size : bot_insttry_reservation NO-RESERVE trigger
PDP widget in-store availability tried : bot_insttry_variant STOCK-CITE lookup
Edge cases and reroutes
Five cases outside tier 1 standard online shop bot.
Customer wants BOPIS pickup: BOPIS177-REROUTE-BOT pickup bot purchase online separate pickup
Cross-channel pre-purchase inventory: AVAIL271-REROUTE-BOT #271 before store visit
Web exclusive SKU: WEBEXbot not tryable permanent store
Consultation appointment: APPT717bot distinct booking walk-in
Hold execute bot: INSTTRY739-HANDOFF-BOT agents #739 POS ops only
Bot explain path tier 1. Hold reservation price exception store → agents #739.
Essential industry bot KPIs
Five INSTTRYbot monitoring metrics.
insttry_bot_parcours_deflect: checkout price path resolved without agent
insttry_bot_reserve_cite_rate: RESERVE-CITE-BOT / bot_insttry reservation path
insttry_bot_reserve_promise_violations: hold promise bot audit target 0
insttry_bot_checkout_click_rate: clicks online_checkout_path / sessions bot_insttry
insttry_bot_bopis_misroute_rate: routed BOPIS on insttry bot / total low target
Target: insttry_bot_reserve_promise_violations 0 and insttry_bot_parcours_deflect greater than 50%.
INSTTRYbot anti-patterns
Five common bot errors in the online store journey.
Confirmed hold bot : NO-RESERVE-PROMISE-BOT handoff #739 POS ops
Confusing BOPIS #177 : BOPIS177-REROUTE-BOT try-then-buy distinct pickup
Invented price bot : PRICE-CITE-BOT price_match_policy_copy map only
Checkout link without stock check : STOCK-CITE-BOT lookup before deep link
Omitted associate code : associate_referral_code_flag checkout path map
INSTTRYbot with Qstomy
Qstomy on Shopify: detect bot_insttry intent, INSTTRY-MAP RAG grounded, stock variant lookup, NO-RESERVE guardrail, handoff #739 ops tier 2.
Pipeline: #740 bot stock trial purchase final tier 1 → #739 agents hold reservation price exception store ops.
Explore AI support and request a demo.
Checklist, FAQ and going further
INSTTRYbot Checklist (8 steps)
Sync INSTTRY-MAP #739: RAG bot QR counter email post-visit PDP
Policy INSTTRYBOT-SUP: 6 rules RESERVE NO-RESERVE STOCK PRICE BOPIS
8 intents bot_insttry_*: flow ITB-1 to ITB-8
4 templates TPL-INSTTRYbot-*: JOURNEY CHECKOUT PRICE HANDOFF
Inventory API sync locations: STOCK-CITE-BOT lookup test agents
QR poster counter embed chat: bot_insttry_parcours proactive
Red team 10 prompts: hold promised BOPIS confused price made up
Dashboard KPI: insttry_bot_* section 9 reserve_violations deflect checkout_click
FAQ
Difference #739?
#739 = agents hold reservation price exception store ops. #740 = bot tier 1 journey stock checkout handoff without promised hold.
Bot confirms store reservation?
No. TPL-INSTTRYbot-HANDOFF NO-RESERVE-PROMISE-BOT INSTTRY739-HANDOFF-BOT.
Difference Click & Collect?
Try-then-buy = store fitting then web checkout. BOPIS → BOPIS177-REROUTE-BOT #177.
Difference omnichannel bot #272?
#272 = stock pickup return general. #740 = store trial journey online purchase map INSTTRY.
Going further
This week: index INSTTRY-MAP RAG QR counter, red team reserve_promise_violations audit, sync email post-visit checkout deep link payload.
Enzo
July 1, 2026
