Executive summary
- What: Bulk queries and bulk mutations on the GraphQL Admin API now require an explicit per-app permission that partners grant in the Partner Dashboard.
- Why: An app that starts a bulk operation without that permission receives an access denied error, on every Admin API version, with no deprecation runway.
- Who: Public and custom apps built by partners, which covers most of the ERP, OMS and PIM middleware that moves catalog and order data at volume.
What changed
Shopify has split bulk operation access into two separate permissions. Running bulkOperationRunQuery requires bulk query access. Running bulkOperationRunMutation requires bulk mutation access. A partner grants each one under API access requests on the app's page in the Partner Dashboard. The change took effect on November 6, 2026 and applies to every version of the GraphQL Admin API, so pinning an older version buys you nothing.
Shopify pre-enabled access for apps with recent bulk activity, so most live integrations kept working on day one. The detail that deserves attention is the lapse rule. An app that has not started a bulk query or bulk mutation in the previous 31 days loses access to that operation type and has to request it again. Apps that merchants create themselves in the Shopify admin or the Dev Dashboard are exempt for now. No app config change, version release or merchant reinstall is required.
Why it matters
Bulk operations are how real data volume moves between Shopify and the systems of record in ERP integration work. A full catalog export, a nightly inventory reconciliation, a price list rebuild across company locations: these run as bulk jobs because paginated queries cannot finish inside a sane window.
The 31-day lapse rule is the part that will bite enterprise merchants. Quarterly price reviews, annual catalog refreshes and disaster recovery scripts are all plausible candidates to sit dormant for a month and then fail on the next run. Nothing here requires a merchant action in the admin, which is exactly why it is easy to miss. The failure surfaces as an access denied error inside a partner's scheduled job, and scheduled jobs are the code nobody watches until the data stops arriving.
Role-specific impact
- Marketers: Little direct impact. Expect delays on bulk catalog or segment work if an export feeding a campaign feed lapses and needs re-enabling.
- Developers: Confirm both permissions on every partner-built app you maintain, then handle the access denied response so a lapse fails loudly instead of quietly.
- Store admins: Ask each integration vendor to confirm bulk query and bulk mutation access in writing before peak trading, and treat an unexplained gap in synced data as a candidate symptom.
Use-case example
Real-world scenario
A distributor runs a nightly ERP to Shopify inventory sync through a partner-built connector, plus a bulk mutation job that rewrites B2B price lists after each quarterly cost review. The nightly job keeps its bulk query access because it runs daily. The price list job last ran 40 days ago, so its bulk mutation access has lapsed. The next quarterly run fails with access denied, and roughly 11,000 price list entries sit at last quarter's cost for three days until someone notices margin erosion on wholesale orders. Re-enabling access takes two clicks. Finding the cause took most of a week.
Implementation checklist
- List every app on the store that was built by a partner, including custom apps your agency or integrator maintains.
- For each one, open the Partner Dashboard, select the app, and check API access requests for the Run bulk operations section.
- Enable Allow bulk queries, Allow bulk mutations, or both, matching what the app actually runs.
- Inventory your scheduled bulk jobs and flag any that run less often than monthly, since those are the lapse candidates.
- Add alerting on the access denied response for bulk operations so a failure pages someone rather than going to a log.
- For low-frequency jobs, either re-enable access as a pre-run step or schedule a lightweight monthly bulk query to keep access active.
- Record the review in your integration runbook with a recheck date set before your next peak event.
FAQ
Q: Does this affect custom apps our own team created in the Shopify admin?
A: No. Apps created by merchants in the Shopify admin or the Dev Dashboard are out of scope at this time. The requirement covers public and custom apps built by a partner.
Q: Can we avoid this by pinning an older Admin API version?
A: No. The gate applies to all GraphQL Admin API versions. Worth noting separately: from version 2026-01 an app can run up to five concurrent bulk queries per shop, against one per operation type on earlier versions.
Resources
Enabling access to bulk operations
Need guidance? Talk to Makro.