Research library

Sources checked: October 20, 2026

B2B Reverse Logistics: Return Identity, Receipt, and Disposition

Reverse logistics spans several handoffs: a return is authorized, a parcel may travel back, a facility receives and inspects items, inventory is assigned a disposition, and the order or financial record is completed. A return request, a carrier scan, a warehouse receipt, and a refund or exchange are different events. Keep their identifiers and owners connected without treating any one event as proof that the others happened.

For Educational and Informational Purposes Only — Not Legal or Financial Advice.

This guide is general technical research for B2B commerce teams. It does not provide legal, tax, accounting, financial, security, performance, pricing, compliance, or individualized implementation advice. Confirm current product behavior and document the workflow with the responsible system, operations, and finance owners.

What this guide covers

This guide focuses on the post-sale path from an approved return through physical receipt, item-level disposition, and an owned commercial outcome. It is distinct from the outbound freight and LTL guide, which covers carrier movement and delivery handoffs; the 3PL onboarding guide, which covers provider and site readiness plus multi-provider fulfillment exceptions; and the OMS architecture guide, which covers broader order routing and orchestration.

For B2B workflows, the challenge is often preserving the scope and identity of what was authorized across multiple contacts, locations, line items, packages, and facilities. The guide offers a vendor-neutral model for documenting those handoffs. A product's status names and available transitions still depend on that product, its configuration, and the team's operating process.

Separate the records and state owners

Before choosing automation, draw the path for one return from request to closure. Record which system creates or changes each state, which systems consume it, and what evidence is sufficient for the next owner to act. A useful local model may keep records like these distinct:

Record or eventEvidence and relationship to preserve
Return authorizationOriginal order and line references, approved items and quantities, reason or case reference, destination, decision owner, and any applicable operating window.
Return parcelReturn authorization, package ID, label or carrier reference, tracking number, expected contents if known, and return destination. One authorization may involve multiple parcels.
Carrier movementPackage-level source events and timestamps. Keep these separate from a facility's receipt record.
Facility receiptReceiving location, arrival time, package-to-authorization match, items and quantities physically counted, and any discrepancy. A parcel can arrive with only part of the expected contents.
Inspection and dispositionUnit or line inspected, observed condition, quantity, disposition decision, destination location or next action, evidence, and accountable reviewer.
Order or financial outcomeRefund, credit, exchange, replacement, or another documented outcome; its reference, owner, state, and relationship to the return and received quantities.

Use identifiers the connected systems can retain. A local correlation key can help operators find an item across commerce, warehouse, shipping, and finance tools, but it should not overwrite each system's source identifier. Keep the source system beside identifiers that are not globally unique, and preserve links when an order line, package, or return is split, corrected, or reassigned.

Shopify's Admin GraphQL documentation provides one scoped illustration: its Return object exposes return line items, exchange line items, refunds, status, and associated reverse fulfillment orders. Shopify describes a ReverseFulfillmentOrder as a group of one or more return items to be processed at a fulfillment service, and notes that more than one can exist for a return at a location. These are Shopify object definitions; they do not prescribe a universal data model for other platforms. See Shopify's Return and ReverseFulfillmentOrder references.

Keep authorization distinct from return transport

An approval records what the business has accepted for return under its own workflow. A label or tracking number describes a transport path. Neither alone proves that the expected goods arrived, that all authorized quantities were present, or that an item passed inspection.

Make the handoff explicit: approved return lines and quantities create or update the expected return scope; the parcel record points back to that scope; carrier events update transport visibility; and the receiving operation records what physically arrived. Do not automatically mark a return received just because a carrier status appears complete, or close the authorization when only one of several expected packages is delivered.

The provider-specific details can differ. For example, Shippo's current Returns API documentation describes scan-based return labels for USPS, FedEx, and UPS and says its documented return label must use the outbound shipment's carrier. In that workflow, Shippo documents setting extra.is_return and says its API swaps the address direction for those carriers. These statements apply to Shippo's documented workflow and listed carriers; check the selected provider's current instructions for any other configuration. See Shippo's Returns documentation.

Match each physical unit to the approved scope

Design the receiving lookup around an authorization and its lines, not a buyer name or product description alone. Depending on the business and systems involved, useful references can include an RMA or case number, original order and line IDs, buyer or company account, ship-from or receiving location, product identifier, package or tracking ID, and serial, lot, or customer PO references where the operation already uses them.

At receipt, compare expected and observed contents at a useful unit or line level. Keep requested, authorized, shipped back, received, inspected, and dispositioned quantities distinguishable. When a package contains only some expected lines, record the partial quantity and leave the remainder visible. When the parcel cannot be confidently matched, hold it in an exception path for review rather than attaching it to the closest-looking order.

Avoid a data contract that assumes one return equals one package, one order line, or one facility visit. A return can arrive in multiple cartons, multiple lines can share a carton, and a corrected authorization or destination can affect the expected receipt. Preserve the history and link each change to the responsible system and operator so a later reconciliation can explain what was expected at the time.

Receive partial and unexpected returns deliberately

Provide distinct outcomes for expected, partial, excess, unidentified, damaged-package, and otherwise mismatched receipts. Record the affected authorization, package, line, quantity, location, timestamp, evidence source, and next owner. If the workflow permits an operator to correct the expected scope, preserve both the original instruction and the correction reason instead of silently replacing the earlier value.

Make repeated inputs safe to review. A duplicated carrier notification should not create a second package receipt, and a retry after an uncertain downstream response should not apply the same receipt or quantity twice. Where systems provide event or transaction identifiers, retain them with the processing result. If the source cannot distinguish a retry from a new business event, use an owned review step and reconcile before applying another inventory or financial effect.

Useful queue views can show the age of a return, last known state, expected versus observed quantity, facility, unresolved discrepancy, source references, and the person or team responsible for the next action. Set review timing and escalation based on the operation's own needs; do not infer a universal service target from a software feature description.

Give inspection and disposition explicit ownership

Physical receipt should not silently make an item available for sale. Model the local inspection and disposition decision separately from package delivery and receiving. Possible outcomes might include a quality-approved return to stock, quarantine for review, repackaging or repair, vendor return, or another controlled inventory adjustment. The applicable choices, evidence, approvals, and inventory statuses depend on the product and business process.

For each inspected quantity, capture the observed condition, any serial or lot identity already used by the operation, the location or hold status assigned, the disposition decision, who made or approved it, and any supporting note or image reference. Define which system is allowed to release a quantity into an available inventory state and what confirmation is needed from that system. Keep a distinct exception for an item that is received but still awaiting assessment.

Test cases where several items in a return receive different outcomes, where only part of a line is present, or where an item must wait for a second review. A return-level status can hide item-level work, so confirm that support, warehouse, and inventory users can find the remaining open quantities and their owners.

Close order and financial outcomes with the right owner

Record the commercial outcome as a separate handoff linked to the return and the quantities it covers. Refunds, account credits, exchanges, replacement shipments, and order adjustments can involve different records and owners. Specify which system originates the decision, which system records the completed outcome, what identifier confirms it, and how later corrections are reconciled. For B2B accounts, document how the team's own ERP, finance, or customer-account process represents that outcome; this guide does not prescribe accounting or tax treatment.

Shopify's merchant help documentation is one product-specific example of separate return-processing choices: it describes selecting return items to receive, optionally selecting a restock location, selecting exchange items to release, and choosing whether to issue a refund now or later. This describes the Shopify Admin workflow documented on that page, not a required sequence or capability set for another commerce system. See Shopify's processing and managing returns guide.

Before closing an operational case, compare authorized quantities with received and dispositioned quantities, and check that the linked exchange, credit, refund, or other result has a traceable reference. Keep a partial outcome open when there is still an expected parcel, inspection, replacement, or finance action. If a supported correction is needed, capture the reason, scope, authorized owner, and downstream records that must be reconciled.

Reconcile and recover by return, line, and package

Use bounded comparisons rather than relying on a single aggregate count. A practical review can compare:

  • Authorized lines and quantities with packages expected and tracking references issued.
  • Carrier events with facility receipt records, including partial or unmatched arrivals.
  • Received quantities with inspected quantities and the resulting inventory dispositions.
  • Completed refund, credit, or exchange references with the authorized and processed return scope.
  • Open exceptions with their last known state, owner, next action, and age.

Investigate a mismatch at the record and quantity level. Identify the source of each value, the relevant timestamps, and any manual correction before deciding which system should change. Bound a replay or correction to the affected records, use the target system's documented controls, and verify that the next ordinary update does not reintroduce the discrepancy. Avoid treating a successful message delivery as proof that the receiving application or physical operation completed its work.

Evaluate and test a narrow workflow first

Ask each system owner to walk through one representative return using the identifiers and screens operators will actually see. Before broadening the workflow, test ordinary, partial, and exception paths in a suitable non-production or otherwise controlled environment:

  • One approved line returned in one package, received, inspected, dispositioned, and linked to its documented commercial outcome.
  • One authorization arriving in multiple packages, including a delayed or missing parcel.
  • A partial quantity, an unexpected item, or an unreadable or missing return reference.
  • A received item held for inspection, followed by separate disposition outcomes for different units.
  • A repeated event or uncertain response that must be reconciled before another side effect is applied.
  • A changed return destination, canceled or corrected authorization, or return arriving at an unexpected location.
  • An exchange or replacement with its own order, inventory, fulfillment, and customer-support handoff.

For each case, record expected state transitions, evidence, source and destination identifiers, accountable owner, exception route, and recovery action. Expand only when the people operating the return can explain how to recognize a mismatch and how an authorized correction will be recorded in each affected system.

First-party source register

The first-party documentation pages below were opened and checked on October 20, 2026. Shopify and Shippo examples in this guide are limited to the linked documentation and named product workflows. The operating model and recommendations are vendor-neutral design considerations, not claims that every platform supports the same object, status, carrier, or transition.

Editorial and education-only note

This guide is general educational technical research for B2B commerce teams. It does not provide legal, tax, accounting, financial, security, performance, pricing, compliance, or individualized implementation advice. Product behavior, return policies, carrier support, state transitions, and recovery options vary by configuration and operating context. Confirm current first-party documentation and validate workflow decisions with the responsible system, operations, and finance owners before acting.

Continue reading