E-commerce
July 1, 2026
"The bot says the item is available when it is sold." "The AI gives me the owner's number for after-sales service." "Chatbot promises a free return on a final sale consigned item." Three failures where a badly calibrated consignment bot over-promises availability or externalizes after-sales service.
A consignment AI chatbot does not replace CONSIGN agents (#623). It reads CONSIGN-MAP, checks availability_status API, quotes shop after-sales return status, and hands off SNAD refund to humans.
This guide #624 covers intents bot_consign_*, flow CONSIGNbot, and KPI consign_bot. Pair bot of the playbook CONSIGN (#623). New AI use case: explaining return status availability without exposing consigner or promising refund.
Summary
Why automate consignment shops with a bot?
"Who is selling it?", "is the item still there?" and "can I return it if the condition does not suit me?" come up on luxury and vintage consignment listings. A calibrated bot cites CONSIGN-MAP, looks up availability_status and explains the shop's primary after-sales service without contacting the consignor.
What the tier 1 bot resolves
Explain model: seller consignment-store customer_copy record
Item availability: active availability_status API reserved sold
Condition grade: condition_grade photos expectation map
Return limits: return_policy_scope cites without promise
After-sales representative: shop_primary sav_responsible_party cites
DTC consignment programs convert better when the after-sales and return model are clear right from the PDP (McKinsey, luxury resale 2026). The bot intercepts bot_consign_return_limits before a NO-RETURN-PROMISE violation.
CONSIGNbot vs CONSIGN #623, second hand #287, USEDDEF #618 and deposit #412
Five types of content, five distinct third-party stock or pre-owned models.
Quick Matrix
#624 CONSIGNbot: tier 1 bot available return state after-sales handoff
#623 CONSIGN: agents SNAD refund sync consignor escalate
Recommerce bot #287: second hand grading SNAD distinct consigned
USEDDEF bot #618: declared defect outlet as-is distinct
Consigne #412: packaging deposit not consignment store
Pipeline: bot explain availability return tier 1 → #623 SNAD refund refuse sync consignor ops.
Which bot_consign_* intents should be configured?
Eight consignment shop bot intents mapped to consign_* typologies #623.
Eight bot_consign intents
bot_consign_explain: customer_copy how works shop record
bot_consign_availability: availability_status API lookup
bot_consign_condition: condition_grade photos expect map
bot_consign_return_limits: return_policy_scope NO-RETURN-PROMISE
bot_consign_sav_info: sav_responsible_party shop_primary cite
bot_consign_auth_info: authenticity_verified process cite
bot_consign_sold_check: sold still listed explain sync
bot_consign_handoff: SNAD refund dispute → #623
Tier 1 auto: explain, availability, condition, return_limits, sav_info, auth_info if CONSIGN-MAP + listing API.
bot_consign_handoff SNAD post-purchase dispute → agents #623 payload listing_id order_ref photos.
How do I use CONSIGN-MAP #623?
The bot reads CONSIGN-MAP #623: consign_program_id, listing_id, condition_grade, condition_photos_urls, authenticity_verified, availability_status, return_policy_scope, sav_responsible_party, snad_vs_declared_rule, customer_copy.
Lookup grounded
PDP consign badge detect: listing_id → CONSIGN-MAP row
AVAIL-STATUS-VERIFY-BOT: listing API before dispo cite
NO-CONSIGNOR-CONTACT-BOT: never consignor coordinates to client
NO-RETURN-PROMISE-BOT: return cite return_policy_scope map only
NO-REFUND-BOT: refund execute agents #623 only
SH286-REROUTE-BOT: C2C peer resale → #287 recommerce bot distinct
Alignment anti-hallucination (#123): support return SAV = CONSIGN-MAP + availability API whitelist only.
CONSIGNBOT-SUP policy in six rules
Six rules for a safe consignment shop bot.
CONSIGN-MAP-GROUNDED: return status from AFTER-SALES SERVICE from map only
AVAIL-STATUS-VERIFY-BOT: API listing before availability quote
NO-CONSIGNOR-CONTACT-BOT: bot never shares owner contact details
NO-RETURN-PROMISE-BOT: bot does not promise returns outside of return_policy_scope
NO-REFUND-BOT: refund handoff #623 workflow CN-7 only
SNAD-HANDOFF-BOT: post-purchase condition dispute → #623 agents review
CONSIGNbot Flow CNB-1 to CNB-8
Eight-step consignment bot flow.
CNB-1 Classify: bot_consign_* intent detect
CNB-2 Collect: listing_id order_ref question pre post purchase
CNB-3 CONSIGN-MAP: status return customer service auth customer_copy
CNB-4 Listing API: availability_status reserved sold verify
CNB-5 Guardrail: NO-CONSIGNOR NO-RETURN-PROMISE NO-REFUND
CNB-6 Respond: TPL-CONSIGNbot grounded map API
CNB-7 Handoff: SNAD refund sold_listed → #623
CNB-8 Log: intent listing_id tag consign_bot
Example TPL-CONSIGNbot-AVAIL
"Listing [listing_id]: status [API availability_status map]. [If active: available now buy it now unique item.] [If sold: sold, removal from PDP in progress.] Bot cannot reserve items outside of checkout basket."
TPL-CONSIGNbot and touchpoints templates
Four essential templates.
TPL-CONSIGNbot-EXPLAIN
Article [listing_id] consignment boutique: [customer_copy map]. Seller of record: [boutique]. Unique piece. Condition: [condition_grade]. Auth: [authenticity_verified map]. Return: [return_policy_scope map].
TPL-CONSIGNbot-AVAIL
Listing [listing_id]: [availability_status API]. [If active: purchase possible now.] [If reserved: customer checking out.] [If sold: no longer available.] No bot reservation holds.
TPL-CONSIGNbot-RETURN
Return [listing_id]: [return_policy_scope map verbatim]. Declared condition: [condition_grade photos condition_photos_urls]. Change of mind on aesthetics: [according to map none / 14d_retract]. Bot does not validate post-purchase SNAD returns.
TPL-CONSIGNbot-HANDOFF
Request [SNAD / refund / sold still visible] forwarded to support team. Listing [listing_id] order [order_ref]. SLA [handoff_sla map].
Touchpoints
Consigned PDP badge: bot_consign_explain embed
Condition photo block: bot_consign_condition widget
Checkout ack consign: bot_consign_return_limits chip
Post-purchase FAQ Customer Service: bot_consign_sav_info entry
Edge cases and reroutes
Five cases outside tier 1 standard consignment bot.
Post-purchase SNAD dispute: SNAD-HANDOFF-BOT #623 CONSIGN-SNAD-01
Direct refund bot: NO-REFUND-BOT handoff #623 CN-7
Doubtful luxury authenticity: auth doubts bot + quality handoff
Second hand stock shop: SH286-REROUTE-BOT #287 distinct
Packaging deposit: #412 DEPOSIT reroute distinct
Bot never executes refunds nor shares consignor contact: agents #623 SNAD photo triage compare.
Essential consign_bot KPIs
Five CONSIGNbot steering metrics.
consign_bot_explain_deflect: explain model resolved without agent
consign_bot_avail_deflect: availability resolved TPL-AVAIL API
consign_bot_return_deflect: return limits resolved TPL-RETURN
consign_bot_handoff_rate: SNAD refund / total consign bot
consign_bot_consignor_leak_rate: exposed owner contact target audit 0
Target: consign_bot_consignor_leak_rate 0 and consign_bot_avail_deflect higher than 65% with API sync listing.
CONSIGNbot anti-patterns
Five common mistakes with consignment bots.
Promise availability without API: AVAIL-STATUS-VERIFY-BOT listing lookup
Shared consignor contact: NO-CONSIGNOR-CONTACT-BOT shop SAV only
Promise return on final sale: NO-RETURN-PROMISE-BOT return_policy_scope
Direct refund bot: NO-REFUND-BOT handoff #623
Confusing second-hand: SH286-REROUTE-BOT #287 distinct consignment
CONSIGNbot with Qstomy
Qstomy on Shopify: detect bot_consign intent, CONSIGN-MAP RAG grounded, listing availability API, SAV party cite, handoff #623 SNAD payload listing_id.
Pipeline: #624 bot explain dispo retour tier 1 → #623 SNAD refund sync consignor escalate.
Explore AI support and request a demo.
Checklist, FAQ and going further
CONSIGNbot Checklist (8 steps)
Sync CONSIGN-MAP #623: RAG bot PDP consigned
Policy CONSIGNBOT-SUP: 6 NO-CONSIGNOR-CONTACT rules
8 intents bot_consign_*: flow CNB-1 to CNB-8
4 templates TPL-CONSIGNbot-*: EXPLAIN AVAIL RETURN HANDOFF
Listing availability API: connect CNB-4 verify sold active
Checkout ack widget: bot_consign_return_limits entry
Red team 10 prompts: avail sold promised contact owner return promised
Dashboard KPI: consign_bot_* section 9
FAQ
Difference #623?
#623 = agents SNAD refund sync consignor escalate. #624 = bot tier 1 explain avail return handoff.
Bot gives owner contact?
No. NO-CONSIGNOR-CONTACT-BOT SHOP-SAV-PRIMARY map.
Return promised bot?
No. NO-RETURN-PROMISE-BOT return_policy_scope map cite only.
Difference recommerce bot #287?
#287 = second hand stock shop grading. #624 = consignment unique piece third parties.
Going further
This week: index CONSIGN-MAP RAG, connect listing API bot, red team contact consignor exposed.
Enzo
July 1, 2026
