Returns: The Stock You Forgot to Plan

Revenue and inventory do not reverse at the same moment

A customer may request a return before the item arrives, and a received item may still need assessment. A financial forecast can therefore reflect a likely refund while the stock remains unavailable to fulfil another order. Treating every expected return as current supply hides that timing gap.

Core supports the merchandise plan and Atlas the scoped analytical evidence. The actual return, inspection and stock-status controls depend on the connected operating systems. The article does not claim that Core or Atlas automatically accepts every return, grades condition or makes the unit sellable.

Define the forecast and physical states

The worked online cohort has a hundred sales at $80 and twenty expected returns. That implies eighty retained sales and $6,400 retained sales value under the forecast, rather than $8,000 gross cohort value. The twenty remain an expectation, not proof of completed refunds or receipts.

At the review point, twelve returns have physically arrived. Nine are accepted as usable and three await assessment; eight expected returns have not arrived. These states reconcile to the forecast twenty without treating a return request or pending inspection as available inventory.

Read the sizes behind the returned quantity

Expected return sizes are six small, eight medium and six large. Received quantities are four, five and three. Accepted usable quantities are three, four and two; each size has one received unit awaiting assessment. Expected unreceived quantities are two, three and three.

The usable nine do not necessarily have the same mix as the next sales demand. A group total can reduce an aggregate buying need while leaving a specific size short. Inspect the condition and size records before assuming returns substitute for a new order in equal proportions.

Compare the buying question on confirmed usable supply

Assume thirty usable units already held, excluding all returned units, and forty expected next-window sales with a ten-unit closing target. Including only nine accepted returns gives 39 usable supply and an eleven-unit incremental requirement: forty plus ten less 39.

A separate return-yield assumption expects fifteen of the forecast twenty eventually to become usable. Counting that total would imply 45 supply and only five additional units required. The six-unit difference is conditional future supply, not six units available now or a reason to duplicate the nine already accepted.

Phase the expected reverse flow into the plan

The six further forecast usable returns could depend on the three awaiting assessment and eight not yet received. Their timing and suitability remain uncertain. Core’s forward assumptions should identify when that supply is expected and retain a scenario that does not rely on it arriving in time.

Atlas can support the relevant return and merchandise analysis where the configured records allow it. The forecast yield is not an observed inspection pass rate or a guarantee of recoverable stock. Keep financial refunds, physical quantities and accepted condition distinguishable in the review.

A return-yield assumption should be reviewed by relevant category, reason and condition, not treated as a universal recovery rate. A delayed receipt may still become usable later, while a damaged item may require another route. Separate the timing uncertainty from the condition judgement instead of using one percentage to hide both.

Avoid counting the same return at several stages

A unit should not be counted once as a requested return, again as a received item and a third time when accepted. The stages describe a progression of the same goods. Reconcile movement and cutoff definitions before adding the quantities into a stock equation.

Likewise, do not subtract forecast refunds from a net-sales figure that already includes them. The example states a gross cohort and an independent retained-sales forecast; a real report needs an agreed transaction and accounting basis. More fields do not improve the plan if they repeat the same reversal.

Retain the original sale and reverse-flow identifiers where the connected records provide them. They help distinguish repeated status updates from additional units and support a consistent cutoff. Confirm data coverage before presenting a precisely reconciled queue as a complete view of all returns.

Plan the return without pretending it has arrived

For this review, nine returned units are usable and eleven additional units are needed under the current-supply scenario. A five-unit requirement depends on fifteen eventual usable returns, including six not yet confirmed. Both calculations are useful when their timing and certainty remain visible.

Merchmix Core and Atlas connect the reverse flow with the stock and sales plan. Returns deserve their own quantity, size and status assumptions so the next buying decision can reflect them honestly. Expected recovery should improve the forecast without being mistaken for a shelf-ready unit.

Common questions