E-commerce
July 1, 2026
"It was for a birthday on Saturday, package arrived on Monday." "Why is the date I chose no longer available at checkout?" "Can I change the delivery date after ordering?" Three tickets where a poorly managed fixed-date delivery generates gift disappointment, negative reviews, and date promise disputes.
The e-commerce mandatory delivery date support covers pre-purchase feasibility, committed calendar date, cut-off lead time, post-order modification, and compensation if the date is missed. Distinct from time slot #427: here, it is a fixed calendar date gift event customer constraint.
This guide #641 covers policy FIXDATE-SUP, flows FD-1 to FD-8, and matrix FIXDATE-MAP. Companion customer service of the future bot FIXDATE (#642).
Summary
Why does scheduled delivery generate support tickets?
The customer chooses "deliver on June 15" for a wedding or a birthday. They do not understand the D-3 cut-off, the greyed-out date at checkout, or the difference between a calendar date and a time slot. Without a SOP, the agent promises a date without checking the lead time or confuses a fixed date with express tomorrow.
Five typical fixed date frictions
Missed date: delivery after promised event date
Cut-off passed: order placed too late for the target date
Date unavailable: checkout calendar greyed out and not understood
Modification refused: changing date post-order impossible
Ruined gift: arrival before or after the planned surprise
Shopify and delivery scheduler apps allow delivery dates at checkout (Shopify, delivery dates 2026). Without a FIXDATE-MAP, agents improvise feasibility and compensation.
FIXDATE #641 vs slot #427, express #338, gift #205 and bot #642
Five contents, five distinct delivery promises.
Quick Matrix
#641 FIXDATE: fixed calendar date gift event lead time
Slot #427: time window 2pm-6pm distinct calendar date
Express #338: tomorrow cut-off speed not event date
Gift order #205: packaging message recipient distinct delivery date
#642 FIXDATEbot: bot tier 1 feasibility handoff
#427 = what time. #641 = which calendar day for event or gift.
Which fixdate_* typologies should be classified?
Eight scenarios for delivery tickets with an imposed date.
Eight fixdate typologies
fixdate_how_it_works: customer does not understand fixed date at checkout
fixdate_feasibility: can I receive before date X pre-purchase
fixdate_cutoff_missed: ordered too late for chosen date
fixdate_not_available: date greyed out on checkout calendar
fixdate_change_request: modify date post-order
fixdate_date_missed: delivered after promised event date
fixdate_date_early: delivered before surprise gift date
fixdate_event_gift: wedding anniversary date constraint on map
Tags: fixdate, fixed_delivery, gift_date. FIXDATE-MAP-GROUNDED: lead_time cutoff from map only.
How should the FIXDATE-MAP matrix be structured?
The FIXDATE-MAP matrix documents each fixed-date program for agents and future bot #642.
FIXDATE-MAP Columns
fixdate_program_id: fixed-date delivery identifier
eligible_skus_categories: fixed-date eligible SKU categories
lead_time_days_min: min days between order and map delivery date
cutoff_time_rule: D-0 cutoff time for D+X map date
blocked_dates_calendar: public holidays warehouse closure map
carrier_fixed_date_map: Colissimo scheduled date rules map
modify_date_policy: change date before ship Y/N fee map
miss_date_compensation_rule: refund partial fee gift voucher map
customer_copy: checkout phrase fixed-date choice map
gift_sync_note: link gift message #205 if applicable
Sync checkout date picker, email confirmation committed date, helpdesk macros, and fixed-date FAQ.
Six-rule FIXDATE-SUP policy
Six rules support imposed delivery date.
FIXDATE-MAP-GROUNDED: lead_time cutoff compensation from map only
FEASIBILITY-CITE-ONLY: do not promise date without lead_time_days_min map
DATE-PROMISE-CITE: committed date order cite verbatim API
SLOT427-REROUTE: time slot → #427 SLOT distinct calendar date
GIFT205-LINK: gift wrapping → #205 gift distinct date mechanics
MISS-DATE-COMPENSATE-CITE: miss_date_compensation_rule cite if date missed
Flow FIXDATE FD-1 to FD-8
Flow agent eight steps fixed date delivery.
FD-1 Intake: fixdate_* intent + order_ref target_date event_type
FD-2 Program lookup: FIXDATE-MAP lead_time cutoff modify compensate
FD-3 Order verify: committed_delivery_date ship_status API
FD-4 Classify: feasibility cutoff missed change early event
FD-5 Policy triage: FEASIBILITY-CITE DATE-PROMISE MISS-DATE-COMPENSATE
FD-6 Respond: macro FIXDATE grounded map customer_copy
FD-7 Execute: modify date ops compensate refund escalate carrier
FD-8 Close: tag fixdate_resolved fixdate_program_id on_time Y/N
SLA: fixdate_date_missed answered with DATE-PROMISE-CITE and MISS-DATE-COMPENSATE map in one interaction.
Essential FIXDATE macros
Four macro scheduled delivery agents.
FIXDATE-EXPLAIN-01
"Scheduled delivery [fixdate_program_id]: [customer_copy map]. Target date checkout selection. Min lead time [lead_time_days_min map] days. Cut-off [cutoff_time_rule map]. Distinct time slot #427."
FIXDATE-FEASIBILITY-01
"Target date [target_date]: [feasible / not feasible map]. Order by [cutoff_date time map] for delivery on [date]. Blackout dates: [blocked_dates_calendar cite]. FEASIBILITY-CITE-ONLY map."
FIXDATE-COMMIT-01
"Order [order_ref]: committed delivery date [committed_delivery_date API map]. Shipment status [unfulfilled / in_transit / delivered]. [If change request: [modify_date_policy map].]"
FIXDATE-MISS-01
"Committed date [committed_delivery_date map]: delivered [actual_date API]. Delay [days] days. Compensation: [miss_date_compensation_rule map]. Carrier escalation if [carrier_fixed_date_map claim]. Event: [event_type note]."
Edge cases: multi-package, changed address, out of stock, and local delivery
Five cases outside the standard fixed-date macro.
Multi-parcel different dates: split committed_date by line item
Address changed #183: recalculate feasibility date post-edit
Out of stock promised date: notify customer reschedule or refund
Same-day local delivery: #429 LOCAL distinct carrier calendar date
General carrier delay: delay communication distinct from fixed promised date
Active fixed date = committed_delivery_date on order metafield. Do not promise a new date without FEASIBILITY-CITE ops confirm.
Essential fixdate KPIs
Five FIXDATE steering metrics.
fixdate_miss_rate: deliveries after committed_date / fixed date orders
fixdate_ticket_rate: fixdate_* tickets / fixed date orders
fixdate_on_time_rate: delivered on promised day or before / total
fixdate_feasibility_cite_rate: % FEASIBILITY-CITE map responses
fixdate_gift_event_miss_rate: miss on fixdate_event_gift / events
Target: fixdate_feasibility_cite_rate greater than 95% and monthly tracking of fixdate_miss_rate by carrier.
Anti-patterns FIXDATE
Five common errors regarding support for fixed-date delivery.
Promising a date without lead time: FEASIBILITY-CITE-ONLY FIXDATE-MAP
Confusing slot #427: SLOT427-REROUTE distinct hour day
Committed date not mentioned: DATE-PROMISE-CITE API verbatim
Ignoring miss compensation: MISS-DATE-COMPENSATE-CITE map
Modifying date without policy: modify_date_policy ops only
FIXDATE with Qstomy
Qstomy on Shopify: detect fixdate intent, FIXDATE-MAP RAG grounded, committed_delivery_date lookup, FEASIBILITY-CITE, handoff #642 bot tier 1 feasibility.
Pipeline: #642 bot feasibility pre-purchase tier 1 → #641 agents miss change compensate escalate.
Explore AI support and request a demo.
Checklist, FAQ and going further
FIXDATE Checklist (8 steps)
FIXDATE-MAP v1: lead_time cutoff blocked modify compensate
FIXDATE-SUP Policy: 6 FEASIBILITY-CITE DATE-PROMISE rules
8 fixdate_* typologies: helpdesk tags
4 FIXDATE-* macros: EXPLAIN FEASIBILITY COMMIT MISS
Checkout date picker: customer_copy lead_time visible
Promised date email: FIXDATE-COMMIT-01 confirmation
30-min agent training: FIXDATE vs #427 vs #338 vs #205
KPI Dashboard: fixdate_* section 9 miss_rate on_time
FAQ
Difference with slot #427?
#427 = Thursday 2pm-6pm time slot. #641 = Thursday calendar date for event.
Greyed out date at checkout?
FIXDATE-FEASIBILITY-01 lead_time_days_min blocked_dates_calendar map.
Parcel arrived after birthday?
FIXDATE-MISS-01 MISS-DATE-COMPENSATE-CITE map escalate carrier.
Relationship with #642 bot?
#642 = bot tier 1 pre-purchase feasibility. #641 = agents miss change compensate escalate.
Going further
This week: index FIXDATE-MAP eligible SKUs, audit customer_copy checkout date picker, test macro FIXDATE-MISS-01 agents.
Enzo
July 1, 2026
