Weave Code
Laravel Magento Customer Prices Nova Laravel Package
justbetter/laravel-magento-customer-prices-nova
Manage Magento customer-specific prices directly in Laravel Nova. This package provides Nova resources for browsing, creating, and updating customer price records, so your team can keep Magento pricing data accurate and accessible without building custom admin tooling. Ideal for stores with per-cust...
Laravel Nova integration for justbetter/laravel-magento-customer-prices
Frequently asked questions about Laravel Magento Customer Prices Nova
- What does justbetter/laravel-magento-customer-prices-nova actually do?
- It is a Laravel Nova integration for the justbetter/laravel-magento-customer-prices package, providing Nova resources for browsing, creating, and updating Magento customer-specific price records. In practice it lets your back-office team maintain negotiated or contract pricing without logging into Magento admin. It is best understood as a thin adapter rather than a pricing engine: Magento stays the system of record for prices and Nova is only the operator UI.
- How do I install and configure this package in a Laravel Nova app?
- Install it with Composer using composer require justbetter/laravel-magento-customer-prices-nova; it follows standard Laravel package conventions, including auto-discovery. Expect a publishable config file for Magento connection details and registration of the package's Nova resources or tool in your NovaServiceProvider. The real work usually sits on the Magento side, where you need an integration user with the correct ACL scope for the operations you intend to allow.
- Which Laravel, Nova, and PHP versions are supported?
- Release 4.5.0 added Laravel 13 support and contained exactly one change, with no breaking changes, deprecations, or behavioural fixes, so it is a compatibility-widening release. Because the package is coupled to two moving targets at once, Laravel/Nova majors and Magento majors, check the repository's composer.json for the exact constraints rather than assuming. The 4.5.0 notes say nothing about Magento support, so that axis must be verified separately.
- Does this package read customer prices, write them, or both?
- The release notes do not document this, but the package is described as providing Nova resources for browsing, creating, and updating customer price records, which implies at least optional write access. That distinction changes the risk profile entirely, since an incorrect write is a commercial incident rather than a UI bug. If your workflow only needs visibility, scope the Magento integration user to read-only and confirm the package still functions that way.
- Which Magento editions and versions does it support?
- The 4.5.0 release gives no information on Magento version or edition support, so this must be verified directly against the source and your Magento instance. The package targets Magento as the pricing authority, but you should confirm the API surface it relies on exists in your version before committing. Do not assume Open Source and Adobe Commerce behave identically for customer price entities.
- How does the package authenticate with Magento, and where should secrets live?
- The authentication model is not described in the release notes; the common pattern for Magento integrations is an integration token with a scoped ACL, though OAuth or admin credentials are also possible. Whatever the mechanism, keep secrets in environment variables or a secret manager, never in the publishable config file or version control. Confirm the exact mechanism in the package config and README before deploying to production.
- Does it support multi-store, multi-website, and customer-group pricing?
- Multi-store, multi-website, and customer-group pricing support is not stated anywhere in the release notes, which describe customer-specific price records specifically. If your pricing model depends on website scope, store view, or customer group tiers, verify those dimensions are exposed before assuming parity with Magento admin. Missing scoping is a common cause of misleading prices in an admin UI.
- What test coverage exists, and does it run against a real Magento instance?
- The 4.5.0 release notes do not describe the test suite or CI setup, and the changelog references only a single contributor for that release. Check whether tests run against a real Magento instance or a mock, because a mock cannot catch ACL mismatches or API surface drift. Given that a pricing defect is a commercial incident, review the tests yourself before enabling write access.
- Is the package actively maintained, and should I auto-merge minor releases?
- The strongest health signal is that 4.5.0 added Laravel 13 support, but release cadence is driven by upstream compatibility pressure rather than feature development. Version 4.x with a one-line changelog reflects a narrow feature surface, not a mature API contract, so treat minor bumps as reviewable rather than auto-mergeable. It is also a niche package from a single vendor with one visible contributor, so vendoring or forking it as a bus-factor mitigation is a cheap, deliberate decision to make up front. Licence terms and commercial support options should be confirmed with JustBetter directly.
- When should I avoid this package, and what should I use instead?
- Skip it if Nova is not your back-office surface, if Magento is not your pricing authority, or if you have no genuine operational need for per-customer negotiated or contract pricing, because in those cases it adds a dependency without removing work. If you only need read-only visibility into customer prices, a small custom Nova resource or a direct read-only Magento API call may be simpler to own and audit. If you need rule-based pricing evaluation, this package is an adapter for Magento data, not a pricing engine.
Weaver
How can I help you explore Laravel packages today?