Holding 60 units for inspection does not mean losing 60 units. Some may return to saleable stock, some may go back to the supplier, and only part may be approved for scrap. Recording the entire quantity as a loss at the first quality concern changes inventory before the decision is complete and leaves finance explaining a difference that the warehouse still physically holds.

At ToDoOps, we design the path from discovery to closure: where the goods wait, who decides their outcome, and which reference explains the quantity and financial effect. The objective is a warehouse manager and an accountant who can read the same case and reach the same explanation.

Decide the Outcome Before Selecting Scrap

Start with the condition of the product. Is it awaiting inspection? Can the supplier accept a return? Is repair practical? Has an authorised person decided it should leave usable stock permanently? Those answers lead to different workflows and different evidence.

An internal quarantine keeps goods under your control while their use is restricted through the agreed location design and operating procedures. Approved scrap removes the quantity from operational stock. An unexplained count shortage is another case again. Using scrap for every discrepancy produces a loss report that cannot distinguish damaged goods from missing goods.

What an Odoo Scrap Movement Represents

Odoo 19.0 documentation describes validated scrap moving quantities to a virtual Inventory Loss location, removing them from usable stock. Scrap can be recorded from stock or a related operation, with product, quantity, location and relevant tracking information 1.

During implementation, agree on the reason and reference staff will use later: a receipt, inspection result or internal case. Test the intended roles and authorisation procedure in the project environment. Permission to process a movement does not by itself settle who should make the business decision. Any additional approval requirement is assessed as an internal procedure or customization; an extra native approval workflow is not assumed.

A Hypothetical Case: 500 Units, but Only 20 Lost

Assume 500 company-owned units at a simplified constant unit cost of SAR 24. Staff place 60 units in an internal inspection hold. Assume the hold location has been configured and tested to exclude its quantity from reservation and delivery. With no other reservations or parallel movements in this example, available stock becomes 440, while total owned stock remains 500.

Inspection accepts 40 units back into available stock and approves 20 for scrap. The figures below illustrate a reconciliation; they are not a customer result or an implementation service price.

Review point Available (units) On hold (units) Approved scrap (units) Remaining inventory (units)
Before the hold 500 0 0 500
After holding 60 440 60 0 500
After releasing 40 and scrapping 20 480 0 20 480

Before the decision, the assumed stock value is 500 × 24 = SAR 12,000. The loss is 20 × 24 = SAR 480, leaving 480 × 24 = SAR 11,520 at that constant cost. Quarantine alone did not reduce the total quantity, and the approved loss was not the cost of all 60 inspected units. The reconciliation also separates the value lost from a future cash payment to buy replacements.

Use the calculators to prepare an initial implementation budget and operational scope for a warehouse project. The inventory loss itself is assessed from quantity, costing and finance settings, separately from the project estimate.

Finance Needs More Than a Lower Quantity

The IFRS Foundation’s IAS 2 overview describes inventory measurement at the lower of cost and net realisable value, and inventory losses recognised as an expense in the period they occur 2. Your finance team determines the applicable accounting framework and treatment of the actual case.

For Odoo acceptance, review the product category, valuation method and loss account with the accountant. Compare the scrap movement to the financial outputs expected from that configuration. A lower warehouse balance alone is insufficient. Finance should be able to follow the reason and value through the relevant reports and identify any additional treatment or approval needed.

Do not copy an account number from someone else’s demonstration database. Agree on the expected result first, then test it against the chart of accounts and valuation setup used in your own project. This makes a financial discrepancy a specific acceptance finding rather than a vague concern after launch.

Keep a Case That Explains the Decision

Use a common reference from discovery through inspection, approval and processing. Depending on the product, evidence might include the damage description, an internally approved photograph, quantity, lot or serial number, and inspection outcome. Assign responsibility for recording the concern, inspecting the goods, approving their destination and reconciling the financial effect.

A month later, the manager should be able to ask why that quantity was lost. A broad reason such as “damaged” may not distinguish a handling problem from a receiving or storage problem. Start with a short reason list that staff understand, then review whether it supports an operational decision. Collecting more fields is useful only when someone can use the information.

Acceptance Tests for Warehouse and Finance

  1. Hold stock internally. Confirm the total quantity remains intact and availability reflects the intended restriction, including an attempted reservation or delivery from the hold location.
  2. Release part of the hold. Reconcile the quantity still awaiting a decision, and confirm that a draft scrap record does not reduce stock before validation.
  3. Approve and process scrap. Link the movement to the correct case reference.
  4. Test a tracked product. Confirm the lot or serial number actually removed.
  5. Explain the value. Finance reconciles the before-and-after result with the configured valuation method and records whether the expected accounting entry is generated under that setup.
  6. Test replacement requirements. If replenishment is required, demonstrate the applicable product rules and the resulting planning action.

Questions Before Going Live

Should a Quality Concern Immediately Become Scrap?

When the outcome is undecided, start with quarantine and inspection. Scrap becomes appropriate when removal is approved, after considering a supplier return or repair where relevant.

Should Every Count Difference Be Scrapped?

Keep an unexplained shortage distinct from documented damage. The investigation and adjustment path should allow management to understand the kind of difference involved.

Does Scrap Automatically Create a Purchase Order?

Replenishment depends on the product’s applicable rules and configuration. Test the planning requirement and how it progresses to purchasing or manufacturing when appropriate. A replenishment option alone does not establish a supplier commitment.

Connect Loss Control to the Implementation Scope

We review this workflow with the relevant Odoo apps and your industry’s operating requirements. The limited sales and stock demo introduces an order journey. Quarantine, scrap and valuation need their own project acceptance scenario.

Scrap Workflow Reference

Odoo 19.0 official documentation: scrap inventory, valuation and Inventory Loss locations.

Inventory Measurement Reference

IFRS Foundation, IAS 2 Inventories.

Discuss a Traceable Scrap Workflow

Discuss implementation with us and bring a representative case, its current approval process and valuation approach. Prepare the scope through the calculators and explore our services at ToDoOps.