Inventory Control in ERP: Replenishment, Near-Expiry Stock, and Exceptions

Inventory work is full of repeated decisions. Which location will run short? Is stock available elsewhere? Will a batch expire before demand consumes it? Should the business transfer, purchase, promote, return, or accept a shortage?

Oyo’s inventory review can assemble the evidence and prepare a controlled response. It should not optimize one metric while ignoring working capital, expiry, customer commitments, or source-location risk.

Build dependable inputs

Oyo needs:

• On-hand and available stock
• Reservations
• Open sales and purchase orders
• Transfers
• Forecast or demand rate
• Lead time
• Safety policy
• Pack and minimum order
• Batch and expiry
• Warehouse status
• Supplier status
• Cost and budget

Fix timing and unit errors before enabling rule-based actions.

Project availability

Calculate inventory over time by item and location:

Opening available + expected receipts - expected demand - required safety stock

Keep facts and estimates separate. Show the forecast source and confidence.

Transfer before purchase

Oyo should check eligible surplus elsewhere before recommending new purchasing.

It must protect the source warehouse, account for transfer lead time, batch and expiry, ownership, cost, and customer restrictions.

The proposal shows source, destination, item, batch, quantity, need date, and expected effect.

Prepare replenishment

Purchasing recommendations apply:

• Approved supplier
• Lead time
• Pack
• Minimum quantity
• Price tolerance
• Budget
• Order calendar
• Shelf life
• Capacity

Create a draft or request first. Procurement approves supplier commitment.

Near-expiry workflow

Oyo can:

1. Identify batches crossing a threshold.
2. Estimate consumption before expiry.
3. Check demand in eligible locations.
4. Consider transfer time and minimum shelf life.
5. Recommend reallocation.
6. Route promotion, return, or disposal decisions.
7. Track approved action.

Never transfer risk blindly to another branch.

Exception states

Use:

• Missing demand
• Missing lead time
• No eligible source
• Supplier blocked
• Budget exceeded
• Approval waiting
• Stock changed
• ERP action failed
• Duplicate prevented
• Manual planning required

Each exception needs an owner and next action.

Controls

Define item, warehouse, quantity, value, supplier, and time limits. Recheck availability at execution. Use idempotency. Apply ordinary ERP validation. Record trigger, evidence, proposal, approval, document, and confirmation.

Metrics

• Availability
• Stockout
• Inventory days
• Excess and obsolete value
• Near-expiry value
• Emergency purchase
• Transfer lead time
• Planner touch time
• Recommendation acceptance
• Exception and reversal

Measure working capital with service.

First release

Choose one item family and two or three locations. Run observation mode. Compare proposals with planners. Correct data and policy. Then permit approval-required transfers. Add purchasing only after the transfer workflow stabilizes.

Segment the item portfolio

One policy does not fit every item. Segment by demand, value, lead time, criticality, shelf life, supply risk, and substitution.

Examples include fast and stable demand, intermittent demand, long-lead imports, perishable goods, critical production material, promotional items, new items, and end-of-life stock.

Define the forecast, safety, review frequency, and approval for each segment. Oyo reviews use the assigned policy and highlight missing classification.

Improve lead-time evidence

Measure order approval, supplier confirmation, preparation, transit, receiving, quality, and putaway. Track median and variability by supplier, item, route, and period.

Use confirmed dates separately from estimates. Oyo can prepare policy evidence, but procurement approves a change.

Balance service and working capital

Availability can be improved by holding too much stock. Balance customer or production service, inventory value, expiry, emergency purchase, transfer cost, supplier minimum, and capacity.

Show the projected effect of every proposal. A purchase that protects service but creates six months of excess needs explicit review.

Supplier performance

Measure confirmation time, on-time delivery, fill, quality, price variance, shelf life, documentation, and lead-time variability.

Oyo can prepare exceptions and approved alternatives. It should not select an unapproved supplier or accept new terms.

Count and adjustment

Use cycle counting based on value, movement, variance, and risk. Control movement during count. Record system quantity, physical quantity, recount, reason, approval, and adjustment.

Oyo can prioritize counts and assemble history. Only physical count or trusted device evidence confirms physical stock. Do not let replenishment conceal shrinkage.

Reservations and allocation

Define whether stock is reserved by order, priority, date, customer tier, or production need.

During shortage, show affected commitments and alternatives. Authorized planners own allocation decisions. Record override reason and outcome.

Returns and blocked stock

Returned stock passes inspection before availability. Separate saleable, damaged, quality, expired, and supplier-return states.

Exclude blocked, quarantined, expired, recalled, and reserved stock from ordinary proposals.

Execution design

For each available action, specify document type, fields, status, permission, value and quantity limit, validation, duplicate prevention, approval, confirmation, and reversal.

A transfer action should not become a generic adjustment. A purchase-request action should not release a supplier order.

Exception review

Classify missing data, forecast uncertainty, no source, supplier block, budget block, approval delay, changed stock, ERP rejection, duplicate prevention, and physical difference.

Fix recurring root causes instead of staffing a permanent queue.

Acceptance tests

Test normal replenishment, stock elsewhere, source safety breach, near-expiry batch, supplier minimum, price tolerance, blocked stock, changed availability, duplicate, rejection, timeout, partial receipt, return, and reversal.

Confirm stock, commitment, finance impact, audit, and recovery.

Operating cadence

Review urgent availability daily, exceptions weekly, and policy monthly. Compare acceptance, override, error, service, inventory, expiry, emergency buying, planner time, and operating cost.

Expand rule-based execution only for stable low-risk segments.

Create the planning policy record

For each item segment, store:

• Planning method
• Review frequency
• Demand source
• Forecast horizon
• Safety rule
• Order cycle
• Lead-time source
• Minimum and pack
• Transfer priority
• Expiry rule
• Supplier list
• Approval
• Policy owner
• Effective date

Do not hide these values inside a written instruction. The ERP policy record should make them reviewable and versioned.

When policy changes, identify open recommendations that used the previous version. Recalculate them or retain the original policy reference.

Model multi-echelon inventory

Stock may exist at plant, central warehouse, regional depot, branch, van, store backroom, or shelf. Define which locations can supply one another, transfer lead time, cost, ownership, and receiving constraints.

Oyo should evaluate the network, not only one location. It should also avoid creating circular transfers or moving stock repeatedly between branches.

For a proposal, show the expected network effect before and after action. Include service risk at source and destination, quantity in transit, and remaining shelf life.

Handle new and discontinued items

A new item lacks dependable history. Use launch plan, comparable item, customer commitments, supplier minimum, and manual review. Keep initial authority narrow.

For discontinued items, stop ordinary replenishment, cancel inappropriate open supply, consume or transfer eligible balance, manage customer commitments, and review write-off risk.

Oyo can prepare tasks, but commercial, procurement, and finance owners decide disposition.

Plan for production materials

A production component needs demand from released and planned orders, bill-of-material quantity, yield or scrap factor, substitute policy, quality status, lead time, and line schedule.

Shortage analysis should identify affected production orders and customer commitments. A purchase quantity alone is not enough.

Where substitution is permitted, show specification, quality, cost, and affected orders. Require the authority defined by engineering, quality, and procurement.

Prevent alert overload

Group repeated signals for the same item and location. Suppress an alert while an approved action is already in progress unless the risk materially changes.

Prioritize by service impact, production impact, value, expiry, lead time, and exception age. Let planners see why one case ranks above another.

Measure alerts that lead to no action. A high rate may indicate poor policy, noisy demand, stale data, or a missing status.

Handover and continuity

Document policy, item segmentation, action scope, approval, exception states, monitoring, and manual planning. Train backup planners and administrators.

During an outage, protect reservations and avoid duplicate purchase or transfer actions. On recovery, reconcile manual documents with pending proposals before restarting execution.

Review the first full replenishment cycle after go-live. Compare availability, inventory, expiry, emergency actions, planner effort, exceptions, and Oyo review cost with the baseline.

Build the planner review screen

For each proposal, show item, location, current and projected availability, demand basis, open supply, batch and expiry, source alternatives, supplier terms, quantity, value, expected arrival, service effect, and working-capital effect.

Highlight missing data and policy conflict. Let the planner approve, change, reject, or take over with a recorded reason.

Group routine proposals but keep material exceptions visible. A batch action should not hide one item with unusual value, expiry, or production impact.

Confirm the outcome

Creating a transfer or purchase request is not the final objective. Monitor dispatch, receipt, supplier confirmation, delay, short receipt, quality hold, and updated projected availability.

If the expected result does not occur, reopen the exception with new evidence. Do not create another supply document without checking the first.

Audit the full decision

Retain trigger, policy, source records, forecast or estimate, alternatives, proposal, approval, action input, ERP document, confirmation, override, and recovery.

Sample decisions after launch. Confirm that source stock remained protected, purchase terms were approved, expiry rules were followed, and documents were not duplicated.

Expand by segment

Move from one stable item group to the next. Rebaseline demand, lead time, exception, and value. A policy proven for fast-moving packaged goods may not suit intermittent spare parts or critical imported material.

Keep new segments approval-gated until their evidence passes.

Review master-data health

Publish completeness for unit, pack, supplier, lead time, safety policy, batch rule, shelf life, location, and active status. Show records excluded from Oyo review work and the owner responsible for correction.

Measure how often a planner changes a proposal because master data is wrong. Correct recurring fields before broadening authority.

Archive obsolete items and relationships through a controlled process. Do not delete history or allow inactive records to re-enter planning through an old order or integration.

Good inventory decisions depend on dependable definitions. Oyo review quality cannot compensate for ambiguous units, locations, availability, or ownership.

Review commercial overrides

Track when sales, production, procurement, or management overrides an inventory proposal. Record the reason and expected outcome.

Some overrides reflect information outside the ERP, such as a promotion, supplier disruption, strategic customer, or maintenance event. Add reliable recurring information to the planning process.

Other overrides may protect a local target while harming the network. Review the later service, inventory, expiry, and cost result.

The aim is not to eliminate human changes. It is to learn which evidence and policy produce better decisions.

Feed verified lessons into the next policy version and test them against historical cases before production release.

Related Oyo guides

• ERP for FMCG distribution
• Supermarket ERP and POS

Sources and further reading

• GS1 traceability standard
• Odoo replenishment documentation
• ERPNext stock documentation
• NIST Risk Management Framework

Test one replenishment cycle

Bring an item family, three locations, demand history, open orders, lead times, and safety policy.

See Oyo monitor the business