E-commerce
July 1, 2026
"I ordered standard, can you change it to express?" "It is for tomorrow, I will pay the difference now." "The package has not shipped yet, is an upgrade possible?" Three tickets where a post-order delivery upgrade without a playbook leads to impossible promises, uncollected extra costs, and packages shipped standard despite the urgency.
The support for changing dynamic delivery methods post-payment covers cutoff feasibility, fulfillment status, express extra cost, WMS pick prioritization, and reasoned refusal if too late. Distinct from express checkout (#338) and address change (#183): here, we focus on upgrading post-purchase shipping speed.
This guide #513 covers policy SHIPUP-SUP, flow SU-1 to SU-8, and matrix SHIPUP-MAP. First delivery upgrade content. Future customer service pair upgrade bot (#514).
Summary
Why does the shipping upgrade generate support tickets?
The customer chose standard shipping at checkout. A few minutes or hours later, the urgency changes: a gift, a trip departure, an event. Shopify does not natively allow modifying the shipping line after payment.
Five typical points of friction
Cutoff passed: express shipping impossible despite the package not being shipped
Unclear extra cost: customer does not know how much to pay to upgrade
Already picked: WMS has scanned, carrier change is too late
Ineligible zone: postal code excluded from express shipping but customer insists
Agent's promise: "we'll switch to express" without operational verification
Shopify Order Editing allows certain post-purchase modifications depending on the plan and apps (Shopify, order editing 2026). The shipping method often remains locked without a dedicated SOP upgrade.
SHIPUP #513 vs express #338, address #183 and order modification
Four contents, four post-purchase modification layers.
Quick matrix
#513 SHIPUP: standard to express upgrade post-payment
#338 EXPRESS: express checkout cut-off promises
#183 address: delivery address change
Order edit: general order modification
#338 = express choice at checkout. #513 = customer wants to speed up after paying standard.
Which ship_up_* typologies should be classified?
Eight delivery upgrade ticket scenarios.
Eight ship_up typologies
ship_up_express_request: switch standard to express
ship_up_cutoff_check: still time before express cutoff
ship_up_fee_quote: how much does the upgrade difference cost
ship_up_too_late: parcel picked or shipped upgrade refused
ship_up_zone_ineligible: postal code outside express zone
ship_up_preorder: pre-order upgrade impossible before stock arrival
ship_up_gift_urgent: gift tomorrow express upgrade
ship_up_downgrade_refund: express to standard refund of extra cost
Tags: ship_up, order_edit. Lookup fulfillment_status + WMS stage before macro SHIPUP-FEASIBLE.
How to structure the SHIPUP-MAP matrix?
The SHIPUP-MAP matrix documents upgrade feasibility by order status, zone, and carrier for agents and the future bot #514.
SHIPUP-MAP Columns
from_method: standard economy relay
to_method: express next_day chronopost
fulfillment_stage: unfulfilled picked shipped
cutoff_time: deadline for same-day upgrade time zone
upgrade_fee_eur: exact differential additional cost
zone_eligible: PC list or shipping profile
wms_action: reprioritize pick tag express flag
payment_method: draft invoice payment link manual
upgrade_allowed: Y/N reason if N
SHIPUP-SUP Policy in six rules
Six delivery upgrade support rules.
SHIPUP-MAP-GROUNDED: fee feasibility from map only
VERIFY-WMS-FIRST: fulfillment stage before upgrade promise
PAY-BEFORE-PRIORITY: extra cost collected before pick reprioritization
NO-UPGRADE-SHIPPED: fulfilled shipped → SHIPUP-TOO-LATE
CUTOFF-CITE: exact cutoff_time in Europe/Paris timezone
DOWNGRADE-REFUND-MAP: extra cost refund in case of map row downgrade
Flow SHIPUP SU-1 to SU-8
Flow agent eight steps delivery upgrade.
SU-1 Intake: ship_up_* intent + order lookup
SU-2 Fulfillment check: unfulfilled picked shipped WMS
SU-3 SHIPUP-MAP: upgrade_allowed fee cutoff zone
SU-4 Classify: feasible too_late zone fee gift
SU-5 Respond: macro SHIPUP grounded
SU-6 Payment: draft order payment link if fee > 0
SU-7 Ops notify: WMS reprioritize express tag Slack
SU-8 Close: tag ship_up_resolved outcome
SLA: ship_up_express_request answered in one interaction with feasibility or cutoff cited.
Essential SHIPUP macros
Four macro agents.
SHIPUP-FEASIBLE-01
"Express upgrade possible before [cutoff_time]. Additional cost [upgrade_fee_eur] €. Payment link: [payment_link]. Priority picking upon receipt of payment."
SHIPUP-TOO-LATE-01
"Parcel already [fulfillment_stage]. Upgrade impossible. Current delay: [current_eta]. Alternative: #129 urgent gift."
SHIPUP-NO-ZONE-01
"Express not available for PC [postal_code]. Options: expedited relay [alt_method] or change of address #183 if eligible zone."
SHIPUP-DOWNGRADE-01
"Standard switch confirmed. Refund of additional cost [upgrade_fee_eur] € within 5 business days. New delay: [standard_eta]."
Edge cases: pre-order, multi-package, and time slot
Four cases outside the standard macro.
Pre-order: ship_up_preorder: upgrade after shipping date stock only
Partial multi-parcel: one parcel shipped: upgrade unfulfilled lines only
Time slot: #427 slot: express upgrade can reset time slot
Intercept carrier: shipped < 2 h: carrier hold ops escalation is rare
Each shipping profile requires a SHIPUP-MAP line if cutoff_time or upgrade_fee_eur differs.
Essential ship_up KPIs
Five SHIPUP management metrics.
ship_up_request_rate: upgrade requests / standard orders
ship_up_success_rate: % of upgrades executed before cutoff
ship_up_too_late_rate: rejected because picked or shipped
ship_up_fee_collected: total extra cost collected in EUR
ship_up_sla_met: % of feasibility responses < 1 h
Target: ship_up_success_rate > 70% if SHIPUP-FEASIBLE-01 and ops reprioritisation within 30 min post-payment.
SHIPUP Anti-patterns
Five common mistakes.
Promising express without WMS check: VERIFY-WMS-FIRST
Reprioritizing without payment: PAY-BEFORE-PRIORITY
Invented fee: SHIPUP-MAP-GROUNDED violation
Confusing address #183: distinct speed upgrade
Duplicating express #338: #513 = post-purchase only
SHIPUP with Qstomy
Qstomy on Shopify + WMS: detect ship_up intent, SHIPUP-MAP feasibility, cutoff countdown, payment link draft, ops Slack reprioritize, handoff #514 bot tier 1 quote.
Pipeline: #513 agents upgrade payment ops → #514 bot cutoff fee quote tier 1.
Explore AI support and request a demo.
Checklist, FAQ and going further
SHIPUP Checklist (8 steps)
SHIPUP-MAP v1: methods stages fee cutoff zone
Policy SHIPUP-SUP: 6 ops rules + agents
8 ship_up_* typologies: helpdesk tags
4 SHIPUP-* macros: FEASIBLE TOO-LATE NO-ZONE DOWNGRADE
Payment link SOP: draft order extra cost upgrade
WMS express tag SOP: post-payment pick reprioritization
Training cutoff vs pick 20 min: VERIFY-WMS-FIRST
Dashboard KPI: ship_up_* section 9
FAQ
Difference express #338?
#338 = express at checkout. #513 = upgrade after standard payment.
Can customer downgrade express?
If unfulfilled before pick: SHIPUP-DOWNGRADE-01 map row.
Is Bot #514 enough?
Tier 1 cutoff fee quote. Payment ops → agents #513.
Parcel already shipped?
SHIPUP-TOO-LATE-01. Intercept carrier exception rare ops.
Going further
This week: document SHIPUP-MAP by shipping profile, test SHIPUP-FEASIBLE-01 on simulated unfulfilled order, measure ship_up_success_rate.
Enzo
July 1, 2026
