E-commerce
July 7, 2026
"The use-by date is in two days, is that normal for an online order?" "You are selling short-date products without warning me." "After the best-before date, can I still eat it?" Questions about expiration dates are not just "product return" tickets: they are issues of trust, INCO compliance, and sometimes health safety.
ANSES points out that only exceeding the use-by date poses a health risk; the best-before date indicates a possible loss of quality, not an automatic danger (ANSES, DLC and DDM 2026). Victoris Avocat recommends a minimum threshold of remaining use-by date upon delivery and fair information on products with close best-before dates (Victoris, e-commerce food 2026).
This guide #326 covers expiration date customer support: transparency, use-by/best-before date education, short-date complaints. It complements perishables (#313) with the dates, batches, and trust angle, distinct from the perishable bot (#314).
Summary
Why do expiration dates turn the medium into a matter of trust?
A customer who receives a yogurt with a use-by date of D+2 does not just pose a logistical question: they wonder if you respect their health and if they can trust you for their next order. If poorly handled, the ticket becomes a public review saying "expired products" even though the date sometimes complies with your policy.
Three specific date tensions
Expectation vs FEFO reality: the customer expects D+10, the warehouse ships D+3 in compliance with policy
Use-by date/Best-before date confusion: same "expired" wording used for two different legal frameworks
Pre-purchase transparency: lack of PDP info regarding date range or short shelf-life
Legal framework to know on the support side
Selling beyond the use-by date is prohibited (Consumer Code L214-1 et seq.). An exceeded best-before date can remain sellable if there is fair disclosure and the product is safe (L.412-7). Service Public specifies the terms "use by" vs "best before" (Service Public, dates 2026). Support never gives medical advice: they quote policy and direct to ANSES if there is a health-related doubt.
Principle #326
EXPDATE-LOOP Pipeline: question → EXPDATE-INTENT → use-by/best-before tree → EXPDATE-POLICY response → EXPDATE-CLAIM action if dispute → trust log.
How does it differ from the perishable after-sales service #313, bot #314, and batches #327?
Five neighboring pieces of content, five distinct focuses.
Perishables (#313)
Perishables support (#313): cold chain, transport delay, spoilage, return impossible. #326 zooms in on displayed dates, customer expectation, PDP transparency, and DLC/DDM education.
Perishable Bot (#314)
Perishable Bot (#314): freshness automation. #326 structures the after-sales policy and date macros that the bot will execute.
Traceability (#312)
Traceability (#312): batch lookup, recall. #326: disputed date received, not a full product recall.
Manufacturing Batches (#327)
Batches (#327): batch numbers, recall, order lookup. #326 covers DLC/DDM and date trust, with a batch link when the customer mentions a number.
General Returns
E-commerce returns: 14-day window. Perishable goods: exclusion of the right of withdrawal (Service Public, widthdrawal 2026). #326: conformity guarantee if DLC is not respected upon delivery.
Promise #326
EXPDATE-INTENT, EXPDATE-POLICY, EXPDATE-DISPLAY, DLC/DDM tree, EXPDATE-CLAIM, EXPD macros, date trust KPI.
What EXPDATE-INTENT taxonomy should be used to route date-related tickets?
The EXPDATE-INTENT taxonomy isolates "date" verbatims from spoilage or generic delivery tickets.
10 date intents
exp_dlc_short: Received shelf life (DLC) deemed too short vs expectationexp_dlc_past: Shelf life (DLC) exceeded upon receipt (maximum severity)exp_ddm_confusion: "expired" but actually Best Before Date (DDM), can we eat it?exp_ddm_short_sale: Purchase of product advertised with close or exceeded Best Before Date (DDM)exp_pre_purchase_date: What shelf life (DLC) upon receipt before purchase?exp_pdp_missing_info: Date missing or illegible on product pageexp_opened_shelf: Duration after opening vs packaging dateexp_lot_date_mismatch: Lot cited, date does not match the lotexp_discount_short_date: Anti-waste product, unclear conditionsexp_trust_erosion: "I will not order anymore", negative review imminent
Customer Service Prioritization
Immediate P0: exp_dlc_past (compliance + safety). P1: exp_dlc_short within 24 hours of receipt. P2: education exp_ddm_confusion. Tag exp_date crossed with perishable (#313) for analytics.
What should the internal EXPDATE-POLICY document contain?
The EXPDATE-POLICY document aligns PDP marketing, FEFO picking, and agent decisions on dates.
14 policy date blocks
SKU Typology: Mandatory Expiry Date (DLC) vs Best Before Date (DDM) vs Dateless (unpackaged fresh)
Minimum delivery DLC: e.g., fresh D+3, ultra-fresh D+5 upon receipt (Victoris 2026)
"Short date" threshold: PDP display if remaining DLC is < X days at standard dispatch
Near DDM: "best before" badge, % discount if L.412-7
Anti-waste: exceeded DDM sale authorized yes/no, mandatory PDP mention
Pre-purchase window: PDP text "DLC upon receipt: minimum {n} days"
Date claim window: 24h packaging photo + visible date
Remedy for non-compliant DLC: full refund + reship or credit, no physical return
Remedy for compliant short DLC: optional goodwill gesture if < customer threshold
Agent prohibition: guarantee exact DLC before picking
DDM education: ANSES script, no "it's fine" without nuance
Escalation: exceeded DLC, alleged food poisoning, press
Batch number: collection if dispute, handoff #327 / #312 recall
Owner: support responds, quality validates recurring FEFO breach
E-commerce INCO rule
Prelium reminds: packaging details including DLC/DDM must appear on the PDP before purchase (Prelium, INCO 2026). EXPDATE-POLICY references the PDP template by category.
How to structure PDP transparency with EXPDATE-DISPLAY?
The EXPDATE-DISPLAY protocol defines what the client sees before purchasing to avoid post-reception tickets.
Four recommended PDP blocks
Date class: "Product with Use-By Date (DLC)" or "Product with Best-Before Date (DDM)" in client terms
Freshness range: "Minimum Use-By Date (DLC) {n} days upon reception with standard delivery"
Conservation: temperature + "consume within X days after opening"
Possible short date: visible badge if promotional anti-waste batch
Intent exp_pre_purchase_date
Identify SKU and cold/date class
Cite the EXPDATE-POLICY range, not the exact batch date
Explain FEFO: "We always ship the closest batches first, in compliance with our minimum Use-By Date (DLC) of {n} days."
Suggest quick delivery slot if ultra-fresh
Intent exp_pdp_missing_info
Ticket reporting missing date on PDP: merchandising escalation within 24 hours, client macro "Thank you, our team is updating the product page. In the meantime: Use-By Date (DLC) class, conservation {x}, range {n} days." The INCO requires complete pre-contractual information.
Checkout and confirmation email
Remind the Use-By Date (DLC) range in the food order confirmation email. Victoris: evidentiary email must include conservation and cold conditions if applicable.
How do agents apply the DLC (Use-By Date) vs DDM (Best-Before Date) decision tree?
The EXPDATE-DLC-DDM tree avoids treating jam (DDM) like a steak (DLC).
Step 1: identify the date type
Customer photo mandatory. Statement reading: "use by" = DLC. "best before" = DDM. No statement on non-prepackaged fresh product: guide towards caution, ANSES recommended duration 3 days (Ouest-France, consumer rights 2025).
DLC Branch
DLC expired upon receipt: immediate full refund, tag
exp_dlc_past, quality alert + stock withdrawal if same lotFuture DLC but < minimum policy: compare to EXPDATE-POLICY. Compliant → explain + optional gesture. Non-compliant → EXPDATE-CLAIM refund
DLC OK but dissatisfied customer: education on pre-purchase range, no aggressive legal arguments
DDM Branch
DDM expired: product may remain consumable if healthy (Public Service). No refund obligation if sold compliantly (fair information, intact packaging). Goodwill gesture possible. Near DDM sold as anti-waste: check PDP badge and discounted price.
Intent exp_ddm_confusion
Macro EXPD-DDM-01: "The 'best before' statement indicates a date of minimum durability (DDM). Past this date, the product may lose taste or texture but is not automatically dangerous if the packaging is intact and the product looks normal. In case of doubt (smell, mold, swelling), do not consume and contact us with a photo."
How to execute the EXPDATE-CLAIM protocol on a short expiry date or non-compliant best-before date?
The EXPDATE-CLAIM workflow processes date disputes with photo proof and short deadlines.
7 steps for date claims
Qualification: EXPDATE-INTENT + order date (< 24-48 h ?)
Proof collection: photo of the front of the packaging, legible date, batch number if visible
Auth: email + order number
Use-by/Best-before date tree section 6
Decision: refund / reship / partial gesture / education only
Execution: refund without physical return of the food item
Post-mortem: tag
fefo_breachif warehouse policy breach
Intent exp_dlc_short
Example: D+5 minimum policy, customer receives D+4. Non-compliant → refund + apology + 10% credit option for future order. Compliant example D+6, customer wanted D+15: explain nature of fresh product + link EXPDATE-DISPLAY PDP.
Intent exp_trust_erosion
Customer threatens 1-star review: do not over-promise. Acknowledge emotion, state facts (date vs policy), offer EXPDATE-POLICY remedy. Escalate to manager if 2nd date incident for same customer within 60 days.
Intent exp_discount_short_date
Anti-waste sale: clear PDP conditions (exact date or range, non-refundable if compliant, storage). Support verifies that the customer purchased in the "short date" category before refunding.
Which EXPD macros should be used depending on the date intent?
Standard EXPD macros standardize a reassuring and compliant tone. Prefix with EXPD- in Gorgias/Zendesk.
8 essential macros
EXPD-PRE-01: pre-purchase self-life (DLC) range + FEFO explained
EXPD-DLC-OK: date complies with policy, educational explanation on freshness expectations
EXPD-DLC-BREACH: non-compliant, refund initiated, no return required
EXPD-DLC-PAST: expired shelf-life (DLC), immediate refund + quality report
EXPD-DDM-01: explanation of best before date (DDM) vs expiration date (DLC) (ANSES)
EXPD-OPEN-01: shelf-life after opening, references packaging
EXPD-LOT-01: request for batch number for investigation, 48-hour quality feedback loop
EXPD-TRUST-01: acknowledgment + remedy + guided invitation for re-ordering
Confidence tone
Avoid a dry "it's within standards". Prefer: "Your product shows an expiration date of {date}, complying with our minimum commitment of {n} days upon receipt. We understand this period might seem short for your consumption; here are some recipe ideas / freezing tips if applicable." Shopify FEFO protects freshness and reduces warehouse waste (Shopify, perishable inventory 2026).
Macro forbidden actions
Never say "eat it anyway" on an expired shelf-life (DLC). Never promise a specific expiration date before shipping. Never minimize odors or bloated packaging.
Which key dates to prioritize according to your food vertical?
The EXPDATE segment matrix adapts EXPDATE-POLICY and macros to the catalog.
Ultra-short shelf-life (meal kit, cold-pressed juice)
Dominant exp_dlc_short and exp_pre_purchase_date. Minimum use-by date D+3 to D+5. Over-transparency on the PDP. Scheduled slot delivery mandatory.
Dry grocery + best-before date (DDM)
Dominant exp_ddm_confusion. Few use-by date tickets. Activate anti-waste sales with the EXPDATE-DISPLAY badge.
Frozen food
Use-by date + packaging freezing date. Intent exp_opened_shelf after thawing. Storage link #313 perish_storage.
Supplements and cosmetics "PAO"
Period after opening (6M, 12M) distinct from use-by date. Dedicated instructional intent, not a strict food decision tree.
Multi-SKU discovery box
Frequent exp_lot_date_mismatch intent: a short-dated item in the mix. Policy: partial compensation for the item in question, no full box refund except in the event of a global breach.
Which KPIs should be measured for date support and customer trust?
Measure date compliance and trust, not the raw volume of "expired" tickets.
EXPDATE Monthly KPIs
exp_ticket_rate: EXPDATE-INTENT tickets / food orders
exp_dlc_breach_rate: Expiry Date complaints < policy / fresh deliveries
exp_dlc_past_incidents: Confirmed exceeded Expiry Date (target 0)
exp_first_contact_resolution: Closed without quality escalation
exp_refund_date_cost: Date-reason refunds / food revenue
exp_repeat_date_claim: Customers with 2+ date tickets in 90 days
exp_csat_date: Post-date ticket satisfaction vs global
exp_pdp_fix_sla: Correction delay for flagged INCO product sheet
Phase 1 Objectives
After EXPDATE-POLICY + PDP deployment: exp_dlc_past_incidents = 0, exp_dlc_breach_rate < 2%, exp_first_contact_resolution > 75%. Correlate the increase of resolved exp_pre_purchase_date via PDP with the decrease of post-purchase exp_dlc_short.
Quality Review
Monthly: Top 5 SKUs by exp_dlc_breach_rate → warehouse FEFO review. Quarterly: Audit of 10 random PDPs vs INCO Prelium.
How does Qstomy enhance date transparency without medical advice?
Qstomy automates EXPDATE-INTENT, DLC/DDM pedagogy, and photo proof collection, citing EXPDATE-POLICY without ever diagnosing a product as "edible".
Capabilities
Intent
exp_pre_purchase_date: range from policy + SKU classIntent
exp_ddm_confusion: EXPD-DDM-01 ANSES scriptIntent
exp_dlc_short: compliance tree + auto refund handoff if breachUpload photo date + structured batch number
Immediate quality escalation
exp_dlc_pastBridge traceability (#312) if batch recall
Quantified DTC Scenario
Delicatessen + fresh, 2,800 food orders/month. Before #326: 89 date tickets/month, exp_dlc_breach_rate 4.1%, exp_first_contact_resolution 48%, 3 "expired" reviews/quarter. After EXPDATE-POLICY + macros + Qstomy (10 weeks): tickets 41/month, breach rate 1.2%, FCR 79%, exp_dlc_past_incidents 0 over 6 months, exp_csat_date 4.4/5. Pre-purchase tickets exp_pre_purchase_date bot: 62% resolved without a human.
Integration
Versioned EXPDATE-POLICY corpus. See AI customer support, demo. Linking: manufacturing batches (#327).
Which playbooks should be deployed to organize support dates?
Playbook 1: 90-day date verbatim audit (3 h)
Export "expired", "best before", "date", "fresh". Classify EXPDATE-INTENT. Measure share of best before vs. use by date vs. confusion.
Playbook 2: EXPDATE-POLICY + PDP (2 days)
14 blocks section 4. Update top 30 fresh SKUs with EXPDATE-DISPLAY. Validate legal compliance if selling past best before date.
Playbook 3: use by/best before decision tree + macros (4 h)
Train agents on section 6 tree. Publish 8 EXPD macros. Role-play 12 scenarios including 3 best before and 2 use by expired.
Playbook 4: EXPDATE-CLAIM + quality (1 week)
24h photo workflow. Tag link fefo_breach → warehouse alert. Refund test without return.
Playbook 5: monthly KPI review (45 min)
Section 10 dashboard. Adjust PDP range if exp_dlc_short persists post-transparency.
Useful links
Enzo
July 7, 2026
