Reverse logistics starts with different decisions for RTO and customer returns

An undelivered parcel returns to the origin with its outer packaging sealed. Another product comes back after the customer used it and requested a return. The warehouse puts both into the same “returns received” queue and automatically restores stock.

Start the two workflows with their actual reason and authority. Return to origin reverses an unsuccessful delivery journey. A post-delivery return follows a customer request and the applicable return decision. Both need receiving controls, but they do not share every commercial implication.

Define the return family at creation

For RTO, link the original outward shipment, relevant delivery exceptions, return instruction, carrier acknowledgement and return movement. Preserve whether the outward order was cancelled, remains open or needs a separate customer-service decision.

For a customer return, link the original delivered order line, return authorisation, expected item and quantity, reason and approved collection arrangement. Record whether a replacement or credit decision has already been authorised.

Microsoft's sales-return documentation distinguishes physical-return and credit-only processes. It also separates authorising a return from accepting goods or granting credit. Those distinctions are useful when designing the local state model. Microsoft Dynamics 365 — Sales returns

A credit without physical return should not create expected inbound stock. A parcel arriving without authorisation should still be recorded as controlled custody while its identity and treatment are resolved.

Two streams with different unresolved balances

The following illustrative snapshot uses one unit per parcel and mutually exclusive states within each stream.

Within the seventeen received RTO units, fifteen pass the applicable receiving and disposition checks and two remain held. Within the eight customer returns, five are approved for normal stock, two require repair review and one has an identity mismatch.

Physical returned custody is seventeen + eight = twenty-five units. Normal-stock eligibility is fifteen + five = twenty. The remaining five received units are controlled exceptions. Another five units are still inbound and must not be counted as warehouse custody.

The same number five appears in two different groups: five received exceptions and five unreceived movements. Keep them distinct. Adding the initiated thirty to the received twenty-five would double count the return population.

Do not infer condition from the journey label

An RTO parcel may have remained unopened by the intended consignee, but it can still have transit damage, packaging compromise, missing contents or identity problems. A “sealed” observation records only what was checked; it does not establish universal resale suitability.

A customer return may be unused and eligible for stock under the applicable policy, or it may require repair, quarantine, supplier return or another disposition. The reason selected by the customer is not the inspection result.

The authorised product or quality owner sets acceptance criteria. The warehouse records observations and follows the approved handling process. Software should not infer product safety or release permission from a generic returns category.

Microsoft documents disposition codes whose actions affect both physical handling and financial outcomes. Configuration must therefore be reviewed for the intended consequences, not selected merely because the label sounds appropriate. Microsoft Dynamics 365 — Specify how to dispose of returned items

Keep the lifecycle visible

A single “closed” status hides unfinished work. A return can be received but awaiting disposition, or financially resolved while goods remain in transit under an authorised exception policy. Display those states independently.

Preserve identity through repacking and partial receipts

Use the original order and shipment references plus a separate return reference. If the carrier issues a new AWB, map it to the return movement without replacing the outward AWB history.

For a bundle, record expected and observed components separately. A parcel count of one says little about whether all three items arrived. For multi-piece shipments, retain partial return quantities and the missing-piece case.

If several returns are consolidated into one bag or pallet, preserve their individual identities. Repacking creates a new handling-unit relationship; it does not merge customer entitlements or refund decisions.

Duplicate return scans must resolve to the existing receipt. A second physical parcel against the same authorisation requires an exception, not automatic suppression based only on the repeated reference.

Choose a workflow that preserves the separate decisions

A small operation can use one receiving station with clearly separated return families and queues. Native returns software is useful when it maintains authorisation, receipt and disposition relationships. An integration should carry the expected return lines and the observed result without converting every receipt into a refund instruction.

Test an RTO still inbound, an unauthorised arrival, a partial bundle, a wrong serial and a credit-only case. Verify both stock and financial outputs. The correct result for some cases is an owned hold, not a completed return.

Measure time from initiation to receipt, receipt to disposition and authorised refund to settlement separately. The slowest stage may belong to the carrier, warehouse, quality team or finance; a single average obscures that ownership.

Return the record to a usable state before the stock

A reliable reverse-logistics process explains why the goods came back, what arrived and which decision remains. That supports both inventory control and fair handling of the customer or carrier obligation.

Next actions

1. Define separate entry events for RTO and authorised customer returns.
2. Map outward and return identities without overwriting either journey.
3. Reconcile expected, received, eligible and held quantities.
4. Test financial outputs independently from receiving and disposition.