mirror of
https://github.com/OCA/rma.git
synced 2025-02-16 17:11:47 +02:00
aa9e542129
It was assumed that this method (used for any model) always had an RMA in return, which wasn't correct at all and could lead to cross-model and cross-customer subscripting if an RMA id matched the one of the form model creating (eg.: `crm.lead` in 'Contact Us' form)
RMA (Return Merchandise Authorization)
Management of Return Merchandise Authorization (RMA) in Odoo : product return, warranty control, product exchange, product refund,...
The workflow allowed by this project looks like:
- Receive an email from customers and automatically creates a Claim
- Route this claim correctly and affect a responsible and open it
- Find the invoice concerned by the claim
- Check the warranty status
- Choose between various possibilities :
- Refuse the Claim (e.g. out of warranty)
- Return the customer's goods and send new ones in 2 click
- Send the goods to the supplier
- Refund the customer
Main modules:
product_warranty Extend the warranty details to product/supplier form
- supplier warranty
- return product to company, supplier, brand
- return instructions
crm_claim_rma
Management of Return Merchandise Authorization (RMA) in OpenERP. Upgrade the standard crm_claim module to add :
- product returns (one by one, mass return by invoice)
- warranty control & return address (based on invoice date and product form)
- product picking in / out
- product refund
- product exchange
- access to related customer data (orders, invoices, refunds, picking in/out)