E-commerce
July 1, 2026
"The bot promises deposit refund within 24 hours, that's false." "The AI invents a drop-off point that does not exist." "How to return the bag, the bot answers with greenwashing." Three failures where an ungrounded reusable packaging bot worsens deposit disputes and abandonment of the reuse program.
A reusable packaging e-commerce AI chatbot does not replace REPACK agents (#501). It reads REPACK-MAP, explains return and deposit, cites proof_url, refuses claims outside the map, and hands off deposit disputes and rejected returns.
This guide #502 covers intents bot_repack_*, flow REPACKbot, and KPI repack_bot. Companion bot of the REPACK playbook (#501). New AI use case: packaging deposit return without ops invention.
Summary
Why automate reusable packaging using a bot?
Deposit return questions arrive upon parcel receipt and peak at D+15 if the refund is delayed. A calibrated bot cites REPACK-MAP in seconds, without inventing delays or drop-off points.
What the bot solves
How return: dropoff_methods return instructions from map
Deposit explain: factual return_window_days deposit amount
Refund SLA: refund_sla_days after scan, not an immediate promise
Benefits cite: proof_url documented benefits, not zero waste
Loop recalls that the simplicity of the return journey determines the reuse rate (Loop, reuse packaging 2026).
ECGT (EU) requires substantiation of packaging claims starting September 2026 (European Commission, ECGT 2026). The bot never says "100% reusable" if forbidden_phrases map prohibits it.
REPACKbot vs REPACK #501, ECOship #500 and sustainability #225
Four contents, four packaging and transport responsibilities.
Quick matrix
#502 REPACKbot: bot return deposit tier 1 benefits
#501 REPACK: litigation agents deposit state refusal
#500 ECOship: carbon transport bot checkout
#225 eco global: material sustainability life cycle
#502 = tier 1 how_return deposit explain. #501 = deposit disputes > SLA and contested rejected return.
Which bot_repack_* intents should be configured?
Eight reusable packaging bot intents.
Eight bot_repack intents
bot_repack_how_return: how to return returnable bag box
bot_repack_deposit_explain: deposit amount why how to recover
bot_repack_dropoff_map: where to drop off relay box map
bot_repack_refund_status: deposit refunded when scan status
bot_repack_condition_rules: state criteria accepted refused
bot_repack_benefits: reuse benefits proof proof_url
bot_repack_dispute: handoff #501 deposit not refunded > SLA
bot_repack_damaged: handoff #501 broken packaging upon receipt
Tier 1 auto: how_return, deposit_explain, dropoff_map, refund_status, condition_rules, benefits.
Intent bot_repack_dispute and bot_repack_damaged route to agents #501 with payload order_id, deposit_amount and return_scan_status session.
How should REPACK-MAP #501 be consumed?
The bot reads REPACK-MAP #501: packaging_type, deposit_amount, return_window_days, dropoff_methods, condition_rules, refund_sla_days, proof_url, forbidden_phrases.
Lookup grounded
Order context: packaging_type linked to order if post-purchase
deposit_amount exact: EUR amount map only, no invented rounding
dropoff_methods list: relay box map URL, never an invented address
forbidden_phrases block: 100% reusable zero waste guaranteed
proof_url mandatory: if bot_repack_benefits or eco packaging claim
Mandatory alignment with anti-hallucination (#123): packaging reuse corpus = whitelist REPACK-MAP only.
REPACKBOT-SUP policy in six rules
Six rules bot safe reusable packaging.
NO-PACK-INVENT: never point of return deposit delay outside REPACK-MAP
REFUND-SLA-CITE: refund_sla_days map, no immediate refund
CONDITION-GROUNDED: rejection criteria from condition_rules only
NO-ZERO-WASTE-CLAIM: ECGT: no zero waste without substantiation map
FORBIDDEN-PHRASE block: forbidden_phrases map before sending
DISPUTE-HANDOFF: deposit > refund_sla or contested rejection → #501
Flow REPACKbot RPB-1 to RPB-8
Eight-step reusable packaging bot flow.
RPB-1 Classify: bot_repack_* intent
RPB-2 Context: pre-purchase PDP or post-order packaging_type
RPB-3 REPACK-MAP: lookup deposit dropoff refund_sla
RPB-4 Guardrail: forbidden phrase NO-PACK-INVENT check
RPB-5 Respond: grounded TPL-REPACKbot
RPB-6 Dropoff: access point map, proof_url link if dropoff intent
RPB-7 Handoff: dispute damaged → #501 payload
RPB-8 Log: deposit_cited sla_cited tag repack_bot
Example TPL-REPACKbot-RETURN
"Reusable [type] packaging, deposit [deposit_amount] u20ac. Return within [return_window_days] days via [dropoff_methods]. Refund within [refund_sla_days] days after scan. Guide: [proof_url]."
TPL-REPACKbot templates and touchpoints
Four essential templates.
TPL-REPACKbot-DEPOSIT
Deposit [deposit_amount] € included at checkout. Refund after compliant return within [refund_sla_days] business days. Return window: [return_window_days] days.
TPL-REPACKbot-DROPOFF
Drop off at [dropoff_methods]. Interactive map: [proof_url]#dropoff. Keep proof of deposit until refund.
TPL-REPACKbot-CONDITION
Return accepted if: [condition_rules]. Example photos: [proof_url]#condition. Rejection = deposit non-refundable, criteria details on the help page.
TPL-REPACKbot-BENEFITS
Reuse program: [documented map benefits or proof_url]. No zero-waste claim without published substantiation.
Touchpoints
PDP eco packaging: chip "How to return packaging?"
Post-delivery email: link bot_repack_how_return order context
Order status page: deposit status scan pending refunded
FAQ packaging: bot_repack_benefits pre-purchase conversion
Edge cases and reroutes
Five cases outside tier 1 bot.
Deposit not refunded > SLA: handoff #501 finance ops
SKU product return: reroute returns guide
Carbon transport: reroute ECOship #500
Product material sustainability: reroute #225
Gift wrapping: reroute gift wrap #337
Multi-parcel: bot counts packaging_type per line order, one deposit per unit map, no invented global refund.
Essential repack_bot KPIs
Five REPACKbot monitoring metrics.
repack_bot_auto_resolve: % tier 1 without agent
repack_bot_map_grounded_rate: REPACK-MAP compliant answers
repack_bot_pack_invent_violation: NO-PACK-INVENT, target 0
repack_bot_sla_cited: % with refund_sla_days cited
repack_bot_handoff_dispute: sessions → #501 dispute
Monthly red team: 10 prompts "immediate deposit refund", "relay point rue X", "100% zero waste packaging". Any response off-map = NO-PACK-INVENT violation.
REPACKbot Anti-patterns
Six common mistakes.
Promised 24h refund: REFUND-SLA-CITE violation
Invented pickup point: NO-PACK-INVENT
Generic zero waste: NO-ZERO-WASTE-CLAIM ECGT risk
Confusing product return: reroute returns SKU
Duplicating #500 transport: packaging focus only
Ignoring required scan: OPS-SCAN-REQUIRED #501
REPACKbot with Qstomy
Qstomy on Shopify: REPACK-MAP RAG per order, dropoff map embed, refund_sla guardrail, scan status webhook, handoff #501 payload deposit dispute.
Pipeline: #502 post-delivery how_return → #501 deposit dispute → AI governance #142 audit claims packaging.
Explore AI support and request a demo.
Checklist, FAQ and going further
REPACKbot Checklist (8 steps)
Sync REPACK-MAP #501: RAG bot whitelist only
Policy REPACKBOT-SUP: 6 NO-PACK-INVENT rules
8 intents bot_repack_*: flow RPB-1 to RPB-8
4 templates TPL-REPACKbot-*: RETURN DEPOSIT DROPOFF BENEFITS
Forbidden phrase filter: map forbidden_phrases
Red team 10 prompts: immediate instructions for invented drop-off points
Post-delivery chip return: order page bot_repack_how_return
KPI Dashboard: repack_bot_* section 9
FAQ
Difference #501?
#501 = dispute agents, deposit, refusal, condition. #502 = bot tier 1 how_return and deposit explain.
Difference #500 ECOship?
#500 = carbon transport checkout. #502 = returnable packaging customer return.
Can the bot promise zero waste?
Prohibited unless exact substantiation is provided in REPACK-MAP proof_url.
When is the deposit refunded?
Bot cites refund_sla_days after partner scan, never immediate.
Going further
This week: index REPACK-MAP in bot corpus, test red team "deposit refund tomorrow", measure repack_bot_map_grounded_rate. Publish forbidden_phrases to bot ops console.
Enzo
July 1, 2026
