Weave Code
App Bundle Laravel Package
shopware/app-bundle
A Symfony bundle for building Shopware apps, providing the core infrastructure for app manifests, lifecycle events, webhooks, and platform integration. It streamlines app registration, configuration, and communication so developers can add custom features to Shopware 6.
Symfony Bundle for Shopware App Backend
Frequently asked questions about App Bundle
- What is shopware/app-bundle used for?
- It is a Symfony bundle that covers the backend half of a Shopware 6 app. It handles app manifests, the registration and confirmation handshake, webhook signature verification, lifecycle event dispatch for install, update and uninstall, plus an Admin API client. You use it when your Shopware app runs as a separate hosted PHP service rather than as an in-process plugin.
- Does shopware/app-bundle work with Laravel?
- No. It is a native Symfony bundle built around Symfony bundle registration, the service container and Symfony configuration, so it is not installable as a Laravel package. If your backend is Laravel, Node or Python, implement the Shopware app registration and signature specification directly, since the handshake is essentially two endpoints plus HMAC comparisons.
- How do I install shopware/app-bundle?
- Require it with Composer, enable the bundle in your Symfony kernel or bundles.php, then add its configuration. After that you define your app manifest and wire the registration, confirmation and webhook routes into your application. Standard Composer and Symfony bundle practices apply, and nothing proprietary is needed beyond your Shopware app credentials.
- Which PHP and Symfony versions does shopware/app-bundle support, and is it actively maintained?
- The bundle targets PHP 8.x on Symfony, and 6.1.0 is a minor, non-breaking release that should be a drop-in from 6.0.2. Pin the exact version against your target Shopware platform version and treat that pair as the unit under test in CI, checking the composer.json constraints against your baseline. Release cadence looks real, since 6.1.0 shipped about four weeks after 6.0.2, but the project has a small maintainer team and a small dependent base, so pin versions and read the source.
- How does shopware/app-bundle verify webhook signatures?
- The bundle verifies incoming webhook signatures against the shop secret before dispatching the request, so your handlers only receive validated calls. Version 6.1.0 changed the request-body path to decode the body once instead of repeatedly, which is a performance win but sits directly upstream of HMAC verification. Confirm that byte-exactness of the raw payload is preserved behind proxies and with chunked or streamed requests.
- Where should I store the Shopware shop secret?
- The bundle does not prescribe how shop secrets are persisted, encrypted or rotated, so that responsibility stays in your application. In practice you store the secret returned during registration confirmation per shop, encrypt it at rest, and support rotation when a shop re-registers or reinstalls. Plan this explicitly, because credential handling is a common gap in Shopware app backends.
- Can I call the Shopware Admin API from the bundle?
- Yes, Admin API integration for Shopware resources is one of the features the bundle provides, so admin calls can live in your Symfony services. You still own token acquisition, error handling, retries and rate-limit behavior in your own code. Verify that the client covers the specific endpoints you depend on before building around it.
- Is upgrading from shopware/app-bundle 6.0.2 to 6.1.0 safe?
- 6.1.0 is described as a minor, non-breaking release with no configuration or route changes, so a drop-in upgrade is expected. The one caveat is the body-decoding change on the request path used by signature verification. Keep signature test vectors with exact raw payload bytes signed by a known secret, run them before and after the bump, and retain the ability to fall back to 6.0.2 if byte-exact behavior regresses.
- Do I need shopware/app-bundle, or can I implement the Shopware app registration myself?
- The bundle is an accelerator, not a hard dependency. The contract with Shopware is the public app manifest and registration specification, so you can implement the registration and confirmation endpoints and the HMAC comparisons yourself. The bundle mainly saves you the plumbing while adding lifecycle event dispatch and an Admin API client.
- Is shopware/app-bundle a migration path from a Shopware plugin to an app?
- No, not by itself. Moving a plugin to an app is a re-architecture: you need a manifest, public endpoints, webhook handling, hosting and a credential store, and the bundle covers only the backend half of that. Use it for greenfield app backends, or adopt it incrementally endpoint by endpoint behind existing routes if you already run a custom app backend.
Weaver
How can I help you explore Laravel packages today?