Ecommerce Admin Livewire Laravel Package

Product Decisions This Supports

• Build vs. buy the back office. This package is a ready-made store admin (orders, products, customers, promotions, shipping, tax, reports, settings) for teams building on the ArtisanPack UI ecommerce engine. The core PM decision it unlocks is whether to spend engineering cycles on differentiated storefront/commerce logic instead of rebuilding admin CRUD, permissions, CSV tooling, and accessibility plumbing.
• Launch readiness and scope of an MVP. v1.0.0 is a stable release covering the operational surface a store needs on day one: order lifecycle (status/sub-status, shipments, tracking, label purchase, refunds with restock, edits with totals diff and rollback, cancellation, notes, timeline), catalog management across all product types, and reporting with CSV export.
• Compliance and procurement posture. WCAG 2.2 AA is an explicit target with an axe check on every screen in the browser suite, keyboard reordering with announcements, focus return, error summaries, and captions/sort state on tables. That supports public-sector, enterprise, and EU accessibility requirements as a roadmap gate rather than a post-launch retrofit.
• Market expansion sequencing. Shipping with English, Spanish, French, and German translations, plus per-currency scheduled prices and locale-aware notification templates, makes localization a configuration and content decision rather than an engineering project.
• Operational risk decisions. Refunds by amount are spread across order lines, pending refunds count against the refundable balance, and "Refunded" only appears once payment is actually refunded. Bulk actions skip records the user cannot change. These are the kinds of guardrails that determine whether you can give support agents and store managers broad access without a bespoke approval flow.
• Extensibility strategy. Registries and filters exist for navigation, dashboard widgets, palette providers, order panels, product type panels, customer tabs, settings tabs, config forms, pickers, and table columns/filters/bulk actions. This is the deciding factor for whether the admin can absorb your differentiators (custom product types, bespoke order workflows, internal tooling) without forking.
• Platform and dependency commitments. Requires engine 1.0, Laravel 12 or 13, and Livewire 3.6+ or 4. Real-time dashboard and order updates depend on Laravel Echo and are off unless rebing/graphql-laravel is present (now suggested, not required). Decide whether live updates are a launch requirement or a later enhancement.
• Identity and access architecture. RBAC is delegated to the engine's ability catalog and ecommerce:sync-permissions, with a shop-manager role and cms-framework integration for layout, menu, and permissions. The admin middleware (2FA, verified) also runs on Livewire updates, and mutating updates count against the engine's ecommerce.admin.mutate rate limiter. This shapes your security review and role design.
• Data operations and migration planning. Catalog CSV import (column mapping, dry run, queued and resumable), catalog export, tax rate CSV import/export, coupon export, and bulk inventory adjustment from CSV support onboarding from a legacy platform and ongoing merchandising workflows.
• Licensing and lock-in review. The package is MIT, which lowers legal friction for internal modification and distribution. The coupling to review is to the ArtisanPack UI ecommerce engine and its ability catalog, table prefix, warehouse defaults, and config schemas, not to this admin package's license.

When to Consider This Package

Consider it when:

• You are already building on, or seriously evaluating, the ArtisanPack UI ecommerce engine at version 1.0 and need an admin surface without writing one.
• Your stack is Laravel 12 or 13 with Livewire 3.6+ or 4, and you are comfortable with a Livewire-rendered admin rather than a separate SPA.
• You need broad store operations coverage quickly: orders, refunds, shipments, all product types (simple, variable, digital, grouped, bundled), variants, per-currency scheduled pricing, categories, tags, inventory, digital files, license keys, customers, promotions with a rule builder, coupons, shipping zones and methods, tax classes and rates, reports, notification templates, webhooks, order statuses, and store settings.
• Accessibility is a requirement, not a nice-to-have. The browser test suite with per-screen axe checks is a meaningful signal for WCAG 2.2 AA commitments.
• You expect to extend the admin rather than accept it as-is. The registry and filter surface is the main hedge against "we outgrew the vendor admin."
• You want command-palette navigation and optional real-time updates for support and operations teams handling high order volume.
• You need a shop-manager-style delegated role and are prepared to map your permission model onto the engine's ability catalog.

Look elsewhere, or plan significant integration work, when:

• You are not using the ArtisanPack UI ecommerce engine, or you are on a pre-1.0 engine version. The release is explicitly engine 1.0 compatible, and much of its behavior (table prefix, default warehouse, ability catalog, config schemas, currency and refund limits) is delegated to the engine.
• You require a headless or API-first admin, a non-Livewire front end, or a mobile-native operations app. This is a Livewire server-rendered admin.
• Your admin needs are heavily bespoke in ways the listed extension points do not cover, for example a custom order lifecycle engine or a marketplace with multi-vendor settlement.
• Real-time updates are a hard launch requirement and you are unwilling to add rebing/graphql-laravel and Laravel Echo. Real-time is explicitly off without it.
• You are on Laravel 11 or earlier, or on Livewire 2.x.
• You need a mature third-party ecosystem, marketplace of plugins, or vendor SLA. This is a first stable release; the browser suite covers main flows and accessibility, but it is not a long track record.

How to Pitch It (Stakeholders)

For executives. The store admin that normally consumes a large share of a commerce build is now available as a stable, MIT-licensed package for the ArtisanPack UI ecommerce engine. It covers the operational essentials — orders, refunds, shipments, the full product-type range, inventory, promotions, coupons, shipping, tax, reports, customers, license keys, notifications, and webhooks — with a command palette, optional real-time updates, and accessibility work targeting WCAG 2.2 AA backed by an axe check on every screen. The business case is time-to-market and risk reduction: we buy the undifferentiated back office and spend our engineering on the storefront and commerce logic that customers actually see. The main commitments to acknowledge are the engine coupling, the Laravel 12/13 and Livewire 3.6+/4 baseline, and the fact that real-time needs rebing/graphql-laravel and Laravel Echo.

For engineering. v1.0.0 is the first stable release and is engine-1.0 aligned: every query qualifies columns through its model so the ecommerce_ table prefix works, config forms read the engine's DescribesConfig schemas and validate with the engine's rules, stock uses the engine's default warehouse, license keys are searched by hash, and currencies, navigation, badges, refund limits, and digital-file deletion come from the engine. RBAC is delegated: permissions come from the engine's ability catalog and ecommerce:sync-permissions, with ecommerce-admin:sync-permissions as a deprecated alias. The security posture is solid for a v1: the command palette searches behind admin middleware, the configured admin middleware also runs on Livewire updates, mutating updates hit the ecommerce.admin.mutate rate limiter, webhook secrets stay out of public component state, inline scripts carry the CSP nonce, and picker caches, row selections, and import error reports are capped. Extension points are registries and filters for navigation, dashboard widgets, palette providers, order panels, product type panels, customer tabs, settings tabs, config forms, pickers, and table columns, filters, and bulk actions — treat these as the contract for our customizations rather than editing vendor views. Test coverage is Pest plus Playwright across main flows and accessibility, and ecommerce-admin:install and ecommerce-admin:prune-imports cover setup and import cleanup.

For operations and support. The admin ships with the day-to-day screens a store team needs: dashboard figures with 30-day sales, lowest stock, and recent orders; order detail with shipments, tracking, label purchase, per-item or amount-based refunds with restock, totals-diff order edits with rollback, cancellation, notes, and an activity timeline; review moderation; bulk inventory adjustment from CSV with required reasons and thresholds; license key activations, machine deactivation, and revocation; and a command palette across orders, products, customers, promotions, and coupons with contextual order actions. Bulk actions skip records the user lacks permission to change, and refund limits come from the engine, so guardrails are in the product rather than in a spreadsheet of who is allowed to do what.

Bottom line. Adopt it if you are on the ArtisanPack UI ecommerce engine, need a capable and accessible admin quickly, and are willing to build your differentiators through the provided extension points. Do not adopt it as a general-purpose Laravel admin, as a headless admin, or if real-time is non-negotiable without adding rebing/graphql-laravel.