Stock Adjustment Approval Workflow: UK Warehouse Guide

A stock adjustment approval workflow separates finding an inventory discrepancy from authorising the correction to the stock record. For a UK warehouse, that means recording the count, investigating the difference, approving the proposed treatment and retaining evidence of the movement that was actually applied.

Without that separation, a missing carton can become an unexplained write-off, a delayed receipt can be counted twice, or a well-intentioned correction can conceal the process fault that caused it. If your warehouse needs stronger links between movements, exceptions and accountability, explore the OpsMavix inventory automation system. Approval controls and any accounting handoff should be specified as part of the implementation, rather than assumed from a generic inventory feature list.

In 30 seconds: Treat the count as evidence, the adjustment as a proposed action and the applied movement as a separate result. Record the item, location, unit, count time, explanation and approver. Recheck movements that occurred after the count. Retain correction history and reconcile the outcome before closing the discrepancy.

Why counting and correcting need separate steps

A warehouse operative counts 18 units in a bin where the system shows 24. A supervisor changes the balance to 18. Later, the team finds six units on a trolley awaiting a transfer confirmation. The first correction made the bin appear accurate, but it did not establish what happened to the missing units or whether another location would now be wrong.

The purpose of approval is to improve the decision before a stock movement is posted. It should distinguish genuine loss, wrong-location stock, unrecorded receipts, timing differences and counting errors. Those situations may need different operational actions.

This guide focuses on the correction decision after a discrepancy is identified. The blind inventory count guide covers the counting method itself. A well-run count and a controlled adjustment process solve connected but different problems.

Define what needs approval

Not every correction needs the same route. Build an authority policy around the business’s risks, with input from warehouse management and finance. Avoid copying arbitrary approval values from another company.

Consider quantity, value, item sensitivity, repeat frequency, reason and location. A low-value discrepancy occurring every day may deserve more investigation than an isolated larger correction. Positive adjustments also need scrutiny: adding stock that is not actually available can cause delivery failures.

A reason code should describe an evidenced cause where one is known. Allow an honest “unresolved pending investigation” state rather than forcing a user to select a false explanation just to submit the record.

Build the adjustment record

A useful proposal contains enough information for an approver who was not standing at the bin. Capture the product identifier, description, location, lot or serial reference where relevant, unit of measure, expected quantity and counted quantity.

Retain the count timestamp and the system quantity used for comparison. Add the discrepancy reference, supporting notes, evidence and links to relevant receipts, picks or transfers. Keep any valuation basis clearly identified; a rough unit-cost estimate is not automatically the amount finance will recognise.

Separate proposed values from applied values. If a recount changes a proposed reduction from six units to two, retain the initial finding and the revised proposal. The approver should know which version they are deciding on.

Limit access to sensitive supporting information. A stock correction may need operational evidence without making detailed commercial cost data visible to every counter.

A practical stock adjustment approval workflow

1. Record the discrepancy without posting a correction

Create the exception while the evidence is available. Identify whether affected stock should be held or whether normal activity can continue under an agreed procedure. The decision depends on product risk and operating conditions; a blanket stock freeze is not always necessary or practical.

For paper counts entered later, preserve the original count time. The data-entry time alone cannot explain movements that happened between the physical count and the proposed adjustment.

2. Recount and investigate the movement trail

Check item identity, pack size, unit of measure and adjacent bins. Review open receipts, unconfirmed transfers, picking activity and returns. Use an independent recount where your policy requires it.

The investigation should resolve the cause where possible. If six units were moved legitimately but the transfer was not recorded, completing the correct movement may be more appropriate than using an unexplained adjustment to make two locations look right.

3. Calculate the proposal against a clear baseline

Document the expected quantity at the count time, the observed count and the proposed change. Then account for legitimate subsequent movements before deciding what the current balance should become.

Do not blindly set today’s balance to yesterday’s count. That can undo a valid receipt or dispatch. Ask your software provider to demonstrate how the system handles movement between counting, approval and application.

Odoo’s inventory adjustment documentation distinguishes counted quantities from applying the adjustment and describes recording the resulting difference in adjustment history. That is a product-specific example of the distinction; it does not establish that a separate approval gate is enabled in every installation.

4. Route the proposed action to the right approver

Show the evidence, revised quantity, reason and estimated impact. The approver can approve, reject or return the proposal for clarification. Record their identity, decision time and the version they reviewed.

Where separation of duties is required by your policy, prevent the person proposing the change from approving it through a second screen. For a small team, agree a workable compensating review with the appropriate business owner instead of designing an approval queue nobody can clear.

5. Apply the authorised correction once

After approval, use the appropriate controlled posting route. Retain the resulting stock movement reference and any linked finance reference. If application fails, show “approved, not applied” rather than pretending the discrepancy is closed.

Retries should not post the same correction twice. A proposal ID and an applied-movement link help the operator distinguish an unposted request from one that succeeded before a screen timed out.

6. Reconcile and investigate recurrence

Confirm the resulting quantity and the related locations or documents. Record any remaining exception and who owns it. Close the correction when its outcome is verified, while keeping a separate follow-up open if the underlying process cause still needs work.

Review repeated adjustments by reason, item and location. A growing count of approved corrections may indicate that the approval process is functioning while the warehouse process continues to fail.

Worked UK example: a moving-stock correction

Hypothetical example, quantities and GBP values for illustration only. At 10:00, a bin shows 80 units in the system and a physical count finds 74. The initial discrepancy is minus six units. A recount confirms 74 and the investigation finds no unrecorded movement before the count.

At 11:00, a legitimate receipt of 20 units is recorded and physically put away in that bin. At 12:00, the adjustment is ready to apply.

Setting the current balance to the old count of 74 would remove 26 units, including the 20 legitimately received. The intended correction is six units, with the intervening receipt retained. Real systems differ in how they stage and apply counts, so prove this exact scenario during configuration and testing.

If the business uses an illustrative internal unit-cost estimate of £12, the six-unit discrepancy has an estimated cost of £72. That is a planning figure, not a statement of the required accounting entry, tax treatment or valuation method. Finance should review the relevant accounting consequences using the business’s actual records and policies.

Spreadsheet approval, inventory platform or connected workflow?

Test configuration options in the current system before purchasing another tool. A form with an approval button adds little if someone can bypass it and change the stock directly without the required review.

Likewise, a custom workflow is not automatically cheaper or stronger. It needs maintenance, usable permissions, recovery controls and a clear owner when the connected inventory platform changes.

Implementation costs and operational limits

A complete quote should cover process mapping, authority rules, reason codes, permissions, integration, migration, test scenarios, training and support. Include how evidence and decision history can be exported if you move systems.

For a hypothetical pilot budget, suppose setup and training cost £900, ongoing support costs £80 per month, and an independent review takes four hours per month at an internal cost of £25 per hour. The first three months cost £900 + £240 + £300 = £1,440, excluding VAT. These invented figures are not OpsMavix prices or market averages.

Compare that cost with measured improvements: fewer repeated corrections, less investigation effort or lower confirmed losses. A smaller adjustment total alone does not prove improved stock accuracy; it could reflect corrections waiting in a queue. Track the age of unresolved discrepancies alongside their value.

Avoid an approval process that blocks urgent operational decisions without an exception route. Define emergency authority, evidence requirements and retrospective review. Keep exceptions visible rather than reclassifying them as routine approvals.

What to test before rollout

Use anonymised real discrepancies and include both positive and negative corrections. Ask the provider to demonstrate:

• A count revised after a recount, with both versions retained.
• A receipt or dispatch between the count and the approval.
• A location error resolved through the proper movement rather than a write-off.
• A rejected proposal that remains available in history.
• An approved correction that fails to post and can be retried once safely.
• A user attempting to approve their own request contrary to the configured policy.
• An export showing the proposal, decision, applied movement and supporting references.

Start with one warehouse area and a manageable set of reason codes. Measure unresolved discrepancy age, repeat causes, time to decision and the proportion of approvals with a verified posting result. Review those measures with the people who actually count and move stock.

Frequently asked questions

Should we approve positive adjustments too?

Yes, include them in the control design. Found stock may be genuine, but it can also be in the wrong location, already recorded elsewhere or counted in the wrong unit. Your approval policy should define the route based on the relevant risks.

Does every difference need a write-off?

No. A discrepancy may be resolved by correcting an underlying receipt, transfer or count. Establish the cause and use the appropriate process rather than treating every difference as a loss.

Can stock keep moving during the review?

It can if your workflow reliably accounts for intervening movements and the relevant risks permit it. Other situations may require a controlled pause. The implementation must make the chosen procedure explicit and testable.

Does approval software determine the accounting treatment?

No. It records the operational decision and can connect to the finance process. The correct treatment depends on the actual circumstances, valuation configuration and applicable accounting policies. Involve finance when defining the workflow.

Keep the explanation attached to the correction

A useful adjustment process can answer what was found, why a correction was authorised, what was posted and whether the outcome was checked. Start by proving those links for one common discrepancy before extending the workflow.

Discuss inventory automation with OpsMavix if counts, approval messages and stock corrections are split across systems. Bring one recent discrepancy and its movement history. Send an enquiry to discuss authority rules, evidence and integration requirements before agreeing the build scope.

Sources and further reading

• Odoo 19 documentation: Inventory adjustments — primary product documentation on counted quantities, application and adjustment history; reviewed 19 October 2026.
• OpsMavix: Blind inventory count — related guidance on collecting count evidence.

The proposed controls and GBP calculations are practical design suggestions and hypothetical examples, not client results or accounting advice. The cover shows a person reviewing records on a tablet; it is not a screenshot of the approval workflow described here.