E-commerce
July 1, 2026
"The bot says express tomorrow even though the cutoff has passed." "The AI promises a free upgrade without a payment link." "Parcel already shipped, yet the chatbot still proposes express." Three failures where an ungrounded delivery upgrade bot invents feasibility or confuses address changes.
A post-order delivery upgrade AI chatbot does not replace SHIPUP agents (#513). It reads SHIPUP-MAP, cites the cutoff countdown, quotes the exact extra cost, refuses if the parcel is picked or shipped, and handoffs payment ops.
This guide #514 covers bot_ship_up_* intents, the SHIPUPbot flow, and shipup_bot KPIs. Companion bot of the SHIPUP playbook (#513). New AI use case: post-purchase express upgrade feasibility without ops promises.
Summary
Why automate delivery upgrades with a bot?
The "upgrade to express" request arrives minutes after checkout. A calibrated bot reads the fulfillment stage and SHIPUP-MAP in seconds, without promising an upgrade if the WMS has already picked.
What the bot resolves at tier 1
Feasibility check: upgrade_allowed Y/N from map
Cutoff countdown: cutoff_time live Paris timezone
Fee quote: upgrade_fee_eur exact map
Too late explain: fulfillment_stage picked shipped
Zone ineligible: postal code excluded from express, lists alternatives
Shopify Order Editing limits native shipping line modification (Shopify, order editing 2026). The bot intercepts bot_ship_up_express_request before it becomes an urgent agent ticket.
SHIPUPbot vs SHIPUP #513, express #338 and address #183
Four contents, four post-purchase modification layers.
Quick matrix
#514 SHIPUPbot: bot cutoff fee feasibility tier 1
#513 SHIPUP: agents payment ops reprioritisation WMS
#338 EXPRESS: express checkout cut-off promises
#183 address: delivery address change
Pipeline: bot_ship_up fee quote → #513 payment link ops reprioritize if customer confirms upgrade.
Which bot_ship_up_* intents should be configured?
Eight delivery upgrade bot intents.
Eight bot_ship_up intents
bot_ship_up_express_request : upgrade standard to express
bot_ship_up_cutoff_countdown : time remaining before cutoff
bot_ship_up_fee_quote : how much does the upgrade cost
bot_ship_up_too_late : package picked/shipped, refusal
bot_ship_up_zone_check : zip code eligible for express or not
bot_ship_up_gift_urgent : gift for tomorrow, upgrade possible
bot_ship_up_downgrade : express to standard handoff refund
bot_ship_up_confirm_upgrade : customer confirms → handoff #513
Tier 1 auto : express_request, cutoff_countdown, fee_quote, too_late, zone_check if upgrade_allowed map lookup.
Intent bot_ship_up_confirm_upgrade, downgrade and preorder → agents #513 with payload order_id, fee_cited, fulfillment_stage.
How should SHIPUP-MAP #513 be consumed?
The bot reads SHIPUP-MAP #513: from_method, to_method, fulfillment_stage, cutoff_time, upgrade_fee_eur, zone_eligible, upgrade_allowed, wms_action.
Lookup grounded
Order context: shipping line current method CP
Fulfillment API: unfulfilled partial picked shipped
SHIPUP-MAP row: from_method + fulfillment_stage branch
Cutoff calc: now vs cutoff_time Europe/Paris
Fee cite: upgrade_fee_eur exact whitelist only
Alignment anti-hallucination (#123): fee and feasibility = SHIPUP-MAP only.
SHIPUPBOT-SUP policy in six rules
Six rules for safe delivery bot upgrade.
NO-UPGRADE-PROMISE: upgrade only if upgrade_allowed Y map
SHIPUP-MAP-GROUNDED: never fee or cutoff outside map
VERIFY-FULFILLMENT: fulfillment stage before feasibility
NO-FREE-UPGRADE: quote additional cost if upgrade_fee_eur > 0
PAYMENT-HANDOFF: bot does not reprioritize, handoff #513 post-confirm
ADDRESS-REROUTE: address change → distinct #183
Flow SHIPUPbot SUB-1 to SUB-8
Eight-step delivery upgrade bot flow.
SUB-1 Classify : bot_ship_up_* intent
SUB-2 Context : order lookup shipping line CP
SUB-3 Fulfillment : unfulfilled picked shipped API
SUB-4 SHIPUP-MAP : upgrade_allowed fee cutoff zone
SUB-5 Guardrail : NO-UPGRADE-PROMISE VERIFY-FULFILLMENT
SUB-6 Respond : TPL-SHIPUPbot grounded
SUB-7 Confirm handoff : customer OK → #513 payment ops
SUB-8 Log : fee_cited cutoff tag shipup_bot
Example TPL-SHIPUPbot-FEASIBLE
“Express upgrade possible before [cutoff_time] (in [countdown]). Additional fee [upgrade_fee_eur] €. Confirm to receive payment link and pick prioritization.”
TPL-SHIPUPbot templates and touchpoints
Four essential templates.
TPL-SHIPUPbot-FEASIBLE
Express upgrade possible before [cutoff_time]. Additional cost [upgrade_fee_eur] €. Confirm upgrade?
TPL-SHIPUPbot-TOO-LATE
Parcel already [fulfillment_stage]. Upgrade impossible. Current ETA: [current_eta]. See #129 urgent gift.
TPL-SHIPUPbot-FEE
Standard → express difference: [upgrade_fee_eur] €. Payment required before warehouse prioritization.
TPL-SHIPUPbot-NO-ZONE
Express not available for ZIP [postal_code]. Alternative: [alt_method] or change of address #183 if zone is eligible.
Touchpoints
Order status page: "Upgrade to express" chip if unfulfilled
Post-purchase e-mail: bot_ship_up_express_request link 30 min
Help center FAQ upgrade: bot embed cutoff countdown
Peak season widget: gift urgent bot_ship_up_gift_urgent
Edge cases and reroutes
Five cases out of tier 1 bot.
Express checkout #338 : pre-purchase cutoff distinct post-order promises
General order edit : order modification reroutes if distinct intent
Pre-order : upgrade after stock date only handoff #513
Express bot pre-purchase : express checkout bot if not yet ordered
Intercept shipped : handoff #513 ops carrier hold exception
Bot does not modify Shopify shipping line : handoff #513 payment draft + WMS tag express post-confirmation.
Essential shipup_bot KPIs
Five SHIPUPbot steering metrics.
shipup_bot_auto_resolve: % tier 1 without agent
shipup_bot_feasibility_grounded_rate: SHIPUP-MAP compliant responses
shipup_bot_upgrade_promise_violation: NO-UPGRADE-PROMISE, target 0
shipup_bot_fee_cited: % with exact upgrade_fee_eur
shipup_bot_handoff_confirm: sessions confirm → #513 payment
Monthly Red Team: 10 prompts "guaranteed express tomorrow", "free upgrade promised", "express while package shipped". Feasibility out of map = SHIPUP-MAP-GROUNDED violation.
SHIPUPbot anti-patterns
Six common mistakes.
Promised upgrade without fulfillment check: VERIFY-FULFILLMENT
Invented or free fee: NO-FREE-UPGRADE SHIPUP-MAP
Direct bot reprioritization: PAYMENT-HANDOFF #513
Confusing address #183: distinct speed upgrade
Duplicating express #338: post-purchase focus only
Cutoff ignored: CUTOFF-CITE countdown mandatory
SHIPUPbot with Qstomy
Qstomy on Shopify + WMS: detect ship_up intent, SHIPUP-MAP RAG, cutoff countdown widget, fee quote grounded, confirm handoff #513 payment Slack ops.
Pipeline: bot fee feasibility → #513 payment reprioritize → AI governance #142 audit upgrade claims.
Explore AI support and request a demo.
Checklist, FAQ and going further
Checklist SHIPUPbot (8 steps)
Sync SHIPUP-MAP #513: RAG bot whitelist only
Policy SHIPUPBOT-SUP: 6 NO-UPGRADE-PROMISE rules
8 intents bot_ship_up_*: flow SUB-1 to SUB-8
4 templates TPL-SHIPUPbot-*: FEASIBLE TOO-LATE FEE NO-ZONE
Fulfillment API sync: picked shipped real-time gate
Order status chip upgrade: bot_ship_up entry unfulfilled
Red team 10 prompts: express guaranteed free shipped
Dashboard KPI: shipup_bot_* section 9
FAQ
Difference #513?
#513 = agents payment ops WMS reprioritize. #514 = bot tier 1 cutoff fee quote.
Difference #338 express?
#338 = express checkout. #514 = standard post-payment upgrade.
Does bot collect extra cost?
No. Confirm handoff #513 payment link draft.
Parcel already shipped?
TPL-SHIPUPbot-TOO-LATE. Intercept rare handoff ops.
Going further
This week: index SHIPUP-MAP in bot corpus, test red team "express tomorrow guaranteed", measure shipup_bot_feasibility_grounded_rate. Activate chip upgrade order status page.
Enzo
July 1, 2026
