Direct answer: RMA (Return Merchandise Authorization) is not "the customer sends it back and we sort it out later". It is a traceable pre-authorization process: the customer applies, the company decides warranty/non-warranty, issues an RMA number, agrees packaging/transport/customs, receives and inspects the unit, confirms repair/replacement/refund/charge, and closes the loop. A manufacturer's RMA page should state which cases qualify, which form fields are required, how the RMA number is used, whether cross-border returns use "returned goods" or "repair items", how batteries/dangerous goods are shipped, inspection/quote/turnaround, data wiping, costs and escalation. Otherwise, when a customer asks "where do I apply for an RMA number, who pays freight, how long does repair take, how is the return declared," the answer becomes an ad-hoc explanation.
This guide is for equipment, electronics, components, power-tool and battery-containing manufacturers in Changzhou and nearby areas. It explains how to write and accept an RMA page. Information is current to 2026-11-03. It is a review of public rules, customs supervision modes and project practice, not legal, customs, tax or transport advice; the specific contractual liability, supervision mode, tax/deposit and transport requirements depend on the contract, customs/tax rules and the carrier.
The core of RMA is "authorize first, then trace": a return without an RMA number is easy to lose, misjudge and impossible to settle. For cross-border repair, distinguish "returned goods (4561)", "repair items (1300)", "bonded repair (1371)" and "direct return (4500)"; the wrong mode affects duty/deposit/re-export. The website should state the application entry, form, turnaround, costs, data wiping and escalation—not just a return address.
How does the RMA page relate to warranty, 8D, spare parts and the customer portal?
The warranty/after-sales page answers "is it covered, for how long, what is excluded"; the 8D/complaint page answers "root cause/corrective/preventive"; the spare-parts page answers "which parts to buy"; the customer portal answers "orders/reconciliation/documents"; the RMA page answers "how this return/repair is authorized, shipped, inspected and settled." RMA is the execution process, not the warranty policy itself, and does not replace 8D.
Common breakpoints: only "contact sales if there is a quality issue"; no RMA form/number; the customer ships back and the company discovers missing parts/abuse; the wrong customs mode is used; batteries/dangerous goods are sent as ordinary parcels; inspection/quote/turnaround are not stated; refund/replacement/charge rules are unclear; data is not wiped before repair/resale. A page that states scope, process, form, customs, transport, turnaround, costs and red lines gives after-sales, quality, finance and logistics one playbook.
| Page/topic | Answers | Covers | Cannot replace |
|---|---|---|---|
| Warranty/after-sales | Covered? period? exclusions? | Liability scope | RMA execution |
| 8D/complaints | Root cause/corrective/preventive | Quality improvement | Return logistics/settlement |
| Spare parts | What to buy/how to fit | Parts supply | Repair authorization |
| Customer portal | Orders/reconciliation/documents | Transaction info | RMA inspection/settlement |
| RMA | Authorization/shipping/inspection/disposition | Return/repair execution | Warranty policy/root cause |
This page map is editorial; specific liability follows the contract, warranty terms and applicable law.
Which cases go through RMA?
Common RMA cases: dead-on-arrival (DOA), in-warranty failure, out-of-warranty/abuse, wrong/short/mis-shipped item, transport damage, recall/safety action, customer cancellation/return, sample/trial return and trade-in/upgrade return. Authorization, freight, inspection, charges and disposition differ by case, so the page should separate them rather than use one "returns" entry for everything. RMA is not "the customer can return anything"; it depends on the contract/warranty/sales policy.
Acceptance checks: does the page list eligible/ineligible cases; require contact/application first; distinguish warranty/non-warranty/no-fault; state freight/insurance/customs responsibility; state non-returnable custom/consumable/software/licence items; provide a separate recall/safety channel. Common gaps: "7-day no-reason return" (not necessarily B2B); custom parts listed as returnable; transport damage without keep-packaging/photos; no inspection fee for non-warranty.
| Case | RMA? | Focus | Common gap |
|---|---|---|---|
| DOA | Yes | Arrival window/photos/replacement | Treated as ordinary warranty |
| In-warranty failure | Yes | Serial/proof of purchase | No proof accepted |
| Out-of-warranty/abuse | Yes (quote) | Inspection/repair fee | Free repair |
| Wrong/short shipment | Yes | Packing list/replacement | Treated as return |
| Transport damage | Yes | Keep packaging/carrier claim | Signed without check |
| Recall/safety | Special | Batch/notice/disposition | Mixed with normal RMA |
| Cancellation/stock | Per contract | Restocking/discount | Unconditional return |
This case split is editorial; eligibility, freight and charges follow the contract, warranty and sales policy.
How should the RMA process be designed?
Recommended process: customer submits the application (model/serial/invoice/fault/photos) → company triage (warranty? on-site? safety?) → issue RMA number/authorization → customer ships per packaging/transport instructions → receiving registration/appearance/accessories check → inspection/quote/customer confirmation → repair/replace/refund/return → retest/ship → close and follow up. Each step needs an owner, turnaround, record and customer-visible status; the RMA number should link to the work order/serial/invoice/logistics.
Common gaps: receiving without triage; duplicate/handwritten RMA numbers; no accessory check at receiving; repairing without a quote; replacing without customer confirmation; no retest after repair; no reason/cost record at closure; RMA disconnected from 8D/claims/finance. The process must answer "where is it now, who is handling it, what happens next, how long".
| Step | What to do | Record | Common gap |
|---|---|---|---|
| Application | Form/photos/proof | RMA request | Email only |
| Triage | Warranty/safety/on-site | Triage record | Receive directly |
| Authorization | RMA number/address/requirements | Authorization | Verbal approval |
| Shipping | Packaging/transport/customs | Tracking | Customer ships blindly |
| Receiving | Appearance/accessories/serial | Receiving note | No check |
| Inspection | Reproduce fault/quote | Inspection report | No quote |
| Disposition | Repair/replace/refund/scrap | Customer confirmation | Unilateral action |
| Close | Retest/ship/follow-up | Closure record | No closure |
This process is editorial; specific approvals, authority and records follow the after-sales/quality system.
Which fields should the RMA form contain?
At minimum: customer/contact/email/phone; invoice/order/PO; model/serial/batch; purchase date/warranty status; fault symptom/conditions/frequency; photos/video; use environment/connected equipment; accessories/packaging included; requested disposition (repair/replace/refund/inspection); return address/consignee; data-wipe confirmation; dangerous-goods/battery status; RMA number (company-filled). The fields must support triage and inspection—not just "it is broken".
Acceptance checks: required/optional fields; serial validation; photo/video requirements; fault-description template; proof of purchase; data-wipe checkbox; dangerous-goods/battery flag; privacy notice; auto-reply/RMA number after submission; multilingual. Common gaps: no serial; no proof; fault description "does not work"; no photos; no backup/wipe warning; no battery/dangerous-goods distinction; no confirmation after submission.
| Field | Content | Use | Common gap |
|---|---|---|---|
| Customer | Company/contact/email/phone | Communication | Sales chat only |
| Order/invoice | PO/invoice/purchase date | Warranty check | No proof |
| Model/serial | Model/SN/batch | Traceability | Model only |
| Fault | Symptom/conditions/frequency | Triage/inspection | "Broken" |
| Evidence | Photos/video/logs | Reproduction | None |
| Accessories | Included items | Check | Missing |
| Disposition | Repair/replace/refund/inspection | Authorization | Not stated |
| Data/dangerous | Wipe confirmation/battery | Safety/compliance | No prompt |
This field list is editorial; the form follows the product, contract and privacy requirements.
How should warranty/non-warranty be decided and quoted?
First read the contract/warranty terms: scope, period, start date, exclusions (abuse/unauthorized repair/consumables/software) and proof; then inspect to confirm whether the fault is covered. For non-warranty/abuse/no-fault, get customer confirmation of inspection/repair/freight charges before repairing. Quotes should state labour/parts/freight/tax/validity; replacement/refund should state depreciation/restocking/discount. Do not "repair first and explain later".
Legal baseline: PRC Civil Code Article 582 (remedies for non-conforming performance, including repair, rework, replacement, return, price reduction), Article 617 (quality non-conformity remedies under 582–584) and Article 781 (work-result non-conformity: repair/rework/reduction/compensation). Application depends on the contract type/terms; B2B contracts can define the process/costs but cannot exclude statutory rights.
| Decision | Handling | Evidence | Common gap |
|---|---|---|---|
| In warranty | Free repair/replacement | Proof/inspection | Free without proof |
| Out of warranty | Quote/confirm | Inspection sheet | Repair first |
| Abuse/misuse | Quote/deny | Photos/report | Not explained |
| No fault | Inspection fee/return | Retest record | Free inspection |
| Missing parts/modified | Parts/quote | Receiving note | No check |
| Refund/replacement | Depreciation/restock | Policy/confirmation | Verbal promise |
Warranty decisions follow the contract/warranty; the legal baseline is Civil Code Articles 582/617/781—consult legal counsel for application.
Which customs mode should cross-border returns/repairs use?
Common routes: (1) "returned goods" (supervision code 4561): returned due to quality/spec/contract change and not re-exported; (2) "repair items" (1300): temporarily imported for repair and re-exported, usually with a deposit/deadline; (3) "bonded repair" (1371): repaired in a comprehensive bonded zone/bonded premises and re-exported, with different eligibility/catalogue/approval; (4) "direct return" (4500): returned after arrival but before release. The wrong mode affects duty, deposit, deadline and re-export obligations—confirm with the broker/customs first.
Available policies: for quality/spec reasons, export goods returned in original condition within one year of export release may be exempt from import duty/import taxes subject to conditions; cross-border e-commerce exports (1210/9610/9710/9810) returned in original condition within six months due to unsold/return (excluding food) may qualify for import duty/VAT/excise exemption under the Ministry of Finance/Customs/STA Announcement 2026 No. 16 (with proof of tax repayment/non-refund and return records). Customs/tax determination controls.
| Mode | Use | Key point | Common misuse |
|---|---|---|---|
| 4561 returned goods | Quality/spec/contract change, no re-export | Reason/time/original condition/documents | Treated as repair items |
| 1300 repair items | Repair then re-export | Deposit/deadline/re-export | Not re-exported |
| 1371 bonded repair | Repair in bonded zone/premises | Catalogue/approval/supervision | Treated as ordinary repair |
| 4500 direct return | After arrival, before release | Time/application | Used after release |
| E-commerce return | 1210/9610/9710/9810 | 6 months/original/non-food | Late/not original |
Supervision modes are subject to customs determination; policies: GACC Order 217, MOF/Customs/STA Announcement 2026 No. 16 and the latest customs/tax rules.
How should packaging, transport and data wiping be accepted?
Return packaging must protect the product: original/equivalent packaging, ESD bag, shock protection, locks/pallet, accessory list, RMA label; batteries/dangerous goods must follow UN38.3/dangerous-goods packaging/carrier rules—not ordinary parcels. Data-bearing products should be backed up/wiped/account-removed/encrypted-drive removed before return, with a data-wipe confirmation; devices with customer data must not be repaired/resold directly. Transport damage requires keeping packaging/photos/carrier claims.
Acceptance checks: packaging guide/video; RMA label; accessory list; battery/dangerous-goods marking; insurance/declared value; data-wipe steps/confirmation; arrival photos; quarantine of abnormal units. Common gaps: only "ship it back"; no RMA label; battery as ordinary parcel; no data-wipe reminder; no insurance; no arrival photos; damaged units put into stock directly.
| Item | Requirement | Evidence | Common gap |
|---|---|---|---|
| Packaging | Original/equivalent/shock protection | Guide/photos | Bare unit |
| RMA label | Number/address/contact | Label | No number |
| Accessories | List/complete | Packing list | Missing |
| Battery/dangerous | UN38.3/dangerous-goods packaging | Transport docs | Ordinary parcel |
| Data | Backup/wipe/confirmation | Confirmation | No action |
| Insurance/declaration | Value/insurance | Waybill | Under-declared |
| Arrival | Photos/quarantine | Receiving record | Direct to stock |
Packaging/transport follows the product, carrier and dangerous-goods rules; data wiping follows the information-security/privacy policy.
How should turnaround, costs and customer communication be accepted?
The page should state: application response time, RMA-number turnaround, inspection time after receipt, quote validity, repair/replacement/refund time, return shipping time and escalation. Costs should state who pays freight/insurance/customs/inspection/repair/parts/restocking/tax, and how warranty/non-warranty/no-fault/abuse are handled. Customers should see status (applied/authorized/received/in inspection/awaiting confirmation/repairing/shipped/closed).
Acceptance checks: working-day/time-zone definition; quote/confirmation/payment flow; escalation contact; multilingual; status lookup; notification templates; cost breakdown/invoice. Common gaps: "as soon as possible"; no inspection SLA; quote without validity; repair without customer confirmation; unclear cost basis; status only by phone; no escalation.
| Stage | Suggested turnaround/basis | Evidence | Common gap |
|---|---|---|---|
| Application response | 1–2 working days | Email/system | No reply |
| RMA number | 1–2 days after triage | Authorization | Verbal |
| Receiving/inspection | 2–5 working days | Inspection sheet | No SLA |
| Quote | 1–2 days/validity | Quotation | No validity |
| Repair/replacement | Parts/process dependent | Work order | No update |
| Return shipping | 1–3 days after completion | Tracking | No notice |
| Escalation | Overdue contact | Escalation record | None |
| Costs | Freight/inspection/repair/tax | Invoice | Unclear |
These turnarounds are editorial; specific SLAs depend on product, parts, region and contract—avoid promising what cannot be met.
How should RMA metrics and closure be accepted?
Track: RMA rate (by model/batch/customer), first-time fix rate, average inspection/repair/total cycle, no-trouble-found (NTF) rate, repeat repair rate, warranty/non-warranty mix, freight/repair cost, customer satisfaction and RMA-to-8D/claim count. Metrics should feed design/supplier/manual/training, not just after-sales statistics. Review top faults and repeat issues monthly/quarterly with corrective actions.
Acceptance checks: metric definitions/basis/data source; segmentation by model/customer/region; linkage to 8D/claims/PCN; targets/trends; review records; improvement owner/deadline. Common gaps: counting volume without cause; RMA disconnected from 8D; NTF not analysed; repeat repairs not escalated; cost not calculated; metrics untraceable.
| Metric | Basis | Source | Use |
|---|---|---|---|
| RMA rate | RMA/shipments (by model) | After-sales/ERP | Quality trend |
| First-time fix | First repair success/total | Work order | Repair capability |
| Cycle time | Application→closure | System | SLA |
| NTF | No-fault/total inspections | Inspection | Manual/training |
| Repeat repair | Same unit/fault return | Serial | Root cause |
| Cost | Freight/repair/parts | Finance | Pricing/improvement |
| To 8D | RMA→8D/claim | Quality | Closure |
These metrics are editorial; definitions/targets follow the after-sales/quality system.
How should the website RMA page be written?
A public page should include: eligible/ineligible cases; application entry/form; RMA number/authorization explanation; packaging/transport/dangerous-goods requirements; cross-border returned-goods/repair-items/bonded-repair explanation; warranty/non-warranty/inspection fees; turnaround/status lookup; data wiping; costs/refund/replacement; escalation contact; privacy notice. Write actionably: a customer can apply, ship and track from the page without repeatedly asking sales.
Separate "public process" from "customer-specific information": RMA numbers/inspection results/quotes go through the portal/email, while the public page gives process/form/address; do not publish customer names/fault data. Multilingual pages should match sales countries; address/phone/email must be copyable; the form must submit successfully with an auto-reply. Link the RMA page to warranty, 8D, spare parts and the customer portal.
| Section | What to write | Evidence | Avoid |
|---|---|---|---|
| Scope | Eligible/ineligible cases | Policy | "Everything returnable" |
| Application | Form/email/phone | Form test | Sales only |
| Authorization | RMA number/address/requirements | Template | Verbal approval |
| Transport | Packaging/battery/insurance | Guide | "Ship it back" |
| Cross-border | 4561/1300/1371 | Customs guide | Not explained |
| Costs | Freight/inspection/repair/tax | Price/policy | Vague |
| Turnaround/status | SLA/lookup/escalation | System | No SLA |
| Data/privacy | Wipe/notice | Confirmation/privacy page | No prompt |
This page structure is editorial; specific process/costs/addresses follow after-sales, the contract and customs requirements.
What must not be written?
High-risk claims: "7-day no-reason return" (not necessarily B2B); "all returns free" (freight/inspection/non-warranty not stated); "ship it back first" (no RMA number/authorization); "fully covered in warranty" (abuse/consumables/freight may not be); "any customs mode will do" (wrong mode affects duty/deposit); "batteries can go by ordinary courier" (dangerous goods/UN38.3); "data does not matter" (customer data/privacy); "fixed X days" (parts/cross-border uncertainty). These are inaccurate or misstate responsibility.
Safer wording: "per contract/warranty"; "apply for an RMA number first"; "freight/inspection/repair per..."; "cross-border mode confirmed with customs"; "batteries per UN38.3/carrier requirements"; "wipe data before shipping". External promotion must also comply with advertising/fair-competition law; customer names/cases need authorisation.
| Page wording | Problem | Suggested wording | Basis |
|---|---|---|---|
| "7-day no-reason" | May not apply to B2B | Per contract/policy | Contract |
| "All returns free" | Costs not separated | Freight/inspection/repair listed | Policy |
| "Ship it back" | No authorization | Apply for RMA number first | Process |
| "Warranty covers all" | Exclusions/freight | State scope/exclusions | Warranty |
| "Any customs mode" | Duty/deposit/re-export | Confirm with customs | Customs |
| "Battery by courier" | Dangerous goods | UN38.3/carrier | Transport |
| "Data not important" | Privacy/security | Wipe/confirm | Info security |
These red lines are editorial; whether a claim is false advertising/non-compliant is determined by regulators and the contract, and this is not legal advice.
Go-live acceptance checklist
Ten checks: scope/cases, application form, RMA number/authorization, transport/battery, cross-border mode, warranty/non-warranty/quote, turnaround/status, costs/refund, data wiping, and metrics/closure. Each needs an owner, evidence and review date. The pass condition is not "the page has a return address", but that a customer can apply, ship, track and confirm costs, and the company can trace and close the case.
Before go-live, run one real case through: application → triage → RMA number → shipping → receiving → inspection → quote/confirmation → repair/replacement → return → closure. Any step that fails is a gap in the page or the process.
| Check | Pass condition | Evidence | If it fails |
|---|---|---|---|
| Scope/cases | Eligible/ineligible clear | Policy/page | Add categories |
| Form | Fields/validation/confirmation | Form test | Revise |
| RMA number | Unique/traceable | System | Build process |
| Transport/battery | Packaging/UN38.3/insurance | Guide | Add guide |
| Cross-border | 4561/1300/1371 choice | Customs guide | Consult broker |
| Warranty/quote | Decision/confirmation/validity | Quotation | Add rules |
| Turnaround/status | SLA/lookup/escalation | System | Add SLA |
| Costs/refund | Basis/invoice/restock | Finance | Add policy |
| Data | Wipe/confirmation | Confirmation | Add process |
| Metrics | RMA rate/cycle/NTF | Report | Add metrics |
This checklist is editorial; specific process/costs/customs/transport follow the company policy, contract and competent authority.
Who should read this, who should not, and what decisions does it support?
It suits manufacturers in Changzhou and nearby areas with B2B returns/repairs, cross-border after-sales, battery/dangerous-goods or equipment products. It also suits after-sales, quality, logistics, finance, legal and website teams assessing an RMA page. It does not suit one-off consumer products with no after-sales process, or teams wanting one page to replace contract/customs/transport advice.
Read it if returns/repairs are chaotic, there is no RMA number, the wrong cross-border mode is used, freight/inspection costs are disputed, or data wiping is a risk; you are building/revising a website RMA page. Skip it if you treat RMA as a "return address", ship first and authorize later, or promise "all free/fixed days". It supports self-review of scope, form, authorization, transport, customs, warranty/quote, turnaround, costs, data and metrics.
FAQ
How is RMA different from warranty and 8D?
Warranty is the "covered? period? exclusions?" policy; 8D is the "root cause/corrective/preventive" quality improvement; RMA is the execution process for "how this return/repair is authorized, shipped, inspected and settled." They reference each other but are not interchangeable.
Must an RMA number be requested first?
It is strongly recommended. The RMA number links customer/model/serial/invoice/logistics/inspection/cost; without it, returns are easily lost, misjudged and impossible to settle. The page should state the application entry, required information and the authorized address/packaging.
Should a cross-border return use "returned goods" or "repair items"?
It depends on the purpose: return without re-export due to quality/spec/contract change usually uses "returned goods" (4561); repair then re-export usually uses "repair items" (1300); repair in a bonded zone/premises may use "bonded repair" (1371); return after arrival but before release uses "direct return" (4500). The wrong mode affects duty/deposit/re-export—confirm with the broker/customs.
How are out-of-warranty/abuse repairs charged?
Inspect and quote first; repair only after customer confirmation. Charges may include inspection, labour, parts, freight and tax; no-fault/denied cases should state the inspection fee/return arrangement; refund/replacement may involve depreciation/restocking/contract terms. Follow the contract/warranty—do not "repair first and explain later".
How should returned batteries/dangerous goods be shipped?
Follow UN38.3, dangerous-goods packaging and carrier rules—not ordinary parcels; confirm battery condition (damaged/swollen/recalled), transport documents, declaration and insurance. The page should tell customers to contact first and pack per instructions to avoid carrier rejection or safety incidents.
How long does RMA take, and how to follow up?
The page should state suggested turnaround for application response, RMA number, receiving/inspection, quote, repair/replacement and return shipping, plus an escalation contact; actual timing depends on product/parts/cross-border. Customers should query status by RMA number/portal, and the company should record each step and overdue escalation.
One-sentence takeaway
A Changzhou manufacturer's RMA page should not be "a return address". It should turn eligible cases, the application form, RMA number/authorization, packaging/battery transport, cross-border mode, warranty/quote, turnaround/costs, data wiping and metrics closure into an actionable checklist—so a customer can apply, ship, track and confirm, and the company can trace and close the case.
Method and limitations
This is a review of public rules, customs supervision modes and project practice, not an audit or legal opinion on any company's contract, after-sales, customs, tax or transport. No undisclosed customer return data, RMA records or contracts were used. Processes, fields, turnaround and acceptance items are editorial suggestions, not legal/customs/tax conclusions. Specific liability, supervision mode, tax/deposit, transport and privacy requirements depend on the contract, customs/tax rules, carrier and competent authority.
Sources and scope
Information is current to 2026-11-03. The following are public official/standard pages; their terms, application and latest rules control.
- Civil Code of the People's Republic of China, Articles 582, 617 and 781 (remedies for non-conforming performance/quality/work results): gov.cn.
- Measures of the PRC Customs on the Administration of Direct Return of Imported Goods (GACC Order No. 217, promulgated 2014-03-12, amended 2018): GACC.
- Announcement No. 16 of 2026 of the Ministry of Finance, GACC and STA on tax incentives for cross-border e-commerce export returns (2026-02-06): Beijing Tax Service, STA. Six months/original condition/codes 1210/9610/9710/9810/non-food.
- ISO 9001:2015, Quality management systems — Requirements, 8.7 (control of nonconforming outputs) and 10.2 (nonconformity and corrective action): ISO.