Advanced Overview

Commands, internals, and contributor tooling.

In this section

• Artisan Commands - ecommerce-admin:install, ecommerce-admin:prune-imports, and the deprecated ecommerce-admin:sync-permissions
• Browser Tests - Running and writing the Playwright browser suite

How a request flows

Route → AdminScreenController (returns a page view)
          → page view  @extends( $ecommerceAdminLayout )
              → <livewire:artisanpack-ecommerce-admin-… />
                   → engine policy check
                   → engine service        (writes)
                   → query class on models (reads)

• Pages are controller actions returning a view that embeds one Livewire component. They are not full-page Livewire routes, so route:cache works and the layout can be swapped.
• Writes go through engine services. A component never assembles a multi-table write itself.
• Reads use per-screen query classes in src/Queries/, with eager loading, so filters and sorting are tested without rendering.

Middleware

Both run on every admin route after admin.middleware, and both are registered as Livewire persistent middleware so update requests from an admin page re-run them. Over the limit, the throttle answers 429 with Retry-After and a JSON message; the page turns it into a toast. Change the limit by redefining the engine's ecommerce.admin.mutate rate limiter.

Idempotency

Refunds, cancellations, shipments, order edits, and confirmed bulk actions carry a one-time action token minted when the form renders. The token is consumed in the same transaction as the write, so a double click or a replayed request runs once.

Registering routes yourself

Set admin.routes_enabled to false and register the routes in your own route file. Keep:

• the route names under artisanpack.ecommerce.admin. (the navigation, links, and palette look them up);
• the ecommerce-admin.access and ecommerce-admin.throttle middleware;
• AdminScreenController actions, so pages get their layout.

routes/admin.php in the package is the reference.