DL-009 · Case study
Amazon MWS to SP-API migration for a top 20 seller
BigFly's MWS code was over six years old and no longer supported. We migrated it to the SP-API, rebuilt FBM order and listing management and made the scripts faster.
- Client
- Big Fly
- Location
- USA
- Industry
- Amazon Seller
- Capabilities
- 02Stabilize03Build
01
Challenge
- MWS code over six years old and no longer supported by Amazon.
- FBM order management and listing management depended on that code.
- Operations had to continue during the migration.
02
Environment
- E-commerce reseller founded in 2005, headquartered in Secaucus, NJ.
- End-to-end services: content, advertising, logistics and brand protection.
- 20 MWS endpoints in production use.
03
Intervention
- Rewrote and optimised the source code to SP-API standards.
- Rebuilt FBM order management with new functionality.
- Added listing management features on the SP-API.
- Supported the client during and after the migration.
04
Outcome
- Faster processing and better reliability on the new SP-API code.
- Higher order volume and complexity handled with less effort.
- Project completed smoothly and without issues.
- 01MWS CODE6+ years old- -REWRITTEN CODESP-API standardsretired
- 02SP-API20 endpoints→REWRITTEN CODESP-API standards
- 03REWRITTEN CODESP-API standards→FBM ORDERSOrder management
- 04REWRITTEN CODESP-API standards→LISTINGSListing management
Results, as published.
- 3x
- Better performance of new code
- 20
- MWS endpoints migrated
- 3
- Deltologic team members involved
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→