Sync Amazon FBA Inventory to Google Sheets: An Auto-Update Guide

Last verified: June 2026

If you're selling on FBA and tracking inventory in a spreadsheet by hand, you're running on lag. You download a report, paste it in, do your analysis — and by then the numbers have already moved. For a brand doing 50 orders a day, that's an inconvenience. For one doing 500, it's genuinely expensive. Stockouts cost you the sale and the ranking. Overstock costs you monthly storage fees. Neither is recoverable.

Google Sheets remains the default operations tool for most SME e-commerce brands, and there's nothing wrong with that. It's flexible, shareable, and free. The problem isn't the destination — it's the pipeline. Getting fresh FBA inventory data into Sheets automatically, on a schedule, without someone manually running a report at 8am every morning, is what this guide covers.

We'll walk through four methods: the manual export (which you should understand even if you plan to automate), connector tools, Google Apps Script talking directly to the SP-API, and a brief note on purpose-built integrations. If you've already wired up other Amazon data flows — the process for connecting Seller Central to Google Sheets generally is a useful companion read — some of this will feel familiar.

Before you start

• Active Amazon Seller Central account with FBA inventory (Professional selling plan required for SP-API access)
• Google Account with Google Drive access
• Subscription to a third-party connector tool (if using the connector method)
• Google Cloud Platform project with the Sheets API enabled (if using the direct API or Apps Script method)
• SP-API developer registration approved in Seller Central (for the Apps Script / direct API method) — see Amazon's FBA Inventory API reference for scope requirements

Methods at a glance

Method 1: Manual CSV export from Seller Central

This is the baseline. No setup, no credentials, no third-party tools. Also no automation — a human has to do it every single time, which is exactly why most brands outgrow it quickly. That said, it's worth understanding the export even if you plan to automate, because the field names in the CSV are the same ones you'll reference in any downstream formula or script.

1. Open Seller Central and navigate to Reports > Inventory Reports using the top navigation bar.
2. Select "FBA Manage Inventory" (or "All Listings Report" for a broader view) from the report type dropdown.
3. Click "Request Report" and wait — generation typically takes under a minute for catalogues under a few thousand SKUs.
4. Click "Download" once the status shows Ready. Amazon serves a tab-delimited TXT file.
5. Open a new Google Sheet and go to File > Import. Choose the downloaded file and set the separator type to Tab. Leaving it on Auto-detect or Comma is the most common cause of garbled single-column data.
6. Verify key columns are present: asin, fnsku, available, inbound-quantity, reserved-quantity. These map directly to the fields exposed by the SP-API, which matters if you later automate this.
7. Save the sheet and note the timestamp — this data is already stale the moment it lands.

The honest limitation: manual export is fine for a monthly audit or a one-time reconciliation. It's not a workflow. A brand selling 200 units a day cannot run operations on a spreadsheet that was accurate yesterday morning.

Method 2: Connector tool (Hopted, Zapier, or similar)

Connector tools sit between Amazon and Google Sheets, handle the OAuth authentication for you, and let you schedule automatic pulls without writing a line of code. Hopted is purpose-built for Amazon-to-Sheets syncing and can pull the FBA Inventory report on a schedule. Zapier is more general-purpose but covers the same use case via its Amazon Seller Central integration.

The tradeoff is cost — both require a paid tier for automated, recurring syncs — and some vendor dependency. If the connector goes down or changes its pricing, your pipeline breaks. For most non-technical teams, that's still a better bet than maintaining a custom script.

1. Create an account on your chosen connector tool and select the Amazon Seller Central integration from the app directory.
2. Authenticate your Amazon account by following the OAuth flow — you'll be redirected to Seller Central to grant permissions. Use the same account that owns the FBA inventory you want to sync.
3. Select "FBA Inventory Report" (or equivalent) as the data source. In Hopted this is listed explicitly; in Zapier you'll trigger on a schedule and use the "Get Inventory" action.
4. Connect your Google account and select or create a destination spreadsheet. Specify the target sheet tab and the starting cell — typically A1 on a dedicated "FBA Inventory" tab.
5. Configure the sync schedule. For most mid-volume brands, every hour is sufficient. High-velocity sellers running flash sales may want 15-minute pulls, but check whether your connector plan supports that frequency.
6. Run a manual test sync and verify the data lands correctly. Cross-check three or four SKUs against what you see in Seller Central's Manage FBA Inventory screen.
7. Enable the automation and set up a Slack or email alert for sync failures — connector tools can silently fail if the Amazon token expires or your Seller Central permissions change.

Method 3: Google Apps Script and the SP-API

This is the most technically involved method, but also the most transparent and cheapest to run long-term. You write a script inside Google Apps Script (which lives in your Google Sheet), it authenticates against the SP-API FBA Inventory endpoint, pulls available/inbound/reserved quantities, and writes them to your sheet. You then set a time-driven trigger to run it on whatever schedule you want.

One important reality check: Amazon's SP-API doesn't push data — it only responds to requests. So "live" inventory in this context means "pulled every N minutes." For most brands, every 30–60 minutes is live enough.

1. Register as a developer in Seller Central under Apps & Services > Develop Apps. Complete the use case description — for internal inventory tracking, select "Private Seller App." Amazon will review this, which can take a few days.
2. Create an IAM user in AWS with the AmazonSPAPIRolePolicy attached. Note the Access Key ID and Secret Access Key — you'll need these in your script.
3. Generate an LWA (Login with Amazon) client ID and secret from your developer application in Seller Central. These are separate from your AWS credentials and handle the OAuth token exchange.
4. Open your Google Sheet, go to Extensions > Apps Script, and create a new script file.
5. Store your credentials using Apps Script's PropertiesService rather than hardcoding them: PropertiesService.getScriptProperties().setProperty('LWA_CLIENT_ID', 'your-id'). Do the same for the client secret, refresh token, AWS keys, and marketplace ID.
6. Write the token exchange function. Make a POST request to https://api.amazon.com/auth/o2/token with your LWA credentials and refresh token to get a short-lived access token. The SP-API uses AWS Signature Version 4 for request signing — open-source Apps Script implementations of this exist on GitHub and save significant time.
7. Call the FBA Inventory API endpoint: GET https://sellingpartnerapi-na.amazon.com/fba/inventory/v1/summaries (adjust the regional domain for EU: sellingpartnerapi-eu.amazon.com). Pass granularityType=Marketplace, granularityId (your marketplace ID), and details=true to get the full breakdown including fulfillableQuantity, inboundWorkingQuantity, and reservedQuantity.
8. Parse the JSON response and write the results to your sheet. A simple loop over inventorySummaries writing ASIN, FNSKU, condition, and the quantity fields to sequential rows is sufficient for most use cases.
9. Set a time-driven trigger under Triggers in the Apps Script editor. Choose "Time-driven," set to every 30 or 60 minutes depending on your sales velocity.
10. Add error logging — write failed runs to a separate "Errors" tab with a timestamp, so you know when the token has expired or the API has returned a throttling error (HTTP 429).

Method 4: Direct API integration (custom application)

If you're building a proper internal ops tool — or pulling FBA inventory data into a wider system alongside, say, a Dynamics 365 ERP or a custom dashboard — a direct API integration built outside Google's ecosystem may be the right call. The SP-API is the same; the difference is that your application lives on your own infrastructure and writes to Sheets via the Google Sheets API.

1. Enable the Google Sheets API in your Google Cloud Platform project under APIs & Services > Library.
2. Create a service account in GCP and download the JSON key file. Share your target Google Sheet with the service account's email address (with Editor access).
3. Build your SP-API authentication layer using your preferred language — Amazon's SP-API has official SDK support for Python, Java, and C#. Handle LWA token exchange and AWS SigV4 signing as in Method 3, but in your application's language.
4. Call the FBA Inventory API on your chosen schedule using a cron job or a managed scheduler (AWS EventBridge, Google Cloud Scheduler, etc.).
5. Write the inventory data to Sheets using the Google Sheets API's spreadsheets.values.update or batchUpdate method. The Sheets API reference covers authentication, range notation, and value input options in detail.
6. Handle pagination — the FBA Inventory API returns results in pages using a nextToken parameter. If your catalogue has more than a few hundred active ASINs, you'll need to loop through all pages before writing to the sheet.

This is the approach to consider if you're thinking about a full seven-figure operations stack or planning to add purchase order automation downstream — see our guide on automating your e-commerce PO workflow for what that looks like in practice.

Common errors and how to fix them

Google Sheets displays garbled single-column data after import

Amazon's inventory reports download as tab-delimited TXT files, not standard CSVs. When you import via File > Import, you have to set the separator to Tab manually. Leave it on Auto-detect or Comma and the entire row lands in column A. Re-import with the correct delimiter. For very large catalogues (tens of thousands of SKUs), also check that the sheet hasn't hit Google Sheets' row limit — consider splitting by fulfilment centre or product category if needed.

SP-API returns HTTP 401 Unauthorized

LWA access tokens expire after one hour. If your Apps Script trigger runs on a longer interval, or your token exchange function isn't being called before each API request, you'll hit 401s. The fix: always call the token exchange function at the start of your main function. Never cache the access token across script executions.

SP-API returns HTTP 429 Too Many Requests

The FBA Inventory API has rate limits — check the SP-API FBA Inventory reference for the current burst and restore rates for each endpoint. If you're hitting 429s, add exponential backoff with jitter to your retry logic, and avoid running multiple triggers simultaneously.

Connector tool syncs stop silently

OAuth tokens for Amazon Seller Central can expire or be revoked — particularly if you change your Seller Central password or revoke app permissions. Most connector tools won't alert you when this happens. Set up a simple monitoring formula in your sheet that flags when the "last updated" timestamp hasn't changed within your expected sync window. Something like =IF(NOW()-B1>2/24,"SYNC STALE","OK") in a header cell will catch failures visually.

Scraping Seller Central directly doesn't work

Amazon aggressively blocks automated browser access with CAPTCHAs and IP-based rate limiting. Don't attempt it. The SP-API exists specifically to give programmatic access to this data — use it. Any scraping approach is unreliable and against Amazon's terms of service.

Frequently asked questions

How do I automatically export Amazon inventory reports?

You can't fully automate the manual download from Seller Central — it requires human interaction. For true automation, use a connector tool or the SP-API to pull inventory data on a schedule. Both Hopted and Zapier support scheduled Amazon-to-Sheets syncs without manual intervention.

How do I get FBA data into Google Sheets?

There are four routes: manual CSV download and import, a connector tool with a paid subscription, Google Apps Script calling the SP-API directly, or a custom application using both the SP-API and the Google Sheets API. For most teams without developer resource, a connector tool is the fastest path. For full control and no recurring tool cost, Apps Script is the right call.

Can I link Amazon Seller Central to a spreadsheet?

Yes, but not natively — Amazon doesn't offer a direct Sheets integration out of the box. You link them either through a third-party connector tool or by building an SP-API integration yourself. The result is a scheduled pull of your inventory data rather than a true real-time feed, because the SP-API is request-based, not push-based.

What is the best way to track FBA inventory?

For small catalogues and infrequent audits, a manual CSV export into Sheets is fine. For ongoing operations, an automated sync via connector tool or Apps Script is far more reliable — it removes the human step that causes data to go stale. If you're scaling to multiple channels, a dedicated inventory management system will serve you better than any spreadsheet-based approach over the long term. For broader context on where inventory tracking fits in a growing stack, see our guide to building an e-commerce operations stack for EU expansion.

If you're also syncing Shopify data alongside your FBA inventory, the same principles apply — our guide on syncing Shopify orders to Google Sheets covers the equivalent setup on that side. And if your goal is full Amazon-to-accounting reconciliation rather than just inventory visibility, the Seller Central to QuickBooks guide and our piece on reconciling Shopify payouts in Xero are worth reading alongside this one.

Which method should you pick? If you need something working by end of day and don't want to write code, start with a connector tool — setup is under an hour and the maintenance burden is low. If you're comfortable in Apps Script and want to avoid a recurring subscription, Method 3 is more robust long-term. If you're already running a custom ops platform, or plan to — particularly if you're thinking about channel expansion and tools like syncing Shopify inventory back to FBA — Method 4 gives you the cleanest architecture. The manual export is only defensible for one-off audits. Don't build a business process around it.