Automate Amazon Seller Central

What I mean by automating Seller Central

Automating Amazon Seller Central means a bot handles the repetitive seller work in the console. Updating prices and stock from a sheet, pulling orders and settlement reports, checking your listings, downloading the reports buried a few clicks deep. It is the back-office upkeep of a store you run, gathered into one place, so you are not clicking across a dozen screens to see how the business is doing.

The work is scattered across Seller Central

Seller Central is enormous, and that is the problem. Your orders are on one screen, your inventory on another, pricing somewhere else, your reports behind a download, your account health on its own page. Seeing the whole picture means clicking through all of it, every day.

Amazon has the Selling Partner API for the heavy, structured pulls, and if you are big enough it is worth the setup. For everyone else, the day-to-day is still the console. A bot is good at exactly that, opening each screen, reading what is there, and writing it into one sheet, so the scattered pieces of your store finally sit together. API when you outgrow it, the browser until then.

Who this is for

This is for the Amazon seller without a back office of staff. The solo seller or small team updating prices, watching stock, and pulling reports by hand across Seller Central's screens. You manage the account, you just want the busywork gathered up. No-coders and coders both, since you can build it without code and drop into code when you want.

How I'd approach it

Start with the screen you check most, usually orders or inventory. Point the bot at it, read what is there, and write it to a sheet. For updates, put the new prices or stock in a sheet and let the bot apply them listing by listing. Run it on your own account with your own logged-in session, and be careful with anything that changes a price.

One screen, your account, then schedule it. I would lay out the first draft with Build with description.

Automate Seller Central from a description

Describe the task in plain words in the Chrome extension and it builds the steps for you. Give it a few short lines, check what it made, and run it. Explore no-code.

Automate Seller Central in code

Build with code. If you would rather script it yourself, this is the path. Explore code

import { chromium } from "playwright";

const browser = await chromium.connectOverCDP(
  `wss://cdp-lb.axiom.ai/?token=${process.env.AXIOM_API_KEY}`
);

try {
  const context = browser.contexts()[0];
  const page = context.pages()[0] ?? await context.newPage();

  // Your own Seller Central, using your logged-in session
  await page.goto("https://sellercentral.amazon.com/orders-v3");
  await page.waitForSelector(".order-row");

  // Read each order off the table
  const orders = await page.$$eval(".order-row", els =>
    els.map(el => ({
      id:     el.querySelector(".order-id")?.textContent.trim(),
      item:   el.querySelector(".item")?.textContent.trim(),
      status: el.querySelector(".status")?.textContent.trim(),
    }))
  );

  console.log(orders); // write these to your sheet
} finally {
  await browser.close();
}

+

Build with a Claude skill

Build no-code or code bots with a skill.

Add the Claude skill and describe the Seller Central task you need. It builds the bot for you, no-code or code, gathering your screens into a sheet or updating listings.

Install the skillLearn more

What can you automate?

The scattered Seller Central screens, for the store you run. A couple of cases worth knowing first.

What I'd watch out for

Seller Central is a sprawling app behind a login, so a few things trip up a store bot. Here is what I would watch for.

Be careful changing prices

A bad price update across a catalogue is an expensive mistake, and on Amazon it can trigger a race to the bottom. Run one listing first, double-check the number, and cap how much the bot changes in a run.

API for the heavy pulls

For large, structured exports, the Selling Partner API is sturdier than scraping the screen. Use the browser for the day-to-day and the gaps, and reach for the API when volume is the point.

Use your own session

Sign in as yourself on the account you own, and store the cookies so the bot keeps the session rather than logging in fresh each run.

When the layout shifts

Amazon updates the console often, and buttons move. Repick anything that stops being found with the selector tool, and recheck after a big update.