Statamic Butik Laravel Package

Product Decisions This Supports

• Build vs. buy for content-led commerce: Supports buying an existing Statamic-native commerce add-on rather than building catalog, cart, checkout, and order workflows in-house for small-to-mid storefronts.
• Platform roadmap and upgrade planning: v4.0.0-beta.1 adds Statamic 4 and Laravel 9/10 support, making it relevant to teams planning CMS/framework modernization. It is primarily a compatibility release, not evidence of new merchant-facing features.
• Use-case fit: Best suited to content-driven shops where products, merchandising, and editorial content live together in Statamic—e.g., small catalogs, brand sites with light commerce, or teams already standardized on Statamic/Laravel.
• Risk decision: Because this is a major beta, PMs should treat adoption as an upgrade spike or pilot, not an automatic production rollout. Confirm breaking changes, migration path, and test coverage before committing roadmap dependencies.
• Vendor/dependency strategy: If commerce is a core revenue stream, decide whether relying on a beta add-on is acceptable or whether a stable commerce platform/vendor SLA is required.

When to Consider This Package

Consider it when:

• You already run Statamic and want commerce functionality tightly integrated with content management.
• Your catalog and checkout requirements are relatively straightforward and do not demand enterprise commerce capabilities.
• You are planning or evaluating a Statamic 4 / Laravel 9–10 upgrade and need the commerce layer to remain compatible.
• Your team has Statamic/Laravel expertise and can absorb beta risk with testing, staging, and rollback plans.
• You prefer a lower-cost add-on over a separate commerce platform for a content-led storefront.

Look elsewhere when:

• You need a proven, stable, production-supported commerce release rather than a beta.
• You require complex B2B commerce, multi-store, advanced promotions, ERP/warehouse integrations, high-SKU performance, or enterprise SLAs.
• You are not on Statamic, or your framework roadmap depends on versions not explicitly covered by this release.
• Your organization cannot tolerate migration risk from a major-version upgrade without a documented breaking-change and rollback plan.

How to Pitch It (Stakeholders)

For executives: Statamic Butik is a commerce add-on that lets us sell through our existing Statamic/Laravel content stack instead of funding a separate commerce build or platform. The new v4 beta is important because it keeps the package aligned with Statamic 4 and Laravel 9/10, but it is still beta and should be treated as an upgrade pilot. Recommend a time-boxed validation spike before making it a roadmap dependency.

For engineering: This is a major-version beta focused on platform compatibility. We should review the changelog and upgrade guide, pin versions, test catalog/cart/checkout/order flows in staging, and document breaking changes and rollback steps. Do not assume production readiness from the release notes alone; confirm test coverage, migration effort, and maintainer responsiveness before adopting.