Shopify raises EventBridge payloads to 1 MB
Shopify now delivers webhook and Events payloads of up to 1,000,000 bytes inline through Amazon EventBridge, up from 256 KB. The 17 November changelog says the change applies automatically across API…
Shopify now delivers webhook and Events payloads of up to 1,000,000 bytes inline through Amazon EventBridge, up from 256 KB. The 17 November changelog says the change applies automatically across API versions, without replacing existing subscriptions.
What changes for large resources
Previously, an oversized classic webhook could contain only a resource ID, requiring a follow-up fetch. An oversized Events delivery could provide a temporary payload download URL. More product and order data can now arrive directly in the event.
The new limit is 1,000,000 bytes, leaving space for the EventBridge envelope beneath its 1 MiB entry cap. Larger deliveries retain the existing fallback: an ID-only classic webhook or an Events stub containing payload_url, payload_size_bytes and expires_at.
Keep the overflow path
Shopify advises keeping fallback handling and checking the quotas of downstream AWS targets. Payload selection can still be narrowed where appropriate.
Our recommendation is to test three cases: an ordinary delivery, a resource larger than the old threshold but within the new one, and a resource that still exceeds the new limit. Confirm that each reaches the intended handler and produces the same business result.
Review any assumptions in logging, queues and resource-fetch code as well as the subscription itself. Automatic platform rollout does not mean every downstream component has been tested with a larger message.
For merchants, this is principally an integration-maintenance question for the app or engineering team. Ask whether their order or catalogue pipeline handles both inline and overflow deliveries; there is no merchant-side switch to enable in this announcement.
More from Shopify
See all →
Before Black Friday, test what a Shopify webhook retry sends twice

