E-commerce
July 7, 2026
"Where can I find the batch number on the packaging?" "Is my batch L2403-A affected by the recall?" "Why does my order from yesterday not have the same batch number as my order from last month?" The batch number is the cornerstone connecting your ERP, food safety, and customer trust. If handled poorly in customer support, it becomes an endless ticket or a dangerous promise.
The INCO regulation mandates the batch number on pre-packaged products to allow targeted withdrawal in case of a health risk (Prelium, INCO 2026). RappelConso requires that any food recall be declared on the DGCCRF platform with identified batches and GTINs (RappelConso, DGCCRF guide 2026).
This guide #327 covers batch number customer support: packaging reading, order lookup, recall, and quality dispute. Distinct from traceability bot (#312), expiration dates (#326) and the recall plan (#329 upcoming).
Summary
Why does the batch number generate specific support tickets?
The batch is not a logistical detail for the customer: it is proof that they can trust you or hold you responsible. It links a received yogurt to a production line, a national recall, and sometimes a viral "food poisoning" review.
Three customer functions of the batch
Safety: checking if their product is recalled
Quality: reporting a defect by citing a specific reference
Transparency: comparing two purchases, understanding variability
Regulatory obligation on the merchant side
EC Regulation 178/2002 imposes traceability "one step back, one step forward": identifying suppliers and customers by batch (MAE Innovation, traceability 2026). Data retention: product shelf life + 6 months minimum, often 2 to 5 years. Support must be able to trace batch → order in minutes, not days.
Principle #327
BATCH-LOOP pipeline: question → BATCH-INTENT → BATCH-LOOKUP → BATCH-POLICY response → BATCH-RECALL or BATCH-CLAIM action → traceability log.
How does it differ from bot traceability #312, dates #326, and recall #329?
Five traceability contents, five complementary roles.
Traceability bot (#312)
Traceability bot (#312): TRACE-DISPLAY, automated lot lookup, DPP. The #327: human after-sales support policy, macros, and manual or semi-automated lookup protocols.
Expiration dates (#326)
Dates (#326): Expiry date / Best before date, date trust. The #327: lot identifier as a reconciliation key for date + order + recall.
Perishables (#313)
Perishables (#313): cold chain, spoilage. The #327 zooms in on the lot number in freshness complaints.
Recall plan (#329)
Crisis plan (#329): war room, email/SMS, hub page. The #327 covers daily lot questions and escalation to recall protocol.
Recall bot (#328)
Recall bot (#328): RECALL-BOT-MODE, 4-step flow, automated remedy. The #327 sets the BATCH-RECALL handoff and human agent scripts.
Promise #327
BATCH-INTENT, BATCH-POLICY, BATCH-LOOKUP, BATCH-READ, BATCH-RECALL, BATCH-CLAIM, macros, lot KPIs.
What BATCH-INTENT taxonomy should be used to route batch tickets?
The BATCH-INTENT taxonomy classifies batch verbatims prior to ERP opening.
10 batch intents
batch_read_help: where to find the number on the packagingbatch_order_lookup: which batch in my order #{order}batch_recall_check: has my batch been recalledbatch_quality_issue: product defect, batch citedbatch_date_lot_mismatch: date does not correspond to the expected batchbatch_missing_label: no visible batch on product receivedbatch_compare_orders: different batches between two ordersbatch_pre_purchase: will I get the same batch as beforebatch_b2b_cert: batch certificate for pro customer auditbatch_handoff: confirmed recall, health, press, multiple batches
Customer Service Prioritization
P0: batch_recall_check if RappelConso alert is active on SKU. P1: batch_quality_issue + batch_missing_label. P2: lookup and education. Tag batch_trace crossed with exp_date (#326) if date dispute.
What should the internal BATCH-POLICY document contain?
The BATCH-POLICY document aligns support, quality, and ops on what an agent can say and do with a batch number.
14 batch policy blocks
Internal batch format: structure (e.g., L{YYYYMM}-{suffix}), where it is printed
Customer batch format: packaging label "Lot :", "L :", datamatrix code
Order lookup: ERP/WMS field (batch_id on fulfillment line)
Lookup SLA: customer response within 4 business hours, 30 min if active recall
Active recall: RappelConso sheet link, affected batches, destruction/return instructions
Agent forbidden: confirming "not recalled" without official checklist
Batch quality: threshold of 3 tickets same batch 7 days → quality alert
Missing label: refund or reship if batch missing on prepackaged INCO product
B2B cert: COA issuance owner, 48 h delay
Data retention: batch-order archiving duration (2-5 years)
Escalation: DDPP contact, lawyer, alleged poisoning
Crisis communication: referral to plan #329 when published
Non-food: cosmetic, textile batch (serial number vs manufacturing batch)
Owner: support lookup, quality validates recall, legal validates communication
Warehouse FEFO link
Hello Harel reminds: the shipped batch follows FEFO and mass retail customer criteria (Hello Harel, batch and BBD 2026). BATCH-POLICY documents that two successive orders can have different batches: standardized response, no apology.
How to execute the BATCH-LOOKUP command to batch?
The BATCH-LOOKUP workflow retrieves the shipped batch from a customer order.
Intent batch_order_lookup
Auth email + order no.
Query Shopify fulfillment lines or WMS export
Read batch_id / lot_number on each line item
If multi-SKU: batch stable by reference
Communicate: "Order {order}: {SKU_A} batch {lot_A}, {SKU_B} batch {lot_B}."
Log lookup agent + timestamp
Intent batch_pre_purchase
Refusal of future batch promise: "We apply FEFO rotation: the shipped batch is the one with the closest expiry date while respecting our delivery minimum. I cannot guarantee the same batch as a previous order." Link #326 expiry range.
Intent batch_compare_orders
Two orders, two batches: normal if FEFO. Explain without jargon. If the customer reports a difference in quality: open batch_quality_issue, collect photos of both batches.
ERP Missing Data
If batch is not registered on an old order (> archiving): escalate to ops, honest reply "we are searching our archives, reply within {sla}". Do not invent a batch.
How do I help the customer read the batch with BATCH-READ?
The BATCH-READ protocol reduces "I can't find the number" tickets.
Intent batch_read_help
Macro BATCH-READ-01 with packaging layout by category: food (stamp base or lid), cosmetics (tube crimp), textiles (wash label + production code). rfxcel recommends educating consumers on reading batch codes for informed choices (rfxcel, lot code 2026).
Intent batch_missing_label
Request a photo of the complete product + the expected label area
Check if the product is pre-packaged INCO (mandatory batch number)
Lookup warehouse batch via order despite missing label
If compliance breach: refund or reship + packaging quality alert
Tag
inco_label_breachfor ops
Batch vs date vs GTIN
Education: the batch number identifies the production; the expiry date (DLC/DDM) identifies the consumption; the barcode identifies the commercial product. Three distinct pieces of information on the packaging. Link EXPDATE (#326) if date/batch confusion (batch_date_lot_mismatch).
Site help page
Publish a "Where to find your batch number" visual for the top 10 SKUs. Link macro BATCH-READ and bot #312 trace_batch_order when deployed.
How to manage a recall request with BATCH-RECALL?
The BATCH-RECALL protocol processes batch_recall_check without panic or false reassurance.
6 recall verification steps
Collect customer batch number (photo) or look up order
Cross-reference active recalled batches list (RappelConso + internal quality registry)
If batch matches: official instructions (do not consume, destroy, or return as per sheet)
If batch does not match: factual confirmation + link to the RappelConso sheet for listed batches
Offer refund/replacement according to BATCH-POLICY if recall is confirmed
Escalate to
batch_handoffif health symptoms are alleged
Template messages
Recalled batch: "Your batch {lot} is affected by the recall {réf} published on {date}. Do not consume the product. {consigne}. Refund initiated without physical return." Non-recalled batch: "The recall {réf} concerns batches {liste}. Your batch {lot} is not included. You can consume normally if the packaging is intact and the best-before date is respected."
Support prohibitions
Never say "it's probably nothing" upon suspicion of a recall. Never minimize DGCCRF instructions. RappelConso: one sheet per product category and brand, all batches listed (RappelConso 2026).
Crisis preparation
Before recall: export clients by batch from ERP (downstream traceability MAE Innovation). Ticket #329 will detail communication for mass email/SMS; ticket #327 establishes the individual client ticket.
How to handle a batch quality dispute with BATCH-CLAIM?
The BATCH-CLAIM workflow structures quality claims related to an identified batch.
Intent batch_quality_issue
Collect batch number (photo), order number, defect description
Product + packaging photos mandatory
Lookup: how many orders shipped for batch {lot}?
If ≥ 3 tickets same batch 7 days: quality alert
lot_clusterDecision: line refund, reship new batch, credit, R&D escalation
Keep items for 90 days for internal analysis (photos, no food return if #313)
Intent batch_date_lot_mismatch
Customer expects batch X with date Y, receives another combination: check FEFO vs picking error. If warehouse error: EXPDATE-CLAIM (#326) + tag pick_error. If normal FEFO: BATCH-READ customer education + #326.
Intent batch_b2b_cert
B2B customer requests batch certificate: collect batch + PO, quality ticket, 48h turnaround time. Do not send raw supplier COA if confidential; use BATCH-CERT-01 customer certificate template.
Upstream traceability link
Recurring batch quality: quality goes back to supplier via upstream traceability (MAE Innovation: 4 hours to present upstream/downstream to authorities). Support documents structured verbatim for internal investigation.
Which BATCH macros should be used and which segments should be prioritized?
BATCH macros and the segment matrix accelerate compliant responses.
8 essential macros
BATCH-READ-01: where to find the batch number on the packaging
BATCH-LOOKUP-OK: batch(es) confirmed for the order
BATCH-FEFO-01: different batches between orders, normal
BATCH-RECALL-YES: recalled batch, instructions + refund
BATCH-RECALL-NO: batch not affected, recalled batches listed
BATCH-QUAL-01: complaint received, 48h quality investigation
BATCH-LABEL-MISS: missing label, INCO breach, remedy
BATCH-HANDOFF: immediate quality/legal escalation
DTC Food segment
Dominant volume: batch_recall_check, batch_quality_issue, batch_read_help. 30 min recall SLA. Daily RappelConso list sync.
Cosmetics and Beauty segment
Batch + PAO (period after opening). Intent batch_read_help adapted for bottle. Fewer food RappelConso recalls, but possible ANSM alerts.
Textile and Premium segment
Production batch = workshop traceability (#311). Authenticity questions. BATCH-POLICY distinguishes unit serial number vs manufacturing batch.
Which KPIs should be measured for batch support and customer traceability?
Measure batch resolution and recall responsiveness, not the raw volume of "batch" tickets.
Monthly BATCH KPIs
batch_ticket_rate: BATCH-INTENT tickets / batched product orders
batch_lookup_sla: % of order lookups under 4-hour SLA
batch_recall_response_time: batch_recall_check response time
batch_false_recall_reassurance: "not recalled" errors when the batch was actually affected (target 0)
batch_lot_cluster_count: batches with ≥ 3 quality complaints within 7 days
batch_missing_label_rate: missing batch labels / deliveries
batch_first_contact_resolution: closed without quality escalation
Objectives
batch_lookup_sla > 95%, batch_false_recall_reassurance = 0, batch_recall_response_time < 30 min during active crises. Hello Harel cites 600+ food recalls in France 2024-2025: prepare processes before an incident occurs (Hello Harel 2026).
Quality Review
Weekly during active recall periods. Monthly: top batches by batch_lot_cluster_count → production review.
How does Qstomy speed up batch lookup and recall verification?
Qstomy automates BATCH-INTENT, batch photo collection, Shopify/WMS order lookup, and BATCH-RECALL scripts, without confirming a recall status outside the official list.
Capabilities
Intent
batch_read_help: packaging visuals by categoryIntent
batch_order_lookup: batch by line item post-authIntent
batch_recall_check: cross-referencing versioned recall registryBatch photo upload + optional OCR
Quality handoff payload (batch, order, photos, cluster flag)
Bridge trace_recall_check (#312)
DTC Encrypted Scenario
Artisanal grocery brand, 1,900 batched orders/month. Before #327: 34 batch tickets/month, batch_lookup_sla 71%, batch_first_contact_resolution 54%, 1 false recall reassurance incident. After BATCH-POLICY + Qstomy (8 weeks): tickets 19/month, lookup_sla 97%, FCR 81%, batch_false_recall_reassurance 0, batch_recall_response_time 12 min median (crisis simulation). Traceability CSAT 4.5/5.
Integration
Sync recall registry + BATCH-POLICY. See AI customer support, demo. Next: recall bot (#328), crisis plan (#329).
Which playbooks should be deployed to structure batch support?
Playbook 1: 90-day batch ticket audit (3 h)
Export "batch", "recall", "manufacturing number". Classify BATCH-INTENT. Measure lookup vs recall vs quality.
Playbook 2: BATCH-POLICY + recall registry (1 d)
14 blocks section 4. Connect RappelConso feed → internal Notion. Define crisis owner.
Playbook 3: BATCH-LOOKUP + macros (4 h)
Test lookup 20 ERP orders. Publish 8 macros. Form BATCH-RECALL tree section 7.
Playbook 4: BATCH-READ page + visuals (2 d)
Top 10 packaging SKUs. Help center link. QA bot #312 trace_batch_order if active.
Playbook 5: recall simulation (3 h quarterly)
Fictional batch L-TEST-RECALL. Measure batch_recall_response_time and batch customer export. Link crisis plan (#329).
Useful linking
Enzo
July 7, 2026
