Amazon Seller Central automation with the SP-API: reports, inventory, listings and orders

Most Amazon sellers repeat the same jobs in Seller Central every week. They download the same reports, paste them into a spreadsheet, check which SKUs are running low, fix a batch of listings and copy orders into the accounting system. Amazon Seller Central automation hands those jobs to software that talks to Amazon through its official Selling Partner API (SP-API), so they run on time without anyone logging in.

This guide is for sellers and small brands who are tired of manual exports, or who pay for several tools that each do one small thing. I build automation for Amazon Seller Central covering listings, inventory, orders and reports. Below I go through what the SP-API can do in each area, what Amazon's own tools now handle for free, and where a private tool of your own still makes sense.

What Amazon Seller Central automation covers

The SP-API is Amazon's official way for software to read and change a seller account. It is split into separate APIs, and four areas cover most of what sellers want automated:

Job	SP-API pieces	Typical automation
Reports	Reports API, Data Kiosk	Daily sales per SKU in a sheet or database
Inventory	FBA Inventory API, notifications	Low-stock alerts, stock pushed to other channels
Listings	Listings Items API, JSON listings feed	Bulk price, title or attribute changes
Orders	Orders API, notifications	Orders into accounting, a 3PL or a dashboard

There are more, such as Finances, Product Fees and Fulfillment Outbound, but a first tool almost always starts with one row of that table.

A private SP-API app: no developer fees for your own business

You do not need to become a software vendor to automate your own account. Amazon's registration overview describes three types of application. A private seller application is self-authorised and limited to your own organisation. It needs a Professional selling account, and the primary account user completes the registration. Public apps are listed in the Selling Partner Appstore and authorised by other sellers through OAuth, and they go through more review.

The fee question is settled for now. In November 2025 Amazon announced a yearly subscription and charges on API calls for third-party developers. Sellers building tools only for their own business were exempt from the start. Amazon then dropped the plan, saying it "will not move forward with the SP-API usage and annual fees at this time" (PPC Land dates this to May 2026). "At this time" leaves room for a future model, but today a private tool for your own account carries no Amazon developer fee. The cost of a custom Amazon seller tool is in building and hosting it, not in access.

How to automate Amazon reports

Reports are where most sellers start. The question comes up again and again on the Seller Forums: how do I get the same report every morning without clicking download?

The Reports API works in three steps:

1. Your tool asks Amazon to create a report, or sets up a schedule so Amazon creates it at regular intervals.
2. Amazon processes it. Rather than checking every few minutes, the tool can subscribe to the REPORT_PROCESSING_FINISHED notification.
3. The tool downloads the finished document, parses it and writes the rows somewhere useful.

The value is in where the data lands: a Google Sheet your team already uses, a small database behind a profit dashboard, or a morning email with yesterday's sales per SKU. For sales and traffic figures, Amazon's Data Kiosk takes a GraphQL query and returns only the fields you ask for.

Store the raw file alongside the parsed rows, so you can reprocess history when a calculation changes, and write the parser to tolerate new columns, because Amazon says it adds fields to reports from time to time.

Amazon inventory automation

FBA stock moves all day. The FBA_INVENTORY_AVAILABILITY_CHANGES notification tells your tool when quantities change and includes a snapshot for each store. That makes three automations straightforward:

• Low-stock alerts by SKU, based on days of cover rather than a fixed number, sent by email, Slack or WhatsApp.
• Stock pushed to other channels, so a Shopify or Etsy listing stops selling units that are already gone. I cover this properly in how to stop overselling across channels.
• A weekly restock view that combines Amazon's figures with stock already on order from your supplier.

Amazon's own Restock Inventory tool already recommends quantities from sales history and seasonality, so do not rebuild it. A custom tool earns its place by adding what Amazon cannot see: supplier lead times, stock in your own warehouse, sales on other channels.

The Amazon listings API: bulk changes without spreadsheets

Since 31 July 2025 the Feeds API no longer accepts the old XML and flat-file listings feeds. Integrations now use the Listings Items API for individual changes or the JSON_LISTINGS_FEED for bulk work (Amazon's migration guide). Spreadsheet uploads inside Seller Central are unaffected. Any tool built on the old feeds had to be rewritten.

The JSON route is stricter, which suits automation. The Product Type Definitions API tells your tool which attributes each product type requires, so it can check a change before sending it instead of finding out from an error report the next day. Typical listing jobs are:

• updating prices, handling times or bullet points across hundreds of SKUs from one master sheet;
• creating new variations from a template;
• watching the LISTINGS_ITEM_ISSUES_CHANGE notification so a suppressed listing is flagged within the hour, not whenever someone next looks.

If AI writes listing drafts for you, a person should still approve each one before it is published.

Orders: from Seller Central into the rest of the business

The Orders API (the current version is 2026-01-01) and the ORDER_CHANGE notification let a tool pick up new and changed orders as they happen. The order automations sellers ask for most are:

• orders and fees pushed into accounting software, so month-end does not start with a CSV;
• merchant-fulfilled orders sent to a 3PL or warehouse system;
• a daily summary of orders, refunds and cancellations for the team.

Buyer names and addresses are restricted data: reading them needs extra roles that Amazon reviews and a short-lived Restricted Data Token. If your automation can work without personal data, design it that way.

What Amazon's own tools do now, and where a custom tool starts

In September 2026 Amazon gave Seller Assistant persistent memory and always-on workflows. These watch conditions such as pricing trends, restocking and account health. You choose whether they only make recommendations or also act, and every action is logged. A new Selling Partner plugin connects your Amazon data to Amazon Quick and, in a US beta, to Claude. Seller Central is also gaining tools for managing eBay, Shopify, TikTok Shop and Walmart from inside it, rolling out in the US.

So before paying for anything custom, check whether Seller Assistant already does the job. A custom tool still makes sense when:

• the data has to leave Amazon, for example into accounting, a warehouse system or a sheet your team works from;
• the rules are specific to your business, such as margin after your own landed costs;
• a channel Amazon's tools do not cover is involved, such as Etsy;
• you want the history in your own database, not only inside Seller Central.

I compare the two in more depth in Amazon Seller Assistant vs custom tools.

A checklist for building a custom Amazon seller tool

Whoever builds it, a good SP-API tool:

• Prefers notifications to polling. It reacts to events where Amazon offers them and polls only where it must.
• Respects rate limits. Usage plans are set per operation, for each seller and app, using a token bucket. Going over returns HTTP 429. The tool should back off and retry, never fire hundreds of calls at once.
• Makes every write safe to repeat. If a job runs twice, it must not apply a price change twice or send an order twice.
• Logs what it did and why, so you can answer "who changed this listing?" in seconds.
• Has an off switch. Since 4 March 2026, Amazon's Agent Policy has required automated tools to identify themselves and stop when Amazon asks. My guide to the Amazon Agent Policy covers this step by step.
• Stays in your name. The app is registered in your Seller Central account, and the credentials and code belong to you.

What it costs: build or buy

Off-the-shelf software is the right answer for many sellers. Custom Amazon Seller Central automation pays off when you pay for several single-purpose tools, or when no tool fits how your business actually runs.

My published starting price for marketplace automation is from $2,500 for an MVP. That covers one marketplace connected through its official API and one automation, such as a daily report export, listing updates or order export. Connecting two or more channels, with stock and orders kept in sync and a dashboard, starts from $5,500. These are starting prices. Every project gets a fixed quote after a short brief, payment is in milestones you can open and try, and you own the code. More on my Seller Central automation work.

FAQ

Do I have to pay Amazon to use the SP-API for my own store?

No. Amazon announced developer fees in November 2025 and then cancelled them, saying it would not move forward with them "at this time". Even under that plan, sellers building tools only for their own business were exempt. You still need a Professional selling account to register a private app. Hosting, building and maintaining the tool are your only costs, and Amazon could introduce a fee model again in future, so it is worth checking before you start.

Can I automate Seller Central with a browser extension or script instead?

You can, but it is the riskiest route. Scripts that click through Seller Central break whenever Amazon changes a page, and Amazon's Agent Policy, in force since March 2026, requires automated tools to identify themselves and stop when asked. A script that imitates a person does neither. The SP-API is built for automation, has published rate limits and names your app in every request, so it is the durable choice.

What happens to a custom tool when Amazon changes the API?

Amazon versions its APIs and announces deprecations in advance, as it did before the XML and flat-file listings feeds ended in July 2025. A well-built tool keeps each Amazon API behind its own small module, so an update means changing one part rather than rewriting everything. Budget for occasional maintenance, and keep the code, credentials and handover notes in your name so any developer can pick it up.

If you want a Seller Central job off your plate, send me a short brief: which reports, listings or orders you handle by hand today, where the data needs to end up, and which channels you sell on besides Amazon. You can read more about my Amazon automation service, or start with the wider picture in e-commerce automation: what to automate first.