DL-034 · Case study
A middleware API that shields the ERP from SP-API
A personalised-products seller wanted its ERP to talk to Amazon without learning SP-API. We built a middleware API that speaks plain REST and handles Amazon's reports, feeds and tokens.
- Client
- Name withheld
- Location
- Poland
- Industry
- Personalised-products seller
- Capabilities
- 03Build02Stabilize
01
Challenge
- The ERP vendor could not take on SP-API's reports, feeds and token handling.
- Personalised orders carry customisation data that production needs intact.
- VAT invoices had to be uploaded to Amazon for European orders.
02
Environment
- Seller of personalised products on European and US Amazon marketplaces.
- Both merchant-fulfilled and FBA orders.
- ERP calling external services over simple authenticated HTTP.
03
Intervention
- REST API with per-client bearer tokens mapped to Amazon refresh tokens.
- Unshipped orders from reports every 30 minutes, with read markers that expire.
- Customisation data, FBA orders, tracking feeds and VAT invoice uploads.
- Moved feeds to JSON and split report requests above Amazon's marketplace limit.
04
Outcome
- The ERP handles Amazon orders through one small, stable interface.
- Amazon API changes are absorbed in the middleware, not in the ERP.
- Running under a monthly maintenance agreement.
- 01ERPSeller system→MIDDLEWARE APIREST / bearer tokensREST
- 02TOKEN MAPRefresh tokens→MIDDLEWARE APIREST / bearer tokens
- 03MIDDLEWARE APIREST / bearer tokens→REPORTSUnshipped / FBA orders
- 04MIDDLEWARE APIREST / bearer tokens→FEEDSTracking / VAT invoices
- 05MIDDLEWARE APIREST / bearer tokens→CUSTOMISATIONOrder details
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→