Weave Code
Filament Pos Laravel Package
tomatophp/filament-pos
A complete point-of-sale system for FilamentPHP: manage products, orders, payments, and receipts through a fast, intuitive interface. Supports barcode scanning, multiple payment methods, and printable invoices—ready to drop into any Laravel admin panel.
Filament POS is a complete point-of-sale plugin for Filament that turns your admin panel into a fast, cashier-friendly sales terminal. Built on Laravel, it lets you browse products, build a cart, and complete payments without leaving your existing Filament panel.
- Product search & cart with quick-add support
- Multiple payment methods with cash/change handling
- Invoices & receipts generated for every sale
- Customers & inventory integrated out of the box
- Responsive, RTL-ready UI for touchscreens
Frequently asked questions about Filament Pos
- How do I install filament-pos in my Laravel application?
- Install it with composer require tomatophp/filament-pos, then publish the config and migrations and run php artisan migrate. Register the plugin in the plugin array of the Filament panel you want the register to appear on. Because it is a panel plugin and not a standalone app, all routes and the cashier UI render inside your existing admin panel. Confirm the exact publish tags against the package source before running migrations anywhere near production.
- Does filament-pos require Ecommerce Builder to work?
- Yes. Filament POS layers a cashier and checkout surface on top of tomatophp/filament-ecommerce, so products, prices, and orders are read from that catalog. Installing the POS therefore means adopting a two-package commerce schema, which is a platform decision rather than a simple feature toggle. If Ecommerce Builder is not already your system of record, evaluate that commitment first. Verify from source which tables a completed sale actually writes to before you commit.
- Which Laravel, PHP, and Filament versions does filament-pos support?
- The package targets Laravel 10 or 11, PHP 8.2+, and Filament v3 or newer. Pin Filament, Ecommerce Builder, and filament-pos to exact versions and upgrade them as a single unit, because independent minor version drift can break the admin panel with a confusing stack trace. Always check the composer.json constraints in the repository for the authoritative support matrix.
- Can Filament POS process credit card payments?
- No. The payment methods are almost certainly tender recording such as cash, card, or transfer rather than real card processing, so cash and change handling works but no payment service provider is wired in. Any Stripe, terminal, or gateway integration is yours to build behind an adapter. Validate that assumption in the source before you price the work.
- Does filament-pos support refunds, discounts, and tax lines?
- Refunds, discounts, tax lines, and cash-drawer management are exactly the features most likely to be advertised rather than fully implemented. Read the migrations and the checkout action to see what is actually persisted and calculated. If a capability is missing, decide up front whether you will add it at your adapter boundary or fork the package. Budget for that work explicitly instead of discovering it mid-pilot.
- Can two cashiers oversell the same stock at the same time in Filament POS?
- This is the highest technical risk in the package. A server-rendered Livewire register that reads stock and then writes a decrement can oversell when two terminals or two browser tabs check out simultaneously. Look for a database transaction with row-level locking or an atomic decrement in the checkout path. If neither exists, add it at your adapter boundary before any pilot.
- Does Filament POS work with receipt printers, barcode scanners, and cash drawers?
- Receipt printing, cash-drawer kicks, and barcode scanning normally require a local bridge or a browser peripheral API, and nothing in this package suggests that problem is already solved. Prove each device on the actual counter hardware in week one rather than in the demo. If hardware support does not hold up, descope to order entry with emailed or PDF receipts and price the project accordingly.
- Does filament-pos work offline if the store Wi-Fi drops?
- No. Every cart action is a synchronous Livewire round trip to your server, so flaky store connectivity is felt immediately by cashiers. There is no offline queue or local persistence in this package. If your venue has unreliable Wi-Fi, treat that as a blocker or plan a manual fallback process for staff.
- Can I use Filament POS across multiple store locations with Filament tenancy?
- It is not documented whether the plugin wires into Filament's tenancy primitives or requires a parallel scoping scheme of its own. Verify that products, orders, and stock levels scope correctly per location before committing to multi-store use. If scoping is absent, you will need to build that layer yourself, which changes both effort and exit strategy.
- Is filament-pos production-ready and actively maintained?
- Treat it as unproven. It has a low star count, no downstream dependents, and release metadata that needs independent verification, so no community is surfacing bugs before you do. Run a timeboxed two-week spike with the three packages pinned, one register, one cashier, a small real catalog, and an end-to-end sale through tender and receipt. MIT licensing means fork-and-own is credible, but only if you keep the integration thin and avoid editing vendor files.
Weaver
How can I help you explore Laravel packages today?