Where Shopify work gets difficult
The storefront is the easy part and has been for years. Difficulty concentrates in a handful of places, and they are the same places on almost every enterprise account.
- Inventory across multiple locations, 3PLs and marketplaces, where Shopify is one opinion among several
- B2B pricing and account hierarchies that exceed what native catalogs and price lists express cleanly
- Subscription and recurring order logic interacting with fulfillment and returns
- Catalogs large enough that bulk operations and API cost budgeting become architectural concerns
- App accumulation, where a dozen apps each hold a piece of business logic nobody has documented
- Checkout extensibility limits, particularly after migrating off legacy customizations
Integration is the majority of the work
In practice most of our Shopify engagements are integration engagements. The platform is healthy; what is unhealthy is the boundary between it and ERP, PIM, CRM, OMS or the warehouse.
We build against the Admin GraphQL API with bulk operations for large reads and writes, webhook handling with idempotency and replay tolerance, and Shopify Flow or external orchestration depending on whether the logic needs to be auditable.
Migration, and when to refuse one
We migrate onto Shopify Plus from Adobe Commerce, legacy Magento, custom platforms and older Shopify accounts carrying a decade of accumulated customization.
We also talk clients out of migrations. If the pain is inventory accuracy, product data or order routing, replatforming moves that pain rather than resolving it, at considerable expense and with a launch risk attached.
App strategy and technical debt
Every app is a dependency with its own data model, update cadence and failure behaviour. A store running thirty of them has thirty vendors' roadmaps embedded in its operations.
We audit what each app actually does, what would break if it were removed, and which ones hold business logic that belongs in a system you control. Reducing app count is frequently the highest-return work available on a mature Plus store.
Common questions
- When is Shopify Plus outgrown?
- Rarely because of traffic. The constraints that actually bite are checkout logic that cannot be expressed within the platform's extensibility model, B2B pricing rules deeper than the native catalog supports, and API rate limits under bulk operations against very large catalogs. Each has a workaround before it has a replatform.
- Headless or a standard theme?
- Headless buys presentation freedom and costs you the platform's built-in behaviour, which then has to be rebuilt and maintained. It is justified by genuine multi-experience requirements or a design system shared across properties. It is not justified by page speed alone, which is usually cheaper to fix in the theme.
- How do Shopify API rate limits affect integrations?
- The Admin GraphQL API is governed by a calculated cost budget that refills over time rather than a simple request count, so a small number of expensive queries can throttle you as hard as a flood of cheap ones. Bulk operations exist for large reads and writes, and any integration touching a large catalog should use them rather than paginating in a loop.