Weave Code
Laravel Magento Prices Nova Laravel Package
justbetter/laravel-magento-prices-nova
A Laravel Nova package for bringing Magento product prices into your admin panel. Add Magento price fields to Nova resources, display formatted prices, and view pricing alongside your Laravel models. Ideal for Magento-connected apps that need quick, convenient price visibility in Nova.
Laravel Nova integration for justbetter/laravel-magento-prices
Frequently asked questions about Laravel Magento Prices Nova
- How do I install justbetter/laravel-magento-prices-nova in a Laravel Nova app?
- Install it with Composer using composer require justbetter/laravel-magento-prices-nova. Then publish the package configuration and set your Magento connection details, such as base URL, store code, and API credentials. After that, add the provided price field to the Nova resources that should display Magento pricing. Check the README for the exact publish tags and field class names before wiring it into production resources.
- Does this package support Laravel 13, and which Nova versions are supported?
- Release 4.5.0 adds Laravel 13 support according to its changelog. The changelog does not state the exact Nova constraint, the minimum PHP version, or whether Laravel 12 and Nova 4 remain supported. Because Laravel and Nova majors are coupled, pin the package version and test the Nova and Laravel upgrade in a branch before deploying. If you need a definitive support matrix, check the composer.json constraints or open a GitHub issue with JustBetter.
- How do I add a Magento price field to a Laravel Nova resource?
- You add a Magento price field by including the field class provided by this package in that Nova resource's fields method. The field reads price data through justbetter/laravel-magento-prices and renders it as a formatted price in Nova. You control which resources expose pricing by adding or removing the field, so start with the product or catalog resources operators actually need. Confirm the exact field class name and available options in the README.
- How do I configure Magento API credentials for this Nova package?
- Configuration is handled by publishing the package config file and supplying Magento API credentials, typically the Magento base URL, store code, and an integration token or admin credentials. Store those values in environment variables or a secrets manager rather than committing them to the repository. Use a read-only Magento integration token where possible, because the package only needs to read prices. Then clear Laravel's config cache and verify the connection in a staging environment.
- Does it cache Magento prices, and can I change the cache TTL?
- The package sits in front of a remote Magento price source, so caching behaviour matters for both performance and correctness. The evaluation notes that cache TTLs are configurable and should be part of your configuration hygiene, but the exact default TTL and per-store-view options should be confirmed in the package config. Treat price staleness as a business risk and decide an acceptable TTL with the people who own pricing. Test cache invalidation after a Magento price change before going live.
- How does the package handle Magento API failures inside Nova?
- The evaluation flags error surfacing as one of the areas to harden, and the provided README excerpt does not specify the exact behaviour. Possible outcomes include a silent null, a stale cached value with a warning, or an exception that breaks the Nova resource index, so verify this in staging. A reasonable production approach is to keep the last known price visible with an explicit warning rather than letting a Magento outage blank the admin panel. Confirm the behaviour in code or with JustBetter before relying on it.
- Can I show different Magento prices per store view or multi-store setup?
- Multi-store scoping is a configuration concern because the package requires a Magento store code, so you can point it at a specific store view's pricing. The evaluation recommends confirming that your Magento store-view hierarchy is settled, because a small package of this shape is unlikely to model multi-brand or multi-instance Magento. Per-store-view TTL configuration is listed as a question to verify rather than a confirmed feature. If you need complex multi-store pricing, test it explicitly or consider a thin internal client.
- Is justbetter/laravel-magento-prices-nova safe to use in production?
- It can be production-safe for internal admin visibility, but price is commercially sensitive, so treat caching and failure handling as correctness risks rather than performance details. The package is a small, single-purpose library maintained by JustBetter with a single named contributor on the release, which is a bounded but real bus-factor risk. Pin the version explicitly, keep Magento tokens read-only, and monitor for stale prices. Plan one to two sprints to harden credentials, cache strategy, and error surfacing before production use.
- How should I test this package in a staging or local environment?
- For a proof of concept, install the package in a staging Laravel Nova app connected to a non-production Magento instance and add the price field to one resource. Expect roughly half a day for that proof of concept, then test cache TTL behaviour, credential handling, and Magento API failure modes. Because the package reads from a remote system, tests should mock the Magento price client rather than hitting a live store. Confirm the package's own testing approach in its repository or README.
- What are the alternatives to this package, and how is it supported?
- If you are not running Laravel Nova, this package is not the right abstraction; use justbetter/laravel-magento-prices directly or write a thin internal Magento price client. If price lives in a PIM, ERP, or custom pricing service rather than Magento, a small internal client will fit better than a Nova field package. Support appears to be GitHub-issues-only, and the evaluation notes there is no stated commercial support arrangement. For a long-lived dependency, confirm maintenance expectations with JustBetter or fork the small codebase.
Weaver
How can I help you explore Laravel packages today?