Warranty, Returns, and After-Sales Service (RMA) with ERP: From Claim to Supplier Recovery

For companies that sell durable goods such as electronics, machinery, vehicles, furniture, or spare parts, the sale is not the end of the relationship with the customer. After delivery come warranty claims, repair requests, returned faulty goods, and replacement units. In many companies all of this is managed through WhatsApp messages, paper, and spreadsheets. As a result, technicians do not know whether an item is still under warranty, the warehouse does not know where returned goods should go, and finance does not know what warranty really costs.

Tidy after sales service management, often called RMA (return merchandise authorization), turns that mess into a tracked process: from an incoming claim, warranty verification, receipt of goods, repair or replacement, return to the customer, and claim to the supplier. This article covers that flow, the data needed in an ERP, the stock and accounting treatment, and how to use warranty data to improve products and suppliers.

Summary

• Good after sales service starts with data: serial number, purchase date, and warranty period recorded per unit
• A clear RMA flow covers authorization, receipt, inspection, decision, action, and closure, with statuses visible to every department
• Returned goods need their own stock location and status so they are not mixed with sellable stock
• Warranty cost needs to be recorded as a provision and as actuals, and supplier claims need to be tracked so costs can be recovered
• Claim data analyzed by product, lot, and supplier is the most valuable tool for raising quality and reducing future claims

Why after sales so often falls into disorder

Some patterns commonly seen in mid sized companies:

• Warranty information exists only on the invoice or in the memory of sales staff, so verifying a claim takes time and often causes arguments
• Faulty goods are received by the warehouse without documents, then pile up in a corner with unclear status
• Customers ask about repair progress and nobody can answer with certainty
• Replacement units are shipped without being recorded as a stock issue, so system stock differs from physical stock
• Repair and replacement costs are not visible as warranty cost, so product margins look better than reality
• Goods that were actually defective from the supplier are never billed back because there is not enough record

These problems do not only annoy customers. They quietly erode margin and make the company lose valuable information about product quality.

The data foundation: unit, serial number, and warranty period

Everything starts with being able to answer one simple question: who was this unit sold to, when, and until when is it under warranty. For that the ERP needs to store a few things.

• Serial number per unit for high value goods, or lot number for bulk goods, recorded when goods are issued to the customer
• Handover date or activation date as the warranty start point, not only the invoice date if the two differ
• Warranty rules per product: duration, coverage, what is excluded, and conditions such as mandatory periodic servicing
• Unit history: all claims, repairs, and replacements that have ever occurred for that serial number
• Link to the customer and the originating project or sales order

Similar concepts are discussed in the article on lot, batch, and expiry date tracking with ERP; the serial number is the most detailed form of traceability. The quality of this data depends on tidy master data, especially consistent item codes and customer data.

The RMA flow step by step

1. Claim intake

Claims can arrive by phone, WhatsApp, email, customer portal, or dealer. Whatever the channel, the claim is recorded as one document in the system, ideally linked to a customer support ticket system so communication and response time targets are tracked. Record the complaint, serial number, evidence such as photos or video, and the customer's contact.

2. Warranty verification and authorization

The system checks the serial number against sales history and warranty rules, then shows the status: still under warranty, expired, or not covered. An officer decides whether the claim is approved, rejected with a recorded reason, or accepted as a paid repair. Once approved, issue a return authorization number to be shown on the package, so goods arriving at the warehouse can be recognized.

3. Shipment and receipt of goods

The goods are sent by the customer, collected by a courier, or inspected on site. On arrival, the warehouse matches the goods to the authorization number, photographs the condition, then records receipt into a dedicated returns location, not onto sellable stock shelves. This matching matters so goods do not get lost between shipment and receipt.

4. Inspection and diagnosis

A technician inspects and records findings: type of damage, suspected cause, and whether there are signs of misuse that void the warranty. Structured notes with standard damage codes, not only free text, make later analysis possible.

5. Decision and action

The inspection result leads to one of these decisions:

• Repair: using spare parts and labor hours, recorded as cost on that claim
• Unit replacement: a new unit is issued from stock, the old unit enters assessment
• Refund or credit note, according to policy
• Rejection with a written explanation and a paid repair option
• A claim to the supplier if the damage stems from a production defect

6. Return to the customer and closure

Repaired goods or the replacement unit are sent back, proof of handover is recorded, and the claim is closed after customer confirmation or after a set time limit. Every step has a status visible to sales, warehouse, and customer service, so customer questions are answered from the system.

Stock treatment for returned goods

Returned goods must not be mixed straight into sellable stock. A common practice is to provide separate stock locations and statuses:

• Awaiting inspection: goods just received and not yet decided
• Under repair: being worked on by a technician, possibly using spare parts issued from stock
• Ready to resell: goods that pass inspection, which can be sold as new or as certified used goods per policy
• Refurbished or grade B goods: sold at a lower price with a clear label
• Damaged or scrapped goods: returned to the supplier, dismantled for parts, or written off with approval
• Awaiting return to supplier: goods claimed from the supplier and not yet replaced or credited

A warehouse structure that supports these statuses is discussed in the article on warehouse management systems for growing businesses. For products with strict quality control, a similar quarantine flow is described in QC quality control in manufacturing with ERP.

Accounting for warranty cost

A warranty is an obligation that arises when the product is sold, but its cost only occurs later. Good recording keeps financial statements honest.

• Warranty provision: the expected warranty cost is recorded at the time of sale based on historical experience, for example a certain percentage of sales value, according to the accounting standards that apply to your company
• Actuals: the real repair costs, in the form of spare parts, labor, shipping, and replacement units, are charged against the provision or to warranty expense
• Adjustment: the provision is reviewed periodically and adjusted to actual claims
• Paid repair revenue: claims outside warranty are recorded as service revenue with a separate invoice
• Supplier claims: receivables from suppliers are recorded and tracked until credited or paid

The exact accounting rules depend on the standards and tax provisions that apply to you, so discuss them with your accountant. What matters is that warranty cost is visible per product, not scattered anonymously in general expenses.

Supplier claims: billing back what is rightfully yours

Many companies bear the entire warranty cost even though most failures come from component or production defects that are the supplier's responsibility. To bill back, data is needed.

• Link the unit's serial or lot number to the supplier and the originating purchase document
• Record damage codes and inspection evidence on every claim
• Watch claim deadlines per the supplier agreement, because late claims can be rejected
• Create supplier claim documents from the system, and track their status: submitted, approved, replaced, credited
• Report defect rates per supplier as input for [supplier performance assessment](/blog/manajemen-pemasok-dan-penilaian-vendor-dengan-erp) and the next price negotiation

Companies that previously did not bill back are often surprised by the size of the legitimate claims once the data is neatly gathered.

Using claim data to improve the business

The greatest value of an RMA system actually comes from analyzing its data.

• Claim rate per product and per model: which products have problems most often
• Claim rate per lot or production period: whether a production or shipment group has a problem
• Distribution of damage codes: what failures are most common, so they can be traced to design improvements or usage instructions
• Average resolution time and its spread: how long customers wait, and at which stage time is wasted
• Warranty cost as a percentage of sales per product, so pricing and supplier decisions are fact based
• Repeat claim rate on the same unit, signaling incomplete repair or a design defect

This analysis can be shown on a business dashboard for daily decisions, so management sees trends before they become a crisis, for example a spike in claims after a component supplier change.

Paid maintenance and service contracts

After sales is also a revenue opportunity. Many companies offer periodic service contracts, warranty extensions, or spare part packages. An ERP can help with service schedules based on date or usage hours, automatic reminders to customers, and recurring billing. For companies that routinely service customer equipment, the approach resembles asset and equipment maintenance management with ERP, only the asset being maintained belongs to the customer.

Steps to implement gradually

1. Map the current claim flow and mark the points where goods or information often get lost.

2. Make sure serial or lot numbers are recorded when goods are issued for the main products.

3. Set warranty rules per product and store them in master data.

4. Create an RMA document with standard statuses and an authorization number.

5. Provide a dedicated stock location and status for returned goods.

6. Define uniform damage codes that must be filled in at inspection.

7. Record warranty cost per claim, and set up the supplier claim flow.

8. After three months of data, review claim reports by product and supplier.

Start with one product line that has the most claims. Extending to all products is easier once the flow has proven itself.

Frequently asked questions

Do all goods need serial numbers? No. Use serial numbers for high value goods or goods whose warranty is often claimed, and lot numbers for bulk goods. Recording serial numbers for cheap goods is often not worth the cost.

What if the customer has no proof of purchase? With data in the ERP, the purchase can be looked up from the serial number, customer name, or order number. This is one real benefit of recording up front, because it does not depend on lost paper.

Should ordinary returns and warranty claims be separated? Preferably yes, because their causes, policies, and accounting treatment differ. Ordinary returns relate to the goods return policy and are discussed in the article on returns and refunds in online stores, while warranty claims relate to defects or functional failure.

How long does it take to implement? For one product line, the basic flow can usually run within a few weeks. Analysis and supplier claims follow once data has accumulated.

Conclusion

Tracked after sales service protects three things at once: customer satisfaction because claims are handled quickly and transparently, margin because warranty cost is visible and can be billed back to suppliers, and product quality because damage data becomes feedback for design and purchasing. Start with serial number data and warranty rules, build a clear RMA flow with separate stock statuses, then use the claim data for decisions. From something long seen as a burden, after sales can become a source of insight and customer loyalty.