aimeos/aimeos-headless

aimeos-headless is a focused starting point for teams building a custom SPA, PWA, mobile app, or other API client. It preconfigures an API-first Laravel commerce backend with JSON:API, GraphQL administration, and JWT authentication while retaining Aimeos capabilities such as multi-vendor, multi-channel, multi-warehouse, subscriptions, pricing, discounts, localization, and marketplaces. This separation prevents front-end teams from first having to remove a bundled storefront.

Headless commerce depends on a reliable API contract. The project would benefit from more visible schema versioning, generated SDKs, pagination and error conventions, webhook specifications, idempotency rules, cache semantics, rate limits, and compatibility guarantees. Example clients should demonstrate token refresh, cart concurrency, payment retries, localization, and offline recovery rather than only the happy path. This distribution is best for experienced teams that intentionally want to own their front end and deployment architecture; organizations wanting a ready-made shop interface should choose the full distribution instead.

Aimeos Headless is a strong, well-positioned Laravel ecommerce distribution for teams that want API-first commerce without giving up the maturity of the Aimeos ecosystem. The repo communicates its value clearly: JSON:API support, GraphQL administration, cloud storage options, multi-vendor/multi-channel capability, subscriptions, vouchers, configurable products, many languages, and serious scale claims. The README is especially useful because it gives a quick installation path with Composer, local php artisan serve instructions, /jsonapi and /admin entry points, authentication examples, and concrete AWS/Azure/Google Cloud filesystem snippets. The project also has healthy community signals with roughly 2.5k stars, active Aimeos ecosystem links, 12 tags, an MIT license declaration, and no visible open issues or PR backlog at review time.

The main improvement I’d suggest is tightening the onboarding details for production evaluators. The repository currently looks like a distribution wrapper around substantial Aimeos packages, so adding a small “architecture overview” section explaining which responsibilities live in this repo versus aimeos/aimeos-laravel, ai-client-jsonapi, and related packages would help new maintainers and enterprise adopters orient faster. I’d also align version messaging across the README and composer.json: the README says PHP >= 8.2, while composer.json allows PHP ^8.1 and currently depends on Laravel ^12.0; making those requirements unambiguous would reduce install-time surprises. Finally, the README would be even stronger with visible CI/test status, a short example of a real storefront consuming the API, and links to contribution/security policies. Overall, this is a very capable and practical headless ecommerce starter with unusually broad commerce features for a Laravel-based open-source project.