Articles on: Operations

🔄 Bulk update your Shopify data from Airtable

If you need to edit many records in Airtable at once, the bulk update feature is the best option to update your Shopify data from your Airtable-synced base. It helps you avoid Shopify API limitations when making large changes in bulk. You can access it from the SyncBase app in your Shopify admin.

This feature is available on Elite and Enterprise plans only.

Without this feature: For general bulk operations best practices (batching, rate limits, timing large runs), see our Bulk operations guide.

When to use bulk update

Use this feature when you want to make bulk changes from Airtable and send them back to Shopify. It is especially useful if you want to update a large amount of data more safely and efficiently than editing record by record.

Before you start

Make sure:

Your task queue is down to 0. Check in the SyncBase app: Status > Tasks section. Starting a bulk update with a pending queue can cause conflicts between what's already in flight and what the bulk update is about to push.
You've reviewed the state of your Airtable base. The bulk update pushes the entire current state of your base, not just the fields a script or automation touched — see the warning below.

Steps to bulk update your Shopify data

Open the SyncBase app from your Shopify admin.
Go to the Operations tab.
Find the Bulk update from Airtable section.
Follow the 3 steps shown in the app.

Step 1: Pause synchronization

Pause the instant synchronization between Shopify and Airtable. This lets you edit your Airtable base safely before sending the changes back to Shopify.

Once you pause synchronization via the Bulk Update feature, there is no resume or cancel. Pausing commits you to completing the bulk update.

Step 2: Edit your Airtable base

Make the changes you need directly in your Airtable-synced base, including any automation or script runs. Once your edits are ready, confirm in SyncBase to move to the next step.

We recommend running a small test batch first: update one product and its variants, then check every field in Shopify — including metafields — before pushing your full dataset. This catches formatting issues before they affect hundreds of records.

Step 3: Push to Shopify

Choose which tables you want to push from Airtable to Shopify, then start the bulk update.

⚠️ The bulk update pushes the entire current state of the selected tables, not just the fields your script or automation touched. Any stale or unintended edit sitting in the base will go live in Shopify. Confirm you're happy with the full state of the base before triggering this step.

Wait until the process reports fully finished, and avoid making any other changes in Shopify or Airtable while it runs.

Validate your values before pushing

Shopify silently rejects invalid values sent from SyncBase — the update doesn't error loudly, the field just stays empty. Two common cases to check for:

Reference metafields (e.g. a product_reference type metafield) require the Shopify GID of the referenced entity, not its display name. Passing plain text returns "Value must be a valid product reference" and the field stays empty.
Duplicate handles. Shopify rejects a handle that's already in use. 👉 How to fix duplicate handles in Airtable

Blank cells are not a "no-op." If a cell previously held a value and is now blank at the time of the push, that counts as a change — the bulk update will push the blank to Shopify and clear the existing value.

How the bulk update works

When the bulk update starts, SyncBase temporarily sets your webhooks to inactive. This prevents ongoing synchronization events from interfering with the update.

This process helps protect your updates while the bulk action is running. It makes sure your Airtable changes are pushed first, and that new incoming events are handled afterward.

If new events happen during the process, such as:

a new order
an update made by a colleague
any other incoming change

they are stored in the queue temporarily.

Once the bulk update is complete, SyncBase sets the webhooks back to active and starts processing the queue again.

Webhooks reconnect automatically at the end of the process. Do not reactivate them yourself at any point during the run.

Good to know

"Skipped" in the results summary means no change existed in that cell for that record. It is not an error.
Run a small test batch (one product + variants) before a large push, and verify field by field in Shopify, including metafields.

Need help?

For advanced setups involving reference-GID metafields or metaobject relations, our team can help you validate your data structure before a large push. Chat with us

Updated on: 17/08/2026

Was this article helpful?

Thank you!