How Do You Put Returned Products Back into Stock? A Guide to the Quarantine Area, Four Condition Classes, Recoverable Sales Value, Inventory Entries, Intake Time and Return Reason Feedback
How do you put returned products back into stock? Quarantine, four condition classes, inventory entries, intake time and recovery rate: an 8-lesson guide with examples.
Contents 14 sections
- What will you be able to do by the end of this training?
- Lesson 1: Why doesn't a returned product go straight into sellable inventory?
- Lesson 2: How do you set up four condition classes and a checklist?
- Lesson 3: How are 500 returned products distributed across the classes?
- Lesson 4: How do you calculate recoverable sales value?
- Lesson 5: How do you record inventory by class?
- Lesson 6: Why does the time it takes a return to re-enter inventory matter?
- Lesson 7: How do you feed back return reasons?
- Lesson 8: How do you monitor returns going back into inventory?
- What are the most common mistakes when putting returned products back into inventory?
- How does NetKasam make it easier to put returned products back into inventory?
- Mini quiz: Test what you have learned
- Conclusion: Send every return through a gate before it enters inventory
- Frequently Asked Questions About Putting Returned Products Back into Inventory
A package returned by a customer is not sellable inventory the moment it enters the warehouse. Inside you might find a brand-new product, an opened and used one, one with a crushed box but an intact product, or a damaged one. Taking all of them into inventory through the same door under a single code makes the number in the system look correct; then an unsellable product goes back on sale, a second return follows, or a discrepancy turns up in the shelf count. Putting returned products back into inventory correctly is a small but valuable process that breaks this chain at the start.
This article is not a narrative but an 8-lesson practical training. We will answer the question how do you put returned products back into inventory using an example business that receives 500 returned products a month: why a return shouldn't go straight into sellable inventory, the four condition classes, how the 500 returns are distributed across the classes, recoverable sales value, the right recording setup, how re-entry time affects sales, feeding return reasons back to suppliers and production, and monitoring indicators. At the end there is a mini quiz with an answer key. All figures are example values chosen to illustrate the method; follow the same steps with your own data.
What will you be able to do by the end of this training?
In short: You will inspect returned products in quarantine, sort them into four classes, record inventory correctly for each class, calculate the recovered value and feed return reasons back to their source.
- 01ReceivePlace the return in the quarantine area; don't put it into sales inventory.
- 02InspectExamine the product, packaging and any missing parts with a checklist.
- 03ClassifyCode it as sellable, refurbishable, discounted or scrap.
- 04RecordMake an inventory entry or exit according to the class.
- 05ValueCalculate the recovered sales value.
- 06Feed backPass return reasons on to the supplier and the product card.
The training's 8 lessons: (1) why a return doesn't go straight into sales inventory, (2) four condition classes and a checklist, (3) how 500 returns are distributed across the classes, (4) recoverable sales value, (5) recording inventory by class, (6) why re-entry time matters, (7) how to feed back return reasons, (8) monitoring indicators.
Lesson 1: Why doesn't a returned product go straight into sellable inventory?
In short: A return counts as goods of uncertain status until the product's condition is verified. A return that goes straight into sales inventory makes the inventory figure in the system higher than what can actually be sold.
A customer who cancels an order or sends a product back doesn't always return it in the condition it was packed. The box may have been opened, an accessory may be missing, the product may have been used or damaged in transit. The system, however, can't know this when the return is recorded; it adds the product to inventory as +1 unit. That +1 unit lets the sales screen accept orders. When it turns out a few days later that the product is damaged, you are left with an order promised to a customer and inventory that doesn't exist.
That's why a separate status is defined for returns: awaiting inspection. A product in this status is physically in the warehouse but is not counted in sellable inventory. After inspection its class is determined, and only then does it enter sales inventory or leave inventory. The same distinction also makes it easier to trace the source when a count discrepancy appears; we cover this separately in the article how to find and close inventory discrepancies. You can calculate the cost of the whole return process with the article how to calculate return cost.
Lesson 2: How do you set up four condition classes and a checklist?
In short: Classify returns as A (sellable), B (refurbishable), C (sellable at a discount) and D (scrap or return to supplier). The class is determined by a checklist written in advance.
| Class | Situation | What to do? |
|---|---|---|
| A – Sellable | Product intact, packaging complete, accessories all present | Enters sales inventory the same day |
| B – Refurbishable | Product intact, packaging damaged or cleaning needed | Repackaged, then enters sales inventory |
| C – Sellable at a discount | Product works but has a cosmetic defect or has been opened | Sold under a separate code at a discounted price |
| D – Scrap | Product damaged, unusable or incomplete | Inventory exit recorded; returned to the supplier if they accept it |
A checklist makes the class independent of who does the inspection. Three questions are enough: does the product work or is it usable, are the packaging and accessories complete, and is there a cosmetic defect? If the answer to the first question is "no", it's D; if the second is "no" and the product can be cleaned, it's B; if the third is "yes", it's C; if all three are positive, it's A. The person doing the inspection records the class along with a photo; if a dispute later arises with the customer or the carrier, this record serves as evidence. Tying the inspection to a written process also stops employees from leaving the class decision to individual interpretation; to separate permissions, see the article how to set up user permissions.
Lesson 3: How are 500 returned products distributed across the classes?
In short: The example business receives 500 returned products a month. After inspection, 300 fall into class A, 100 into B, 60 into C and 40 into D.
The example product's purchase cost is ₺300 and its normal selling price (excluding VAT) is ₺500. The returned products are distributed across the classes as follows:
| Class | Count | Share | Cost value | Normal sales value |
|---|---|---|---|---|
| A – Sellable | 300 | %60,0 | 90.000 ₺ | 150.000 ₺ |
| B – Refurbishable | 100 | %20,0 | 30.000 ₺ | 50.000 ₺ |
| C – Discounted | 60 | %12,0 | 18.000 ₺ | 30.000 ₺ |
| D – Scrap | 40 | %8,0 | 12.000 ₺ | 20.000 ₺ |
| Total | 500 | %100 | 150.000 ₺ | 250.000 ₺ |
- A – Sellable₺30060%
- B – Refurbishable₺10020%
- C – Discounted₺6012%
- D – Scrap₺408%
Prepared with example values. The classes add up to 500 units.
What matters in this table is that the classes always add up to the number of returns received and that no product is left in the "awaiting inspection" status. 80% of the 500 returns (A and B, 400 units) can be sold again; in other words, four out of every five returns can go back into sales inventory. The remaining 20% is either sold at a loss in price or lost entirely. Reducing the number of returns itself is a separate job; for that, follow the steps in the article how to lower the return rate.
Lesson 4: How do you calculate recoverable sales value?
In short: Recoverable value is found by deducting the scrap loss, the discount difference and the refurbishment labor from the normal sales value of the returned products.
- Normal sales value: 500 units × ₺500 = ₺250,000.
- Scrap loss (D): 40 units × ₺500 = ₺20,000. The product can't be sold.
- Discount difference (C): These products are sold at a 30% discount, that is, for ₺350. The difference per unit is ₺150, for a total of 60 × 150 = ₺9,000.
- Refurbishment labor (B): Repackaging and cleaning at ₺15 per unit for 100 products, ₺1,500 in total.
- Normal sales value of returned products₺250,000
- Class D scrap loss−₺20,000
- Class C discount difference (30%)−₺9,000
- Class B refurbishment labor−₺1,500
- Recoverable sales value₺219,500
Prepared with example values. Total: 250,000 − 20,000 − 9,000 − 1,500 = ₺219,500.
The recovery rate is 219,500 ÷ 250,000 = 87.8%. About 12% of the returns is lost. To compare this rate with an uncontrolled-entry scenario, consider this: if 40 scrap products are mistaken for sellable inventory, 40 orders are accepted; these orders can't be fulfilled and are either canceled or the customer receives a damaged product. Either way, you lose the sale and customer trust takes a hit. For the cost of canceled orders, see the article how to cancel an order.
Lesson 5: How do you record inventory by class?
In short: Class A goes straight into sales inventory and class B goes into sales inventory after refurbishment; class C goes into discounted inventory under a separate product code; for class D, an inventory exit and an expense entry are recorded.
- Return invoice or expense voucher (gider pusulası). The document that reverses the sale to the customer is issued first. We explain how to issue it in the article how to issue a return invoice.
- Class A: The product enters sales inventory as +1 under its original code and shelf location. This is done the same day.
- Class B: Once refurbishment is complete, it enters the same way as A. While refurbishment is in progress, the product stays in the "awaiting inspection" area.
- Class C: A separate product code or variant (e.g. "B grade") is created so it doesn't get mixed up with the original product; it is listed at a discounted price and the defect is clearly stated on the product page.
- Class D: The product is removed from inventory; this exit, worth ₺12,000, is recorded not as an inventory discrepancy but as a clearly marked "return-related loss".
Here is why recording class D as a loss matters: in the monthly inventory count, scrapped products don't appear as "missing"; they become an exit with a known reason, and inventory discrepancies are tracked separately. Creating a separate code for class C follows the same logic: sales data for discounted and regular products don't get mixed up, and the profit calculation on the product card isn't distorted. To keep this distinction on marketplaces for products with variants, see the article how to manage products with variants on marketplaces.
Lesson 6: Why does the time it takes a return to re-enter inventory matter?
In short: A sound product can't be sold while it waits in the inspection queue. The longer re-entry takes, the more sales are lost, especially on products with dwindling stock.
In the example business, suppose 300 class A products wait an average of 10 days for inspection. During the same period, suppose sales inventory for some of these products runs out, and as a result 40 units of sales are lost. The unit contribution of a sale is calculated as follows: normal selling price ₺500, cost ₺300, selling expenses (commission, shipping, packaging) 15% of the selling price, that is, ₺75; contribution 500 − 300 − 75 = ₺125. The contribution lost on the 40 missed units is 40 × 125 = ₺5,000.
| Re-entry time | Lost sales (example) | Contribution lost |
|---|---|---|
| 2 business days | 8 units | 1.000 ₺ |
| 5 days | 20 units | 2.500 ₺ |
| 10 days | 40 units | 5.000 ₺ |
- 2 business days₺1,000
- 5 days₺2,500
- 10 days₺5,000
Prepared with example values. Each loss: missed units × ₺125 unit contribution.
This figure covers just one month's batch of returns; it repeats every month and becomes a significant item once annualized. Setting a target of two business days and clearing the inspection queue daily cuts this loss to about one fifth. Prioritizing returns of products with dwindling stock is an additional gain; to set the critical stock level, see the article how to calculate safety stock. To calculate the total cost of stockouts, you can use the article how to calculate stockout cost.
Lesson 7: How do you feed back return reasons?
In short: Enter a single reason code for each return. Each month, report the breakdown by code back to the supplier, the person who writes the product cards and the packing team.
When you have the returned product in hand, the reason is known: the customer stated why they returned it in the system, or you figure it out during inspection. From these, a practical code list emerges:
- Product defect: A manufacturing or material flaw. Reported to the supplier, and a return is requested.
- Wrong product sent: A picking error in the warehouse. Reported to the picking and packing process (how to pick and pack orders).
- Product description didn't meet expectations: A product card error. To fix the card, see the article how to prepare a product card.
- Damaged in shipping: A transport error. We explain how to resolve damage claims with the carrier in the article how to track lost and damaged shipments.
- Customer changed their mind: A return unrelated to the product; it usually ends up in class A.
| Return reason | Count | Share |
|---|---|---|
| Product defect | 75 | %15,0 |
| Wrong product sent | 50 | %10,0 |
| Product description didn't meet expectations | 125 | %25,0 |
| Damaged in shipping | 50 | %10,0 |
| Customer changed their mind | 200 | %40,0 |
| Total | 500 | %100 |
Two conclusions follow from the table. First, 40% of returns are "changed my mind" returns unrelated to the product; most of these fall into class A, and fast inventory re-entry preserves the value of this group. Second, the 25% product description group consists of returns that can be avoided entirely by fixing the product card; cutting just half of this reason prevents about 62 returns a month. The portion of the 75 product-defect returns that ends up in class D is data to discuss with the supplier; how a data-backed conversation is supported is explained in the article how to measure supplier performance.
Recommended readingHow Do You Lower the Return Rate?Lesson 8: How do you monitor returns going back into inventory?
In short: Track four indicators in a monthly table: resellable rate, scrap rate, average re-entry time and recovery rate.
| Indicator | How it is calculated | Sample value |
|---|---|---|
| Resellable rate | (A + B) ÷ Total returns | %80,0 |
| Scrap rate | D ÷ Total returns | %8,0 |
| Recovery rate | Recovered sales value ÷ Normal sales value | %87,8 |
| Average re-entry time | Days between receiving the return and the inventory entry | Target: 2 business days |
| Returns awaiting inspection | Units received but not yet classified | Target: 0 |
- 80%share of resellable returns (A + B)
- 87.8%recovery rate on return value
- ₺219,500sales value recovered from ₺250,000 in returns
- ₺5,000contribution lost to a 10-day re-entry delay
The reason behind the indicators matters as much as their direction. If the scrap rate rises two months in a row, the problem is usually concentrated in one supplier batch or one carrier; looking at the reason table quickly reveals the source. If the "returns awaiting inspection" indicator is above zero, there is a backlog in the queue and the loss described in lesson 6 has started to accrue. To bring the report to your weekly management meeting, you can add a returns row to the layout in the article how to prepare a weekly management report.
What are the most common mistakes when putting returned products back into inventory?
- Putting returns straight into sales inventory without inspection. A damaged product counts as sellable, and a second return follows.
- Using a single "return" status. Sellable and scrap items stay under the same code, and no one knows which products can actually be sold.
- Selling a discounted product under the original code. Sales data and profit calculations get distorted, and customer expectations rise.
- Silently deleting scrap. An inventory discrepancy appears, the cause can't be found and no feedback can go to the supplier.
- Not entering a reason code. The same problem repeats every month, and no one knows which reason dominates.
- Leaving the inspection queue for weeks. Sound products can't be sold, stock runs out and sales are lost.
- Recording the invoice and the inventory entry at different times. The customer return invoice and the warehouse entry don't match.
How does NetKasam make it easier to put returned products back into inventory?
- Cancellation and return management. You manage cancellation and return processes from one place (online sales).
- Return invoice and expense voucher. For cancellations and returns, you create a return invoice or expense voucher with one click.
- Inventory movements. You track a returned product's way back into inventory and its movement history (inventory management).
- Critical stock. By setting a critical stock quantity for your products, you see the stockout risk for products with returns pending.
- Branch- and warehouse-based inventory. You define the returns area as a separate warehouse and track inventory by location (branch and warehouse management).
- Saved reports. You save the monthly report and export it to Excel (reports).
- Bookkeeping is free. e-Invoice, customer and supplier accounts, inventory, cash, bank and expense management are free in every plan; see the pricing page for details.
Mini quiz: Test what you have learned
In short: Answer the 5 questions below, then compare with the answer key. 4 or 5 correct shows you have completed the training.
- If 300 of 500 returns are class A and 100 are class B, what is the resellable rate as a percentage?
- If the normal selling price of 40 scrap products is ₺500, how many ₺ is the loss in sales value?
- If 60 products are sold at a 30% discount for ₺350 (normally ₺500), how many ₺ is the total discount difference?
- If the normal sales value is ₺250,000, the scrap loss ₺20,000, the discount difference ₺9,000 and the refurbishment labor ₺1,500, what is the recoverable value?
- If the selling price is ₺500, the cost ₺300 and selling expenses 15%, how many ₺ is the unit contribution?
Answer key:
- (300 + 100) ÷ 500 = %80.
- 40 × 500 = 20.000 ₺.
- 60 × (500 − 350) = 60 × 150 = 9.000 ₺.
- 250.000 − 20.000 − 9.000 − 1.500 = 219.500 ₺.
- 500 − 300 − (500 × %15 = 75) = 125 ₺.
Frequently Asked Questions About Putting Returned Products Back into Inventory
Should a returned product go straight back into sellable inventory?
No. The product is first placed in an area awaiting inspection, its condition is verified, and it enters sellable inventory only if it is found to be sellable.
How many classes are returned products divided into?
In practice, four classes are enough: sellable (A), refurbishable (B), sellable at a discount (C) and scrap or return to supplier (D).
Does a returned product sold at a discount need a separate code?
Yes. A separate product code or variant is created so it doesn't get mixed up with the original product and sales data isn't distorted, and the defect is clearly stated on the product page.
How is a product sent to scrap shown in the inventory records?
An inventory exit is recorded and "return-related loss" is entered in the reason field. A product that is silently deleted turns into an inventory discrepancy whose cause can't be found.
How long should it take for a returned product to re-enter inventory?
The target is two business days. The longer it takes, the longer a sound product can't be sold, and sales are lost, especially on products with dwindling stock.
How is the recovery rate calculated?
Recoverable sales value is divided by the normal sales value of the returned products. In the example, 219,500 ÷ 250,000 = 87.8%.
Why should return reasons be recorded?
Reasons link a return back to its source: a product defect is reported to the supplier, a wrong item to the picking process, and a description problem to the product card. Without a record, the same return repeats every month.
How often should returned inventory tracking be reported?
A monthly report is enough; however, the number of returns awaiting inspection should be monitored weekly or daily, because a backlog quickly turns into a loss.
Conclusion: Send every return through a gate before it enters inventory
The most useful thing you can do today is create a separate area called "awaiting inspection" for returned products and define the four class codes. The next step is to write the first monthly breakdown in a table and find the recovery rate, then feed the most common return reason back to the party responsible. Keeping the number of returns awaiting inspection at zero keeps both your inventory figure accurate and your sales flowing.
Bookkeeping Is Now Completely Free
Manage your bookkeeping and e-Invoice operations with NetKasam without paying a thing. Customer and supplier accounts, inventory, collections and more in one panel, completely free.