Laravel Magento Customer Prices Nova Laravel Package

Product Decisions This Supports

• Back-office tooling for B2B/negotiated pricing. This package surfaces Magento customer-specific (customer group / negotiated) prices inside Laravel Nova, so sales, customer service, and account managers can see the right price for a given customer without switching into the Magento admin. The core product decision it supports is whether your ops teams get a single, low-friction view of pricing in the tool they already use.
• Build vs. buy for admin integrations. The alternative is building and maintaining a Magento price-lookup integration plus a custom Nova field (API client, auth, caching, error states, formatting). This is a narrow, well-scoped package — the "buy/borrow" case is strong if the fit is exact.
• Architecture roadmap: keeping Nova as the back-office layer alongside Magento. Adopting it is a de facto commitment to "Magento owns pricing, Laravel/Nova owns workflow and presentation." That's a reasonable, common split for B2B commerce, but it should be a deliberate decision rather than an accident.
• Use cases it unblocks: quote/order review screens where the rep must confirm the customer's actual price, account dashboards showing contract pricing, support triage where "what price does this customer see?" is the first question.
• Maintenance/upgrade planning. Release 4.5.0 adds Laravel 13 support. That's a compatibility signal, not a feature: it tells you the maintainer is tracking the framework, which matters for a dependency you'd otherwise have to fork when you upgrade Nova/Laravel.

When to Consider This Package

Consider it when:

• Magento 2 / Adobe Commerce is the system of record for customer-group or customer-specific pricing, and you have (or are building) a Laravel Nova admin.
• You need read-only display of that price inside Nova — a field or column next to your own models.
• Your pricing model genuinely varies per customer or customer group (B2B, wholesale, contract pricing); with a single price per SKU the package adds dependency weight for no benefit.
• You're on a supported Laravel/Nova line — 4.5.0 explicitly targets Laravel 13, so it's a reasonable moment to adopt if you're on that track, and 4.4.x remains an option if you're pinned to an older Laravel.
• You want a small, replaceable dependency rather than owning an integration.

Look elsewhere (or build in-house) when:

• You're not on Magento, or pricing lives in an ERP/PIM with no Magento mirror.
• You need write operations — setting prices, approving quotes, syncing back to Magento. This is a display integration; don't stretch it.
• You need pricing logic inside storefront/checkout or API responses for end customers. That belongs in the commerce layer, not a Nova admin package.
• You need SLA-grade performance or freshness guarantees on large catalogs; verify the caching/refresh behaviour and API call volume before assuming it scales.
• The vendor is a single maintainer and the code is small enough that forking is cheaper than the coordination cost — particularly if your Nova version diverges.

Assessment of this release (4.5.0): A pure compatibility release — Laravel 13 support, no new features, no deprecations, no breaking changes. Low upgrade risk; useful mainly as evidence the package is actively maintained. It does not change the build-vs-buy calculus, but it does remove "will this break on our next framework upgrade?" as an objection.

How to Pitch It (Stakeholders)

For executives: This is a small, low-cost connector that lets our sales and support teams see each customer's actual Magento price directly in our internal admin tool, instead of checking Magento separately. The business value is fewer wrong quotes, faster answers to "what does this customer pay?", and no bespoke integration for us to own. The new 4.5.0 release is a maintenance update — it keeps the package compatible with the latest Laravel — which is the signal we want: someone is keeping it current. Cost and risk are both small, and it's replaceable if it stops fitting.

For engineering: justbetter/laravel-magento-customer-prices-nova is a Nova field that resolves customer-specific prices from Magento. It is read-only, scoped to the admin layer, and does not touch storefront pricing or checkout. 4.5.0 adds Laravel 13 support only — no API changes, no breaking changes, so the upgrade is a version bump plus a smoke test of the field against a real customer account. Before adopting, confirm: Magento API credentials and connection config, how price lookups are cached and how staleness is handled, behaviour when Magento is unreachable (fail closed vs. show nothing), and whether the Nova/Laravel versions in our stack match the supported matrix. If any of those are unclear, the integration surface is small enough to fork or reimplement in a day or two.