Discuss a project

DL-STB-02 · Stabilize / Amazon SP-API

Amazon MWS to SP-API migration

Amazon MWS is retired. Integrations still shaped around it, or pinned to deprecated SP-API versions, break without warning. We move them to current endpoints and keep every function your business relies on.

Discuss a project Scope
51.4344.0060°02STABILIZEDETAIL 02 · STABILIZE · DL-STB-02

Why MWS to SP-API migration stalls

  1. 1.

    MWS-era code untouched for years, business logic undocumented

  2. 2.

    Auth rebuilt from MWS keys to Login with Amazon OAuth

  3. 3.

    Endpoints, reports and feeds that do not map one to one

  4. 4.

    Legacy stacks with no SP-API client, such as Visual FoxPro

A legacy application that called the retired MWS API is rewired through a new SP-API layer that preserves its logic, obtains access tokens from Login with Amazon, calls current SP-API endpoints and keeps feeding ERP and fulfilment.BEFOREretiredsame functionstokenmapped callsAMAZON MWSretiredLEGACY APPorders / listingsSP-API LAYERlogic preservedLOGIN WITH AMAZONrefresh → access tokenSP-APIcurrent versionsERP / FBM OPSorders keep flowing
Fig. 02Migration pathA legacy application that called the retired MWS API is rewired through a new SP-API layer that preserves its logic, obtains access tokens from Login with Amazon, calls current SP-API endpoints and keeps feeding ERP and fulfilment.Scale NTS

What the engagement covers.

  1. 01

    Code analysis

    The old application read end to end, so no business rule is lost in translation.

  2. 02

    Endpoint mapping

    Every MWS call or deprecated SP-API operation mapped to its current replacement.

  3. 03

    Auth rebuild

    Login with Amazon OAuth, token refresh and, where PII is involved, Restricted Data Tokens.

  4. 04

    Upgrade in passing

    Logic simplified and new features or integrations added while the code is open.

  5. 05

    Documentation & support

    New technical documentation and support through and after cutover.

How it runs.

  1. P01

    Analysis

    Understand the logic behind the old application.

  2. P02

    Optimization

    Simplify and optimize that logic for the new version.

  3. P03

    Expansion

    Add requested functions and integrations during the migration.

  4. P04

    Support

    New technical documentation and help with maintenance.

What you get.

ItemDeliverableQty

  1. 01Integration running on current SP-API endpoints1
  2. 02Endpoint map: old call to new call1
  3. 03Updated technical documentation1
  4. 04Post-migration support1

Stack08

  • Amazon SP-API
  • Login with Amazon (LWA)
  • Tokens API
  • Reports API
  • Feeds API
  • AWS Lambda
  • Node.js
  • TypeScript

Related projects.

  1. DL-009Amazon MWS to SP-API migration for a top 20 sellerBig Fly · USA02Stabilize03Build
  2. DL-006Adapter for Amazon SP-API authenticationOrion · USA03Build04Secure
All case studies

Questions engineers ask us.

Q01Is Amazon MWS still available?

No. Amazon has retired MWS; SP-API is the supported API for selling partners. Code still built around MWS needs to be migrated or rebuilt.

Q02We are already on SP-API. Is this still relevant?

Often. Amazon versions and deprecates SP-API operations and feed formats over time. We migrate those integrations the same way.

Q03Can you connect a legacy system with no SP-API library?

Yes. For Orion we built a connector that lets a Visual FoxPro application authenticate and call SP-API, including restricted data.

Q04What does a migration look like at scale?

For a top-20 Amazon seller we migrated 20 MWS endpoints and rebuilt FBM order and listing management on SP-API.

Related services.

Still running on MWS-era code?

Tell us what the integration does today. We map what has to move and what can improve on the way.

Discuss a project