From channel to back office, in six steps.
- 01
An order arrives from a channel
A customer places an order on Glovo, Uber Eats, Just Eat, Deliveroo, the restaurant's direct site, a QR menu, or a kiosk. The marketplace or direct platform delivers the order payload to Sinqro through a connector — product list, modifiers, special requests, channel, order type (delivery / pickup / dine-in), customer details, and the price the channel charged. The connector is bidirectional: it also listens for menu updates, channel-pause commands, and status returns.
- 02
Order Hub centralizes and resolves it
Order Hub takes the inbound order, resolves the menu mapping (channel product → POS product), normalizes modifiers, applies channel-specific pricing rules, and places it in the unified inbox. The Work App shows it to the team on the floor, color-coded by channel and labeled with type, status, prep timer, customer name, and total. The team accepts, edits, or rejects it from a single screen.
- 03
Order Hub hands off to the POS
Once accepted, Order Hub pushes the order into the restaurant POS (Revo, Square, ICG, Agora, Lightspeed, Hosteltáctil, or another supported system) as if a member of the team had typed it. The POS prints to the right station, fires to the kitchen, and tracks the ticket exactly as it would for a counter order. Status changes in the POS (preparing, ready, dispatched) flow back to Order Hub and the originating channel so the marketplace UI shows the right state to the customer and the courier.
- 04
Data Sync moves the data downstream
When the ticket closes, Data Sync collects the final POS record, the marketplace settlement metadata, the payment method, the channel attribution, and the modifiers — and routes them downstream. Sales totals and tax breakdowns land in accounting (Holded, Sage, A3, Quaderno). Stock movements update the stock platform. Channel-attributed sales feed BI dashboards (Looker, Metabase, custom data warehouses) and analytics. Reconciliation becomes a derived check, not a manual closing-day task.
- 05
Automations close the operational loops
Sinqro Automations runs rules against the live data: pause Just Eat when the kitchen crosses a saturation threshold; mark a product sold-out across every channel when stock drops below a threshold; route orders to a specific kitchen station based on the modifier mix; alert the operations team when a marketplace channel produces an anomalous rejection rate. Automations are configured per venue or per brand and execute on the same connected data the rest of Sinqro uses.
- 06
Dashboard runs the multi-venue picture
Sinqro Dashboard is the back-office surface where operators configure accounts, venues, brands, integrations, billing, users, automations, and reporting. Multi-venue groups (chains, franchise networks, multi-brand operators, hotel groups) see every venue in one operational view and configure changes once for many. Work App and Rider App are the on-the-floor surfaces that the team uses during service — same data, different context.