E-commerce
July 1, 2026
"I paid for the complete training, why was only module 1 shipped?" "The page said delivery in 3 waves, nobody gave me the dates." "Package 1 received, package 2 announced in 6 weeks, can I cancel the rest?" Three tickets where a poorly explained split order over time generates chargebacks, missing content disputes, and negative reviews.
The e-commerce scheduled shipments support covers wave calendar, content of each shipment, partial cancellation, and wave delay. Distinct split shipment #356: here, shipments are planned over multiple dates according to documented rules, not just multiple logistical packages.
This guide #723 covers policy SCHDPART-SUP, flows SP-1 to SP-8, and matrix SCHDPART-MAP. Future customer service pair bot SCHDPART (#724).
Summary
Why do time-split orders generate tickets?
The brand sells a training program with monthly modules, a seasonal box in waves, a mixed basket with immediate stock + scheduled restock, or a discovery box spread over 8 weeks. The customer pays once, receives the first wave, then waits without a clear schedule. Without a SOP, the agent treats this as missing parcel #356, pre-order only #187, or promises wave 2 without a map date.
Five typical frictions in scheduled shipments
Vague schedule: wave 2 and wave 3 dates not communicated on map
Unknown wave content: customer does not know SKU per wave map
Missing parcel confusion: agent routes split_wismo instead of schdpart map
Partial cancellation: refund policies for unshipped waves are vague map
Wave delay: scheduled date passed without update map
Shopify documents partial fulfillments and sequential shipments based on line availability (Shopify, order routing and fulfillments 2026). Without SCHDPART-MAP, support and ops diverge on the wave schedule.
SCHDPART #723 vs split #356, pre-order #187, bundle #681, and bot #724
Six contents, six distinct delivery models.
Quick Matrix
#723 SCHDPART: scheduled shipments calendar waves content by date
Split shipment #356: multi-parcel logistics distinct tracking split_wismo
Pre-order #187: SKU preorder waiting for production distinct schedule waves
Incomplete bundle #681: missing bundle component distinct scheduled wave
Fixed date #428: one-off committed_date distinct multi-wave calendar
#724 SCHDPARTbot: bot explain calendar content parcel tier 1
#356 = multiple parcels one order, often close together. #723 = shipments planned over time with documented waves calendar.
Which schdpart_* typologies should be classified?
Eight scenarios for time-split order tickets.
Eight schdpart typologies
schdpart_schedule: scheduled wave dates calendar map
schdpart_wave_content: SKU content by wave map
schdpart_wave_status: wave status in progress shipped pending map
schdpart_wave_delay: wave date delay exceeded map
schdpart_partial_cancel: cancel unshipped waves map
schdpart_address_change: change address for future waves map
schdpart_mixed_cart: immediate stock + scheduled waves map
schdpart_missing_confusion: customer thinks missing vs pending wave map
Tags: schdpart, scheduled_ship, partial_fulfillment, wave. WAVE-CITE: wave_schedule cite map only.
How should the SCHDPART-MAP matrix be structured?
The SCHDPART-MAP matrix documents each scheduled shipments program for agents and future bot #724.
SCHDPART-MAP Columns
schdpart_program_id: waves map program identifier
eligible_skus: concerned SKUs or bundles map
wave_count: number of scheduled waves map
wave_schedule: dates or intervals per wave map
wave_line_items: SKU content per wave map
partial_cancel_policy: cancellation of waves pending refund map
delay_notification_policy: wave delay update map
checkout_disclosure_copy: checkout schedule wording map
customer_communication_copy: macro schedule wave map
bot_intent_map: bot_schdpart_* #724 mapping
Sync metafields order wave_id, OMS fulfillments API and helpdesk macros.
SCHDPART-SUP Policy in six rules
Six rules support scheduled shipments.
SCHDPART-MAP-GROUNDED: wave content schedule from map only
WAVE-CITE: wave_schedule cites map verbatim
FULFILL-LOOKUP-VERIFY: Shopify fulfillments API before missing claim
NO-MISSING-PROMISE: no missing confirmed if wave pending map
PARTIAL-CANCEL-CITE: partial_cancel_policy cited if map cancellation
SPLIT356-REROUTE: pure multi-package logistics → #356 SPLIT distinct wave schedules
Flow SCHDPART SP-1 to SP-8
Flow agent eight steps time-split order.
SP-1 Intake: schdpart_* intent + order_ref wave question
SP-2 SCHDPART-MAP: schedule content cancel delay disclosure
SP-3 Order lookup: order email API fulfillments wave meta verify
SP-4 Classify: schedule content status delay cancel missing confusion
SP-5 Triage: WAVE FULFILL-LOOKUP NO-MISSING PARTIAL-CANCEL SPLIT356
SP-6 Respond: macro SCHDPART grounded customer_communication_copy
SP-7 Execute: ops partial cancel address update delay notify refund wave
SP-8 Close: tag schdpart_resolved wave_cited missing_false Y/N
SLA: schdpart_schedule answered with wave_schedule wave_line_items in one interaction.
Essential SCHDPART macros
Four scheduled send macro agents.
SCHDPART-SCHEDULE-01
"Order [order_ref map] program [schdpart_program_id]: [wave_count map] waves. Schedule: [wave_schedule map.] Wave 1 [API status]. Wave 2 [date map.] WAVE-CITE."
SCHDPART-CONTENT-01
"Content per wave: [wave_line_items map.] Wave received: [fulfillments API items]. Next wave: [wave_line_items next map.] FULFILL-LOOKUP-VERIFY."
SCHDPART-DELAY-01
"Wave [N map] postponed: [delay_notification_policy map.] New date [wave_schedule updated map.] Proactive update sent."
SCHDPART-CANCEL-01
"Cancellation of unshipped waves: [partial_cancel_policy map.] Pending waves: [list map.] Refund [amount rule map] within [delay map.] PARTIAL-CANCEL-CITE."
Edge cases: mixed cart, pre-order, address, and logistics split
Five cases outside of standard scheduled macro mailings.
Mixed cart stock + waves: schdpart_mixed_cart immediate stock + waves map program
SKU preorder in wave: #187 preorder delay distinct program calendar
Address change future waves: #183 if unfulfilled wave pending
Logistic split same wave: SPLIT356-REROUTE #356 distinct multi-package tracking schedule
Component pack truly missing: #681 MISSBND verify distinct wave pending
Wave pending = NO-MISSING-PROMISE. All delivered fulfillments missing item = reroute #681.
Essential delivery schedule KPI
Five SCHDPART steering metrics.
schdpart_wave_cite_rate: WAVE-CITE / total schdpart_schedule content
schdpart_false_missing_rate: resolved missing_confusion wave pending / total
schdpart_wave_delay_rate: wave_delay / active scheduled waves
schdpart_partial_cancel_rate: partial_cancel / active schdpart orders
schdpart_churn_signal_rate: chargeback cancel after wave_delay ticket
Target: schdpart_wave_cite_rate above 95% and schdpart_false_missing_rate decreasing post checkout_disclosure_copy.
SCHDPART anti-patterns
Five common errors in scheduled shipment support.
Treating as a missing package: FULFILL-LOOKUP wave pending NO-MISSING-PROMISE
Inventing a vague date: WAVE-CITE wave_schedule map only
Confusing split #356: SPLIT356-REROUTE distinct logistics schedule
Partial cancellation without policy: PARTIAL-CANCEL-CITE partial_cancel_policy map
Wave delay without update: SCHDPART-DELAY-01 delay_notification_policy map
SCHDPART with Qstomy
Qstomy on Shopify: detect schdpart intent, SCHDPART-MAP RAG grounded, wave schedule cite, fulfillments lookup, handoff #724 bot tier 1.
Pipeline: #724 content calendar bot tier 1 → #723 agents delay partial cancel ops execute.
Explore AI support and request a demo.
Checklist, FAQ and going further
SCHDPART Checklist (8 steps)
SCHDPART-MAP v1: waves schedule content cancel delay disclosure
Policy SCHDPART-SUP: 6 rules WAVE FULFILL-LOOKUP NO-MISSING
8 typologies schdpart_*: tags helpdesk scheduled_ship wave
4 macros SCHDPART-*: SCHEDULE CONTENT DELAY CANCEL
Checkout disclosure: checkout_disclosure_copy visible before payment
Email confirmation wave: wave_schedule wave_line_items post-purchase
Agent training 30 min: SCHDPART vs #356 vs #187 vs #681
KPI Dashboard: schdpart_* section 9 wave_cite false_missing
FAQ
Difference split shipment #356?
#356 = multi-parcel logistic tracking. #723 = schedule of planned shipments over time.
Difference pre-order #187?
#187 = SKU preorder awaiting production. #723 = multi-wave program with documented schedule.
Customer says items are missing?
FULFILL-LOOKUP-VERIFY wave pending NO-MISSING-PROMISE SCHDPART-CONTENT-01.
Relation #724 bot?
#724 = bot to explain schedule content tier 1. #723 = agents delay partial cancel ops execute.
Going further
This week: index SCHDPART-MAP wave programs, sync checkout_disclosure_copy PDP, test macro SCHDPART-SCHEDULE-01 agents API schedule.
Enzo
July 1, 2026
