---
title: "Receive and Inspect Returned Goods"
description: "Record all returned goods physically received, including goods that may fail quality inspection. A rejected item must not disappear from inventory simply becaus"
space: "Vuna Transport"
url: "https://docs.navari.co.ke/vuna-transport/returns/inspection"
updated: "2026-11-09"
---

Record all returned goods physically received, including goods that may fail quality inspection. A rejected item must not disappear from inventory simply because it cannot be sold.

## Receive before classifying quality

For a customer Delivery Note return, submit the Return Request, then use **Create → Sales Return**. Review the draft return Delivery Note: original source, actual return quantity, UOM, warehouse and batch/serial allocation. Receive all applicable rows into one holding/quarantine warehouse before submitting it. The physical receipt is this ERPNext stock document; do not add a separate custody-only receipt step.

For a depot return, post the receiving **End Transit / Material Transfer** into the approved Return Warehouse. Use the receiving Stock Entry, not the pickup/loading entry, as the inspection source. Authorised receiving staff review quantities and stock identity before submission.

Do not count a submitted pickup proof as a submitted return receipt. Check the receiving document itself.

## Create and complete the inspection

1. From the submitted linked Sales Return use **Create → Return Inspection**. For supported depot-return stock, use the corresponding Return Inspection action on the receiving Stock Entry or request.
2. Check the returned item and source row. Inspection quantities are in **Stock UOM**.
3. Split rows as needed for different quality results or rejection reasons. Keep the source item/batch identity and do not assign one serial number to two groups.
4. Select Accepted or Rejected, enter a reason for each rejected group and select a **Target Warehouse on every result row** before submission. Form-level accepted/rejected warehouses are defaults, not mandatory substitutes when every row already has a valid target.
5. Complete and link the required standard Quality Inspections. If **Require Quality Inspection for Returns** is enabled, each result group needs its own submitted Quality Inspection with matching source/item and outcome.
6. Ensure the result groups account for the complete received quantity, then submit Return Inspection.

The current worksheet requires the source quantities to balance. Do not treat an incomplete set of results as an approved partial inspection release. Stock movement is a separate reviewed step after inspection.

For customer returns, the mandatory-QI setting is checked during draft validation too. The automatic Create Return Inspection action starts with empty QI links, so it can stop with a missing-QI message when that setting is enabled. Ask the administrator and quality lead to review this path before adopting it for live work; do not bypass a required quality control just to create the worksheet.

## Example: packaging received, pieces inspected

Two Cartons were returned; the original conversion is ten Pcs per Carton. The Sales Return receives two Cartons, equivalent to twenty Pcs. Inspection records:

| Stock quantity | Result | Reason | Destination |
| --- | --- | --- | --- |
| 10 Pcs | Accepted | — | Approved saleable warehouse |
| 2 Pcs | Rejected | Physical Damage | Rejected holding warehouse |
| 4 Pcs | Rejected | Coagulation | Rejected holding warehouse |
| 3 Pcs | Rejected | Reason A | Rejected holding warehouse |
| 1 Pc | Rejected | Reason B | Rejected holding warehouse |

All twenty pieces remain accounted for. Keep the detailed reasons on the inspection even if stock treatment combines compatible result groups.

## Move stock after the decision

Use **Create → Stock Entry (Material Transfer)** from the submitted inspection. Review source/destination warehouses, quantities and standard batch/serial controls, then submit it. A draft Stock Entry has not moved anything. A rejected destination must satisfy the applicable warehouse validation; customer-return rejection targets must be marked Rejected Warehouse.

Holding rejected goods is not automatically a write-off. Authorised stock/accounting staff decide any later scrap, consumption, reprocessing or write-off through the applicable ERPNext transaction. Sites with automatic rejected-warehouse write-off behaviour must use a holding warehouse until that consequence is intended.

## Check batch and serial identity before posting

Use the receipt's Serial and Batch Bundle information where available, retaining legacy Batch No or Serial No information when it is used. Never select arbitrary stock identities to make totals balance. Generated draft transfers still require review of their stock identity; source tracking does not promise that every new bundle is already allocated.

Where one customer return source row contains several batches, ask quality/stock staff to verify the supported split before posting. Do not infer the rejected batch distribution from the item's total alone.

> [Screenshot: Return Inspection split result rows, Stock UOM quantities, rejection reasons, per-row Target Warehouse and linked Quality Inspections]

Next, resolve any [customer commercial follow-up](/vuna-transport/returns/commercial-resolution).