E-commerce

AI chatbot for catalog removal: explain timing, alternatives, and remaining stock

AI chatbot for catalog removal: explain timing, alternatives, and remaining stock

July 1, 2026

"The bot promises 50 remaining units while the API says 3." "The AI claims the fragrance will return to the collection." "Chatbot suggests a substitute outside of PRODRET-MAP." Three failures where a poorly calibrated catalog removal bot invents stock, promises restock, or improvises alternatives.

An e-commerce catalog removal AI chatbot does not replace PRODRET agents (#699). It reads PRODRET-MAP, performs Shopify inventory API lookups, cites last_order_cutoff alternative_sku_recommendations, and overrides handoff rush notify post_sav to humans.

This guide #700 covers intents bot_prodret_*, flow PRODRETbot, and KPI prodret_bot. Bot pair of the PRODRET playbook (#699). AI product end-of-life usecase: explain timing, stock, and alternatives without promising restock or inventing quantities.

Summary

Why automate catalog removal by bot?

"Until when can I order?", "how many in stock?" and "what should I get instead?" skyrocket as soon as the last chance badge appears on the PDP. A calibrated bot cites PRODRET-MAP cutoff delist, inventory API qty, and alternative_sku without promising restock or inventing stock.

What the tier 1 catalog retirement bot resolves

  • Cutoff timing: last_order_cutoff_date delist_date map

  • Remaining stock: inventory API qty cite map

  • Alternatives: alternative_sku_recommendations map

  • Restock policy: reassort_policy no_restock cite

  • Post-sales support explanation: post_retirement_support_policy map

Shopify inventory levels API and product archived status frame grounded stock answers (Shopify, inventory API 2026).

PRODRETbot vs PRODRET #699, PRODUPDbot #672, OUTLETbot #690 and LOWSTOCKbot #660

Five pieces of content, five distinct end-of-life product moments.

Quick matrix

Pipeline: #700 bot timing stock alt tier 1 → #699 agents rush notify post_sav escalate.

Which bot_prodret_* intents should be configured?

Eight catalog withdrawal bot intents mapped to prodret_* typologies #699.

Eight bot_prodret intents

  • bot_prodret_timing: last_order_cutoff delist_date map

  • bot_prodret_stock: inventory API qty STOCK-API-CITE

  • bot_prodret_alternative: alternative_sku_recommendations map

  • bot_prodret_reassort: reassort_policy NO-REASSORT-PROMISE

  • bot_prodret_post_sav: post_retirement_support_policy explain

  • bot_prodret_accessories: accessories_avail_after map

  • bot_prodret_notify: stock alert explain handoff

  • bot_prodret_handoff: rush notify post_sav → #699

Tier 1 auto: timing, stock, alternative, reassort if SKU PRODRET-MAP + inventory API + guardrails.

bot_prodret_handoff rush notify post_sav → agents #699 payload sku intent urgency.

How should PRODRET-MAP #699 be consumed?

The bot reads PRODRET-MAP #699: prodret_program_id, retiring_sku, last_order_cutoff_date, delist_date, stock_limited_flag, reassort_policy, alternative_sku_recommendations, post_retirement_support_policy, accessories_avail_after, customer_communication_copy.

Lookup grounded

  • TIMING-CITE-BOT: last_order_cutoff_date delist_date cite map verbatim

  • STOCK-API-CITE-BOT: inventory qty API before stock respond

  • NO-STOCK-INVENT-BOT: no invented qty outside API map

  • NO-REASSORT-PROMISE-BOT: reassort_policy cite no_restock ever

  • ALT-RECOMMEND-CITE-BOT: alternative_sku_recommendations map only

  • NO-ALT-INVENT-BOT: no substitute outside map whitelist

  • POST-SAV-EXPLAIN-BOT: post_retirement_support_policy explain handoff

  • PRODRET699-HANDOFF-BOT: rush notify post_sav → #699 agents PR-7

Alignment anti-hallucination (#123): timing stock alternatives = PRODRET-MAP + inventory API only.

PRODRETBOT-SUP policy in six rules

Six rules bot removal catalog responsible.

  1. PRODRET-MAP-GROUNDED-BOT : timing alt replenishment from map only

  2. TIMING-CITE-BOT : cutoff delist cite before urgency respond

  3. STOCK-API-CITE-BOT : inventory API qty before stock promise

  4. NO-REASSORT-PROMISE-BOT : reassort_policy cite never return promised

  5. ALT-RECOMMEND-CITE-BOT : alternative_sku map only not invented

  6. NO-RUSH-EXECUTE-BOT : notify rush ship agents #699 never bot alone

Flow PRODRETbot PRB-1 to PRB-8

Flow eight steps bot catalog removal.

  1. PRB-1 Classify: bot_prodret_* intent detect PDP badge chat widget

  2. PRB-2 Collect: sku variant product context urgency

  3. PRB-3 PRODRET-MAP: cutoff delist reassort alt post_support accessories

  4. PRB-4 Inventory lookup: Shopify inventory API qty variant map

  5. PRB-5 Guardrail: TIMING STOCK NO-INVENT NO-REASSORT ALT-RECOMMEND

  6. PRB-6 Respond: TPL-PRODRETbot grounded customer_communication_copy

  7. PRB-7 Handoff or close: notify rush post_sav #699 payload

  8. PRB-8 Log: intent prodret_program_id tag prodret_bot timing stock handoff Y/N

Example TPL-PRODRETbot-TIMING

“ [retiring_sku map]: last order [last_order_cutoff_date map]. PDP removal [delist_date map]. Current stock [inventory API qty]. [customer_communication_copy map.] TIMING-CITE-BOT STOCK-API-CITE-BOT. ”

TPL-PRODRETbot and touchpoints templates

Four essential templates.

TPL-PRODRETbot-TIMING

Program [prodret_program_id] [retiring_sku]: order before [last_order_cutoff_date map]. PDP retired [delist_date map]. [customer_communication_copy map.] TIMING-CITE-BOT.

TPL-PRODRETbot-STOCK

Stock [retiring_sku]: [inventory API qty map] unit(s). [stock_limited_flag map.] Order recommended before cutoff. STOCK-API-CITE-BOT NO-STOCK-INVENT-BOT.

TPL-PRODRETbot-ALT

After retirement [retiring_sku map], alternatives: [alternative_sku_recommendations map PDP links]. [If PRODUPD671 upgrade: link upgrade_path.] ALT-RECOMMEND-CITE-BOT.

TPL-PRODRETbot-HANDOFF

Request [notify stock / rush ship / post_sav warranty] forwarded to team. Recap [sku qty intent urgency]. NO-RUSH-EXECUTE-BOT PRODRET699-HANDOFF-BOT.

Touchpoints

  • PDP last chance badge widget: bot_prodret_timing proactive

  • PDP low stock chip: bot_prodret_stock inventory API

  • Chat keyword last chance: bot_prodret_alternative trigger

  • Post-delist FAQ page: bot_prodret_post_sav entry

Edge cases and reroutes

Five cases outside tier 1 bot standard catalog removal.

Bot cites timing stock alt tier 1. Notify rush post_sav warranty → agents #699 PRODRET macros.

Essential prodret_bot KPIs

Five PRODRETbot management metrics.

  • prodret_bot_timing_deflect: timing stock alt resolved without agent

  • prodret_bot_timing_cite_rate: TIMING-CITE-BOT / bot_prodret_timing

  • prodret_bot_stock_api_cite_rate: STOCK-API-CITE-BOT / bot_prodret_stock

  • prodret_bot_reassort_promise_violations: restock promised bot audit target 0

  • prodret_bot_stock_invent_violations: qty invented bot audit target 0

Target: prodret_bot_reassort_promise_violations 0 and prodret_bot_timing_deflect greater than 65%.

PRODRETbot anti-patterns

Five common bot catalog removal errors.

  1. Invented stock bot: STOCK-API-CITE inventory API only

  2. Promised restocking: NO-REASSORT-PROMISE reassort_policy map

  3. Invented cutoff date: TIMING-CITE last_order_cutoff_date map

  4. Alternative outside map: ALT-RECOMMEND-CITE alternative_sku whitelist

  5. Confusing PRODUPDbot #672: version v2 distinct announced commercial removal

PRODRETbot with Qstomy

Qstomy on Shopify: detect bot_prodret intent, PRODRET-MAP RAG grounded, inventory API stock cite, alternatives recommend, handoff #699 rush notify tier 2.

Pipeline: #700 bot timing stock alt tier 1 → #699 agents rush notify post_sav escalate ops.

Explore AI support and request a demo.

Checklist, FAQ and going further

PRODRETbot Checklist (8 steps)

  1. Sync PRODRET-MAP #699: RAG bot PDP badge last chance widget

  2. Policy PRODRETBOT-SUP: 6 TIMING STOCK NO-REASSORT ALT rules

  3. 8 intents bot_prodret_*: flow PRB-1 to PRB-8

  4. 4 templates TPL-PRODRETbot-*: TIMING STOCK ALT HANDOFF

  5. Inventory API sync: Shopify qty bot agents macros test

  6. PDP badge embed widget: bot_prodret_timing proactive cutoff

  7. Red team 10 prompts: invented stock promised restock alt out of map rush bot

  8. Dashboard KPI: prodret_bot_* section 9 timing_deflect violations

FAQ

Difference #699?
#699 = agents rush notify post_sav escalate ops. #700 = bot tier 1 timing stock alt handoff.

Difference PRODUPDbot #672?
#672 = version v2 changelog upgrade. #700 = commercial withdrawal last chance alternatives.

Bot promises restock?
No. NO-REASSORT-PROMISE-BOT TPL-PRODRETbot-REASSORT reassort_policy map.

Reliable stock?
STOCK-API-CITE-BOT inventory API qty only NO-STOCK-INVENT-BOT.

Going further

This week: index PRODRET-MAP RAG PDP widget, sync inventory API bot, red team invented stock restock bot violations.

Enzo

July 1, 2026

Convert over 2,000 customers on average per month with Qstomy.

The world’s 1st Shopify AI dedicated to customer conversion

Empowering 200+ e-commerce merchants

Subscribe to the newsletter and get a personalized e-book!

No-code solution, no technical knowledge required. AI trained on your e-shop and non-intrusive.

*Unsubscribe at any time. We do not send spam.

Subscribe to the newsletter and get a personalized e-book!

No-code solution, no technical knowledge required. AI trained on your e-shop and non-intrusive.

*Unsubscribe at any time. We do not send spam.