Aimeos Headless Laravel Package

Product Decisions This Supports

• Build vs. buy vs. "buy the engine, build the experience": Aimeos Headless is the middle path — adopt a commodity commerce core (catalog, cart, checkout, pricing, orders, promotions, subscriptions, multi-vendor) and spend in-house engineering on what differentiates us: storefront UX, vertical workflows, integrations, and data products.
• Headless/composable architecture: Because it is API-first (JSON:API over Laravel), it cleanly supports a decision to decouple the commerce backend from any number of frontends — web (Vue/Nuxt/Next/React), mobile apps, POS, partner portals, or B2B self-service — without re-platforming the core.
• Which business models to pursue in the roadmap: It explicitly targets the harder commerce shapes — B2B (customer-specific pricing, tiers, quotes, procurement flows), multi-vendor marketplaces (#gigacommerce), and high-SKU/high-locale catalogs. This makes "expand from D2C into B2B and marketplace" a credible roadmap item rather than a greenfield build.
• Feature scope decisions: Where the PM would otherwise spec and build catalog modeling, price rules, tax/currency/site handling, checkout state machine, and order lifecycle — buy those, reserve product scope for the differentiators.
• Build vs. buy at scale: Open-source + self-hosted means the commerce layer does not scale linearly with GMV via SaaS fees; the trade is operational ownership. This is a genuine TCO lever for high-volume scenarios.
• Vendor/data strategy: No SaaS vendor lock-in; catalog, customer, and order data stay in our infrastructure — relevant for data sovereignty, compliance, and ML/personalization pipelines.

When to Consider This Package

Consider it when:

• The team is PHP/Laravel-fluent or willing to invest — this is a Laravel distribution, not a foreign stack.
• Requirements exceed what turnkey SaaS comfortably handles: complex B2B pricing/quoting, multi-vendor marketplace, multi-site/multi-locale/multi-currency, or very large catalogs.
• You want a headless API contract to serve multiple frontends and channels from one commerce core.
• Open source (no license fees), self-hosted, container-friendly fits your infrastructure, security, and procurement constraints.
• You can staff ongoing hosting, upgrades, and integration engineering — adopting it is a platform commitment, not a purchase.

Look elsewhere when:

• You need a simple D2C store live in weeks with minimal engineering — Shopify/BigCommerce are faster and cheaper at small scale.
• The organization has no PHP/Laravel capacity and no appetite to build it.
• You require a fully managed SaaS with SLAs, a large app/plugin marketplace, and zero operational burden (e.g., commercetools, Saleor Cloud, Fabric).
• You need out-of-the-box enterprise CPQ, PIM, or ERP-grade functionality without integration work.
• You want native mobile SDKs / commerce-as-a-service with vendor support contracts rather than an OSS project you operate.
• The domain model learning curve (product/attribute sets, sites, price rules) is a poor fit for a very small, fast-moving product team.

How to Pitch It (Stakeholders)

For executives: Aimeos Headless is an open-source, API-first commerce engine built on Laravel. The strategic case: we buy the undifferentiated commerce plumbing (catalog, checkout, pricing, orders, marketplaces) and build the differentiated experience and data layer in-house. Benefits are (1) no per-transaction SaaS licensing that scales with GMV, (2) no vendor lock-in — code and data remain ours, (3) native support for B2B and marketplace models we want on the roadmap, and (4) a single commerce API serving web, mobile, and partner channels. The cost is that we own operations — hosting, upgrades, security, integrations — so this decision requires a Laravel-capable team and a funded platform-ownership line item. It is a "buy the engine, operate the engine" decision, not a managed SaaS purchase.

For engineering: This is a Laravel distribution that installs the Aimeos commerce core as a package and exposes a JSON:API. We do not fork it — we extend via Laravel service providers, events, and custom frontends (Vue/Nuxt, Next, React, native). The domain model — products and attribute sets, sites/locales/currencies, price and promotion rules, customer groups — is powerful but non-trivial; budget onboarding time. Deploy containerized to match our existing infra, pin versions, and establish a disciplined upgrade cadence and integration test suite. Expect to own the surrounding concerns: search, media/CDN, payments, tax, and observability, wired in as our own services.