Platform constraints that shape every Shopify integration
These are not obstacles so much as the physics of the platform. Designing against them at the start is considerably cheaper than discovering them during a peak-season incident.
- Admin GraphQL cost budgeting: query cost, not request count, is what throttles you
- Bulk operations for large reads and writes, rather than paginated loops
- Webhook delivery is at-least-once and unordered, so idempotency is mandatory
- Inventory is per-location, and what you publish should be available-to-promise rather than on-hand
- Metafields and metaobjects carry structured data the core schema does not, and need governance
- Checkout extensibility is bounded, which matters most when migrating off legacy customizations
The integration shapes we build most
Scope usually expands outward from whichever one currently consumes the most manual effort.
- Shopify to ERP: orders, fulfillments, inventory, items and financial reconciliation
- Shopify to accounting: invoices, payouts, fees and tax, reconciled to settlement
- Shopify to PIM: product creation and enrichment flowing into the storefront catalog
- Shopify to CRM and lifecycle: unified customer records with order and subscription context
- Shopify to marketplaces: catalog, pricing and shared inventory pools across channels
- Shopify to 3PL, WMS and carriers: fulfillment requests, tracking and returns
When the app is the problem
A mature Plus store frequently runs dozens of apps, several of which hold business logic nobody documented. Each is a vendor roadmap embedded in your operations, and app-to-app interactions are where the strangest bugs live.
Auditing what each app does, what would break without it, and which ones hold logic that belongs in a system you control is often the highest-return work available before any new integration is built.
Common questions
- What is the difference between a Shopify app and a Shopify integration?
- An app is distributed software installed into your store, usually with its own data model and its own opinion about how a process should work. An integration is a data contract between Shopify and another system you already run. Apps are faster to adopt; integrations are what you own and can change.
- How do Shopify API rate limits affect integrations?
- The Admin GraphQL API uses a calculated cost budget that refills over time rather than a simple request count, so a few expensive queries can throttle you as hard as many cheap ones. Anything touching a large catalog should use bulk operations instead of paginating in a loop.
- Are webhooks reliable enough to build on?
- Yes, provided you assume they will occasionally be delivered twice, out of order, or not at all. That means idempotency keys, a reconciliation job that catches what was missed, and never treating a webhook as the only path for a business-critical record.