Amazon SP-API Consulting: How to Hire the Right Developer
What an Amazon SP-API consultant does, when a connector is enough, engagement models, questions to ask and red flags before you hire an SP-API developer.
- Written by
- Md AshikSenior Software Engineer, Artisan Dojo
- Published
- Reading time
- 7 min read
Quick summary30-second read
- An SP-API developer scopes, builds, hosts, monitors and maintains the link between your Amazon account and your ERP or warehouse system.
- If a maintained connector or ERP plugin already covers your flows, use it; hire help when it cannot model your business rules.
- Common engagement models are fixed-scope projects, time and materials, and maintenance retainers that cover monitoring and Amazon API migrations.
- Effort depends on data flows, marketplaces and regions, your ERP, restricted buyer data, volume and business rules.
- Before hiring, confirm who owns the code, developer account and credentials, and how monitoring and deprecations like Orders API v0 are handled.
An Amazon SP-API consultant or developer scopes, builds, hosts and maintains the code that connects your Amazon seller account to your ERP, warehouse system or internal tools. You need one when an off-the-shelf connector or your ERP's plugin cannot handle your processes, and nobody in-house has time to own an integration that Amazon keeps changing. If a maintained connector already covers your flows, use it and save the money.
This is a buyer's guide: what the work actually involves, how engagements are usually structured, and how to tell a solid provider from a risky one. For the technical side of the API itself, see our Amazon SP-API integration guide.
What does an Amazon SP-API consultant actually do?
Writing API calls is the smallest part. A good SP-API developer or agency covers the whole lifecycle:
- Scoping. Mapping your processes (orders, shipping, stock, prices, listings, returns, settlements) to the right APIs, and deciding which system is the source of truth for each type of data.
- Developer registration and roles. Setting up a developer profile in the Solution Provider Portal and requesting only the roles you need. Roles that expose buyer personal data are restricted and require extra information about how the data is used and protected.
- Authorization and credentials. Wiring up Login with Amazon (LWA), storing refresh tokens and client secrets safely, and rotating the LWA client secret, which Amazon requires every 180 days.
- Building the ERP side. Mapping Amazon orders, products and payouts to your ERP's data model. This is often the harder half of the project.
- Rate limits and reliability. Queues, retries with backoff, idempotent order import, and bulk operations instead of one call per SKU.
- Hosting. Running the integration somewhere reliable, with a way to deploy fixes.
- Monitoring. Logging and alerts, so a stalled order import is noticed by the provider before your customers notice it.
- Maintenance. Reading Amazon's changelog and deprecation schedule and updating the code before something is switched off.
The last point is the one people underestimate: Amazon retires API versions and formats on fixed dates, and an unmaintained integration eventually stops working.
Do you need to hire an SP-API developer?
Not always. There are three realistic options.
| Factor | Do it yourself | Connector or ERP plugin | Hire an SP-API developer |
|---|---|---|---|
| Best for | In-house developer with time, simple flows | Supported ERP, standard processes | Custom logic, unsupported systems, high volume |
| Upfront effort | Your team's time | Setup and configuration | A build project |
| Ongoing cost driver | Staff time | Subscription, often tied to volume or plan tier | Hosting and maintenance |
| Fit for unusual processes | As far as your team can take it | Limited to what is configurable | Full control |
| Who handles Amazon API changes | Your team | The vendor | The developer, if it is in the contract |
| Who owns code and data | You | Mostly the vendor | You, if the contract says so |
| Main risk | Knowledge leaves with one person | Gaps filled with manual work | Choosing the wrong provider |
Use a connector or your ERP's plugin if it already supports Amazon and your other marketplaces with the flows you need. You are buying a solved problem, and the vendor deals with API changes. Our custom integration vs connector guide goes deeper.
Build it yourself if you have a developer who can own it long term, your scope is small (for example orders in, stock out) and you sell in one Amazon region.
Hire help if the connector cannot model your business rules, your ERP is unusual or heavily customized, you sell across many Amazon marketplaces, you run into rate limits, or you already have an integration that keeps breaking.
Top tip
Before talking to any provider, ask your ERP vendor whether a maintained Amazon connector exists and exactly which flows it covers. If it handles everything you need, you may not need a developer at all, and an honest consultant will tell you so.
What engagement models do SP-API developers offer?
- Fixed-scope project. An agreed list of flows, for an agreed price and timeline. Works well when requirements are clear. Expect a scoping phase first, and change requests for anything outside the scope.
- Time and materials. You pay for hours worked. Suits projects where requirements will evolve, or where an existing integration needs investigation before anyone can estimate a fix.
- Maintenance retainer. A recurring agreement covering monitoring, fixes, Amazon API migrations and small changes. This is what keeps a custom integration alive after go-live; see integration maintenance.
A common pattern is a short paid assessment or scoping phase, a fixed-scope build, then a retainer. Be wary of a quote for the build with no plan for what happens afterwards.
What drives the effort and cost of an SP-API project?
The API is the same for everyone. Scope is what makes projects differ:
- Number of data flows. Order import alone is far smaller than two-way stock, prices, listings, returns and finance sync.
- Number of marketplaces and regions. Each Amazon region is authorized separately, and marketplaces differ in taxes, languages and listing requirements.
- Your ERP or WMS. A well-documented ERP API is quick to work with. A legacy system with file imports or a heavily customized database takes longer.
- Restricted data. If you need buyer names and addresses, for example to ship merchant-fulfilled orders, restricted roles and data protection requirements add work and waiting time.
- Volume. Thousands of SKUs or orders per day push you toward feeds, reports, notifications and careful rate limit design.
- Business rules. Bundles, multi-warehouse stock allocation, B2B pricing and custom invoicing all add logic.
The marketplace ERP integration checklist helps you pin these down before you ask for quotes.
Questions to ask before hiring an SP-API developer
A competent provider will answer these clearly.
- Who owns the code, and where does it live? You want it in a repository you control, or at least a contractual right to receive it.
- Whose developer account and app will be used? For a seller connecting its own systems, the usual setup is a private application under your own developer profile. If the provider proposes its own public app instead, ask whether it is listed in the Selling Partner Appstore, since Amazon requires that of public developers.
- Who holds the credentials? Refresh tokens and client secrets belong in a secrets manager, with access you can revoke. Ask how the 180-day client secret rotation is handled.
- Which roles will you request, and why? Requesting restricted roles you do not need adds review effort and data protection obligations.
- How do you handle rate limits and failures? Listen for queues, retries with backoff and idempotent imports.
- How will we know when something breaks? Ask what is logged, what triggers an alert, who receives it and how fast they respond.
- How do you track Amazon deprecations? Ask for a current example. Two good ones: Orders API v0 is scheduled for removal on March 27, 2027, with v2026-01-01 as the replacement; and the old XML and flat-file listings feeds have already been retired in favor of the Listings Items API and
JSON_LISTINGS_FEED. - What does maintenance cost, and what does it include? Get it in writing before the build starts.
Red flags when choosing an SP-API agency
- They mention MWS or AWS request signing for new work. MWS is gone, and SP-API stopped requiring AWS signing in 2023.
- They plan new work on deprecated formats, such as XML listings feeds or Orders API v0, with no migration plan.
- They ask for your Seller Central password instead of setting up proper API authorization.
- They want to keep the code and credentials with no handover clause.
- There is no answer on monitoring. "We have never had problems" is not a monitoring strategy.
- The quote covers only the build. No mention of maintenance usually means you find out the cost later, during an outage.
- Every problem needs a custom build. If a provider never suggests a connector or plugin, even when one would fit, their advice is not neutral.
What should you prepare before the first call?
A little preparation makes the first call more useful and the estimate more accurate:
- Your systems. ERP, WMS, shop system and accounting software, with versions, and whether each has an API.
- Marketplaces. Which Amazon marketplaces you sell in now and plan to add, and whether you use FBA, FBM or both.
- Flows and direction. Orders, shipping confirmation, stock, prices, listings, returns, settlements: which ones, and which system is the source of truth.
- Volume. Rough orders per day and active SKU count.
- Current pain. What breaks, what is done by hand and how much time it takes.
- Account access. Who is the primary user of your Seller Central account, since that person has to complete developer registration.
- Existing integrations. Anything already connected to Amazon, and who maintains it.
FAQ
How much does Amazon SP-API consulting cost?
It depends on scope: the number of flows, marketplaces, your ERP and whether you need restricted data. Ask for a scoping phase or assessment before a fixed quote, and always ask for the maintenance cost alongside the build.
Should the developer account be in my name or the agency's?
For an integration between your own systems and your own Amazon account, register the developer profile and private app under your own seller account and give the developer the access they need. That way you keep control if you change providers.
Can an SP-API developer fix an existing integration?
Yes, and it is a common request. Start with a review of the current code, credentials setup, error logs and API versions, then decide whether to repair, migrate or rebuild.
How long does it take to hire and onboard an SP-API developer?
Developer registration and role reviews happen on Amazon's side and can take time, especially for restricted roles, so start them early.
Do I still need a developer after go-live?
Someone has to own it. Amazon deprecates versions and formats regularly and requires client secret rotation, so plan for monitoring and maintenance, in-house or on a retainer.
Talk it through with an engineer
Artisan Dojo builds and maintains Amazon SP-API integrations for sellers in Europe and the US, and we will tell you when a connector is the better answer. The first 30-minute call is free. Describe your ERP, your Amazon marketplaces and what is not working below, and we will tell you what we would do.