POS and ERP integration connects your business data directly to digital screens — menu boards that update prices from the POS system, sales dashboards driven by ERP data, inventory displays that show stock levels in real time, and production line KPIs from manufacturing systems. SpinetiX players consume business data through REST APIs, CSV exports, and database feeds, rendering it in branded templates without middleware or custom development.
POS Integration
Automated Menu Boards
Menu items, prices, descriptions, images, allergen info, and calorie counts come from the POS system. SpinetiX menu board templates render this data beautifully. When the kitchen runs out of an item, the POS marks it unavailable — the menu board hides it instantly. No staff member touches the signage.
Order Confirmation Displays
Drive-through and counter order confirmation screens show the order in real time as items are entered into the POS. The customer sees item names, quantities, prices, and running total. Integration uses a POS callback or shared data file that updates with each transaction.
Kitchen Display System (KDS)
Back-of-house screens show the order queue from the POS — orders in progress, preparation time, and order status (new, preparing, ready). Kitchen staff see a clear queue prioritized by order time. Average preparation times display as KPIs for kitchen performance management.
ERP Integration
Sales Dashboards
Corporate dashboards display real-time sales data from the ERP: daily/weekly/monthly revenue, top-performing products, regional comparisons, and target vs actual. SpinetiX renders these as visual dashboards with charts, gauges, and trend indicators. Data refreshes every 5–15 minutes.
Inventory and Warehouse
Warehouse and logistics screens show inventory levels, picking queue status, and shipment tracking. Data comes from ERP warehouse modules. Critical stock alerts (below reorder point) display on management screens with escalation indicators.
Integration Patterns
| System | Data Path | Display Use Case | Refresh |
|---|---|---|---|
| POS (menu) | API → JSON → Player | Menu board, prices | Real-time |
| POS (orders) | Callback → shared file | Order confirmation | Per-transaction |
| ERP (sales) | OData API → HUB → Player | Sales dashboard | 5–15 minutes |
| ERP (inventory) | Database view → CSV → Player | Stock levels | 15–30 minutes |
| ERP (production) | API → JSON → Player | Production line KPIs | 1–5 minutes |
Key Parameters
| Parameter | Value | Why It Matters |
|---|---|---|
| POS systems | Oracle MICROS, Square, Toast… | Universal compatibility |
| ERP systems | SAP, Oracle, Dynamics | Enterprise data connectivity |
| Data format | JSON, XML, CSV | Standard formats, no custom parsers |
| Auth via HUB | OAuth, API key, cert | Secure credential management |
| Out-of-stock | Auto-hide from menu | No manual menu updates |
Common Mistakes
- Displaying raw ERP data. A field titled "MAT_GRP_2_REV_CUM_MTD" on a lobby dashboard confuses everyone. Transform and label ERP data into human-readable metrics before display.
- Menu board not linked to POS. A "digital" menu board that requires manual price updates defeats the purpose. Always connect the menu board to the POS data source — instant updates, zero manual effort.
- No data validation. If the POS exports a corrupted price (0.00, negative, or absurdly high), the menu board shows it. Add validation rules in the template — flag suspicious values instead of displaying them.
- Over-exposing business data. A sales dashboard showing revenue figures on a public lobby screen exposes confidential data. Ensure sensitive dashboards are on private screens only (management offices, control rooms).