What information should be captured when a receiving exception is created?

• A. SKU and PO number only.
• B. SKU, PO number, received quantity, inspected condition, disposition, and person who reported.
• C. Carrier and date received.
• D. Supplier name and delivery location.

Answer: (B)

When a receiving exception is created, you need enough information to pin down what happened, who is responsible for following up, and what should be done next. The SKU and PO number tie the exception to the exact item and purchase order in the system, ensuring you’re addressing the right lot and aligning with both inventory and supplier records. Recording the received quantity shows what actually arrived versus what was expected, which is essential for inventory accuracy and for determining shortages or overages. The inspected condition captures the state of the item or package at inspection, providing evidence if there’s damage, defects, or missing pieces. The disposition defines the next action to take—whether to hold for further inspection, return to supplier, scrap, or rework—so the workflow moves forward correctly. Finally, noting who reported the exception creates accountability and a traceable contact for follow-up if more information is needed.

Options that omit one or more of these fields don’t give a complete picture for resolving the discrepancy and updating systems and records, and focusing on carrier/date or supplier/location alone misses the core details required to process the exception properly.