DL-035 · Case study
MWS to SP-API and feed migration for a textbook seller
A textbook seller ran Amazon on its own Python scripts. We moved them from MWS to SP-API, then replaced retired feeds, keeping the file formats its team already used.
- Client
- Name withheld
- Location
- US South
- Industry
- Textbook retailer
- Capabilities
- 02Stabilize03Build
01
Challenge
- In-house scripts for orders, tracking and listings depended on the retiring MWS.
- Amazon later deprecated several feeds the inventory loader relied on.
- The internal team wanted to keep its own input and output formats.
02
Environment
- Python scripts run by the seller's in-house IT team.
- Order lists, tracking uploads and price and stock feeds.
- Flat-file inventory loads for a large catalogue of book listings.
03
Intervention
- Rewrote order, tracking and price and stock calls against SP-API.
- Replaced deprecated feeds and the flat-file loader with current SP-API equivalents.
- Kept every script's existing file formats so downstream processes did not change.
- Added ISBN-to-ASIN lookup and offer scripts, and assessed Buy Shipping.
04
Outcome
- Daily order and listing scripts run on SP-API instead of MWS.
- Feed deprecations handled without retraining staff or reworking downstream files.
- The seller's own team still owns and runs the scripts.
- 01SCRIPT FILESUnchanged formats- -MWSRetiredbefore
- 02SCRIPT FILESUnchanged formats→SP-API LAYERCalls + feeds
- 03INVENTORY LOADERFlat files→SP-API LAYERCalls + feeds
- 04SP-API LAYERCalls + feeds→ORDERS APIOrders / tracking
- 05SP-API LAYERCalls + feeds→FEEDS APIPrice / stock
- 06SP-API LAYERCalls + feeds→CATALOGISBN to ASIN
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→