Introduction

Documentation Index

Fetch the complete documentation index at: https://docs.laravelshopper.dev/llms.txt

Use this file to discover all available pages before exploring further.

Shopper is an open-source headless e-commerce package for Laravel. It provides a production-ready admin panel, a flexible product catalog, and all the commerce logic your store needs, built on the tools you already know, without taking over your codebase.

​

Why Shopper?

There are several ways to add e-commerce to a Laravel application. You could integrate an external platform like Shopify, adopt a full e-commerce system like Lunar or Bagisto, or build everything from scratch. Each approach has trade-offs. Shopper takes a different path. It is a Laravel package, not a platform. You install it into your existing application the same way you would install spatie/laravel-permission or laravel/cashier. Your routes, your middleware, your authentication, your deploy pipeline stay unchanged. You add e-commerce to your app, not the other way around.

​

Building Blocks, Not a Monolith

Most e-commerce systems assume one-size-fits-all. But selling cars is not the same as selling sneakers, and a subscription box service has nothing in common with a marketplace. Shopper recognizes this by giving you composable building blocks instead of a rigid platform. Every Eloquent model is swappable via configuration. Every Livewire component can be overridden. Every feature can be toggled on or off. You start with a solid, production-ready foundation and shape it to match your business.

​

Headless from Day One

Shopper handles the commerce logic and the admin panel. You build the storefront with whatever stack your team already ships with. Blade, Livewire, Inertia, Next.js, Nuxt, React Native, or anything else. Shopper has no opinion on how you present your store to customers.

​

A Package, Not a Platform

This distinction matters. A platform owns your application. You build on top of it, adapt to its conventions, and work within its constraints. A package is a tool you control. Shopper adds e-commerce capabilities to your Laravel application without replacing your User model, your authentication system, or your application structure. Your User model gains Shopper capabilities through a trait. The admin panel is a feature of your app, not the other way around. Your database is extended, not replaced.

​

Tech Stack

Shopper is built on top of Laravel, Filament, and Tailwind CSS. The admin panel uses Livewire for its interactive components.

​

Packages

Shopper is made up of several Composer packages that work together:

• shopper/core is the e-commerce engine: models, contracts, migrations, enums, observers, and all business logic. It has no dependency on any UI layer.
• shopper/admin is the admin panel, built on Filament, for managing products, orders, customers, and more. It extends core models with media support and provides all Livewire pages and components.
• shopper/cart handles shopping cart management.
• shopper/payment provides a driver-based payment processing architecture with an official Stripe addon (shopper/stripe).
• shopper/shipping manages carriers, zones, and shipping rate calculation.
• shopper/types is an npm package (@shopperlabs/shopper-types) with TypeScript type definitions for storefront development.

The core package defines contracts (interfaces) for every model. The admin package extends core models with media support. When you swap a model via configuration, the entire system (admin panel, relationships, route bindings) uses your custom class automatically.

​

Key Features

Shopper ships with everything you need to run an online store:

​

Extensibility

Shopper is designed to be extended, not forked. Three mechanisms make this possible. Model swapping lets you replace any Eloquent model with your own. Define your custom class in config/shopper/models.php and the entire system uses it, including the admin panel, relationships, and route model binding. Component overriding lets you replace any admin panel page or form. Run php artisan shopper:component:publish {feature} to get a configuration file where you can point any component to your own Livewire class. Feature toggling lets you disable entire sections of the admin panel. Set any feature to FeatureState::Disabled in config/shopper/features.php and it disappears from the UI.

​

Stability and Versioning

Shopper follows Semantic Versioning. Minor and patch releases never contain breaking changes. Every component is tested, and upgrade guides are published for every major version bump. For details on supported versions and maintenance windows, see the Version Support Policy.

​

When Shopper Fits

Shopper is the right choice when you already have a Laravel application (or want to build one) and need to add e-commerce capabilities without adopting an opinionated platform. It works well when your storefront is non-standard: a product configurator, a subscription service, an auction site, or anything that does not fit the typical “browse and checkout” template. If you need a store running in an hour, Shopify is a better fit. If you need dynamic product attributes managed entirely through the admin UI, Lunar handles that well. If you are not in the Laravel ecosystem, MedusaJS is worth considering.

​

Next Steps