- Is splash/shopify a Shopify SDK for Laravel, or something else?
- It is not a conventional Shopify SDK that your Laravel code calls into directly. splash/shopify is an embedded connector module for the SplashSync framework: Splash supplies the sync engine, object model, field mappers, and commit/acknowledge protocol, while this package supplies the translation layer to Shopify. You would not simply composer require it and call a pushOrder() method.
- How do I install splash/shopify in a Laravel application?
- It is Composer-installable, MIT-licensed, and pure PHP with no exotic runtime dependencies. However, because it is an embedded connector, installation in practice means standing up a Splash host runtime rather than dropping the package into an existing Laravel app. Plan for a Splash container with its own database schema and worker process.
- Does splash/shopify support Laravel 10 and Laravel 11?
- The package does not publish an explicit Laravel version constraint in the material reviewed here; its real compatibility surface is the pinned splash/core version set. Splash is built on Symfony components that Laravel also uses, including HttpFoundation, Console, Process, HttpClient, and Serializer, so there is meaningful overlap. The friction sits at bundle registration and container compilation, so treat Laravel 10 or 11 support as something to verify in a spike rather than assume.
- Can I use splash/shopify without running the Splash framework?
- Not cleanly. The embedded designation means the connector is designed to run inside a Splash host application, not as a library that a Laravel app calls into. You can lift the connector's internals into your own codebase, but that becomes a code-porting exercise against your own queue and HTTP client rather than a normal dependency.
- Which Shopify API version does splash/shopify target, and does it support GraphQL?
- The evaluation flags Shopify API drift as a high-risk area: Shopify ships quarterly API versions with roughly a 12-month support window and is pushing migrations from REST to GraphQL with cost-based rate limiting. The specific pinned version is not documented in the overview and should be confirmed from the repository and its commit history. Check the cadence of version bumps before committing.
- Does splash/shopify support Shopify webhooks for order sync?
- Webhook support is not confirmed by the material available. Whether sync is polling, webhook-driven, or Splash-orchestrated incremental is listed as a key open question, and the answer materially changes your operational design. Verify this early in any feasibility spike.
- Is splash/shopify production-ready and actively maintained?
- The signals are weak: roughly two GitHub stars, zero dependents, and single-org maintenance with no visible contributor base outside the maintainer. The composite score of 0.41 against an opportunity score of 0.76 suggests a reference implementation rather than a battle-tested dependency. The test story is also unclear, so confirm whether there are integration tests against a Shopify development store or only unit tests with fixtures.
- How should I architect splash/shopify inside a Laravel service?
- Do not embed the Splash runtime inside your Laravel application. Run the connector as an isolated Splash/Symfony service with its own database schema and worker process, and expose a narrow internal contract to Laravel. Laravel stays the system of record for your domain while Splash acts as an anti-corruption layer for Shopify, which keeps your framework upgrade path clean and contains the blast radius if the package is abandoned.
- Does splash/shopify support multi-store, multi-currency, or multi-location setups?
- Multi-store, multi-currency, and multi-location support are not confirmed in the material reviewed and are listed as open questions. If your roadmap includes multiple Shopify stores or per-location inventory, treat this as a must-verify item before commitment. Ask the maintainer directly and inspect the object model for location and currency fields.
- What are the alternatives to splash/shopify for Laravel Shopify integration?
- If your sync surface is small, covering products, inventory, and orders, forking the connector and re-implementing its mapping logic against your own queue and HTTP client is a reasonable single-deployable option. If you expect to add a second channel such as Amazon, BigCommerce, or a POS later, running Splash as an isolated service preserves its orchestration instead of rebuilding it piecemeal. Conventional Shopify SDKs combined with a custom Laravel integration are the other path to evaluate.