Amazon returns and refunds in Business Central
Integrate Amazon returns, refunds, credit notes and stock status with Business Central. Get control of both FBA and FBM returns.
· 3 min read
Amazon returns and refunds in Business Central: when the sale goes the other way
Integrations are often designed around the happy path:
Order → stock → delivery → payment.
But e-commerce does not stop at the delivery.
Some items come back. Some customers get refunds. Some items can be sold again. Others cannot.
That is why Amazon returns and refunds in Business Central should be part of the integration design from the start.
Amazon’s Reports API can be used for, among other things, report data on returns, inventory and orders, while Amazon also has separate processes for seller-fulfilled returns. Amazon Developer Docs
Returned and refunded are not the same thing
It is important to distinguish between two events.
Refund: the financial event.
Return: the physical movement of goods.
They can be connected, but they should not be treated as the same data type.
A customer can, for example, receive a refund before the physical item has been received.
That is why finance and stock should not be updated blindly off the same event.
With FBA, Amazon handles much of the physical process
With FBA, Amazon takes over a large part of fulfilment and returns handling.
That does not mean the company can ignore returns data.
Business Central may still need to know:
- which original order the return relates to
- which SKU is involved
- which amount has been refunded
- how stock status is affected
- whether the item can go back into inventory
- how the financial event should be handled
Read more about [Amazon FBA integration for Business Central](/en/amazon-fba-integration-business-central/).
With FBM, the company’s own warehouse becomes part of the process
With FBM, the company or its 3PL often receives the item physically.
That raises a new question:
What condition is the item in?
A returned item can be:
- sellable
- damaged
- defective
- awaiting inspection
- for scrapping
It is not necessarily correct to put it straight back into available stock.
Also read [Amazon FBM integration for Business Central](/en/amazon-fbm-integration-business-central/).
Return reasons are valuable data
If one particular SKU has markedly more returns than others, that is not only a customer service problem.
It can point to:
- product quality
- an incorrect product description
- sizing problems
- packaging
- transport damage
Once returns data is structured and linked to product and sales data, the company can put it to active use.
The returns flow should be defined
An example of an FBM flow:
Amazon return request → Business Central → warehouse/3PL → physical inspection → stock status → refund/credit → reporting
An FBA flow may have a different physical process, but Business Central still needs the relevant ERP and financial data.
Avoid building returns as an afterthought
It is much easier to design returns handling together with the order flow than to add it afterwards.
From the start you should define:
Which key connects the return to the original order?
When does stock status change?
When does the financial posting take place?
How are partial refunds handled?
How are items that cannot be resold handled?
The key takeaway
A good Amazon flow does not only run from Business Central to the customer.
It also has to be able to handle data moving back.
When returns and refunds are an integrated part of the system architecture, the warehouse, customer service and finance are each spared from inventing their own manual process.