Shops For Laravel Laravel Package

Product Decisions This Supports

• Build vs. buy for tenant/shop customization: The new ShopModel::shop() helper lets host applications resolve the configured shop class safely, returning the custom class only when it extends the package’s base Shop. This supports buying the package instead of maintaining a fork when teams need white-label, multi-brand, or customer-specific shop models.
• Roadmap for extensibility: The release improves first-class support for swapping the packaged shop model. PMs can prioritize tenant-specific model customization without requiring package-level changes.
• Testing and release confidence: Factory fixes ensure tests build the configured model after a host swaps it. This reduces false test coverage and makes CI more representative of production behavior.
• Use cases: Multi-tenant SaaS, white-label commerce platforms, franchise/storefront systems, and Laravel applications where different customers or brands need slightly different shop behavior while sharing core package logic.

When to Consider This Package

• Consider it when the product is a Laravel/PHP application with a clear “shop” or tenant/storefront domain object and a need to let host applications subclass or swap that model.
• It is a good fit if engineering wants a packaged default Shop and ShopFactory but must support customer-specific model extensions without forking.
• Adopt it when test factories must remain accurate after model swaps; the 1.1.0 fix directly addresses that risk.
• Look elsewhere if the product needs a full multi-tenancy framework, database-per-tenant orchestration, or complex tenant lifecycle management beyond model substitution.
• Avoid it if the application is not Laravel/PHP, does not need model-level customization, or already has a mature internal abstraction for tenant/shop models.

How to Pitch It (Stakeholders)

This is a low-risk minor release that improves the package’s extensibility and test reliability. It lets host applications safely swap in a custom shop model while preserving a sensible default, and it fixes factories so tests exercise the configured model rather than a stale packaged one. For executives, the value is reduced custom maintenance and lower risk when serving white-label or multi-brand customers. For engineering, it means less forking, cleaner tenant-specific model resolution, and more trustworthy test coverage. No breaking changes or deprecations are indicated.