Replace paper kitchen tickets with live, station-routed prep screens inside Business Central — built, installed and supported by ECOSIRE as a per-tenant AL extension. Built to order by ECOSIRE for Dynamics 365 BC (build-to-order) — indicative price from $499.00 USD; request a quote for a scoped proposal.
イメージプレビューReplace paper kitchen tickets with live, station-routed prep screens inside Business Central — built, installed and supported by ECOSIRE as a per-tenant AL extension.
自分での設定は不要 — ECOSIRE が構築・インストール・サポートする実働アプリです。
一回限りの構築料金から始めます。キックオフで一緒に範囲を決めます。
ECOSIRE がお客様の Dynamics 365 Business Central 上で構築・設定・インストールします。
約2〜4週間で稼働し、リリース後のサポート期間が付きます。
The Kitchen Display System (KDS) turns your Microsoft Dynamics 365 Business Central environment into a paperless, timed kitchen operation. The moment an order lands in Business Central — from your POS, retail front-end, or an online channel writing through the BC REST/OData API — it appears on the relevant station screen with its lines, modifiers, allergen flags and a running prep timer.
This is a build-to-order extension, not an instant AppSource download. ECOSIRE designs, builds and installs KDS as a per-tenant AL extension directly on your Business Central environment (cloud/SaaS or on-prem), then supports it. Because it ships per-tenant rather than through the public marketplace, we can route orders to your station layout, match your menu structure, and honor your prep workflow instead of forcing a generic template.
Technically, KDS is delivered as a set of table and page extensions plus an AL event-subscriber layer. When a sales document or POS order is posted or released, an event subscriber projects its lines into a KDS order table, applies your routing rules (by item category, kitchen station, or course), and pushes status changes. Station screens are BC pages (or a lightweight web client served from BC data via OData) that support bump-bar and touch ready-to-serve actions. Color-coded SLA timers escalate late tickets. A job queue entry can sweep stale or abandoned orders. Permission sets isolate kitchen-staff access from back-office finance, and order/station data can optionally surface in Dataverse / Power Platform for Power BI kitchen-throughput dashboards.
You keep one source of truth — Business Central — for orders, inventory consumption and reporting, while the kitchen finally works off screens instead of paper.
Wants paperless, timed kitchen flow tied to the same ERP that already runs orders, inventory and reporting — no separate disconnected KDS appliance to reconcile.
Runs multiple virtual brands and channels through one Business Central tenant and needs orders routed to the right station instantly, with SLA timers to keep delivery prep on track.
Needs the kitchen solution delivered as a clean per-tenant AL extension with proper permission sets, job queue hygiene and a documented upgrade path — not unmanaged customizations.
| 基準 | エコシエール | カスタムビルド | 競合他社 | オドゥー ネイティブ |
|---|---|---|---|---|
| Live, real-time order display tied to Business Central data | 付属 | 付属 | 部分的なサポート | |
| Per-station routing by category, course or kitchen station | 付属 | 部分的なサポート | 部分的なサポート | |
| Color-coded SLA timers and late-order escalation | 付属 | 部分的なサポート | 付属 | |
| Bump-bar / touch ready-to-serve actions | 付属 | 部分的なサポート | 付属 | |
| Modifier and allergen highlighting from item data | 付属 | 部分的なサポート | 部分的なサポート | |
| Delivered as a clean per-tenant AL extension with permission sets | 付属 | 部分的なサポート | 付属 | |
| Configured to your menu, stations and workflow (not a fixed template) | 付属 | 付属 | 含まれていない | |
| Built, installed and supported for you with BC upgrade compatibility | 付属 | 含まれていない | 部分的なサポート | |
| Optional Dataverse / Power BI throughput dashboards | 付属 | 部分的なサポート | 部分的なサポート |
Because KDS is build-to-order, there is an honest lead time. Typical delivery is around 3 to 5 weeks from kickoff: a short discovery on your stations, menu and routing, then the build, a sandbox install for you to test, and finally production deployment. Timelines vary with the number of stations, channel integrations (POS/online ordering) and whether you want the Dataverse/Power BI layer. We confirm a dated schedule before work starts.
No. KDS is not a public AppSource app you self-install. ECOSIRE builds it and installs it as a per-tenant extension directly on your Business Central environment. That is deliberate — it lets us fit your station layout, menu structure and prep workflow instead of shipping a one-size-fits-all template.
An AL event subscriber fires when a sales/POS order is posted or released, projecting its lines into a dedicated KDS order table and applying your routing rules. External channels (online ordering, third-party POS) can write orders in through the Business Central REST/OData API. Station pages reflect status changes live, and a job queue entry sweeps stale tickets.
Every build includes a post-go-live support window, and we offer ongoing support and maintenance afterward. Because it is a per-tenant extension, ECOSIRE keeps it compatible across Business Central monthly and major version upgrades, fixes issues, and ships enhancements you request. You also receive the source code, so you are never locked out of your own solution.
Yes, within scope agreed at discovery. KDS ingests orders from POS or online channels via REST/OData and reads modifiers and allergen flags from your item attributes and order lines. During the build we map your menu, modifiers and allergens so cooks see accurate special instructions and risk highlighting on every ticket.
A build-to-order AL extension that brings Adyen's 150+ global payment methods and unified settlement reconciliation into Business Central accounts receivable, complementing the first-party D365 Commerce Adyen connector.
Replace paper kitchen tickets with live, station-routed prep screens inside Business Central — built, installed and supported by ECOSIRE as a per-tenant AL extension.