Batch and Lot-Date Tracking at German Prep Centres: FIFO Workflows for Expiry-Sensitive SKUs
Batch and Lot-Date Tracking at German Prep Centres: FIFO Workflows for Expiry-Sensitive SKUs
FBA Prep Germany
We streamline your German Amazon operations by handling FBA prep, managing removal orders, and forwarding shipments to any German Fulfillment Center for FBA and Vendor accounts.
A cosmetics seller ships two batches of the same SKU to a German prep centre six weeks apart. Both arrive, both get prepped, both enter Amazon inventory. Six months later, the newer batch has sold through while the older batch — still sitting in an FC — is approaching its expiry window. Amazon flags it. The seller raises a removal order. The cost is not just the removal fee; it is the margin on every unit that could have sold first.
This is not a rare edge case. It is what happens when Amazon inventory prep storage relies on visual rotation rather than a logged FIFO system. For expiry-sensitive categories — supplements, cosmetics, food-adjacent products — batch and lot-date tracking at intake is the control point that prevents this outcome. This article explains how a German prep centre enforces FIFO operationally, from intake logging through to pick sequencing and seller reporting.
Why Manual Rotation Fails Expiry-Sensitive SKUs
Manual stock rotation sounds straightforward: older stock goes to the front, newer stock goes behind. In a low-volume, single-SKU environment, it works. In a prep centre handling dozens of sellers and hundreds of active SKUs, it breaks down quickly.
The failure mechanism is not carelessness. It is the absence of a data layer. When a picker pulls units for an FBA shipment, they work from a location, not from a batch record. If two pallets of the same SKU sit in adjacent bays — one from March, one from May — the picker has no system-level instruction telling them which pallet to draw from first. They pick from whichever is physically accessible.
For non-perishable goods, this is a minor inefficiency. For expiry-sensitive SKUs destined for Amazon FBA prep in Germany, it is a margin risk. Amazon's receiving system does not reorder inventory by expiry date once it is inside the FC. The sequence in which units enter the inbound shipment determines the sequence in which they are available to sell. If newer-dated units enter first, older-dated units may sit until they are close to or past the threshold Amazon requires for customer-facing inventory.
Batch and lot-date logging replaces the assumption of correct rotation with a verified, system-driven pick sequence. That is the operational difference this article covers.
What Batch Logging Captures at Intake
When a shipment arrives at a German prep centre, batch logging begins before units are moved to storage. Each carton or pallet is checked against the delivery note, and the lot number or production batch code is recorded against the SKU and the quantity received.
The key data fields captured at intake are: the lot or batch identifier printed on the unit or outer carton, the best-before or expiry date associated with that batch, the quantity received per batch, the date of arrival, and the storage location assigned. This creates a batch record that is distinct from the general inventory count.
For sellers running Amazon FBA prep in Germany across multiple product lines, this means each SKU can have multiple open batch records simultaneously — each with its own expiry date and remaining quantity. The prep centre's warehouse management system holds these records and uses them to drive pick sequencing. Without this intake step, FIFO is a policy intention rather than an enforced workflow. With it, the system knows which batch to draw from before the picker reaches the shelf.
What Breaks Without Batch-Level Records
When intake logging captures only total quantity — not batch identity or expiry date — the prep centre loses the ability to enforce FIFO at the pick stage. The consequence is not immediately visible. Inventory counts look correct. Shipments go out on time. The problem surfaces later, when Amazon flags units approaching expiry inside the FC or when a customer receives a product with a shorter remaining shelf life than expected.
For sellers using long-term storage for e-commerce inventory, the risk compounds over time. A batch that was not rotated correctly in month one may sit undisturbed for several months while newer stock moves. By the time the issue is visible, the options are limited: raise a removal order, accept a disposal fee, or absorb the stranded inventory cost.
The commercial consequence of missing batch records is not a single incident — it is a recurring margin drain that is difficult to trace back to the intake failure that caused it. Sellers often attribute it to slow sales velocity rather than incorrect rotation, which means the root cause goes unfixed.
Shelf-Life Thresholds and the Prep Centre's Role
Amazon sets minimum remaining shelf-life requirements for products it will accept into FCs and make available for sale. These thresholds vary by category and are enforced at receiving. A unit that arrives at an Amazon FC below the required remaining shelf life may be refused, flagged as unsellable, or disposed of — generating a cost the seller did not plan for.
A German prep centre handling expiry-sensitive SKUs needs to apply its own shelf-life threshold check before units leave for the FC. This is a pre-Amazon storage control point. When batch records are in place, the prep centre can filter the pick queue by remaining shelf life and exclude batches that fall below the seller's configured threshold.
This threshold is typically set by the seller in coordination with the prep centre — for example, units must have a minimum number of months remaining at the point of FC delivery. The prep centre applies this rule at the pick stage, not at the point of Amazon receiving. Catching a short-dated batch before it enters an inbound shipment avoids the receiving rejection and gives the seller time to decide: expedite sale through another channel, or raise a removal from the prep centre's pre-Amazon storage buffer.
FIFO Pick Sequencing: How It Works in Practice
FIFO pick sequencing is the operational output of batch logging. Once intake records exist for each batch — with lot identifier, expiry date, quantity, and location — the warehouse management system can generate pick instructions that always draw from the earliest-expiry batch first.
In practice, this means the picker receives a task that specifies not just the SKU and quantity, but the exact batch to pick from and the storage location of that batch. If a seller's inbound shipment requires 200 units of a supplement SKU and there are two open batches — one expiring in eight months and one expiring in fourteen months — the system directs the picker to the eight-month batch first, up to its available quantity, before drawing from the fourteen-month batch.
This sequencing logic holds even when batches are stored in different physical locations within the prep centre. The system resolves the pick order before the picker moves. The picker does not make a rotation decision; they execute a system-generated instruction.
For sellers managing Amazon sellers storage Germany across multiple SKUs with overlapping batch cycles, this matters at scale. A prep centre handling fifty expiry-sensitive SKUs simultaneously cannot rely on individual pickers to remember which pallet arrived first. The batch record and the pick instruction carry that logic. The picker's job is execution, not inventory management.
Configuring Batch Rules for Your SKU Profile
Not every expiry-sensitive SKU has the same rotation requirement. A supplement with a two-year shelf life and steady weekly sales velocity has a different risk profile than a cosmetic with a twelve-month shelf life and seasonal demand spikes. Batch rules at a German prep centre should reflect this difference.
Sellers working with a prep centre on Amazon FBA prep in Germany can typically configure per-SKU or per-category rules covering: the minimum remaining shelf life at point of FC dispatch, whether mixed-batch shipments are permitted or whether each inbound shipment must contain a single batch, and the alert threshold at which the prep centre flags a batch to the seller before it reaches the minimum.
Setting these rules at onboarding — rather than after the first rejection — is the correct sequence. A prep centre that captures these parameters at intake can apply them automatically at the pick stage. A prep centre that does not have this configuration layer will default to a generic rotation policy that may not match the seller's actual risk exposure.
When FIFO Sequencing Surfaces a Problem
FIFO sequencing does not just prevent errors — it also surfaces inventory problems that would otherwise stay hidden until they become costly. When the system attempts to build a pick list and finds that the earliest-expiry batch falls below the configured shelf-life threshold, it generates an exception rather than proceeding with the pick.
This exception is the operational signal that matters. It tells the seller: you have units in pre-Amazon storage that cannot go to the FC under current rules. The seller then has a decision to make before the shipment is built, not after Amazon refuses receiving.
Common decisions at this point include: adjusting the inbound plan to use a later-expiry batch, requesting a seller-side review of the flagged units, routing the short-dated batch to a different sales channel, or initiating a removal from the prep centre's storage buffer. Each of these options is available when the exception is caught at the prep stage. None of them are clean options once the units are inside an Amazon FC and flagged at receiving. The FIFO exception is not a failure of the system — it is the system working correctly.
Example Workflow: Supplement SKU Across Two Batches
A seller sends 500 units of a supplement SKU to a German prep centre in March (Batch A, expiring January next year). In May, another 500 units arrive (Batch B, expiring July next year).
The prep centre records each batch separately with its lot ID, expiry date, quantity, and location. The seller has set a minimum shelf-life requirement of four months at FC dispatch.
In June, the seller requests 300 units. Batch A still has 500 units and seven months of shelf life remaining, so all 300 units are allocated from Batch A.
In October, the seller requests another 300 units. Batch A has 200 units left but only three months of shelf life remaining, below the four-month threshold. The system flags an exception, and the seller chooses to route those 200 units to a DTC channel while using Batch B for the Amazon shipment. This avoids FC rejection and removal orders.
Reporting Back to the Seller: What the Batch Log Should Show
Batch tracking at the prep centre level is only operationally useful if the seller can see the data. A batch log that exists inside the prep centre's WMS but is not accessible to the seller creates an information asymmetry: the prep centre knows which batches are aging, but the seller cannot plan around that information.
Effective seller-facing batch reporting covers at minimum: current open batches per SKU with lot identifier and expiry date, remaining quantity per batch, the date each batch entered storage, any exceptions generated during recent pick cycles, and batches approaching the configured shelf-life threshold within a defined forward window.
For sellers managing Amazon inventory prep storage across multiple SKUs, this reporting functions as an early-warning system. A batch approaching threshold in sixty days is a planning input, not a crisis. The seller can adjust inbound plans, increase sales velocity on that SKU, or arrange a pre-Amazon storage transfer to a different channel before the threshold is breached.
Sellers who receive this data only on request — rather than as a scheduled report or live dashboard view — are operating with a lag. By the time they ask, the batch may already be below threshold. Proactive batch reporting is the difference between inventory management and inventory recovery. A prep centre that builds this reporting into the standard service relationship removes a recurring planning gap for expiry-sensitive sellers.
Intake Checklist: What to Verify at Arrival
- Lot number or batch code recorded per carton or pallet
- Best-before or expiry date captured per batch, not per SKU
- Quantity per batch confirmed against delivery note
- Storage location assigned and linked to batch record in WMS
- Seller-configured shelf-life threshold applied at intake
- Mixed-batch cartons flagged and handled per seller rule
- Intake record confirmed and visible in seller reporting within agreed SLA
Pick and Dispatch Checklist: What to Verify Before Shipment
- Pick list generated from batch records, not from general inventory location
- Earliest-expiry batch assigned first per FIFO rule
- Remaining shelf life checked against seller threshold before pick is confirmed
- Exception raised and seller notified if any batch falls below threshold
- Mixed-batch shipment rule applied if seller has restricted single-batch inbounds
- Batch identifiers recorded against outbound shipment for traceability
- Post-dispatch batch record updated to reflect quantity drawn
Putting Batch FIFO Into Operation: The Setup Sequence
Sellers who want batch FIFO enforced at a German prep centre need to complete a setup sequence before the first expiry-sensitive shipment arrives. Attempting to retrofit batch tracking after inventory is already in storage creates gaps: units already on shelf have no batch record, which means the system cannot sequence them correctly until they are physically audited and re-logged.
The correct sequence begins at onboarding. The seller provides the prep centre with the SKU list for expiry-sensitive products, the lot or batch code format used by their supplier, the minimum remaining shelf-life threshold per SKU or category, and the rule for mixed-batch shipments. The prep centre configures these parameters in the WMS before the first inbound arrives.
When the first shipment lands, the intake team applies the batch logging protocol immediately. Every subsequent shipment follows the same intake process. The batch record builds over time, and the FIFO pick logic has accurate data to work from on every outbound cycle.
For sellers already using Amazon FBA prep in Germany without batch tracking in place, the transition requires a physical audit of current stock to establish opening batch records. This is a one-time cost. Once the opening records exist, the ongoing process is the same as for a new onboarding. The audit is worth completing before the next inbound shipment adds more untracked inventory to the storage buffer. Delaying it compounds the gap.
Batch Tracking Across Multiple SKUs: Scaling the Model
Managing a single expiry-sensitive SKU is straightforward. Managing multiple SKUs with different shelf-life requirements requires a systematic approach.
For sellers using Amazon storage in Germany, the prep centre's WMS should maintain batch rules for each SKU individually. A supplement and a cosmetic, for example, may have different shelf-life thresholds and handling requirements. The system applies the correct rules automatically during allocation and dispatch.
At scale, reporting becomes equally important. Instead of reviewing individual batch logs, sellers need a consolidated view that highlights the SKUs closest to their shelf-life thresholds. Effective pre-Amazon storage management therefore depends on both physical inventory control and clear data visibility, enabling sellers to make informed replenishment and allocation decisions.
Intake Control
Batch logging starts at arrival. Every lot number and expiry date is recorded per SKU before units move to storage. No batch record means no FIFO enforcement downstream.
Pick Sequencing
The WMS assigns picks from the earliest-expiry batch first. Pickers follow system instructions, not physical proximity. Shelf-life threshold checks run automatically before each pick is confirmed.
Seller Reporting
Open batch records, remaining quantities, expiry dates, and threshold alerts are visible to the seller. Proactive reporting replaces reactive discovery when batches approach their dispatch limit.
What to Decide Before Your Next Expiry-Sensitive Shipment
If you are shipping cosmetics, supplements, or any expiry-sensitive SKU to a German prep centre, the question to resolve before the next inbound is not whether FIFO is a good idea — it is whether your current prep centre has the batch logging infrastructure to enforce it.
The practical checks are straightforward. Does the prep centre record lot numbers and expiry dates at intake, or only total quantity? Does the WMS generate pick instructions from batch records, or from storage location? Does the seller receive proactive batch reporting, or only on request? Is there a configurable shelf-life threshold that triggers an exception before a short-dated batch enters an inbound shipment?
If the answer to any of these is unclear or negative, the risk is already present in your current inventory. Units in pre-Amazon storage without batch records are rotating on assumption, not on data. For low-volume, single-batch SKUs, that assumption may hold. For sellers managing multiple active batches across a catalogue of expiry-sensitive products, it will eventually produce a removal order, an FC rejection, or a stranded inventory cost that traces back to an intake process that never captured the data needed to prevent it.
The setup investment is a one-time audit and configuration. The ongoing benefit is a pick process that enforces FIFO without relying on individual judgment at the warehouse floor level.
If you are managing expiry-sensitive SKUs through Amazon FBA prep in Germany and want to confirm whether your current prep workflow includes batch logging, FIFO pick sequencing, and proactive shelf-life reporting, FLEX. can review your intake and storage setup and identify where the gaps are before they produce a cost.
Contact FLEX. to discuss batch tracking configuration for your SKU profile and storage buffer at our German prep centre.
