OMS Returns-to-Vendor (RTV) Workflows

A customer return often is not the end of the story — defective, recalled, or overstocked merchandise frequently needs to travel one step further, back to the original vendor, in a process distinct enough from customer returns that it deserves its own order type inside the OMS: returns-to-vendor.

A customer return order is about restoring the buyer's satisfaction; an RTV order is a B2B transaction between the retailer and the supplier governed by a vendor agreement — defect thresholds, restocking fee terms, and authorization requirements that look nothing like consumer return policy. The OMS should model RTV as its own order type with its own approval workflow rather than forcing it through the same state machine built for consumer returns.

RTVs are typically generated from several distinct sources, and the OMS needs to route each to the right initiation path:

• Aggregated customer-returned defects that exceed a vendor's quality threshold, batched into a single RTV shipment
• Warehouse-discovered damage or quality issues found during receiving inspection, never having reached a customer
• Manufacturer recalls requiring return of specific lots regardless of condition
• Overstock or discontinued inventory returned under a vendor's buy-back or stock-rotation agreement

Most vendor agreements require a return authorization number before shipping goods back, and the retailer typically issues a debit memo against the vendor's account rather than waiting for the vendor to process a traditional refund. The OMS needs to track the debit memo amount against the actual credit the vendor eventually confirms, since discrepancies between claimed and approved credit are common and need a dispute-tracking mechanism rather than being absorbed silently as margin loss.

Shipping individual RTV items back to a vendor as they accumulate is usually far more expensive than batching. The OMS should support an RTV staging status that holds qualifying items until a batch threshold (dollar value, unit count, or a fixed schedule) is reached, then generates a consolidated outbound shipment — mirroring the same cost-optimization thinking applied to customer-facing split shipments, but in reverse.

An RTV is not complete until the vendor credit posts and matches the debit memo, closing the loop between physical goods movement and financial settlement. The OMS should keep the RTV order open in an "awaiting credit" state until this reconciliation happens, and surface aging RTVs whose vendor credit is overdue as a distinct exception queue for accounts payable to chase — otherwise, unresolved vendor credits become a slow, invisible source of margin leakage.