# Standard Work for Warehouse Returns and Exceptions

Canonical: https://millbase.ca/blog/standard-work-for-warehouse-returns-and-exceptions
Author: [Coby Birenbaum](https://www.linkedin.com/in/cobybirenbaum/)
Published: 2026-10-19
Updated: 2026-10-19
Archive edition: 2026-09-28

Returns and exceptions need a defined route because they do not follow the normal receiving flow.

Returns and exceptions need a defined route because they do not follow the normal receiving flow. Give workers a clear place to put uncertain material and a way to record why it is there. Avoid requiring them to invent an inventory decision on the spot.

## Define the route

- Identify the source job or movement when known.
- Separate usable returns from damaged, mixed, or unidentified material.
- Assign a reviewer and expected response time.
- Record the final quantity, location, and disposition.

## A useful handoff

A hypothetical installer brings back mixed unused hardware. The receiving person records the job and places it in a labeled review area. A knowledgeable reviewer identifies usable parts before they become available stock.

## Review the queue

Monitor unresolved exceptions and their age. If the queue grows, investigate ownership or decision complexity rather than merely expanding the storage area.

## Related reading

- [Tracking Work in Progress Inventory in a Millwork Shop](https://millbase.ca/blog/tracking-work-in-progress-inventory-in-a-millwork-shop)
- [Warehouse Inventory Management for Project-Based Manufacturing](https://millbase.ca/blog/warehouse-inventory-management-for-project-based-manufacturing)

## Definitions and further reference

- [Oracle: inventory management explained](https://www.oracle.com/scm/inventory-management/what-is-inventory-management/)

## How Millbase can help your shop

### Connect material records to the cabinet job

When a component shortage or material change affects a job, start with the recorded stock and the work it supports. [Millbase inventory](https://millbase.ca/#inventory) keeps quantities, material costs, receipts, stock lots, and usage history together. Use [project tracking](https://millbase.ca/#projects) to review the associated labour and material costs, then reconcile the physical material before making a new commitment.

Ask the [Millbase AI agent](https://millbase.ca/#how-it-works) a question grounded in your workspace records. For example: *“What inventory records do we have for this material, and what usage is recorded against this project?”* You can select a project or worker, ask follow-up questions, and request [supported reports and CSV exports](https://millbase.ca/#insights).

Use the answer to locate the relevant records and investigate the exception. A physical count, approved specification, or supplier confirmation still establishes facts that have not been recorded.

## Explore the wider topic

For the broader workflow and decisions behind this guide, read [Warehouse Inventory Management for Project-Based Manufacturing](https://millbase.ca/blog/warehouse-inventory-management-for-project-based-manufacturing).

## Frequently asked questions

### Should every return be inspected?

Use an appropriate check for identity, condition, and intended use. The depth depends on the material and risk.

### Can the review area be informal?

It should be identifiable and controlled enough that material is not accidentally picked or forgotten.