Can you run multichannel stock and prices from Airtable?

Why sellers try Airtable first

Airtable looks like a spreadsheet but works like a database. You can link a product table to a supplier table, filter by channel, and give a teammate a clean form to fill in. Many sellers start in a spreadsheet, hit its limits, and try Airtable as the next step. If you are weighing it against other tools, my Airtable alternatives guide covers the field.

The goal is simple: one row per product or variant, one column per price and stock level, and every channel reads from that row. The hard part is getting the numbers out of Airtable and into Shopify, Amazon (a large online marketplace) and Etsy (a marketplace for handmade, vintage and craft goods) without a person copying them over.

The four setups brands try

1. The CSV round trip

You export your products from Shopify as a CSV file (a plain text table), paste the rows into Airtable, edit prices there, export again and re-import into Shopify. It needs no code and costs nothing extra. Shopify says the product CSV cannot exceed 15 MB, an import cannot be cancelled once it starts, and there is no history of past imports. It also warns that a column left blank in your file overwrites the matching value in your store as blank. That is the main danger of this setup. If you want the full steps, read my guide to bulk price updates in Shopify.

2. Airtable as the master, a script as the pusher

A small script or an automation reads changed rows in Airtable and calls the Shopify Admin API, the programming interface Shopify offers for changing store data. This is the setup most people mean when they say "Airtable and Shopify integration". It is real and it works. It also needs someone who can write and maintain the script.

3. A no-code connector

Tools such as Zapier, a service that links apps with simple "when this happens, do that" rules, can watch Airtable and update Shopify. Fine for a few changes a day. For hundreds of changes, check how the tool counts and charges for each one, and how fast it runs, before you rely on it.

4. Airtable as a reporting copy only

Shopify stays the master. Orders and stock levels flow into Airtable so you can sort and report. This is the safest use, because a mistake in Airtable cannot change a live price.

The limits that matter

These are the numbers I check before I let anyone build on Airtable. All prices are as of November 2026, in US dollars.

Limit	Free	Team	Business
Price per collaborator, billed annually	$0	$20 ($24 monthly)	$45 ($54 monthly)
Records per base	1,000	50,000	125,000
API calls per workspace per month	1,000	100,000	Unlimited
Automation runs per workspace per month	100	25,000	100,000

On top of that, Airtable's API allows 5 requests per second per base. Go over it and you get a 429 error (the code for "too many requests") and must wait 30 seconds before calls succeed again. A "base" is one Airtable database file.

Shopify has limits too. Its APIs use a leaky bucket, which means each request adds to a bucket that drains slowly, and a full bucket gives you a throttle error. Shopify recommends backing off for about one second before you retry. Any input list is capped at 250 items. And once a store has 500,000 variants, no more than 10,000 new variants can be created per day unless the store is on Shopify Plus.

A worked example (made-up figures)

Say a seller has 8,000 variants on Shopify and Amazon. A script checks stock every hour and writes one Airtable call per variant. That is 8,000 calls an hour, or about 5.76 million calls in 30 days. The Team plan allows 100,000 a month. Even if you batch rows together, check how Airtable counts a batched call before you plan around it. And 8,000 calls at 5 per second takes about 27 minutes, so the "hourly" sync is already running nearly half the time.

Records are the other squeeze. Eight thousand variants across three channels, plus orders and suppliers, will pass 50,000 records faster than most people expect.

Where it breaks for Amazon and Etsy

Shopify's own app for selling on other marketplaces is Shopify Marketplace Connect (formerly called Codisto). It syncs listings, orders and stock between Shopify and Amazon, eBay, Walmart and Target Plus (Walmart and Target Plus are United States only, per Shopify's help page). Shopify's help pages say new connections to Etsy cannot be made with that app at this time. Stores already connected can keep using it. So a new Etsy seller cannot lean on that route and needs another path.

That matters because Airtable cannot write to Amazon or Etsy by itself. You need a second script for each channel, each with its own limits and sign-in rules. Now you have three syncs to keep alive, and any one of them can quietly fall behind.

The deeper issue is stock. Airtable is not built to subtract one unit safely when two orders arrive at the same second. A stock number that two systems both write to will drift. If you already feel that drift, my guide to running multichannel stock from a spreadsheet shows the same failure from the spreadsheet side.

When to move to a proper app

• You oversell more than once a month.
• Your sync script needs fixing more than once a quarter.
• You have passed roughly 30,000 records, or the monthly API calls are close to your plan.
• More than two people edit stock, or you need to see who changed what.
• You sell on a channel that no ready-made connector supports.

A ready-made tool is the first thing to check, such as the options in my multichannel inventory software guide. If your process is unusual, a small app built on your own rules is the next step, and my guide on turning a spreadsheet into a web app explains how that move works. For the wider picture of what a stock system should do, read the inventory management system guide.

How I'd approach this

I would not rip Airtable out. I would use it for what it does well: a clean product catalog, supplier details, and reporting. Then I would keep live stock out of it. Stock changes should live in one place that every channel reads, and that place should handle two orders landing together.

If you are under about 2,000 variants and change prices a few times a month, the CSV round trip is fine. Back up your store first and always import a small test file. Above that, or the moment you sell on Amazon and Etsy as well, I would build a thin sync layer with a queue, retries and an alert when anything fails. That layer is a small piece of software, not a big project, and it is usually cheaper than one weekend of oversold orders.