- What Laravel and Filament versions does tomato-inventory-module support?
- The v1.0.0 release notes and excerpt do not list exact composer.json constraints, so check the package's composer.json for php, laravel/framework, and filament/filament requirements before adopting it. The technical evaluation flags Filament version coupling as the main gating check because Filament v3 to v4 is a breaking change across resources and widgets. Treat v1.0.0 as a first tag and verify compatibility in a throwaway Laravel app at your target versions.
- Does Tomato Inventory Module track stock movements as an auditable ledger?
- The available v1.0.0 materials do not confirm whether the module owns a reversible, auditable stock-movement ledger or simply mutates quantity columns. The technical evaluation calls this out as a key open question and a correctness risk for inventory use. Inspect the migrations, models, and service classes, then exercise product and stock movement flows in a spike before relying on it for auditability.
- How do I install tomatophp/tomato-inventory-module in a Laravel app?
- Install it with composer require tomatophp/tomato-inventory-module, then publish its config and migrations and run php artisan migrate. Register the module with the TomatoPHP module loader and seed or point it at your existing product data. Expect installation to be straightforward and reserve most effort for SKU mapping and opening-balance reconciliation.
- Does it support multiple warehouses and stock transfers?
- The overview says the module tracks warehouses and stock movements, but the v1.0.0 notes do not confirm full multi-warehouse transfer semantics. Multi-warehouse, lot or serial tracking, and unit-of-measure support are listed as unverified questions in the technical evaluation. Validate transfers, reservations, and backorders in a test app before committing to the package.
- Can I use Tomato Inventory Module without the TomatoPHP admin panel?
- It is built as a TomatoPHP ecosystem module with Filament admin resources, so it delivers the most value when you already run that stack. On a bespoke admin layer you would either adopt the module's UI conventions or use only its underlying services and migrations. Confirm that the service classes are usable independently before assuming a headless integration.
- Is tomato-inventory-module compatible with Filament v4?
- The excerpt does not state whether v1.0.0 supports Filament v4, and Filament v3 to v4 is a breaking API change across resources and widgets. Check the declared filament/filament constraint in composer.json and run the module's admin resources in a test app against your target Filament version. Do not assume forward compatibility from the 1.0.0 tag alone.
- Does it handle product costing such as FIFO or weighted average?
- The v1.0.0 materials do not say whether FIFO, weighted average, or any costing method is implemented. Costing is called out in the technical evaluation as a common shortfall and an unverified correctness risk for inventory packages. Confirm it in code and tests before using the module for valuation, margin reporting, or accounting integrations.
- How do I migrate an existing product catalog and opening stock?
- Map your existing SKU and product master to the module's schema, then import opening balances as real stock-movement records rather than direct quantity updates. That preserves an audit trail and avoids invisible adjustments that are hard to reconcile later. Treat data reconciliation, not Composer installation, as the main integration effort.
- Does it include barcode printing and inventory reports?
- The package description advertises inventory reports and barcode printing as part of the module. The technical evaluation does not detail supported barcode formats, label templates, or report customization options. Check the admin resources and any publishable config or views during the spike to confirm they meet your printing and reporting requirements.
- Is tomato-inventory-module production-ready and actively maintained?
- Treat v1.0.0 as a first tagged release rather than a stability guarantee: the changelog has no substantive content beyond a compare link, and no deprecation or upgrade policy is visible. The TomatoPHP ecosystem is small and community-driven, so single-maintainer and bus-factor risk is moderate to high. Run a spike, check test coverage and CI at the tag, and roll out behind a feature flag with read-only validation first.