E-commerce
July 1, 2026
"I paid, the bot says package on the way even though I chose delivery in 2 weeks." "The AI invents a shipping date that is not in my order." "Pre-order or ship later, the bot answers with generic WISMO." Three failures where a poorly calibrated delayed shipping bot exacerbates anxiety or confuses hold stock and preorder.
An e-commerce ship later AI chatbot does not replace SHIPLATER agents (#495). It reads scheduled_ship_date, explains normal unfulfilled, guides modify cutoff, reroute preorder #187, and handoff if ops date is exceeded.
This guide #496 covers intents bot_ship_later_*, flow DELAYSHIP, and KPI delay_ship_bot. Bot pair of the SHIPLATER playbook (#495). Distinct from the WISMO bot (#184): here, voluntary hold before chosen ship date.
Summary
Why automate "ship later" via bot before WISMO?
The ship_later_status tickets (#495) arrive at D+1 post-purchase when the customer sees "unfulfilled". A bot that cites the scheduled date avoids 60 to 70% of tier 1 contacts.
What the bot solves
Pre-ship status: scheduled_date + normal hold
Modify date: cutoff SHIPLATER-MAP + edit link
Pay now explanation: reserves stock, not charge-later
Preorder reroute: tag preorder → #187 branch
Shopify fulfillment holds allow holds until the scheduled release (Shopify, hold 2026).
The bot intercepts premature WISMO before it becomes an agent ticket or chargeback.
DELAYSHIP vs SHIPLATER #495, WISMO #184 and preorder #187
Four bots, four order statuses.
Quick matrix
#496 DELAYSHIP: hold stock, future shipping date selected
#495 SHIPLATER: late ops agents cancel
#184 WISMO: shipped package tracking
#187 preorder: long production
Router: hold tag + scheduled_date → DELAYSHIP. fulfilled + tracking → #184. preorder tag → #187.
Which bot_ship_later_* intents should be configured?
Eight bot intents for delayed shipping.
Eight intents bot_ship_later
bot_ship_later_status: what is the status of my order before the date
bot_ship_later_why_unfulfilled: why has it not shipped yet
bot_ship_later_change_date: modify scheduled date
bot_ship_later_early: ship earlier request
bot_ship_later_pay_now: why immediate charge
bot_ship_later_mixed: cart part now part later
bot_ship_later_vs_preorder: difference preorder explain
bot_ship_later_handoff: date passed cancel complex
Tier 1 auto: status, why_unfulfilled, pay_now, vs_preorder, mixed. Handoff: late, cancel.
How should SHIPLATER-MAP #495 be consumed?
The bot reads SHIPLATER-MAP #495: max_defer_days, modify_cutoff, cancel_before_ship, on_time_sla, hold_tag.
Lookup grounded
scheduled_ship_date: mandatory order metafield
hold tag: ship_later_hold line or order
today vs scheduled: late if today > scheduled + SLA
modify allowed: cutoff date from map
NO-INVENT-DATE: never any date outside of metafield.
DELAYSHIPBOT-SUP policy in six rules
Six bot rules ship later sure.
CITE-SCHEDULED-DATE: date from metafield only
NORMAL-UNFULFILLED: before date = normal status explained
NO-INVENT-DATE: no LLM-invented ETA
ROUTE-PREORDER: preorder tag → #187 not DELAYSHIP
MODIFY-GROUNDED: edit according to modify_cutoff map
LATE-HANDOFF: date passed → #495 P1
Flow DELAYSHIP DSB-1 to DSB-8
Eight-step delayed shipping bot flow.
DSB-1 Classify : bot_ship_later_* intent
DSB-2 Order lookup : auth order + line tags
DSB-3 Branch : preorder WISMO shipped DELAYSHIP
DSB-4 SHIPLATER-MAP : rules modify cancel SLA
DSB-5 Respond : TPL-DELAYSHIP status explain
DSB-6 Action : modify link or early request ops
DSB-7 Handoff : late cancel → #495
DSB-8 Log : scheduled_date intent resolved
Example TPL-DELAYSHIP-STATUS
“Order #{order}: shipping scheduled on {scheduled_date}. Product in stock, voluntary shipping hold. Normal status. Tracking upon shipment.”
TPL-DELAYSHIP templates and touchpoints
Four essential templates.
TPL-DELAYSHIP-WHY
Unfulfilled normal: shipping scheduled for {scheduled_date}. Not a delay.
TPL-DELAYSHIP-MODIFY
Modifiable until {modify_cutoff}: {edit_url}.
TPL-DELAYSHIP-PAY
Immediate payment reserves stock and price. Shipping on {scheduled_date}.
TPL-DELAYSHIP-PREORDER
Pre-order = production in progress. Ship later = stock hold. Your order: {type}.
Touchpoints
Order status page: "My shipping date" chip
Post-purchase D+1: proactive if hold tag
WISMO keyword pre-ship: reroute DELAYSHIP not #184
Edge cases and reroutes
Five cases outside tier 1 bot.
Essential delay_ship_bot KPIs
Five DELAYSHIP steering metrics.
delay_ship_bot_status_resolve: % status without agent
delay_ship_bot_invent_date_violation: NO-INVENT-DATE, target 0
delay_ship_bot_preorder_misroute: preorder poorly served DELAYSHIP
delay_ship_bot_modify_success: % modify within cutoff
delay_ship_bot_handoff_late: sessions date exceeded → #495
Anti-patterns DELAYSHIP
Six common mistakes.
WISMO tracking response: confusing hold with shipped package
Inventing ship date: NO-INVENT-DATE
Preorder production macro: ROUTE-PREORDER
Promising auto early ship: ops ticket required
Ignoring mixed cart: split line status
Duplicating entire #495: bot tier 1 only
DELAYSHIP with Qstomy
Qstomy on Shopify: detect hold tag, scheduled_date lookup, DELAYSHIP branch vs WISMO #184, modify cutoff cite, handoff #495 late payload.
Pipeline: checkout ship date → #496 status D+1 → release hold → #184 tracking.
Explore AI support and request a demo.
Checklist, FAQ and going further
DELAYSHIP Checklist (8 steps)
Sync SHIPLATER-MAP #495: RAG + metafield validator
Policy DELAYSHIPBOT-SUP: 6 NO-INVENT-DATE rules
8 intents bot_ship_later_*: flow DSB-1 to DSB-8
4 templates TPL-DELAYSHIP-*: STATUS WHY MODIFY PAY
Router hold vs preorder vs shipped: 3 test branches
Proactive D+1 hold orders: email + bot chip
Tests for 6 scenarios: status, modify, preorder, mixed, late, no metafield
Dashboard KPI: delay_ship_bot_* section 9
FAQ
Difference #495?
#495 = agents late ops cancel compensation. #496 = bot tier 1 status modify explain.
Difference #184?
#184 = shipped package tracking. #496 = hold before scheduled ship date.
Does bot modify date on its own?
Edit link if modify_cutoff is OK. Outside cutoff → handoff #495.
Go further
p: Gift (#205)
This week: route WISMO pre-ship hold to DELAYSHIP, test NO-INVENT-DATE red team, measure delay_ship_bot_status_resolve.
Enzo
July 1, 2026
