- Is NexoPOS a Composer package I can require into an existing Laravel app, or a standalone POS application?
- NexoPOS is a standalone Laravel monolith - an application, not a drop-in Composer library. You deploy it as its own Laravel application with a Vue-driven frontend and an HTTP API used by the POS client. You extend or integrate it rather than requiring it as a package inside another app.
- How do I install and deploy NexoPOS?
- Deploy it like a standard Laravel application on PHP-FPM with MySQL or MariaDB: configure the web root, environment file, database, and queue workers. Because it is a full POS and retail management system, plan for upgrade migrations and schedule permission polling and queue processing. Follow the repository installation guide for exact commands and requirements.
- Which Laravel, PHP, and database versions does NexoPOS 6.2.4 support?
- The provided 6.2.4 changelog does not declare supported Laravel, PHP, or database versions, and it does not state whether they changed from 6.2.3. Treat the repository composer.json and installation docs as the source of truth before upgrading. Test against your target MySQL or MariaDB version in staging first.
- How do I extend NexoPOS with custom modules?
- NexoPOS has a modular Laravel core designed for custom add-ons, so you build modules that hook into its existing order, inventory, customer, and reporting surfaces. Because 6.2.4 tightens authorization and validation behavior, review module permission declarations and re-test any price or discount actions. Keep custom modules versioned against the 6.x line and test against each release.
- Can I integrate NexoPOS with external e-commerce, accounting, or procurement systems?
- Yes. NexoPOS exposes an HTTP API consumed by its POS client, which adjacent systems can also call for orders, inventory, customers, and reporting. The 6.2.4 release adds procurement fields such as purchase units and reorder quantities that are useful for system-of-record integrations. Plan to re-test payloads because authorization and discount and price validation are stricter.
- What authorization and validation changes in NexoPOS 6.2.4 could require retesting my integrations?
- 6.2.4 adds generic CRUD authorization and read protection across protected resources, and it validates restricted price, wholesale price, product-discount, and cart-discount actions server-side. Integrations that previously posted price or discount overrides may now receive rejections, and custom modules may need explicit permission declarations. The changelog also reports broad request-handling fixes across orders, payments, refunds, stock, coupons, and reports, so regression testing should cover every workflow you touch.
- Do custom modules need to explicitly declare permissions for the new generic CRUD authorization?
- The 6.2.4 changelog does not state whether custom modules must declare permissions explicitly, so treat this as a compatibility risk rather than a documented contract. Because enforcement behavior changed rather than method signatures, test each module's read and write routes against a restricted role. If your module bypassed the standard authorization layer, expect failures and add explicit permission checks.
- Are the purchase unit and scheduled reorder quantity migrations in 6.2.4 reversible?
- The release notes describe the default purchase units and scheduled reorder quantities as a forward migration, making 6.2.4 non-trivially reversible. The backfill default for existing products and installations is not specified in the provided materials. Back up the database and confirm rollback behavior in staging before upgrading production.
- How do temporary POS action permissions and permission polling affect in-flight actions?
- 6.2.4 introduces temporary POS action permissions and asynchronous permission polling, so permission decisions can expire or refresh while a POS session is active. The polling interval and cache TTL are not published in the provided changelog. Integrations that cache or precompute permission decisions should re-check them instead of assuming a static grant.
- What is the license and commercial use policy for NexoPOS?
- The provided materials describe NexoPOS as open-source but do not name the license, so check the repository LICENSE file before a commercial deployment or fork. Redistribution and hosted-service obligations depend on that license. Also confirm the 6.x support lifecycle and security-response policy with the maintainers, since neither is published in the release notes.