Weave Code
Tomato Ecommerce Module Laravel Package
tomatophp/tomato-ecommerce-module
A Laravel ecommerce module for the TomatoPHP ecosystem, adding products, categories, carts, checkout, and order management to your admin panel. Drop it into a TomatoPHP app to get a ready-made storefront backend without building commerce logic from scratch.
a full frontend/backend e-commerce system built on top of TomatoPHP, with Cart functions and ordering functions
Frequently asked questions about Tomato Ecommerce Module
- How do I install the TomatoPHP ecommerce module in Laravel?
- Install it with composer require tomatophp/tomato-ecommerce-module, then publish the config and migrations and run php artisan migrate. The package is a Laravel module in the TomatoPHP ecosystem, so its service provider is auto-discovered and the admin screens are expected to appear through TomatoPHP's Filament-based panel. Check the repository README for the exact publish tags and any required TomatoPHP core packages before installing.
- What Laravel, PHP, and Filament versions does this package support?
- Treat Laravel 10 and 11, PHP 8.1+, and Filament 3 as the working assumption until you read the composer.json constraints directly. The v1.0.0 release notes do not publish a supported-version matrix or CI status, so confirm the laravel/framework, PHP, and Filament constraints in the package metadata. Filament major upgrades are a known coupling risk for TomatoPHP modules.
- Does this module provide a complete storefront or only admin order management?
- The module is described as a full frontend/backend ecommerce system with cart and ordering functions built on TomatoPHP, which in practice means a ready-made storefront backend inside your admin panel. Whether it owns payment orchestration or only catalog and order records is the key question to resolve before adopting it. If your storefront is a separate SPA or headless front end, scope it narrowly as an admin and order-management layer.
- How are carts and checkout handled in this Laravel ecommerce module?
- Cart functions and ordering functions are part of the package scope, so you get cart records, checkout flow, and order creation tied to the TomatoPHP admin surface. The v1.0.0 release does not document an explicit order state machine or its extensibility, so inspect the migrations and models to see whether transitions are hard-coded. Test concurrency around order placement and inventory decrement before relying on it.
- Does it handle payments, taxes, shipping, and inventory?
- The release does not specify what the module owns versus delegates for payments, tax, shipping, or inventory. Assume you will wire your own payment and shipping providers into whatever abstraction it exposes, and budget a spike for that integration. Verify tax, rounding, and currency handling directly in the code because money-touching paths are the highest-risk area in a young 1.0.0.
- Can I integrate it with an existing products or orders database?
- Adopting it alongside an existing commerce platform is only safe if you keep money movement in your proven path and use the module narrowly for catalog authoring, order records, and admin tooling. Check the shipped migrations for table name and prefix collisions with your current schema before running them. Migrating live order data into an unproven 1.0.0 schema is the highest-regret move available here.
- Is tomatophp/tomato-ecommerce-module production-ready at v1.0.0?
- Treat v1.0.0 as a semver commitment rather than proof of battle testing, because the release was published with only a changelog link and no scope or breaking-change notes. Pin the dependency to the v1.0.0 commit SHA instead of a floating constraint while you evaluate it. Production readiness depends on your own coverage of checkout, tax, rounding, and order-state concurrency.
- How do I test checkout and order state transitions?
- The repository does not state test suite coverage or CI status in the release, so do not assume checkout and order transitions are covered. Write feature tests that exercise cart creation, checkout, payment callback handling, and every order status transition you depend on. Also test against your target database, since MySQL, PostgreSQL, and SQLite can behave differently with JSON columns and collations.
- Does it support multi-currency, multi-store, or multi-warehouse?
- Multi-currency, multi-store, and multi-warehouse support are not documented for this release, so treat them as absent until you confirm otherwise in the code or with the maintainers. If your business requires them, that is a first-class evaluation question rather than a configuration detail. Pricing stored in integer minor units versus decimals is also worth verifying early.
- How does this compare to alternatives, and what is the maintenance and upgrade path?
- Compared with building commerce logic from scratch or adopting a larger Laravel ecommerce platform, this module is attractive when you are already on TomatoPHP and Filament and want catalog, cart, and order screens quickly. Maintenance risk sits in the Filament coupling and the absence of a published deprecation policy for 1.x, so ask the maintainers what the upgrade path is. Review the license and commercial support terms before committing.
Weaver
How can I help you explore Laravel packages today?