See all services → Shopify Plus Partner
API Developer

Enable bulk operations access before your sync jobs fail

Apps now need explicit access before running bulk queries or mutations on the GraphQL Admin API. Access is granted per operation type in the Partner Dashboard, and apps that go 31 days without using one lose access to it.

Executive summary

What changed

Bulk queries and bulk mutations are now gated independently. Running bulkOperationRunQuery requires bulk query access, and bulkOperationRunMutation requires bulk mutation access. Holding one does not imply the other, which is the detail most teams will trip over, since plenty of integrations read in bulk and write individually or the reverse.

Shopify has already enabled access for apps that currently run bulk operations, and you can confirm that in the Partner Dashboard. No configuration change, app version release, or merchant reinstall is needed, and access applies across every store with your app installed. The requirement covers all Admin API versions, so pinning to an older version is not an escape route.

The clause worth writing down is the lapse rule. An app that has not run a bulk query or bulk mutation in the last 31 days loses access to that operation type and has to enable it again.

Why it matters

For most teams the grandfathering means nothing breaks today. The risk is the 31 day window, because it is shorter than several patterns that are completely normal in enterprise integration work. A quarterly catalogue reload, an annual price list rebuild, a seasonal inventory reconciliation, or a bulk mutation path that only runs during a migration or a disaster recovery replay will all sit idle past 31 days and then fail at exactly the moment someone needs them.

That failure mode is unpleasant because it is silent until invoked and it looks like an authentication problem rather than a permissions one. Bulk operations are also how most middleware moves volume between Shopify and an ERP or OMS, so the blast radius is order and inventory sync rather than a cosmetic feature. If you run integrations of this shape, it is worth confirming how your middleware layer handles bulk access and whether it would surface a denial clearly.

Role-specific impact

Use-case example

Real-world scenario

A merchant on Plus runs a nightly bulk query to pull orders into an ERP, and a bulk mutation that rewrites contextual pricing when the annual price list changes. The nightly query keeps its access indefinitely because it runs daily. The pricing mutation runs roughly twice a year, so by the time the January rebuild is attempted it will have been dormant for months and will return access denied against about 42,000 variant updates. Catching that during a scheduled dry run costs ten minutes in the Partner Dashboard. Catching it on the night of the price change costs a launch window.

Implementation checklist

  1. In the Partner Dashboard, open Apps, select your app, then API access requests.
  2. Under Run bulk operations, confirm or request Allow bulk queries, Allow bulk mutations, or both.
  3. Audit your codebase for every bulkOperationRunQuery and bulkOperationRunMutation call site.
  4. Document which of those paths run less often than monthly, since those are the ones at risk of lapsing.
  5. Add a scheduled low cost bulk call, or a dry run, to keep infrequent operation types active.
  6. Make access denied a distinct alert in your error handling rather than folding it into generic retry logic.

FAQ

Q: Do we need to ship a new app version or ask merchants to reinstall?

A: No. Access is granted in the Partner Dashboard and applies to every store where your app is installed, with no configuration change or reinstall required.

Q: Can we avoid this by staying on an older Admin API version?

A: No. The requirement applies to all GraphQL Admin API versions, so version pinning does not defer it. Merchant created apps from the admin or Dev Dashboard are out of scope at this time, but that is stated as current rather than permanent.

Resources

Enabling access to bulk operations

Need guidance? Talk to Makro.