E-commerce
July 1, 2026
"The bot displayed the order amount to the recipient." "The AI gave the buyer's name on a follow-up request." "The chatbot sends branded tracking with the sender's email visible." Three failures where a poorly calibrated anonymized order bot ruins the surprise faster than an untrained agent.
An e-commerce anonymized order AI chatbot does not replace ANONORDER agents (#695). It reads ANONORDER-MAP, verifies the buyer/recipient role, cites limited tracking recipient_info_scope, and handoffs modify leak to humans.
This guide #696 covers intents bot_anonorder_*, flow ANONORDERbot, and KPI anonorder_bot. Pair bot of the ANONORDER playbook (#695). AI use case: confidential tracking without exposing buyer identity or amount.
Summary
Why automate anonymized order tracking using a bot?
"Where is my secret gift?", "tracking package without revealing who pays" and "I am the recipient, where is the package?" come up frequently before holidays and birthdays. A calibrated bot distinguishes buyer and recipient, quoting status from Shopify without prices or sender's name to the wrong role.
What the tier 1 bot solves - anonymous tracking
Buyer WISMO: full status buyer_info_scope map
Limited recipient tracking: public carrier status without price map
Lookup denied: recipient_lookup_fields explain map
Scope privacy: recipient_info_scope cite map
Delay explained: delay without revealing buyer map
The CNIL reminds of minimization and purpose limitation in customer relations (CNIL, legal bases 2026). The bot intercepts bot_anonorder_recipient_tracking before sharing a branded link that includes prices.
ANONORDERbot vs ANONORDER #695, ANONGIFTbot #550, WISMO and gift #205
Five contents, five distinct privacy layers and tracking scopes.
Quick Matrix
#696 ANONORDERbot: tier 1 bot ROLE-VERIFY tracking scope handoff
#695 ANONORDER: agents modify leak escalate AO-7 ops
ANONGIFTbot #550: sender anonymity revelation consent distinct tracking mechanics
WISMO bot: standard parcel tracking distinct dual-channel anonymity
Gift #205: masked price distinct packaging bot tracking scope
Pipeline: #696 tier 1 limited tracking bot → #695 agents modify leak → #550 or #549 identity revelation upon sender request.
Which bot_anonorder_* intents should be configured?
Eight anonymous tracking bot intents mapped to anonorder_* typologies #695.
Eight bot_anonorder intents
bot_anonorder_buyer_wismo: buyer complete status notification_routing map
bot_anonorder_recipient_tracking: recipient limited tracking PRIVACY-SCOPE
bot_anonorder_role_verify: collect buyer_lookup vs recipient_lookup fields
bot_anonorder_lookup_fail: order not found explain scope map
bot_anonorder_privacy_scope: recipient_info_scope buyer_info_scope explain
bot_anonorder_delay_explain: ETA delay without revealing buyer
bot_anonorder_cross_identity: who sent NO-CROSS-REVEAL reroute
bot_anonorder_handoff: modify leak notification -> #695
Tier 1 auto: buyer_wismo, recipient_tracking, role_verify, lookup_fail, privacy_scope, delay_explain if ANONORDER-MAP + gift_anonymous_flag + ROLE-VERIFY-BOT.
bot_anonorder_handoff modify ship notification leak -> agents #695 payload order_ref role intent.
How do I consume ANONORDER-MAP #695?
The bot reads ANONORDER-MAP #695: anonorder_program_id, gift_anonymous_flag, buyer_lookup_fields, recipient_lookup_fields, recipient_info_scope, buyer_info_scope, notification_routing, tracking_link_type, modify_ship_window, customer_communication_copy.
Lookup grounded
PRIVACY-SCOPE-CITE-BOT: recipient_info_scope cite map verbatim
ROLE-VERIFY-BOT: buyer email match vs recipient shipping match API
NO-CROSS-REVEAL-BOT: never buyer identity to recipient without ANONGIFT550 consent
NO-PRICE-DISPLAY-BOT: amount never displayed to recipient tracking_link_type map
NOTIF-ROUTE-CITE-BOT: notification_routing cite before resend
TRACKING-TYPE-CITE-BOT: tracking_link_type carrier public vs branded map
NO-MODIFY-EXECUTE-BOT: agents address change #695 never bot alone
ANONORDER695-HANDOFF-BOT: modify leak → #695 agents AO-7
Alignment anti-hallucination (#123): scope tracking notifications = ANONORDER-MAP whitelist only.
ANONORDERBOT-SUP policy in six rules
Six rules bot tracked anonymized order responsible.
ANONORDER-MAP-GROUNDED-BOT: lookup scope tracking from map only
ROLE-VERIFY-BOT: buyer vs recipient before status sharing
PRIVACY-SCOPE-CITE-BOT: recipient_info_scope buyer_info_scope cite map
NO-CROSS-REVEAL-BOT: buyer identity never to the recipient without #550 consent
NO-PRICE-DISPLAY-BOT: order amount never to recipient
NO-MODIFY-EXECUTE-BOT: modify ship resend alert agents #695 never bot alone
Flow ANONORDERbot AOB-1 to AOB-8
Eight-step flow for anonymized order tracking bot.
AOB-1 Classify : bot_anonorder_* intent detect chat widget tracking page
AOB-2 Collect : email order_ref zip role claim buyer recipient
AOB-3 ANONORDER-MAP : lookup fields scope tracking notification_routing
AOB-4 Role verify : ROLE-VERIFY-BOT buyer match recipient match API
AOB-5 Guardrail : PRIVACY NO-CROSS NO-PRICE NOTIF-ROUTE TRACKING-TYPE
AOB-6 Respond : TPL-ANONORDERbot grounded customer_communication_copy
AOB-7 Handoff or close : modify leak cross identity #695 #550 payload
AOB-8 Log : intent anonorder_program_id tag anonorder_bot role scope handoff Y/N
Example TPL-ANONORDERbot-RECIPIENT
“Parcel on its way: tracking [tracking_link_type map carrier public]. ETA [API fulfillment]. [recipient_info_scope map verbatim: no sender name or amount.] Questions about the sender: we will contact the buyer if consent is given. PRIVACY-SCOPE-CITE-BOT.”
TPL-ANONORDERbot and touchpoints templates
Four essential templates.
TPL-ANONORDERbot-BUYER
Anonymous gift order [order_ref]: status [fulfillment API map]. Tracking [lien buyer_info_scope map]. Recipient notification: [notification_routing map]. PRIVACY-SCOPE buyer scope.
TPL-ANONORDERbot-RECIPIENT
Parcel tracking [tracking_link_type map] ETA [API]. [recipient_info_scope map verbatim.] NO-PRICE-DISPLAY-BOT NO-CROSS-REVEAL-BOT.
TPL-ANONORDERbot-LOOKUP-FAIL
Order not found with [provided fields]. Anonymous gift: buyer via [buyer_lookup_fields map]. Recipient: [recipient_lookup_fields map] or await delivery. ROLE-VERIFY-BOT.
TPL-ANONORDERbot-HANDOFF
Request [modify address / notification leak / sender identity] forwarded to team. Summary [order_ref role intent gift_anonymous_flag]. NO-MODIFY-EXECUTE-BOT ANONORDER695-HANDOFF-BOT.
Touchpoints
Order tracking page widget: bot_anonorder_role_verify proactive
Gift parcel chat keyword: bot_anonorder_buyer_wismo trigger
Shipping notification email footer: bot_anonorder_recipient_tracking link
Buyer post-purchase: bot_anonorder_privacy_scope explain
Edge cases and reroutes
Five cases outside tier 1 standard anonymous tracking bot.
Who sent the package: ANONGIFT550-REROUTE-BOT #550 reveal consent distinct tracking
WISMO standard non-gift order: WISMO bot full tracking distinct anonymity
Address modification before shipping: NO-MODIFY-EXECUTE-BOT handoff #695 ANONORDER-MODIFY-01
Reported leak notification: bot_anonorder_handoff #695 AO-7 NOTIF-ROUTE audit
Incorrect recipient address: #274 wrong recipient handoff without revealing buyer
Bot cities scope and limited tracking tier 1. Modify ship leak breach → agents #695. Sender identity → #550 or #549.
Essential anonorder_bot KPIs
Five monitoring metrics for ANONORDERbot.
anonorder_bot_wismo_deflect: buyer recipient tracking resolved without agent
anonorder_bot_privacy_scope_rate: PRIVACY-SCOPE-CITE-BOT / bot_anonorder_recipient_tracking
anonorder_bot_cross_reveal_violations: buyer identity revealed bot audit target 0
anonorder_bot_price_display_violations: amount shown recipient audit target 0
anonorder_bot_role_verify_rate: ROLE-VERIFY-BOT before status share
Target: anonorder_bot_cross_reveal_violations 0 and anonorder_bot_privacy_scope_rate greater than 98%.
ANONORDERbot anti-patterns
Five common errors in the anonymized order tracking bot.
Branded tracking to the recipient: NO-PRICE-DISPLAY tracking_link_type map
Status without ROLE-VERIFY: ROLE-VERIFY-BOT buyer recipient match API
Buyer identity revealed: NO-CROSS-REVEAL reroute #550 consent
Modify address bot only: NO-MODIFY-EXECUTE handoff #695 only
Confusing ANONGIFTbot #550: distinct sender revelation tracking status scope
ANONORDERbot with Qstomy
Qstomy on Shopify: detect bot_anonorder intent, ANONORDER-MAP RAG grounded, ROLE-VERIFY buyer recipient, tracking scope explain, handoff #695 modify leak tier 2.
Pipeline: #696 bot limited tracking tier 1 → #695 agents modify leak escalate → #550 disclosure consent if identity.
Explore AI support and request a demo.
Checklist, FAQ and going further
ANONORDERbot Checklist (8 steps)
Sync ANONORDER-MAP #695: RAG bot page tracking anonymous gift widget
Policy ANONORDERBOT-SUP: 6 rules ROLE-VERIFY PRIVACY NO-CROSS NO-PRICE
8 intents bot_anonorder_*: flow AOB-1 to AOB-8
4 templates TPL-ANONORDERbot-*: BUYER RECIPIENT LOOKUP-FAIL HANDOFF
Role verify API sync: buyer email recipient shipping match Shopify
Tracking link types test: carrier public vs branded no price recipient
Red team 10 prompts: price shown identity revealed modify bot alone WISMO confused
Dashboard KPI: anonorder_bot_* section 9 privacy_scope cross_reveal
FAQ
Difference #695?
#695 = agents modify leak escalate AO-7 ops. #696 = bot tier 1 ROLE-VERIFY tracking scope handoff.
Difference ANONGIFTbot #550?
#550 = sender anonymity consent revelation. #696 = status tracking info perimeter without price.
Does bot modify address?
No. NO-MODIFY-EXECUTE-BOT TPL-ANONORDERbot-HANDOFF #695 modify_ship_window.
Does recipient see the amount?
No. NO-PRICE-DISPLAY-BOT recipient_info_scope tracking_link_type carrier public.
Going further
This week: index ANONORDER-MAP RAG tracking widget, test recipient tracking_link_type, red team price identity bot violations.
Enzo
July 1, 2026
