FMCG Stock Management: Stop the Spoilage and Stockouts

The drinks bestseller is unavailable at one depot while another site holds more than it can sell. A slower line has plenty of stock, but much of it is approaching its usable deadline. Purchasing sees the company total and orders more of both.

The numbers may add up. They still do not explain what the business can fulfil, where it can fulfil it from or how much stock is likely to remain unsold.

FMCG stock management connects quantities, locations, demand and shelf-life information so a business can replenish fast-moving consumer goods without losing sight of waste risk. Food, drink and other consumer products have different requirements; not every FMCG line is perishable or has the same replenishment pattern.

The practical goal is a shared, current inventory view that preserves the detail behind availability: batch, site, condition, reservations and relevant dates. A single company-wide total cannot replace those records.

This guide explains how to manage fast and slow lines, plan replenishment by location, track ageing batches and prove improvements before expanding the system.

The same stock total can hide a shortage at one site and excess at another. Location and shelf-life detail change the decision.

Key Takeaways

• FMCG inventory can create stockouts and ageing excess at the same time. Monitor availability and waste risk together.
• Preserve quantities by SKU, batch, location and status rather than treating all physical stock as sellable.
• Expiry-based FEFO can be more appropriate than receipt-based FIFO when later deliveries have shorter shelf life.
• Replenishment needs product and location rules informed by demand, lead time, incoming supply and usable stock.
• Transfers, reservations, returns and write-offs need clear lifecycle records, especially across retail, wholesale and online channels.
• Start with a bounded group of products and sites, then measure stock accuracy, service and waste using consistent definitions.

In this guide:

• Why fast movers run out
• Why slow lines become ageing excess
• The inventory detail you need
• Manage stock across sites and channels
• Set replenishment rules by product and location
• Worked stock and shelf-life examples
• Measure the causes of losses
• Choose software and pilot the change
• Frequently asked questions
• How OpsMavix can help

1. Why Fast Movers Run Out Before the Count Catches Up

A count is a snapshot. The movements after that count determine whether the recorded balance remains useful.

If receipts are entered late, orders are allocated twice or dispatches are missing, the gap between physical stock and recorded availability grows. High transaction volume can expose the gap quickly.

Distinguish a stockout from overselling

A stockout means the required stock is unavailable at the relevant time or place. Overselling means accepting commitments that available supply cannot fulfil under the agreed rules.

The causes overlap, but the remedies can differ. A site may run out because its replenishment was insufficient even though the records are accurate. An online channel may oversell because its advertised availability was stale.

Check a recent incident from order acceptance through allocation and dispatch. Identify whether the failure was demand planning, missing movement capture, allocation or an integration delay.

Update at the event that matters

Agree when stock becomes available, reserved, picked and dispatched. These events should not all reduce the physical balance independently.

For example, reservation commits availability; dispatch records goods leaving. Subtracting the same order twice can create a false shortage.

A current view also needs visible failures. If a channel update did not arrive, the team should know that its figure is uncertain rather than assuming every integration succeeded.

2. Why Slow Lines Become Ageing Excess

Slow-moving stock ties up cash and space. For date-sensitive products, the opportunity to sell or use it may also narrow as the batch ages.

A quantity-only report cannot show that urgency. Two hundred cases with months of usable life are different from two hundred cases that will soon fail customer shelf-life requirements.

Keep the date types distinct

For food, use-by and best-before dates have different meanings. The Food Standards Scotland date guidance identifies use-by as a safety date and best-before as a quality date. Do not make a blanket rule that all stock beyond either date is equivalent.

UK government-published stock-control guidance also emphasises regular checks and controls for use-by stock. Configure the appropriate handling process for the product; the software is not a substitute for those checks.

Other consumer goods may have different shelf-life, storage or product-version requirements. Record the relevant rules rather than applying a food template to the entire catalogue.

Rotate eligible stock in the right order

FIFO selects by receipt chronology. FEFO selects by the relevant expiry or removal date. A newer delivery can need to leave first if it has less remaining life.

Before ranking batches, exclude those that are held, damaged or otherwise unsuitable. Check customer requirements at the expected delivery date, not just the day the order is entered.

Guided picking can help, but it needs the correct dates and validation of the selected batch. The shelf layout should also make the recommended stock accessible.

Act while options remain

Near-date stock needs an owner and a decision. Depending on the product and permitted process, that may involve transferring it to suitable demand, reviewing purchasing, arranging a supplier return or another approved action.

An alert that appears after the usable window has closed is a loss report. Earlier visibility gives the team time to respond.

3. The Inventory Detail You Need Beyond a SKU Total

A shared inventory view can show company totals while preserving the detail needed for fulfilment and replenishment.

Spreadsheets are a question of control and workload

A spreadsheet can hold quantities, dates and sites. The practical limit is maintaining consistent records, permissions and transaction history while several people change them.

Investigate repeated copying, conflicting versions and unexplained adjustments. These are stronger reasons to change the process than the number of tabs alone.

The same diagnosis underpins why stock never matches the system: follow the movements rather than assuming another count will solve the recording gap.

Get receiving right

Record actual quantity, unit, lot, dates, location and relevant status. Review short-dated deliveries before they become ordinary available stock.

Where labels are scanned, confirm whether the barcode identifies only the product or also its batch. A product scan does not automatically capture shelf life.

Receiving and movement capture provide the batch and location detail that replenishment decisions rely on.

4. Manage Stock Across Sites and Channels

Several sites should have different balances because they hold different goods. The aim is agreement about those balances, not forcing every site to display an identical number.

A warehouse, depot, shop and 3PL may also have different update timing, inspection processes and permitted fulfilment routes.

Make transfers a lifecycle

Moving 30 cases between depots should show:

• The source allocation before dispatch.
• The quantity leaving the source.
• Stock in transit while it is moving.
• The quantity actually received at the destination.
• Any damage or receipt discrepancy.

Do not make the goods freely available at both depots during the move. Preserve the lot and relevant dates instead of making a transfer appear to create newly manufactured stock.

Publish availability to the right channels

Retail, wholesale order management and eCommerce channels can draw on shared inventory records. Their advertised availability still needs routing and allocation rules.

Stock at a distant depot may be physically present but unable to meet tomorrow’s delivery. A held lot may be counted but not eligible to sell. Different customers may have different shelf-life requirements.

Handle delay explicitly

Define how stale channel data is detected, failed updates are retried and conflicting orders are resolved. Stock buffers or channel allocations can reduce exposure during delays, but they do not guarantee zero overselling.

For 3PL stock, reconcile movement references and timestamps. Confirm whether its feed includes reservations, holds and lots, rather than assuming its headline quantity has the same meaning as yours.

5. Set Replenishment Rules by Product and Location

A useful rule considers what a line needs during replenishment, what is already committed and what incoming supply can be relied on.

The same SKU can move quickly at one site and slowly at another. Different transfer routes or suppliers can also create different lead times.

Define the quantity being compared

A replenishment trigger might evaluate inventory position, projected availability or another agreed measure. Label it clearly.

A simplified inventory position can be expressed as usable on-hand stock plus relevant incoming supply minus committed demand. That figure is only meaningful when the timing and eligibility of those records are considered consistently.

Near-expiry stock that cannot serve the target demand should not hide a shortage. Conversely, overlooking a confirmed receipt can produce unnecessary buying.

Review demand and lead time

Use an appropriate demand period and account for promotions, seasonality and unusual orders. Historical sales during a stockout can understate demand because customers could not buy the product.

Lead time should include the relevant ordering, supply, receiving and release steps. An average alone can hide recurring delays.

Safety stock is a chosen allowance for uncertainty, not a guarantee. Review its effect on service and ageing inventory together.

Treat order quantity separately from the trigger

Reaching a reorder point answers when to review or replenish. It does not determine how much to buy.

Case multiples, minimum order quantities, supplier schedules, storage capacity and usable shelf life affect the quantity. A minimum order that exceeds likely use may require a supplier or assortment decision rather than an automatic purchase.

Odoo’s replenishment-report documentation illustrates how rules, lead times and future demand can be considered together. Assess the actual settings in whichever tool you use.

6. Worked Examples: Reorder Risk and Ageing Stock

The following figures are hypothetical. They show the decisions a system should expose, rather than prescribing thresholds for every FMCG business.

Example A: a fast-selling depot line

Assume demand is 20 cases per working day, replenishment takes four working days and the chosen safety allowance is 30 cases.

Illustrative reorder point = 20 × 4 + 30 = 110 cases.

Now compare two positions:

At the later review, the position is below 110, so the replenishment rule calls for action under these assumptions.

This is not a time-phased forecast. The 60 incoming cases must arrive early enough to support the demand they are being counted against. If they arrive after a shortage occurs, the total of 100 does not explain that gap.

Example B: a slower batch with a short usable window

Suppose a lot has 80 uncommitted cases and ten remaining selling days before the relevant customer eligibility cutoff. Expected demand is three cases a day, with no other demand or competing batch assumed.

Expected use = 3 × 10 = 30 cases.

Potential excess = 80 − 30 = 50 cases.

At an illustrative stock cost of £12 per case, that is 50 × £12 = £600 of cost exposed to becoming unsold within the window. It is not an inevitable write-off: the demand assumption may change, and permitted actions may reduce the excess.

The useful alert appears now, while the team can review the options, rather than when the 50 cases are disposed of.

Example C: the company total hides a depot problem

Depot A holds 25 usable cases and has demand for 40. Depot B holds 70 and has demand for 20. Company stock is 95 against combined demand of 60.

There is no company-wide quantity shortage in this simplified snapshot. Depot A still has a 15-case local gap. A transfer can help only if it arrives before the required fulfilment time and the selected batches meet the customer’s requirements.

7. Measure the Causes of Stockouts and Write-Offs

Track availability, waste and accuracy together. Improving one measure by worsening another is not necessarily progress.

Keep the definitions consistent

Useful measures include:

• Order-line fill rate for demand due in the period.
• Stockout frequency or duration by SKU and site.
• Count differences by unit, lot and location.
• Near-date stock value within defined time bands.
• Write-off quantity and cost by cause.
• Supplier lead-time and remaining-shelf-life performance.
• Failed or delayed channel updates.

For fill rate, specify whether you measure lines, units or orders and whether partial fulfilment counts. Compare like with like.

Use reasons that support decisions

Separate expiry, damage, quality rejection, short receipt and unexplained count differences. Record the lot, quantity, site, date and relevant approval.

A lost sale caused by insufficient buying is different from one caused by an inaccurate online figure. Label the incident accordingly so the response addresses the right layer.

Do not equate all unfulfilled order value with lost margin or treat every write-off as a rotation failure.

Give each alert an owner

A near-date batch needs a commercial or operational action. A failed update needs a recovery action. A supplier delay needs revised availability and purchasing follow-up.

A shared operations dashboard should show those responsibilities alongside the numbers.

Stock, orders and reporting need common references so the team can trace a shortage or write-off back to its cause.

8. Choose Software and Pilot the Change

Begin with a product group and one or two sites where the operational cost is visible. Include fast and slow lines so the pilot tests both availability and ageing risk.

Check current capability first

Existing inventory software may already support lots, expiry, locations and replenishment rules. Configuration, cleaner data or a supported connection may resolve the gap.

Compare improving the current tools, switching products and building a focused layer against the same requirements. A wider ERP may be appropriate where inventory sits within broader finance, production and multi-company needs. Neither ERP nor custom development should be the automatic answer.

Establish clean opening records

Reconcile selected stock by lot, site and status. Confirm units, dates, open reservations and expected receipts. Review unknown or conflicting records rather than filling gaps with invented values.

Agree record ownership and the cutover process so parallel spreadsheets do not create competing allocations.

Test representative exceptions

Verify a partial receipt, short-dated delivery, held lot, partial dispatch, cancelled order, return awaiting inspection and depot transfer.

Also test simultaneous channel demand, failed updates, retries and an incoming shipment arriving later than expected. Check that the system shows uncertainty without duplicating movements.

Review the result over a relevant period

Compare accuracy, service and manual reconciliation with the baseline. Waste improvements may take longer to observe because batches need to move through a meaningful shelf-life cycle.

Before expanding, define support, backup, integration maintenance and user training. For a custom system, confirm source access, ownership and handover alongside hosting and third-party costs.

Frequently Asked Questions

What is FMCG stock management?

It is managing inventory for fast-moving consumer goods using quantity, demand, location and relevant shelf-life information. The aim is dependable fulfilment with appropriate stock levels, traceability and visibility of waste risk.

Why do we have stockouts and excess stock at the same time?

Different products and sites have different demand, supply and shelf-life patterns. A company total or blanket replenishment rule can hide those differences. Review local availability, incoming timing and ageing stock separately.

Should FMCG stock use FIFO or FEFO?

FIFO prioritises receipt order; FEFO prioritises the relevant date. For date-sensitive goods, FEFO may better address short-dated later receipts. Both need eligibility checks for quality and customer requirements.

Does stock passing its best-before date always need writing off?

Best-before and use-by dates mean different things. Best-before relates to quality; use-by relates to safety. Apply the appropriate product handling and business requirements rather than treating the dates as interchangeable.

How should I set reorder points?

Start with demand during the relevant replenishment period and an appropriate allowance for uncertainty. Review by product and location, using incoming supply, commitments and eligibility. Determine the replenishment quantity separately.

Can stock at another depot prevent a local stockout?

Only if it is available, suitable and transferable in time. Preserve the source, transit and destination records and avoid advertising the same goods as free at both sites during the move.

Can spreadsheets manage FMCG stock?

They can support a controlled small operation. Repeated copying, conflicting records and untraceable changes indicate that the workflow needs stronger controls. Assess those symptoms before selecting new software.

Will automatic stock sync eliminate overselling?

It can reduce risk, but delays, failures and simultaneous demand can still create conflicts. Use appropriate allocations, exception handling and channel buffers where suitable, and monitor failed updates.

Do we need an ERP or a custom inventory system?

That depends on scope. Existing tools or integrations may meet the requirement; custom can address an important unsupported workflow. A broader ERP can fit wider coordinated needs. Compare equivalent requirements and lifetime costs.

How OpsMavix Can Help

OpsMavix helps growing FMCG businesses connect inventory records with replenishment and fulfilment decisions. We begin with the products, sites and incidents where stockouts or ageing excess create recurring cost.

We can help you:

• Map receipts, reservations, transfers, returns and write-offs.
• Define SKU, batch, location and availability records.
• Connect practical inventory workflows.
• Set product and location replenishment rules with visible exceptions.
• Bring shelf-life checks into receiving and picking.
• Connect wholesale orders and eCommerce channels to the agreed stock records.
• Make ageing quantities, shortages and update failures visible.
• Pilot the change with clear acceptance checks and a documented handover.

Bring a recent stockout and a recent write-off. We will trace the demand, dates, movements and replenishment decisions behind each to identify what needs changing first.

Book an Operations Leak Audit to map where FMCG stock accuracy, availability and shelf-life control break down.