E-commerce
July 1, 2026
"I was 47th on the list, why did someone else get theirs before me?" "The pre-order is full but the site is still accepting my payment." "When exactly does my package ship if it's a pre-order limited to 500 units?" Three messages where a poorly explained capped pre-order turns launch excitement into support tickets and chargebacks.
An e-commerce limited pre-order AI chatbot does not replace the agent pre-order policy (#187). It reads capped inventory, queue position, VIP priority, and grounded ship_date, explains the queue and order status, and hands off in case of delay or cancellation.
This guide #405 covers bot_pre_lim_* intents, the WAIT-BOT flow, and lim_pre KPIs. Distinct from pre-order support (#187) (agents, compensation) and the limited edition drop bot (#222): here, AI use cases focus on queue management, customer priority, and capped pre-order transparency.
Summary
Why do limited pre-orders overload the chat?
A limited pre-order sells a future product with a capped quantity (500 units, 2,000 slots) and an estimated shipping date. The customer pays today, waits for weeks, and compares their position to others.
Five typical customer tensions
Opaque queue: "am I still registered?" with no visible number
Unclear VIP priority: early access without clear rules
Cap exceeded: payment accepted even though slots are sold out
Slipping ship date: initial window not met (#187)
Mixed cart: 1 limited pre-order line blocks the shipping of the rest (#357)
Shopify reminds us that a pre-order requires shipping date transparency and proactive delay notification (Shopify, pre-orders 2026). Alhena estimates that 62% of consumers are more likely to buy a limited edition product, but the lack of a response queue multiplies post-drop frustration (Alhena, drop support 2026).
Angle #405 vs neighboring content
Pre-order Support #187: agents, cancellation, compensation. #405 = bot manages queue and transparency 24/7.
LE drop bot #222: instant sold out, live drop stock. #405 = capped pre-order over weeks, not D+0 drop.
Shopify Com #comm: PDP, marketing emails. #405 = post-purchase and pre-purchase queue chat conversation.
Planned Stockout #404: end of line without restock. #405 = dated restock with capped slots.
Prep Bot #396: unfulfilled warehouse delay. #405 = preorder tag + queue before production.
DTC Example
Sneaker brand, limited pre-order of 800 pairs, 8-week ship. Without WAIT-BOT: 214 tickets launch week, queue CSAT 2.9/5. After bot: lim_pre_bot_resolution 78%, queue_position_ticket_rate -61%, chargeback 0.
Limited vs Open Pre-order
Open: no cap, ship date is the only constraint (#187). Limited: capped slots + queue + priority. Two distinct bot configurations.
How does the limited pre-order bot differ from drop #222?
Three product launch models, three bot logics.
Model → bot playbook matrix
#405 WAIT-BOT: capped pre-order, queue weeks, ship_date
#222 drop LE: live stock D+0, sold out in minutes
#187 agents PRE: delay disputes, refund, compensation
Four limited pre-order attributes
preorder_cap: max qty slots (e.g., 800)
preorder_ship_window: grounded production window (e.g., week 12-14)
queue_enabled: waitlist if cap is reached before close
priority_tiers: VIP, newsletter, public (documented order)
Bot conversation cycle
Pre-purchase: remaining cap, queue eligibility, tier priority. Post-purchase: queue position, ship window, production status. Delay: reroute #187 handoff, do not promise via bot alone.
Promise #405
PRE-LIM bot policy, 12 bot_pre_lim_* intents, WAIT-BOT flow, cap guardrails, lim_pre_* KPI.
Which bot_pre_lim_* intents should be configured?
Twelve limited preorder bot intents cover queue and transparency.
Twelve bot_pre_lim intents
bot_pre_lim_cap_remaining: "are there spots left?" pre-purchase
bot_pre_lim_join_waitlist: cap reached, queue sign-up
bot_pre_lim_queue_position: "where am I in the line?"
bot_pre_lim_priority_check: VIP / early access eligibility
bot_pre_lim_ship_date: grounded order delivery estimate
bot_pre_lim_order_status: unfulfilled preorder, production phase
bot_pre_lim_slot_confirmed: validated slot post-payment cap OK
bot_pre_lim_slot_waitlisted: paid but queued, slot not guaranteed
bot_pre_lim_cancel_policy: limited preorder cancellation (#187 reroute)
bot_pre_lim_mixed_cart: preorder cart + standard stock
bot_pre_lim_delay_update: rolling ship window, notification
bot_pre_lim_oversell_detect: cap exceeded, urgent agent handoff
Helpdesk handoff tags
lim_pre, lim_pre_queue, lim_pre_vip, lim_pre_oversell, lim_pre_delay, lim_pre_bot_resolved. Distinct from preorder_general, drop_le.
Upstream router
If order fulfilled → reroute WISMO #184. If unfulfilled without preorder tag → reroute PREP-BOT #396. If cancel/refund request → handoff #187.
How to apply the WAIT-BOT flow in eight steps?
The WAIT-BOT flow structures the limited pre-order response grounded data.
Eight steps WB-1 to WB-8
WB-1 Welcome: "Pre-order AI Assistant [SKU]. Checking your status."
WB-2 Collect: order_id or email + OTP logged-out
WB-3 Lookup: order tags preorder, line_item cap SKU, inventory sold
WB-4 Classify: intent bot_pre_lim_* section 3
WB-5 Queue calc: position, tier priority, slots_remaining
WB-6 Explain: grounded template ship_window + queue status
WB-7 Handoff if needed: oversell, delay > 14 days, cancel refund
WB-8 Close: status portal link, email update opt-in
WB-5 queue position algorithm
Position = rank(order.created_at) among orders tagged lim_pre_confirmed same SKU, adjusted priority_tier (VIP -N positions). Display range "between position 120 and 140" if batch allocation, not exact number if privacy policy.
WB-6 slot_confirmed template
"Your slot #[rank]/[cap] is confirmed. Estimated shipping [ship_window]. Current status: [production_phase]. Email notification if changed."
WB-6 waitlisted template
"Cap reached. You are in queue position ~[rank]. If slot becomes available (cancellation), notification within 24 hours. Refund possible (#187)."
WB-7 handoff ticket fields
order_id, sku, queue_position, priority_tier, cap_sold, ship_window, verbatim, bot_intent.
Which PRE-LIM bot policy should be documented?
The PRE-LIM limited early bot policy governs AI promises and guardrails.
Eight PRE-LIM bot rules
Source cap: Shopify metafield inventory cap or preorder app, read-only bot
Transparent queue: position or range displayed if slot_confirmed or waitlisted
Priority tiers: VIP > newsletter > public, documented /pages/preorder
Ship window: grounded production range, never a firm bot date without metafield
No oversell promise: bot does not confirm slot if cap_sold >= cap_max
Delay reroute: delay > 14 days → handoff #187 compensation
Cancel collect: bot collects reason, agent handoff executes refund
Mixed cart: explain split ship or full hold according to policy #357
Publication /pages/preorder-limited
Total cap, priority tiers, ship window, cancellation policy, queue FAQ. Bot cites URL in WB-6.
Shopify comm sync #comm
PDP and checkout messages aligned with bot templates. No "48h delivery" on limited preorder SKUs.
Weekly review during launch month
Ops update production_phase metafield. Bot reads latest, no stale cache.
What guardrails prevent the bot from over-promising?
The limited early bot allowed vs. forbidden matrix protects the brand and cap.
Bot allowed actions
Lookup cap_remaining live inventory + orders count
Calculate queue position grounded created_at + tier
Explain ship_window metafield production
Register waitlist email if cap full (Klaviyo #48 sync)
Confirm slot_confirmed if order in cap
Explain priority tier eligibility (logged-in tag check)
Create handoff ticket oversell/delay/cancel
Reroute WISMO #184 if fulfilled, PREP #396 if standard unfulfilled
Bot forbidden actions
Confirm slot if cap exceeded (oversell)
Promise firm ship date not grounded
Grant undocumented VIP priority
Process refund or cancel without agent handoff
Commercial gesture compensation (handoff #187)
Modify queue position manually
Hard block oversell
If count(confirmed_orders) > cap_max : bot_pre_lim_oversell_detect → Slack alert + P0 handoff. Template: "Team verification in progress within 4 hours."
Production phase labels
Metafields: tooling, production, QC, inbound_warehouse, ready_to_ship. Bot translates into customer language without factory jargon.
How to integrate Shopify and pre-order apps?
The Shopify limited early bot integration provides cap and queue data without hallucination.
Bot read-only fields
product metafield preorder_cap: max slots
product metafield ship_window_start/end: ISO range
order tag preorder + lim_pre_confirmed: validated slot
order tag lim_pre_waitlisted: queue without slot
customer tag vip_tier: priority eligibility
inventory quantity + continue_selling: cap enforcement
production_phase metafield: factory status
Shopify Admin API orders + product metafields (Shopify, Order API 2026).
Compatible preorder apps
Pre-Order Manager, PreProduct, Timesact: webhook cap_reached → bot trigger waitlist flow. Auto tag lim_pre_* on order create.
Klaviyo waitlist sync
bot_pre_lim_join_waitlist → Klaviyo list #48. Released slot → auto conversion flow before agent contact.
Webhook oversell guard
Order create if count > cap: flag oversell, disable bot slot_confirmed template, immediate bot_pre_lim_oversell_detect route.
How to manage VIP priority and early access?
The PRI-TIER limited preorder priority matrix prevents accusations of favoritism.
Three documented tiers
Tier 1 VIP: LTV > €500 or box subscriber, T-24 h access, queue boost -50 positions
Tier 2 newsletter: registered 30+ days, T-12 h access, boost -20 positions
Tier 3 public: general opening, pure chronological position
Bot priority_check flow
WB-3 lookup customer tags → WB-5 apply boost → WB-6 explain tier + effective position. If not VIP eligible: explain criteria, no bot negotiation.
Customer transparency
"Your tier: Newsletter (T-12 h). Effective position ~85/800 after early access boost." Link /pages/preorder-limited section PRI-TIER.
Distinction drop #222
Drop LE = live stock minutes. PRI-TIER here = preorder window days/weeks. Not Shopify Plus virtual queue checkout alone.
Anti-favoritism
PRI-TIER rules published before launch. Bot cites policy, never invents exception.
Which Bot limit prescription KPIs should be measured?
Limited pre-order bot KPIs drive automation and handoff.
Eight key metrics
lim_pre_bot_resolution_rate: resolved without handoff / lim_pre sessions
queue_position_ticket_rate: "where am I" tickets / total preco orders
waitlist_convert_rate: waitlisted → slot_confirmed / total waitlisted
lim_pre_oversell_incidents: count exceeded cap (target 0)
lim_pre_handoff_rate: escalations #187 / sessions
lim_pre_false_promise: incorrect firm ship promise audit (target 0)
lim_pre_bot_csat: satisfaction sessions tag lim_pre
priority_check_accuracy: tier bot = tier policy / checks
DTC launch benchmark
lim_pre_bot_resolution 70-80%, queue_position_ticket -50% vs without bot, oversell 0, handoff < 22%, bot_csat > 4.2/5.
Launch week dashboard
Sessions by intent, hourly cap_remaining, waitlist growth, oversell alerts, handoff reasons breakdown.
Post-launch months 1-2
delay_update intent trend, ship_window adherence, correlation production_phase updates vs tickets.
Which anti-patterns should be avoided on limited early bots?
Ten capped pre-order bot anti-patterns to avoid.
1. Bot confirms slot without cap lookup
LLM hallucination. WB-3 inventory count mandatory.
2. Invented queue position
Customer checks with agent, contradiction. Deterministic WB-5 algorithm.
3. Mixing up drop #222 and pre-order #405
Drop sold_out intents on capped preorder SKU = confusion.
4. Marketing ship date ≠ prod metafield
PDP "March" vs prod "April". Bot reads prod metafield only.
5. Auto refund bot
Cancel policy #187 = agent or approved workflow. Collect only.
6. Undocumented VIP boost
Queue cheating accusation. Public PRI-TIER before launch.
7. Stale cap cache on launch day
Bot says "200 slots" when actually 0. Live WB-3 refresh.
8. Ignoring waitlisted orders
Customer paid without slot: waitlisted template, not slot_confirmed.
9. No handoff on oversell
Cap +1 = crisis. Immediate P0 alert.
10. Production phase never updated
Bot repeats "tooling" for 8 weeks. Weekly ops update.
11. Mixed cart silence
Customer thinks everything ships D+3. bot_pre_lim_mixed_cart mandatory post checkout.
How does Qstomy manage limited pre-orders?
Qstomy on Shopify: WAIT-BOT with cap lookup, queue position calc, PRI-TIER boost, production_phase templates, oversell hard block, pre-filled handoff #187.
Qstomy lim_pre capabilities
lim_pre_intent_detect: 12 intents section 3
lim_pre_cap_live: inventory + order count WB-3
lim_pre_queue_calc: position + PRI-TIER boost WB-5
lim_pre_ship_grounded: metafield window only
lim_pre_oversell_block: alert + handoff P0
lim_pre_waitlist_klaviyo: sync #48 on join
Complement #187 and #222
Agents #187 execute compensation and disputes. Bot #222 covers instant drops. WAIT-BOT #405 = capped pre-order weeks. Pipeline: transparency bot → exception agent.
Quantified DTC Scenario
Sneakers 800 cap, 6-week ship window, VIP tier 120 clients.
After Qstomy WAIT-BOT: lim_pre_bot_resolution 79%, queue_position_ticket_rate -63%, waitlist_convert_rate 34%, oversell 0, lim_pre_bot_csat 4.3/5.
Explore customer support and request a demo.
What checklist is needed to deploy WAIT-BOT?
WAIT-BOT Checklist (12 steps)
Document cap, ship_window, PRI-TIER policy PRE-LIM
Configure metafields preorder_cap, ship_window, production_phase
Publish /pages/preorder-limited FAQ queue
Align PDP/checkout comms #comm with bot templates
Configure 12 intents bot_pre_lim_* section 3
Implement flow WB-1 to WB-8 + queue algo WB-5
Enable guardrails oversell hard block + no auto refund
Connect Klaviyo waitlist #48 + released slot flow
Setup webhook oversell alert Slack P0
Integrate handoff #187 ticket fields WB-7
Staging tests: cap full, waitlist, VIP boost, oversell, mixed cart
Dashboard KPI lim_pre launch week + audit transcripts
In brief
#405 = capped preorder bot, not LE drop (#222) nor support agents (#187)
WAIT-BOT: cap → queue → ship_window → handoff
PRI-TIER: documented priority, deterministic boost
Guardrails: no oversell, no auto refund, ship grounded
KPI queue_position_ticket_rate: measures transparency success
FAQ
Difference with #222 drop?
#222 = live inventory in minutes, instant sellout. #405 = capped preorder over weeks with queue.
Difference with #187 agents?
#187 = disputes, compensation, cancel execution. #405 = bot queue transparency and 24/7 status.
Display exact position or range?
Range recommended if batch allocation. Exact if documented strict FIFO.
Cap reached mid-checkout?
App preorder block + bot waitlist. Webhook oversell if edge race condition.
Relation with #404 planned OOS?
#404 = end of line without restock. #405 = dated restock with limited slots.
Go further
This week: document cap and PRI-TIER, configure Shopify metafields, enable bot_pre_lim_* intents and test oversell guard in staging.
Share this #405 guide with ops and e-com: a successful limited preorder is as much about the transparent queue as it is about the product.
Can the bot convert waitlist to order?
Not directly. Klaviyo flow #48 sends checkout link for released slot. Bot confirms post-purchase status.
Enzo
July 1, 2026
