Returns and rework are a reality for every manufacturer. Most companies can authorize an RMA. Fewer have the process or vehicles for carrying it through receiving, quality, production, shipping, and accounting.
RMAs and rework can have a significant impact on the top and bottom line. Credits and refunds reduce revenue. Repair adds cost to a product already built and takes capacity away from new, revenue-producing work. Poor execution also puts customer relationships at risk, which is everything in contract manufacturing.
Each RMA type has its own workflow requirements. More complex RMAs, particularly rework, require multiple stakeholders and transactions. A centralized manufacturing system can manage those paths, capture the costs, and produce reporting to reduce future losses.
The True Cost of Rework
A review of industry research and Cetec ERP customer data found that RMA value averaged 3.44% of revenue, with processing and rework adding an estimated 30% for labor and materials. For a $10 million manufacturer, annual exposure would be roughly $447,000. This does not include the risk to customer relationships and reputation.
RMAs can inhibit growth, maturity, stability, and profitability. Processing an RMA efficiently through its lifecycle limits disruption and preserves customer relationships. Reporting on cost and root cause helps reduce future rework.
Understanding RMA Processes
Start with the RMA type because it determines the transactions that follow. A return receives the product and issues a credit; after that, the assembly may be returned to stock, moved to rework, or scrapped. A refund issues a credit without receiving the product. A repair receives the assembly for rework and shipment back to the customer. A replacement sends another unit, sometimes before the original is received.
These are not variations of the same process. A return may require receiving, quality disposition, and a credit. A repair adds a rework order, issued material, production labor, inspection, and shipment. A replacement may require fulfillment before the returned product arrives, while the original return and its financial resolution remain open.
The RMA provides the central hub for these structured but flexible paths. As it moves from customer service or program management through quality, receiving and inventory, production, shipping, and accounting, ownership and status remain connected to the same record. Warranty status, repair history, or quality disposition may change the path without losing the connection to the original order, product history, and customer request.
Initiate the Right Transactions
From the RMA, the system initiates the transactions required for the selected path. The RMA originates from the order or invoice, with traceability to lot and serial data. If a product is coming back, an internal purchase order or equivalent transaction receives it. The assembly can then be controlled pending quality disposition.
If repair is approved, the work instructions and materials are added to a rework order. That order is scheduled and captures the returned assembly as an input. Production can issue components, record labor, and document inspection. The same RMA may also lead to a credit memo, NCR, or corrective action.
These are related transactions, not separate administrative events. Each represents the next decision in the same customer and product history. The system needs the necessary vehicles to initiate the work and maintain the connection between them, with status managed and communicated through the RMA.
Collect and Report on Useful Data
The completed RMA should show what happened, how long it took, and what it cost. Reason and defect data support root cause analysis. Labor, material, freight, scrap, and credits establish the financial impact. Turnaround time shows whether the process is creating customer risk.
A fully integrated manufacturing ERP centralizes this information as part of the RMA process. It connects authorization to receiving, quality disposition, rework, inventory consumption, shipment, credit, and corrective action. This provides the reporting needed to understand cost, identify recurring problems, and mitigate the financial and customer impact.
Scott Ryan is a senior consultant at Cetec ERP.
