- What is mews/laravel-pos?
- mews/laravel-pos is a Laravel package from Mews intended to add point-of-sale integration capabilities to a Laravel application. The overview describes configuration, service bindings, and API clients for connecting Laravel apps to Mews POS services. The technical assessment cautions that POS is an under-specified scope and that the package is likely a thin data-model scaffold rather than a complete POS system.
- How do I install mews/laravel-pos in a Laravel application?
- The mechanical installation path is composer require mews/laravel-pos, then publish the package configuration and migrations and run php artisan migrate. The package is MIT licensed, so internal and commercial use has little legal friction. Before installing, confirm the Laravel and PHP constraints in composer.json and review exactly which tables the migrations create.
- Which Laravel and PHP versions does mews/laravel-pos support?
- The provided assessment does not state a supported Laravel or PHP range and flags this as unknown version-surface risk. Check the package composer.json illuminate constraints and the CI matrix rather than assuming compatibility with your application. If the package pins illuminate components narrowly, it can become an upgrade blocker for the whole Laravel app.
- Is mews/laravel-pos production-ready?
- There is no evidence of production use in the assessment: it has zero Packagist dependents, no downstream issue corpus, and 111 stars that may reflect discovery rather than adoption. The recommended posture is fork-and-vendor rather than direct dependency. Treat the package as a data-model scaffold and validate the schema, tests, and maintenance activity before relying on it.
- Does mews/laravel-pos handle payments, tax, receipts, refunds, and financial rounding?
- The overview mentions POS integration and API clients, but it does not establish coverage of tender capture, tax jurisdiction rules, receipt content, refunds, or rounding. The assessment warns that POS correctness is financial and legal, and these are precisely the areas a small package cannot cover generically. If the package touches payment capture, PCI DSS scope may expand; if it does not, the POS name may over-promise.
- How does mews/laravel-pos affect my Laravel database schema and migrations?
- The package follows the Laravel service-provider plus config and migrations pattern and will likely want to own tables in your schema. In an existing Laravel application, migration and model ownership is the largest source of friction with third-party domain packages. Review the published migrations before running them and decide whether to isolate the tables, rename them, or take ownership through a fork.
- Does mews/laravel-pos support multi-store, multi-currency, or multiple tax regimes?
- The assessment explicitly asks whether the schema assumes single-store, single-currency, and single-tax-regime operation. It notes that multi-store and multi-currency support are usually retrofit-hostile, so this must be verified before design lock-in. Inspect the migrations and models for store, currency, and tax fields rather than assuming the package supports those dimensions.
- Does mews/laravel-pos work offline for physical retail checkout?
- The provided context contains no offline story, and the assessment says physical retail checkout requires degraded-mode operation. It recommends flagging offline support as a gap rather than a defect if the package does not address it. If your checkout must keep operating during network loss, plan for that capability outside this package or verify it directly in the source.
- Who maintains mews/laravel-pos and how active is the project?
- The assessment identifies Mewebstudio as a known individual maintainer and flags a bus factor of one. Support, security response, and Laravel major-version tracking depend on that person's availability. Check the release cadence and issue-response history over the last 12 months, because a single recent release date does not establish a maintenance commitment.
- Should I depend on mews/laravel-pos or fork and vendor it?
- The recommended approach is fork-and-vendor rather than direct dependency: copy the source into your app or a first-party namespace and take ownership of migrations, tests, and upgrades. This package may be a reasonable accelerator for an existing Laravel app that needs lightweight sale or order recording. It is too thin to be the foundation of a POS-first application.