E-commerce
June 30, 2026
"My package arrived two days late, is the yogurt still good?" "The expiration date on the label is tomorrow, is that normal?" "I can't send back damaged salmon, how do I get a refund?" Perishable products turn every ticket into a question of safety, freshness, and trust, rather than a simple size exchange.
Shopify points out that with a short shelf life, every delivery window matters for customer relations, and that the FEFO (First Expired, First Out) strategy protects both margins and reputation (Shopify, perishable stock management 2026). WISMOlabs estimates that for time- and temperature-sensitive packages, a generic carrier notification fuels fear, early refunds, and unnecessary escalations (WISMOlabs, perishable notifications 2026).
This guide #313 addresses customer support for perishable products: dates, preservation, delivery, and returns. No Qstomy content had covered these customer service constraints yet. It complements general e-commerce returns and post-purchase support with the focus on freshness, cold chain, and complaints without physical returns.
Summary
Why do perishable products turn every ticket into a matter of trust?
A t-shirt arriving late generates impatience. A fruit platter or a refrigerated package arriving late generates anxiety: is it still edible? Should I throw it away? Can I get a refund without returning a product unfit for consumption?
Three specificities of perishable customer service
Biological clock: the value of the product decreases every hour after a cold chain breach or exceeding the use-by date
Impossibility of classic returns: requiring the return of spoiled food is sanitary nonsense and logistically costly
Fear before proof: the customer often complains out of fear, not just based on objective facts (WISMOlabs 2026)
French legal framework
The 14-day right of withdrawal does not apply to perishable goods (Service Public, retraction 2026). However, the legal guarantee of conformity and hidden defects do apply if the delivered product is unfit or does not conform to the order (Mon Aide Juridique, online grocery shopping 2026).
Principle #313
PERISH-POLICY document, PERISH-INTENT taxonomy, macros, and PERISH-CLAIM workflow: handle freshness, dates, and delivery with the same operational rigor as your warehouse FEFO rules.
Convert over 2,000 customers on average per month with Qstomy.
The world’s 1st Shopify AI dedicated to customer conversion
Empowering 200+ e-commerce merchants
How does it differ from classic returns, post-purchase, and tracking #312?
Five neighboring pieces of content, five levels of response.
General e-commerce returns
Returns management: deadlines, return label, refund upon receipt. #313: no physical return for foodstuffs, replacement or credit based on photo proof within a short window.
Post-purchase support
Automated post-purchase: WISMO, invoice, tracking. #313 adds contextualized messages: product sensitivity, remaining shelf-life, action required or not.
Bot traceability (#312)
Traceability bot (#312): batch lookup, recall, DPP. #313: human customer service and macros usage when the customer disputes the freshness of a specific delivered batch.
Provenance (#311)
Provenance (#311): origin of materials. #313: received expiry date (use-by/best-before), storage conditions after opening, not just the country.
Fresh subscription
Subscription support: skip, pause. #313: quality dispute on recurring delivery, not contract modification.
Expiration dates (#326)
Expiration dates (#326): PDP transparency, expiry date tree, trust. #313: cold chain, spoilage and delivery beyond just the date dispute.
Promise #313
PERISH-INTENT, PERISH-POLICY, PERISH macros, PERISH-CLAIM workflow, cold chain notifications, spoilage KPI.
What PERISH-INTENT mapping should be used to classify freshness tickets?
The PERISH-INTENT taxonomy prevents "damaged parcel" and "short shelf life (DLC)" from being treated with the same return mode macro.
16 perishable intents
perish_dlc_short: shelf life received close to or deemed too short vs expectationsperish_ddm_clarify: confusion between BBD (DDM) vs Use-By Date (DLC), consumable after date?perish_storage: how to store, freeze, reheatperish_shipping_delay: carrier delay, product still safe?perish_temp_excursion: lukewarm package, melted ice, broken dry pack bagperish_spoilage: moldy, spoiled, abnormal smell upon receiptperish_partial_damage: one item in the fresh basket damaged out of severalperish_missing_cold_pack: absence of cold packs or thermal insulationperish_wrong_item: unaccepted substitution, incorrect variantperish_recall_lot: recalled batch, food safetyperish_refund_no_return: refund request without returnperish_replacement: resending a new package within 24-48 hoursperish_delivery_window: missed window, product left outsideperish_pre_purchase_fresh: freshness question before purchase (PDP)perish_subscription_quality: degraded quality on recurring subscriptionperish_handoff: alleged food poisoning, lawyer, press, multiple batch
Helpdesk tags
perishable, fresh, cold_chain, dlc, spoilage. SLA Priority: perish_recall_lot and perish_temp_excursion within 2 business hours.
How to write the PERISH-POLICY document for agents, warehouse, and marketing?
The PERISH-POLICY document aligns website promise, FEFO picking, and customer service decisions.
10 mandatory blocks
Product classes: ambient / chilled / frozen / ultra-fresh (shelf life < 5 days)
Minimum shelf life for dispatch: e.g. fresh meat 3 days min upon receipt, yogurt 5 days min (Victoris Avocat, INCO e-commerce 2026)
Approaching best before date: display threshold for "short date" on PDP + discount if applicable (L.412-7 French Consumer Code)
Complaint window: 24 hours from receipt for fresh goods, 48 hours for chilled, photo proof mandatory
No-return policy: full or partial refund, never return labels for perishables
Auto-refund thresholds: e.g. < €25 validated photo spoilage = refund without escalation
Transport: carriers authorized by class, no weekend delivery if prohibited
Delay scripts: 24 h / 48 h / 72 h tiers with reship vs refund decision (Belike, perishable fulfillment 2026)
Recall: link to procedure #312, macro RECALL-PERISH, immediate escalation
Abuse: max 2 spoilage complaints / 90 days without new proof → manual review
FEFO rule on the support side
If the warehouse dispatches a batch close to its expiry date by mistake, tag the ticket fefo_breach + ops alert if 3 tickets for the same SKU within 7 days (Shopify FEFO 2026).
Which PERISH macros should be used to respond regarding dates, shelf life, and complaints?
The PERISH macros cover 80% of intents without improvising on food safety.
10 essential macros
PERISH-001 Short shelf life: "We ship with a minimum of {min_dlc} days before the use-by date. Your batch: {dlc_received}. If below our threshold, immediate refund or reshipment."
PERISH-002 Best before date explained: "Best before" is a quality date, not a health hazard if storage conditions are respected (Service Public, DLC/DDM 2026).
PERISH-003 Storage: temperature, shelf life after opening, freezing allowed or not
PERISH-004 Delivery delay: carrier status + "estimated freshness margin {hours} h" + next update
PERISH-005 Warm package: request photo of thermometer if provided, product photos, refund if > {temp_max}
PERISH-006 Spoilage photo: upload link for 3 angles + order number, processed within 4 hours
PERISH-007 Refund without return: "No need to send the product back, secure disposal at your home"
PERISH-008 Express replacement: reshipment D+1 if stock is available + customer's slot
PERISH-009 Missed delivery slot: options wait / refund / reship according to PERISH-POLICY
PERISH-010 Batch recall: safety instructions + traceability (#312) link
Mandatory Lookup
Order → product class → shelf life/BBD fulfillment log → tracking status → route weather route if heat-sensitive. See CS scripts (#34).
How do you explain use-by dates, best-before dates, and storage instructions without causing unnecessary doubt?
Dates and preservation questions dominate food pre-purchase and day-of-delivery (D+0) post-purchase.
Use By Date vs Best Before Date: agent script
INCO Regulation: clearly written mentions "Use by" (Use By Date, microbiological perishable) or "Best before" (Best Before Date, quality). In distance selling, the date can be provided at the latest upon delivery (INC-Conso, labeling 2026).
PDP vs ticket answers
Pre-purchase: Use By Date range upon receipt, not the exact date as the batch is unknown
Post-delivery: real batch date from ERP + preservation link
Expired Best Before Date received: if policy prohibits, PERISH-001; if discounted sale is authorized, remind of the mandatory fair warning mention
Preservation after opening
Document by SKU: fridge 0-4 °C, open duration 48 hours, freezing -18 °C max 3 months. Macro PERISH-003 cites R&D source or label, never medical advice.
Food origin
If the question is "where does this salmon come from?", redirect to origin (#311) then return to the Use By Date of the delivered batch.
How to manage delivery, delays, and cold chain disruption?
Perishable delivery is the leading customer service topic if tracking shows a delay or a temperature anomaly.
Contextualized notifications
WISMOlabs recommends a minimum of four elements: product sensitivity, remaining safe window, customer action required or not, and the next update (WISMOlabs 2026). Replace "your package is delayed" with "your refrigerated box contains products below 4°C (39°F); estimated window 18 hrs; no action required before tomorrow 10 am."
Ops delay thresholds
+24 hrs: PERISH-004 email + ops monitoring
+48 hrs: reship offer or partial refund depending on class
+72 hrs or temperature excursion: full ambient/refrigerated refund, no reshipment
Missed delivery window
Package left on porch in summer = priority perish_delivery_window. Verify carrier scan "delivered" vs "attempted". Align with reducing WISMO (#29) and pre-checkout delivery objections (#24).
Pre-checkout expectations
Hints.live emphasizes: most perishable complaints represent expectation failures, not product defects (Hints, cold chain DTC 2026). Repeat the delivery window on the PDP, checkout, and confirmation email.
What PERISH-CLAIM workflow is used to process spoilage without a physical return?
The PERISH-CLAIM workflow standardizes claim, proof, and decision in less than 15 agent minutes.
7 PERISH-CLAIM Steps
Intake: classify PERISH-INTENT, note reception time vs ticket time
Window: politely reject if out of time PERISH-POLICY, except for recalls
Proof: product photos + packaging + expiration date label + thermometer if provided
Batch trace: lookup order lot (#312), tag
fefo_breachif pattern existsDecision: refund / partial / reship according to the section 4 tree
Execution: Shopify refund without waiting for return, email PERISH-007
Quality: cause code temp / delay / picking / carrier → weekly review if > 3 of the same code
Deliveroo Freshness Promise (benchmark)
Deliveroo allows in-app freshness claims based on shelf life and visual quality criteria; the partner can dispute with proof of correct picking (Deliveroo, Freshness Promise 2026). Take inspiration from this: published objective criteria, short window, documented dispute.
Internal Claim Kit
Belike recommends a ready file: order number, packing date, carrier timeline, batch, customer photos (Belike 2026).
Which vertical playbooks for fresh produce, meal kits, flowers, and pet food?
Perishable support varies according to the cold chain and regulations.
Delicatessen / fresh products
perish_dlc_short and perish_spoilage dominate. Minimum shelf life (DLC) D+3 to D+7 depending on category. Recall = immediate RappelConso alert.
Meal kits
Questions on perish_storage and perish_partial_damage (a punctured sachet). Macro explains consumption D+0/D+1. Delay > 24 h = reship menu or next week store credit.
Flowers and live plants
No food shelf-life (DLC) but perish_shipping_delay is critical. 12-hour claim window. Summer heat packs documented in PDP.
Fresh / refrigerated pet food
Cross perish_subscription_quality with subscription support. Recurring customer reporting quality drop in batch 3 = QA escalation + batch swap.
PAO cosmetics
"6M" after opening date ≠ food DLC. Intent perish_storage from the materials sheet (#166). No spoilage refund if PAO is respected and complaint is subjective.
Chocolate / heat-sensitive ambient
Summer: perish_temp_excursion without refrigeration. Offer autumn reship or partial refund for bloom.
What KPIs should be measured for perishable product support?
Measure perceived freshness and cost of quality, not raw ticket volume.
Monthly KPIs
spoilage_claim_rate: PERISH-CLAIM complaints / fresh class orders
dlc_short_rate: perish_dlc_short tickets / shipped units
cold_chain_incident_rate: temp_excursion + missing_cold_pack / refrigerated packages
mean_time_perish_resolution: intake → refund/reship
repeat_purchase_after_claim: % of customers ordering within 60 days post-resolution
fefo_breach_cluster: SKUs with 3+ tickets within 7 days
carrier_delay_spoilage_correlation: delay > 48 h → claim (by carrier)
Weekly Quality Review
If dlc_short_rate increases on a SKU: FEFO picking audit. If repeat_purchase_after_claim drops: compensation too low or PERISH-CLAIM delays too long. Compare refund vs reship cost by vertical.
How does Qstomy speed up dates, conservation, and freshness claims?
Qstomy routes PERISH-INTENT, reads Shopify order status, and executes self-service PERISH-CLAIM when policy permits.
Capabilities
Post-auth BBD/lot lookup from fulfillment metafields
Dynamic PERISH macros based on product class and tracking delay
Spoilage photo upload + auto-refund if < PERISH-POLICY threshold
Recall mode: perish_recall_lot intent → macro #312
perish_handoff handoff with batch file + carrier timeline
PDP Chips: "What BBD upon receipt?", "How to store?"
Quantified DTC Scenario
DTC meal kit box, 4,200 refrigerated orders/month. Before Qstomy: 890 freshness-related tickets/month, mean_time_perish_resolution 11 h, spoilage_claim_rate 4.2%, repeat_purchase_after_claim 41%. After PERISH-POLICY + PERISH-CLAIM bot: tickets 520/month (-42%), resolution 2.4 h, claim rate stable but repeat 58% thanks to immediate returnless refund and contextual delay notifications.
See AI support, Shopify, demo
Which playbooks to deploy perishable after-sales service in four weeks?
Playbook 1: Freshness Ticket Audit (4 h)
90-day export: "DLC", "expired", "moldy", "lukewarm", "delayed package". Classify under PERISH-INTENT section 3. Top 8 intents = macro priority.
Playbook 2: PERISH-POLICY + DLC thresholds (1 d)
Fill in 10 blocks in section 4 with ops and legal. Publish on Notion + sync metafields perish_class, min_dlc_ship per SKU.
Playbook 3: Macros PERISH-001 to 010 (4 h)
Draft and test on 5 real anonymized tickets. Validate your PERISH-002 DDM vs PERISH-001 DLC with legal if in doubt.
Playbook 4: PERISH-CLAIM workflow + refund without return (1 d)
Configure photo form, Shopify auto-refund thresholds, quality cause tags. Simulated spoilage mystery shop: target resolution < 4 h.
Playbook 5: Cold chain delay notifications (3 h)
Klaviyo templates by product class aligned with PERISH-004. Simulated tracking delay test: message must answer "is it still safe?"
Useful Linking
This week: search for "DLC" or "damaged" in your tickets from the last month. If more than 5% of fresh orders generate a contact, Playbook 1 confirms that #313 is your ops priority.
Enzo
June 30, 2026
