Shopify Laravel Package

Product Decisions This Supports

• Platform upgrade and roadmap planning: v8.0.0 is now shipped as a major release from v7.13.1 and swaps the underlying SDK to shopify/shopify-app-php. Treat this as a breaking-change event affecting upgrade timing, engineering capacity, and QA scope; schedule it explicitly rather than allowing a routine dependency bump.
• Build vs. buy: This package remains a viable “buy/leverage” option for teams on Statamic that need Shopify connectivity without maintaining a custom integration. The SDK migration improves long-term alignment with Shopify’s official PHP ecosystem, but it carries a one-time migration cost that should be weighed against maintaining bespoke SDK glue.
• Feature and integration risk assessment: The release notes list a single change — the underlying library swap (PR #358). That narrows the anticipated blast radius to the SDK integration layer, but PMs should still ask engineering to validate authentication, webhook handling, API versioning, product/order sync, and any custom code extending the package before committing to v8 in production.
• Release sequencing: If Shopify integration is critical to storefront or operational workflows, plan the upgrade as a contained technical initiative (upgrade from v7.13.1, regression-test, then release) rather than bundling it with unrelated feature work.

When to Consider This Package

• Consider it when your stack is Statamic + Laravel/PHP and you need a maintained bridge to Shopify rather than a fully custom integration.
• Adopt v8.0.0 only after confirming your team can absorb a major-version upgrade and has tested the new shopify/shopify-app-php-based behavior in staging.
• Look elsewhere or defer if you need a completely stable, no-migration release, if your integration relies heavily on undocumented internals of the previous SDK, or if you cannot allocate QA time for auth, webhook, and API compatibility checks.
• For greenfield projects, v8 may be a reasonable starting point, but still verify package maturity, documentation, and community support for the new SDK foundation.

How to Pitch It (Stakeholders)

Executive summary: The Shopify integration package has shipped v8.0.0, a major release that replaces its underlying Shopify PHP SDK with shopify/shopify-app-php. This is not a routine patch: it is a breaking-change upgrade that should be planned and tested before rollout. The scope is contained — the release consists of the SDK swap itself — but everything that touches the SDK (auth, webhooks, API calls, sync workflows) must be regression-tested. The strategic value is continued alignment with Shopify’s official PHP tooling and reduced long-term maintenance burden versus a custom integration. The near-term cost is engineering and QA time to migrate safely from v7.13.1. Recommend treating v8.0.0 as a scheduled technical upgrade, not an automatic dependency bump, and gating production adoption on staging validation of authentication, webhooks, and core sync workflows.