// the find
aimeos/aimeos-headless
Aimeos cloud-native, API-first ecommerce headless distribution based on Laravel for ultra fast online shops, scalable marketplaces, complex B2B applications and #gigacommerce
Aimeos headless is a Laravel-based API-first ecommerce distribution exposing a JSON REST API (jsonapi.org spec) and GraphQL admin API, meant to back a frontend of your choice. It's the headless variant of the broader Aimeos platform, which has been around long enough to support multi-vendor, subscriptions, block pricing, and 30+ languages out of the box. Target audience is teams building custom storefronts on Laravel who need a battle-tested commerce engine without rolling their own.
1. The jsonapi.org compliance is genuine — you get sparse fieldsets, relationships, and pagination for free rather than a bespoke JSON shape you have to reverse-engineer. 2. Multi-vendor and multi-warehouse support is built in at the data model level, not bolted on later, which matters a lot if you ever need marketplace features. 3. Cloud filesystem abstraction (S3, Azure Blob, GCS) is wired through Flysystem with documented config, so media storage is not an afterthought. 4. The underlying Aimeos core has a real extension system — you override specific managers or decorators rather than forking framework files, which means upgrades don't wipe your customizations.
1. The repo itself is mostly scaffolding — 90% of the meaningful code lives in upstream Aimeos packages, so debugging anything non-trivial means tracing through multiple Composer dependencies with their own release cadences. 2. Only 27 forks for 2500 stars is a red flag: this repo is more marketing surface than code, and the real usage is in the non-headless distribution. Community help specific to the headless variant is sparse. 3. Laravel Sanctum is used for API auth but the README shows query-string credentials (`?email=&password=`), which is a bad pattern to copy from documentation — it's not how you should send credentials in production. 4. No OpenAPI/Swagger spec is published; you're expected to learn the API from docs that reference a separate documentation site, making it harder to generate client SDKs or write contract tests.