A full-service restaurant POS built on your Magento 2 / Adobe Commerce store, with floor-plan table management, a Kitchen Display System (KDS) and bar screens, course firing, split/merge bills and per-seat ordering. Custom-built, installed and supported by ECOSIRE. One-time license from $799.00 USD for Magento 2 / Adobe Commerce (build-to-order) — includes 12 months of updates and support.

A full-service restaurant POS built on your Magento 2 / Adobe Commerce store, with floor-plan table management, a Kitchen Display System (KDS) and bar screens, course firing, split/merge bills and per-seat ordering. Custom-built, installed and supported by ECOSIRE.
Keine Zahlung jetzt. Dies sendet eine Angebotsanfrage an unser Team – wir melden uns per E-Mail mit Preisen und nächsten Schritten.
Magento 2 Restaurant POS & KDS turns your existing Magento Open Source or Adobe Commerce store into a working front-of-house and kitchen operation, so the catalog, customers, pricing rules and orders you already manage online also drive your dining room and your line.
Floor-plan and table management modeled as a dedicated entity with open / seated / billed states, driven by Magento events and observers
Real-time Kitchen Display System (KDS) and bar display screens fed by REST/GraphQL endpoints and Magento message queues - no paper chits
Course firing so appetizers, mains and desserts hit the line in sequence instead of all at once
Order modifiers, combos and menu options built on Magento custom options and configurable/bundle product logic
Split bill, merge tables and per-seat ordering handled by service classes wired through di.xml
Quick-service and full-service modes toggled in system.xml configuration, gated by admin ACL
This is not an instant Marketplace download. ECOSIRE builds the extension to fit your floor plan, menu structure and printers, then installs it on your Magento install and supports it. The POS ships as a versioned module under app/code/Ecosire/RestaurantPos, registered through registration.php and a module.xml with explicit sequence on Magento_Sales, Magento_Catalog and Magento_InventorySales. Orders are written through the native OrderRepositoryInterface service contract, so a dine-in ticket is a first-class Magento order — visible in the admin grid, reportable, and refundable like any web order.
The floor plan is modeled as its own entity with open, seated and billed states; table actions raise events that observers translate into order and reservation updates. The Kitchen Display System and bar display are real-time screens fed by a dedicated REST/GraphQL endpoint and Magento message queues, so a fired course reaches the line without a paper chit. Course firing, order modifiers, combos, split bill, merge tables and per-seat ordering are handled by service classes wired via di.xml, with plugins/interceptors layered over core checkout logic rather than overriding it. Quick-service and full-service modes are a config toggle in system.xml, gated by admin ACL so only authorized roles change service settings.
Everything respects your store: tax rules, store views, customer groups and inventory all flow through Magento's own stack. You get a clean, upgrade-safe codebase — no core hacks — that ECOSIRE keeps current as your menu and your Magento version evolve.
Runs a sit-down venue and needs table-by-table service: floor plan, course firing, split and merged checks, and a KDS that keeps the kitchen in sync with the dining room - all tied back to the Magento catalog and reporting they already use.
Wants fast counter ordering with modifiers and combos in quick-service mode, while still capturing every sale as a Magento order so online and in-store revenue live in one system.
Already runs eCommerce on Magento Open Source or Adobe Commerce and wants front-of-house and kitchen operations on the same platform instead of bolting on a disconnected third-party POS, keeping menu, pricing and inventory unified across store views.
Kaufen Sie die Lizenz auf ecosire.com und laden Sie die ZIP-Datei des Magento 2 Restaurant POS & KDS-Moduls von Ihrem Konto-Dashboard herunter.
Extrahieren Sie die ZIP-Datei in Ihren Odoo-Ordner für benutzerdefinierte Add-ons auf dem Server (oder laden Sie sie über „Apps“ > „Aus Datei installieren“ auf Odoo.sh/Runbot hoch).
Aktivieren Sie den Entwicklermodus, öffnen Sie „Apps“, klicken Sie auf „Apps-Liste aktualisieren“, suchen Sie nach „Magento 2 Restaurant POS & KDS“ und klicken Sie auf „Installieren“.
Öffnen Sie das neue Menü, fügen Sie Ihren ECOSIRE-Lizenzschlüssel ein, verbinden Sie alle externen Anmeldeinformationen (Shopify, Amazon, Stripe usw.) und speichern Sie.
Führen Sie den integrierten Verbindungstest aus, synchronisieren Sie Ihre ersten 10 Datensätze und planen Sie den wiederkehrenden Cron. Wenden Sie sich an den Support, wenn etwas fehlschlägt.
| Kriterium | ECOSIRE | Benutzerdefinierter Build | Konkurrent | Odoo Native |
|---|---|---|---|---|
| Dine-in tickets stored as native Magento orders (service contracts, admin grid, reporting) | ||||
| Floor-plan / table management with open, seated and billed states | ||||
| Real-time KDS and bar display screens fed by REST/GraphQL + message queues | ||||
| Course firing, split bill, merge tables and per-seat ordering | ||||
| Built to your floor plan, menu and printer layout (not generic) | ||||
| Upgrade-safe (plugins/observers/service contracts, no core overrides) | ||||
| Installed and configured on your Magento instance by the vendor | ||||
| Ongoing bug-fix and Magento-version compatibility support | ||||
| Available as an instant self-service download |
No. Magento 2 Restaurant POS & KDS is built to order. ECOSIRE develops the module to match your floor plan, menu and printer layout, then installs it on your Magento Open Source or Adobe Commerce instance. There is no self-service Marketplace download - you get a custom build, installed and supported on your own store.
A typical build, install on staging, configuration and go-live runs about 3 to 5 weeks, depending on the complexity of your floor plan, menu structure, modifier rules and printer/KDS station setup. After purchase we schedule a short scoping call, confirm the spec, then build against your staging environment before touching production.
Every build includes a post-launch support window covering bug fixes and compatibility maintenance as you upgrade Magento or Adobe Commerce. Because the extension uses plugins, observers and service contracts instead of core overrides, version upgrades stay low-risk. Extended support and enhancement retainers are available if you want a longer engagement.
Yes. The module is written against standard Magento 2 APIs - service contracts, di.xml, plugins, events and message queues - so it runs on both Magento Open Source and Adobe Commerce. On Adobe Commerce it can take advantage of edition-specific features where relevant; the core POS, KDS and table management work the same on both.
They are real Magento orders. Tickets are written through the native OrderRepositoryInterface, so a dine-in check appears in the standard sales order grid, respects your tax rules and customer groups, draws down inventory through Magento's stack, and can be refunded or reported on like any web order. Front-of-house and online share one source of truth.
In most cases, yes. The KDS and bar displays are browser-based screens served by REST/GraphQL endpoints, so they run on standard tablets, mini-PCs or smart displays on your network. During scoping we confirm your station layout and map each screen to the right kitchen or bar area and printer.
A full-service restaurant POS built on your Magento 2 / Adobe Commerce store, with floor-plan table management, a Kitchen Display System (KDS) and bar screens, course firing, split/merge bills and per-seat ordering. Custom-built, installed and supported by ECOSIRE.