DL-033 · Case study
FBM orders API between Amazon and an ERP
An apparel manufacturer fulfils its own Amazon orders from an in-house ERP. We built a small serverless API that hands the ERP every order and confirms shipments back.
- Client
- Name withheld
- Location
- US East
- Industry
- Apparel manufacturer
- Capabilities
- 03Build
01
Challenge
- Merchant-fulfilled Amazon orders were not reaching the ERP automatically.
- Shipping addresses needed restricted data access, which the account lacked.
- Inventory and tracking had to flow back to Amazon without manual entry.
02
Environment
- Long-established manufacturer selling on Amazon with merchant fulfilment.
- In-house ERP owned by the client's IT team.
- A private SP-API application for the client's own seller account.
03
Intervention
- Serverless API returning unshipped orders, refreshed every 30 minutes.
- Item prices, taxes and cancelled orders exposed in a format the ERP reads.
- Shipment confirmations with tracking numbers sent back to Amazon.
- Inventory feed from the ERP and approval for restricted address data.
04
Outcome
- FBM orders flow from Amazon into the ERP without manual exports.
- Tracking and stock levels update on Amazon from the ERP.
- In production since 2025 with follow-on work since.
- 01SELLER CENTRALFBM orders→ORDERS APIServerlessevery 30 min
- 02ORDERS APIServerless→ERPFulfilment
- 03ERPFulfilment→WAREHOUSEPick / pack / ship
- 04ERPFulfilment- -FEEDSTracking / stocktracking + stock
- 05FEEDSTracking / stock→SELLER CENTRALFBM orders
Stack and services.
Tell us what has to work.
A senior engineer reads every brief. Describe the system, what it runs on today and what happens when it fails.
Discuss a project→