Connect Amazon Seller Central to Google Sheets: A Guide

Last verified: May 2026

If you're running an Amazon business and still copy-pasting report data into spreadsheets, you already know the problem. Seller Central holds a huge amount of data — sales figures, inventory levels, fees, refunds, advertising spend — but it's scattered across a dozen report types, locked behind a UI that wasn't built for analysis. Google Sheets, on the other hand, is where most ops and finance teams actually do their thinking.

Getting these two talking properly unlocks real work: building reorder dashboards, tracking ACOS trends, reconciling settlements, forecasting stock before you go out of bounds on FBA. If you're also syncing inventory between Shopify and Amazon FBA, centralising your reporting in Sheets makes cross-channel visibility a lot easier.

This guide covers every viable method — from the humble CSV download to a fully custom SP-API integration — so you can pick the one that actually fits your team's skills and budget.

Before you start

• Active Amazon Seller Central account with a Professional selling plan (Individual plan doesn't expose the full reports suite)
• Google account with access to Google Sheets
• For no-code connector methods: a subscription to a third-party connector service (most require a paid tier for Amazon Seller Central)
• For direct API access: registration as an Amazon SP-API developer — this involves an application process and is not instant

Methods at a glance

Method 1: Manual export from Seller Central

This is the baseline. No third-party tools, no code — just downloading reports and pasting them into Sheets. It's the right starting point if you only need a one-off data pull, or if you're auditing your setup before committing to automation. That said, doing this repeatedly will grind you down. Most sellers spend 2–4 hours a day managing Seller Central reports — time that scales poorly as catalogue complexity grows.

1. Log in to Seller Central and go to Reports in the top navigation bar.
2. Select the report type you need — for example, go to Reports > Inventory Reports and choose your report from the dropdown. For order data, go to Reports > Fulfillment.
3. Click "Request Report" to queue the generation. Depending on report size, this can take a few minutes. When the status changes to "Ready", click Download to save the file as a CSV or TXT to your computer. (This is the standard Seller Central download flow.)
4. Open Google Sheets and create a new spreadsheet (or open an existing one).
5. Go to File > Import, then select Upload and choose the downloaded CSV file from your computer.
6. Set import options: choose "Replace spreadsheet" or "Insert new sheet(s)" depending on your preference, set separator type to "Comma", and click Import data.
7. Verify the data loaded correctly — check that column headers are intact and that numeric fields (units sold, fees, etc.) haven't been formatted as text.

Your Amazon report data is now in Sheets and ready for analysis. The limitation is obvious — this is a snapshot, not a live feed. Every time you want fresh data, you repeat the whole process.

Method 2: No-code connector tools

This is the recommended path for most brands. Tools like Zapier and Make connect Amazon Seller Central to Google Sheets without a single line of code — orders, inventory, refunds, and sales flow automatically on whatever schedule or trigger you configure. Setup takes under an hour. Once it's running, it runs.

The trade-off is cost. You'll need a paid tier on whichever connector you choose, since Amazon Seller Central integrations sit above free plan limits on most platforms. But for a brand doing real volume, the time saved makes that an easy call.

1. Choose a connector tool (Zapier and Make are the most widely supported options for this combination) and sign up or log in.
2. Create a new Zap or Scenario — in Zapier this is "Create Zap", in Make this is "Create a new Scenario".
3. Set Amazon Seller Central as the trigger app. Search for it in the app library and select it. Choose a trigger event — "New Order" or "New Report", depending on what data you need.
4. Connect your Amazon Seller Central account by clicking "Sign in to Amazon Seller Central" and authorising the connection via Amazon's OAuth flow. Grant the requested permissions.
5. Configure the trigger details — select your marketplace (e.g. amazon.co.uk, amazon.de, amazon.com) and any filters you want to apply, such as order status.
6. Add Google Sheets as the action app. Search for "Google Sheets" and select it. Choose an action — "Create Spreadsheet Row" is the standard choice for appending new records.
7. Connect your Google account and authorise Sheets access.
8. Map the data fields: match Amazon output fields (Order ID, ASIN, quantity, revenue, etc.) to the corresponding columns in your target spreadsheet. Add column headers in your Sheet first if you haven't already.
9. Test the integration using your connector tool's built-in test function. Verify that a test record appears correctly in your Sheets tab.
10. Activate the Zap or Scenario and set the sync frequency or confirm the trigger is live.

New Amazon data flows into your spreadsheet automatically on the schedule or trigger you configured — no manual intervention required. If you're building out a broader ops stack, this kind of automation pairs well with work like automating your purchase order workflow.

Method 3: Google Apps Script

Free. No connector subscription. No third-party dependency. That's the pitch for Google Apps Script — a JavaScript-based scripting environment built into Google Workspace that can call external APIs, including Amazon's SP-API, and write the returned data directly into a Sheet.

But you own the code. Which means you're also the one debugging it when Amazon updates an endpoint or your token expires at 3am. We've watched technically capable founders spend a full weekend on a token refresh bug that a connector tool would have handled silently. Worth knowing before you commit.

This method works well for technically comfortable founders who want automation without ongoing connector costs. The Google Sheets API and SP-API combine effectively here, and there are community-maintained script templates that cut the build time considerably.

1. Open your target Google Sheet and go to Extensions > Apps Script to open the script editor.
2. Register as an SP-API developer at developer-docs.amazon.com if you haven't already. Complete the application form — Amazon reviews these manually, so allow a few business days.
3. Create an SP-API application in Seller Central under Apps & Services > Develop Apps. Note your Client ID, Client Secret, and generate a Refresh Token for your selling account.
4. In the Apps Script editor, write an authentication function that exchanges your Refresh Token for an Access Token via Amazon's Login with Amazon (LWA) OAuth endpoint (https://api.amazon.com/auth/o2/token). Store your credentials securely using PropertiesService.getScriptProperties() — do not hardcode them in the script body.
5. Write a function to call the relevant SP-API endpoint — for example, the getOrders endpoint under the Orders API returns order data as JSON. Use UrlFetchApp.fetch() to make the request with your Access Token in the Authorization header.
6. Parse the JSON response and extract the fields you need (e.g. AmazonOrderId, OrderTotal.Amount, PurchaseDate).
7. Write the data to your Sheet using SpreadsheetApp.getActiveSpreadsheet().getSheetByName('Orders').appendRow([...]) — pass your extracted fields as an array.
8. Set up a time-driven trigger in Apps Script under Triggers > Add Trigger. Choose your main function, set event source to "Time-driven", and configure the frequency (e.g. every hour or once daily).
9. Run the script manually once to confirm it executes without errors. Check the Apps Script execution log for any authentication or parsing failures.

Your script pulls fresh data from Seller Central on a schedule and appends it to your Sheet automatically. If anything breaks — token expiry, API version deprecation — you're debugging it yourself.

Method 4: Direct SP-API integration

The Amazon Selling Partner API is a REST-based API that gives you programmatic access to order data, shipment records, payment settlements, inventory positions, and anything else Seller Central tracks. A direct integration — built in Python, Node, or another backend language — gives you the most control and the highest data fidelity. It's also the most work.

This path makes sense if you have in-house engineering resource, need to combine Amazon data with other sources in a custom pipeline, or are building something no connector tool covers. For everyone else, Method 2 gets you 90% of the way there at a fraction of the effort. Honestly, most brands that go down this route do so because it feels like the "proper" solution — not because they actually need the flexibility. Build it when the connector limitations become a real bottleneck, not before.

1. Register as an SP-API developer at developer-docs.amazon.com — complete the questionnaire describing your use case. Amazon's review process is manual.
2. Create a developer application in Seller Central and obtain your Client ID and Client Secret. Generate a Refresh Token by authorising the application against your selling account.
3. Set up your backend environment — Amazon maintains client libraries and code examples for several languages. Install the relevant SDK or construct requests manually using your language's HTTP client.
4. Implement the LWA token exchange: POST to https://api.amazon.com/auth/o2/token with your credentials to receive a short-lived Access Token. Build token refresh logic into your application — Access Tokens expire and must be refreshed automatically.
5. Call the SP-API endpoints relevant to your use case — for example, GET /orders/v0/orders for order data, or the Reports API to request and download pre-built report files.
6. Transform the returned data into the structure you want in Sheets — flatten nested JSON, convert timestamps, normalise currency fields.
7. Write to Google Sheets via the Sheets API — authenticate using a Google Service Account, then use the spreadsheets.values.append method to push rows into your target sheet.
8. Deploy and schedule your integration to run on a cron job or cloud scheduler (Google Cloud Scheduler, AWS EventBridge, etc.) at your desired frequency.

You end up with a fully custom, automated pipeline from Seller Central into Google Sheets — you control the data shape, the refresh frequency, and the error handling logic. That level of ownership is worth the investment if you're building something like the operations stack for a seven-figure brand. Otherwise, see the note above.

Key Amazon reports to sync with Google Sheets

Not all Seller Central reports are equally worth pulling into Sheets. Here are the ones to prioritise:

• Sales and Traffic Report — page views, sessions, conversion rates, and units ordered by ASIN. Essential for performance analysis.
• Inventory Report / FBA Inventory — current stock levels, reserved units, inbound FBA shipments. Pair this with your ASN receiving workflow for a complete picture.
• Orders Report — individual order-level data including order ID, ASIN, quantity, price, and buyer state (useful for regional analysis without exposing PII).
• Settlement Report — what Amazon actually paid you, net of fees, refunds, and FBA charges. This is the source of truth for reconciliation.
• Advertising Reports — Sponsored Products, Sponsored Brands, and Sponsored Display data, if you're running ads. Pull this alongside sales data to track true ACOS.
• Returns Report — return reason codes, units, and refund amounts. Useful context alongside your returns strategy if you run both channels.

Seller Central silos its data aggressively. There's no single report that combines sales, inventory, fees, and advertising — Amazon has no incentive to make that easy for you. That's the whole reason pulling everything into Sheets, where you can join tables and build your own views, is worth the setup effort in the first place.

Common errors and how to fix them

SP-API registration takes too long or gets rejected

Amazon reviews SP-API developer applications manually, and vague use-case descriptions are the most common rejection reason. Be specific: describe exactly what data you'll access, why, and what you'll do with it. Answers like "analytics" get flagged. If you only need report data and not real-time order access, say so — it often speeds up approval.

CSV imports break column formatting in Sheets

Amazon exports use tab-delimited TXT files for some reports and comma-delimited CSVs for others. If your import looks garbled, check the delimiter setting — change it from "Comma" to "Tab" for TXT files. Also watch for currency fields that import as text (you'll see a leading apostrophe in the cell). Use VALUE() or find-and-replace to fix these before building formulas on top.

No-code connector isn't syncing historical data

Most connector tools are trigger-based, meaning they capture new events going forward from setup — they don't back-fill history automatically. If you need historical data, do a one-time manual export for that period, import it into your Sheet, and let the connector handle everything from the go-live date onward.

Apps Script Access Token keeps expiring

SP-API Access Tokens are short-lived by design. If your Apps Script function errors out with a 401, your token refresh logic isn't firing correctly. Make sure your script calls the LWA token endpoint at the start of every execution rather than caching the token across runs. Storing the Refresh Token in ScriptProperties and fetching a fresh Access Token each time is the reliable pattern.

Data across reports doesn't reconcile

This is a known frustration with Seller Central. Order data in the Orders Report doesn't always match what appears in the Settlement Report because of timing — orders settle days or weeks after they're placed. Build your Sheets model to treat these as separate data sets joined by order ID, not interchangeable row counts. That's especially important for financial reconciliation work.

Frequently asked questions

How do I export Amazon seller data to a spreadsheet?

Go to Reports in Seller Central, select the report type you need, click "Request Report", and download it as a CSV or TXT file once it's ready. Then import the file into Google Sheets via File > Import. This works for any report type including orders, inventory, and settlements.

Can you automate Amazon Seller Central reports?

Yes — Amazon supports report automation either through a third-party application or directly via the SP-API. No-code tools like Zapier and Make handle this without custom development, while the SP-API gives you full programmatic control if you have engineering resource.

How do I connect Amazon API to Google Sheets?

The most practical route is a no-code connector tool that supports both Amazon Seller Central and Google Sheets — this sidesteps the SP-API developer registration process entirely. If you want a direct API connection, you can use Google Apps Script to call the SP-API and write results into Sheets using the Sheets API. Both approaches are covered in full above.

What is the best way to track Amazon sales in Google Sheets?

Set up a no-code connector to sync your Orders Report and Sales and Traffic Report into a dedicated Sheet on a daily schedule — this gives you a rolling sales log with zero manual effort. Add a second tab pulling in your Settlement Report for revenue reconciliation. From there, build a summary dashboard using SUMIF and pivot tables to slice by ASIN, date, and marketplace. If you also sell on Shopify, the same principle applies — see our guide to syncing Shopify orders to Google Sheets for a parallel setup.

Choosing the right method

Need a one-time data pull for analysis? The manual export does it in under ten minutes. Want automated, ongoing syncing without writing code? A no-code connector is the right default. Technically comfortable and want to avoid recurring connector costs? Apps Script is a solid middle ground — provided you're prepared to maintain it when something breaks. Have engineering resource and genuinely complex integration requirements? The SP-API build earns its setup cost.

Whatever you choose: start with the two reports that actually drive decisions for your Amazon business specifically — almost always the Orders Report and the FBA Inventory Report. Get those flowing into Sheets, validate that the numbers match what you see in Seller Central, and only then layer in settlements and advertising. A working simple setup beats a broken comprehensive one every time.