Introduction
Lunar’s goal has always been the same: to be the most flexible, modern e-commerce foundation for Laravel developers. v2 brings that into sharper focus. What follows is the result of community input and conversations with the people building stores on Lunar today. Plans evolve as work progresses, so this page is updated as milestones ship.Where v2 is today
Alpha available now The first alphas of Lunar 2.0 are published. Read the 2.0 alpha announcement and the v2.x documentation to try it against a copy of an existing store.
The alpha is for evaluation and feedback only. APIs can still change between alpha releases, and production use is not recommended until the stable release.
What v2.0.0 brings
v2.0.0 is the foundational release. It introduces breaking changes that improve how Lunar works under the hood, alongside new core concepts. Most of this is already in the alpha:- Reworked custom attributes
- A dedicated pricing engine with significant performance improvements to price fields
- Cart performance improvements
- New core concepts including regions and storefront context
- Fulfilments and per-location inventory in core
- A cleaner extension model built on native Laravel seams
The new admin panel
In the alpha The big change in the v2 cycle is a new admin panel, built on Inertia.js and Vue, published aslunarphp/panel. It ships in the alpha today with the full catalog, sales, and settings surface, a customizable widget dashboard, global search, autosaved edit drafts, and mandatory two-factor authentication for staff.
It is faster, cleaner, and built for the kinds of stores Lunar is increasingly used to run. But the bigger story is the proper extension points underneath. v1’s extension surface grew organically and worked, but it was not always predictable. v2 draws a firm line between core and extensions, and that line is what makes everything else on this page possible.
The panel continues to be refined through the beta. See the admin panel documentation for the current state.
Inventory and fulfilment in core
In the alpha v2 brings inventory and fulfilment into core at a basic level. Stock is tracked per variant per location with movements and reservations, and orders are fulfilled through dedicated fulfilment records with methods, carriers, and tracking. See Inventory and Fulfilments. These are things almost every store needs in some form, and having them in core gives Lunar a consistent base to build on. The aim is not to ship a full warehouse management system in core. It is to provide the right primitives, in the right place, so simpler stores get what they need out of the box and the more demanding ones have something solid to extend.Returns
Later in the v2 cycle Returns and RMA (return merchandise authorization) build on the fulfilment and inventory primitives above, including routing returned goods through an inspection state before they become sellable again. This arrives in a later minor release during the v2 cycle. It also sets up the deeper enhancements and ERP-grade functionality that come through Lunar Eclipse later.A better story for Filament developers
In the alpha One of the clearest pieces of feedback from the v1 community has been around control. Filament developers want to own the look, feel, and behavior of their admin, and that has been harder to achieve with Lunar than it should be. v2 changes that with a dedicated Filament package,lunarphp/filament. It is a bridge that exposes Lunar’s components and widgets as building blocks Filament developers can compose freely inside their own panels. Rather than working within a Lunar-shaped Filament admin, developers get the pieces and build the UX they want.
The package supports Filament v5 and is versioned separately from Lunar itself. That lets it follow Filament’s own release cycle more closely, so Filament developers are not waiting on a Lunar release to get support for the latest Filament version.
This is the model for Lunar going forward. Lunar provides the commerce primitives, and the framework used to build the admin stays under the developer’s control.
The existing Filament admin, lunarphp/admin, carries on through v2, so nobody has to migrate the day v2 lands. From v3, the admin package is phased out, but the bridge package stays. See the Filament add-on documentation.
Storefront starter kit
With the stable v2.0.0 release Alongside the panel, Lunar is shipping a storefront starter kit, also built on Inertia.js and Vue. The idea is straightforward: get a developer from zero to a working, customizable storefront in minutes, fully integrated with Lunar’s checkout. It is not a locked-in theme. It is a starting point, designed to be owned and shaped by the team building on it. The v1 starter kit has not yet been updated for v2. Until the new kit ships, the storefront guides walk through building a storefront against v2 from scratch.Checkout
With the stable v2.0.0 release Checkout is a dedicated, open source checkout layer for Lunar, planned to release alongside the storefront starter kit. Building it as its own component keeps it cleanly separated from the storefront and the admin, which means it can move at its own pace and get the kind of focused attention this part of e-commerce deserves. The open source checkout will also be the foundation for a future hosted product, with additional capabilities on top for stores that want a managed setup. More on that in due course.Built for developers and AI agents
Lunar is plain Laravel and Eloquent, with no proprietary DSL, which makes it a natural fit for agentic development. The documentation already ships an MCP server,llms.txt, and Markdown export, and the 1.x core package includes a Laravel Boost skill.
Planned for the v2 cycle:
- A Laravel Boost skill for v2, shipped with the core package
- A first-party storefront REST API
- MCP servers for the admin panel, the storefront, and developer tooling