Inspect returns: Separate receipt, condition and restocking approval

A received return is not automatically an item ready to sell again. When planning the process, keep at least four pieces of information separate: which individual item came back, what was observed, what decision was made and whether it is actually available again. This turns “three items are back” into information the store and warehouse can use.

Identify the individual item

Start with a clear match. Which order and line item belong to the return? Do the product, size, colour and artwork version match the expected variant? A product code alone is insufficient when items in different conditions come back under the same variant.

Use an internal case or item reference for inspection. It supplements the product identifier rather than replacing it. Three returned shirts of the same variant may require three different decisions. A single row saying “3 shirts received” does not preserve that distinction.

Document observations before decisions

First record what is actually visible or has been checked. “Stain on the front” is an observation. “Do not restock” is a decision. “The customer caused the stain” would be an additional claim about its cause, which that observation alone does not establish.

Inspection points depend on the product and agreed service scope. For a textile item, identity, completeness, visible soiling, damage and the condition of the decoration might be relevant. Agree in advance which criteria will be checked, how an uncertain finding will be documented and who may make the subsequent decision. A visual inspection does not automatically confirm every product property.

The Shirtee.Cloud Warehousing and Fulfillment page also describes receiving, inspecting and storing returns in general. This does not establish a universal inspection standard for every item. The specific criteria and process for your assortment need to fit the agreed service.

Three returns, three separate outcomes

The following example is an original planning proposal. It does not describe mandatory warehouse status names or automated behaviour.

Three items have arrived in this example and one is approved for restocking. Until the inventory entry is confirmed, that does not establish an increase in available inventory. Once the entry for R-01 is confirmed, availability increases by one item. The two unresolved cases remain separate.

“On hold” is a planning term here. Before using the process, establish how your warehouse represents that condition. A colour in a spreadsheet alone does not prevent an item from being treated as available by mistake.

Track the customer resolution and item condition separately

The customer resolution and the decision about the goods each need a traceable status. A customer enquiry that has already been handled does not prove that an item can be sold again. Equally, an item in satisfactory condition says nothing about whether the customer case is closed.

This article addresses inspection of goods, not legal return rules or refund deadlines. Record which team handles each decision and what information it needs. Use internal references; do not copy unnecessary customer details into a general inspection checklist or product photograph.

Uncertain cases need a next step

For each unresolved finding, assign a responsible role, the information needed and a follow-up date. For R-03, the next task might be: “Compare the item label with the order line and confirm the differing size.” That is more specific than “check return” and avoids repeatedly rereading the same unresolved case without progress.

Close discrepancies in a way that remains understandable later. Record the decision and when the related inventory adjustment is confirmed. Cleaning, relabelling, disposal and reshipping are separate actions. None should follow automatically from an unclear finding.

Agree the process before the first return arrives

Discuss identification, inspection criteria, evidence, approval roles and inventory reporting with the fulfillment partner, using a real product example. Also establish what happens with missing components, incorrect variants and returns that cannot be confidently identified. Prices and processing times belong in the specific agreement.

The guide to support exceptions and metrics helps with broader exception handling. For the goods themselves, keep reconciling four stages: received, inspected, decided and recorded in inventory. When these stages fit together clearly, your store can reliably understand the status of the returned item.

AI-generated illustration of a fictional returns inspection; not a Shirtee.Cloud site or a specification of required status colours or processes.