Infant formula receiving inspection checklist showing HiPP and Holle products, SKU verification, lot numbers, use-by dates and packaging checks

Infant Formula Receiving Inspection Checklist for Retailers

October 07, 2026

Quick answer: A receiving inspection for infant formula should verify product identity, market version, case quantity, lot/batch code, use-by date, packaging integrity, and purchase-order accuracy before stock is released for sale. Any mismatch, damaged unit, unreadable code, or questionable case should be quarantined until it is resolved. A disciplined receiving process supports traceability, FEFO rotation, recall response, and cleaner inventory data.

Why receiving inspection matters for infant formula

Infant formula is a date-sensitive, highly regulated food category. A case can arrive with the correct brand name but still contain the wrong stage, market version, pack size, or lot. That is why receiving should verify the exact SKU rather than relying on the front-of-box design.

FDA guidance for formula bought by the case specifically recommends checking that lot numbers and use-by dates on the individual containers and the outer case match, and checking containers for damage. EU General Food Law also requires food traceability through production, processing, and distribution, including the ability to identify suppliers and business customers. These principles make receiving records a core control point for a wholesale operation.

Infant formula receiving checklist

Check	What to verify	If it fails
Purchase order	Supplier, PO number, ordered SKU, quantity, case configuration	Hold discrepant cases and reconcile before booking into available stock
Product identity	Brand, product family, stage, market version, package format	Quarantine if the received SKU does not exactly match the order
GTIN/EAN / item code	Barcode or manufacturer item identifier where available	Investigate mismatches rather than substituting by product name
Lot / batch code	Readable code on every sellable unit or traceable case grouping	Do not release unidentified stock
Use-by date	Date is legible, plausible, and consistent with commercial shelf-life requirements	Quarantine short-dated or inconsistent stock for review
Case-to-unit match	Outer-case lot/date information matches the inner containers when both are present	Investigate before stock release
Packaging integrity	No crushed, opened, punctured, wet, leaking, swollen, or materially compromised packs	Segregate damaged units/cases
Count	Actual units per case and number of cases received	Record shortage/overage against the PO
Label / market version	Country-specific package and language match the expected SKU	Keep separate from other market versions
Release status	All checks completed and discrepancies closed	Keep stock in quarantine status

1. Match the shipment to the purchase order

Start with the commercial record before inspecting individual packs. Confirm:

supplier name and purchase-order number;
expected product and stage;
country-market version where relevant;
case quantity and units per case;
pack size; and
expected item code, GTIN/EAN, or manufacturer reference if your system stores it.

This prevents a common receiving error: accepting a visually similar product that is actually a different stage, market version, or formula family.

2. Verify exact SKU identity

Do not receive inventory under a generic brand-level label such as “HiPP Formula” or “Holle Formula.” Record the exact commercial identity.

For example, a HiPP shipment can include standard Combiotic, HA, Comfort, or Anti-Reflux products. Those should remain separate in the catalog and warehouse. The same applies to Holle cow, goat, and A2 families and to different stages within each range.

For assortment architecture, see our European Baby Formula Assortment Guide for Retailers, Holle Formula Assortment Guide, and Specialty Formula Assortment Guide.

3. Capture lot or batch codes before stock release

Lot and batch information is essential for targeted recall response. Recent FDA infant-formula recall notices identify affected product by batch or lot code and use-by date, illustrating why item-level traceability matters.

At receiving, capture the code in a way that can later answer three questions:

Which supplier shipment did this lot come from?
Where is the remaining stock located?
Which business customers received units from this lot, where your operating model requires downstream traceability?

For the operating model behind this, use our Batch & Lot Traceability for Infant Formula Buyers.

4. Verify the use-by date and remaining shelf life

Do not treat the date code as a cosmetic label field. FDA regulations require a use-by date on infant-formula containers sold in the U.S., and FDA explains that the date reflects manufacturer data supporting nutrient content and acceptable product quality through that date.

Your receiving team should compare remaining shelf life with:

expected sell-through;
supplier lead time;
case depth;
customer shelf-life expectations; and
the business's short-dated inventory policy.

Use our Infant Formula Shelf-Life Planning for Retailers and FEFO Inventory Management playbook to turn receiving dates into stock-rotation rules.

5. Compare outer-case and inner-unit codes

When both the shipping case and individual containers display lot or date information, compare them. FDA specifically advises case purchasers to make sure the lot numbers and use-by dates on containers and boxes match.

A mismatch does not automatically prove that product is unsafe, but it is a receiving exception that should be resolved before the units are made available for sale.

6. Inspect packaging integrity

Check both the master case and the sellable units. Examples of exceptions include:

opened or re-taped cases with unexplained contents;
crushed corners that compromise the inner package;
punctures, tears, moisture, leaks, or contamination;
broken seals;
unreadable or altered date/lot coding; and
evidence of relabeling or identity tampering.

FDA warns that counterfeit formula can involve relabeling or altered use-by dates. When product identity or coding is questionable, do not rely on appearance alone.

7. Count cases and sellable units

Receiving quantity should be confirmed physically rather than copied from the packing slip. Record:

cases expected;
cases received;
units expected per case;
units actually present;
damaged or quarantined units; and
net units released to available inventory.

This also protects landed-cost calculations. A case that invoices correctly but arrives short changes the actual cost per sellable box. See How Wholesale Baby Formula Case Pricing Works.

8. Keep country-market versions separate

European formula packaging can vary by market even when the brand and stage look similar. Label language, pack size, naming, recipe, barcode, and regulatory presentation can differ.

Receiving should therefore record market version as a structured field when relevant rather than relying on warehouse staff to recognize packaging visually. For a concrete example, see our HiPP German vs. Dutch vs. UK Formula buyer comparison.

9. Quarantine exceptions instead of improvising substitutions

Create a simple inventory state for stock that has not passed receiving QA. Typical quarantine reasons include:

wrong SKU or stage;
unexpected market version;
lot/date mismatch;
short remaining shelf life;
damaged packaging;
missing or unreadable traceability codes;
quantity discrepancy; or
possible recall match.

Quarantined stock should not be allocated to orders until the exception has been documented and resolved.

10. Check recall information when something looks wrong

Receiving teams do not need to perform a recall search on every normal case, but they should know where to verify alerts when a lot, package, supplier communication, or product condition raises a concern. FDA recall notices routinely identify infant-formula products using product name, batch/lot code, package format, and use-by date.

A recall workflow is much faster when those same fields already exist in the receiving record.

Minimum receiving record for each shipment

A practical B2B receiving record should contain:

receipt date and receiving location;
supplier and PO number;
SKU / internal item number;
brand and exact product title;
stage and formula family;
market version;
GTIN/EAN or manufacturer reference where available;
lot/batch code;
use-by date;
case count and units per case;
quantity accepted;
quantity quarantined or rejected;
exception reason;
photos for damaged or disputed shipments where useful; and
name or ID of the receiver.

How receiving connects to the rest of inventory control

For the replenishment step that follows clean receiving data, use our Baby Formula Reorder Point & Safety Stock Guide for Retailers.

Receiving inspection is the first operational checkpoint, not an isolated task. Clean receiving data feeds:

FEFO: release the earliest eligible use-by dates first;
shelf-life planning: avoid buying more inventory than can sell through safely;
traceability: identify affected lots quickly during a recall;
reordering: calculate available and quarantined stock correctly;
margin analysis: base cost calculations on actual sellable units; and
customer service: answer product-identity and market-version questions with records rather than assumptions.

For the upstream supplier and fulfillment controls, also see How to Evaluate a Baby Formula Wholesale Supplier and How European Formula Wholesale Fulfillment from Germany Works.

Frequently asked questions

Should every case of infant formula be opened during receiving?

The inspection method should match your packaging configuration and quality procedure. At minimum, verify the information needed to identify the product, lot/date, quantity, and visible package condition. If a case is damaged, inconsistent, or suspicious, increase inspection depth and quarantine it while the discrepancy is investigated.

What should happen if the case and inner units show different lot numbers?

Treat it as a receiving exception. FDA specifically recommends checking that case and container lot numbers and use-by dates match when formula is purchased by the case. Do not release inconsistent stock until the supplier or manufacturer documentation resolves the mismatch.

Should short-dated formula automatically be rejected?

Not necessarily. The decision should follow your agreed supplier terms, customer requirements, expected sell-through, and short-dated stock policy. What matters is that the remaining shelf life is identified before the stock enters normal available inventory.

Why record market version if the formula name is the same?

Because country-specific versions can differ in packaging, naming, pack size, barcode, or recipe. A market-version field reduces substitution and catalog errors.

Why are lot codes important if the product has a barcode?

A barcode normally identifies the product configuration, while the lot/batch code identifies a specific production batch. Recall notices commonly target specific lots rather than every unit sharing the same retail barcode.

Sources

Reviewed October 7, 2026. This guide is an operational receiving framework, not a substitute for the requirements that apply to a specific jurisdiction, supplier agreement, warehouse, or product.