Weave Code
Shopify Laravel Package
statamic-rad-pack/shopify
Statamic addon that connects your Shopify store, imports products as Statamic entries, and keeps catalog data in sync so you can build fast, editable storefronts with Laravel and Statamic.
Integrate your Shopify products into Statamic using the Admin API.
Frequently asked questions about Shopify
- How do I install and configure statamic-rad-pack/shopify?
- Install it with Composer using composer require statamic-rad-pack/shopify, then publish the package config file and add your Shopify Storefront API credentials. After credentials are in place you can import products as Statamic entries and start rendering listings and detail pages in Antlers. Confirm the PHP, Laravel, and Statamic version constraints in the package's composer.json before installing, since the v8 release pulls in the official shopify/shopify-app-php SDK.
- Which Laravel, Statamic, and PHP versions does statamic-rad-pack/shopify support?
- The addon targets Statamic 4/5 on Laravel 10/11, and v8.0.0 likely requires PHP 8.2 or newer because of the official Shopify SDK dependency. Because that SDK carries its own PHP and Guzzle/PSR constraints, always check the exact version matrix in composer.json rather than assuming. If your app is pinned to an older Guzzle version elsewhere, test Composer resolution in a branch first, as a PHP floor bump can cascade into infrastructure changes.
- How do I query Shopify products, collections, and variants in Antlers?
- The addon exposes Antlers tags that query the Shopify Storefront API directly, so you can loop products and collections and pull variant data such as pricing and availability into your templates. You can use these tags to build product listing pages and detail pages without writing custom GraphQL calls. Commerce data from Shopify can be blended with Statamic-managed content fields in the same template, which is the core pattern for a hybrid or headless storefront.
- What is the difference between Storefront API queries and importing products as Statamic entries?
- Storefront API queries fetch live Shopify data at render time, so inventory, pricing, and checkout stay authoritative in Shopify. Importing products as entries copies catalog data into Statamic, where editors can enrich it with local content and you can query it like any other entry. Most headless builds combine both: entries for editable marketing content and Storefront API calls for anything that must stay in sync with Shopify.
- How do I upgrade statamic-rad-pack/shopify from v7 to v8 safely?
- Treat v8 as a planned upgrade rather than a patch, because it replaces the underlying Shopify client with the official shopify/shopify-app-php package. Branch, pin statamic-rad-pack/shopify to 8.0.0 in staging against a non-production Shopify store, and run composer update statamic-rad-pack/shopify --with-dependencies while reviewing the full dependency diff. Republish and diff the config file against your v7 config, then exercise app install, product sync, order webhooks, customer sync, and the control panel before promoting, keeping 7.13.1 pinned as a rollback.
- Do I need to re-authorize my Shopify app after upgrading to v8.0.0?
- Possibly. Official Shopify SDKs assume the OAuth and session-token app model, so if your v7 install used a legacy custom-app API password or a stored access token, v8 may reject those credentials or require reinstallation per store. Check whether stored credentials are migrated automatically or must be reissued before you upgrade production. Also check whether the v8 config surface still accepts your old credential keys, since config shape changes are a common breakage point.
- How does the addon verify Shopify webhook signatures and authenticate requests?
- Webhook HMAC verification and request authentication are handled by the Shopify client layer that v8 swapped to shopify/shopify-app-php. Because signature implementations differ between SDKs, re-test every webhook endpoint after upgrading; a mismatch typically fails closed with 401 responses, but silent behavioral drift is also possible. Keep your webhook secret in environment variables and confirm the route still matches what Shopify sends.
- Can I use statamic-rad-pack/shopify with multiple Shopify stores or a multisite setup?
- Multi-store and multi-connection setups were supported in the 7.x line, but each store needs its own session and credentials under the OAuth model introduced in v8. Verify per-store session handling on a staging clone before assuming existing multi-store configs keep working. This is one of the highest-risk areas to test alongside custom code that extends package classes or defines its own webhook routes.
- How do I test the Shopify integration without touching my live store?
- Create a separate development Shopify store and point the addon's credentials at it in a staging environment. Run the full lifecycle there: app install and OAuth, product sync, order and customer webhook receipt, and control-panel listings. Because v8's transport layer changes cursor pagination and rate-limit retry behavior, compare sync throughput and result completeness against your v7 baseline, and clear config:cache so stale cached config does not mask problems.
- Is statamic-rad-pack/shopify production-ready, and what should I watch for in production?
- It is a reasonable fit if you run Statamic 4/5 on Laravel 10/11 and want Shopify commerce behind a Statamic front end, but v8 is a major version with an SDK substitution, so read semantic versioning literally. Plan for a queue worker for sync jobs, cache Shopify responses where possible to reduce API pressure, and confirm a stated support window for the 7.x line if you need to stay on it. If you only need a few Storefront API reads, a custom GraphQL client may be lighter than a catalog sync addon, but you would lose the entry-based editing workflow.
Weaver
How can I help you explore Laravel packages today?