Map
Stack audit
POS, payments, bookings, delivery, accounting, messages, and hardware are listed with owners.
Integrations and setup
Connect the tools that already touch the money.
Elyx does not start by replacing the stack. It maps the POS, payments, bookings, delivery, accounting, and staff messages that already carry the operating truth.
Inputs
POS close
Payment event
Booking change
Supplier note
Staff photo
Source-aware Operator
Same message. Different next move depending on sender, system, and policy.
Outputs
Money waiting
Deposit recovery
Stock memory
Menu margin
Capital context
What connects, what Elyx checks, what the team can act on.
This is the product. Existing tools feed one operating picture instead of another disconnected screen.
POS and till
Sales, receipts, refunds, item mix, checkout totals.
Sales rhythm, item pressure, refund patterns.
Usually read first. Write-backs stay scoped.
Payments
Deposits, failed links, settlements, unpaid balances.
Money waiting, failed payment paths, recovery timing.
Payment actions run inside restaurant rules.
Bookings
Tables, deposits, confirmations, no-show risk.
No-show risk, cover protection, waitlist demand.
Guest-facing changes follow business policy.
Delivery and ordering
Orders, channels, missed demand, tablet pressure.
Channel pressure, direct-order gaps, menu demand.
Keeps channel context attached.
Accounting and P&L
Invoices, settlements, receipts, variance.
Profit movement, cost drift, margin variance.
Finance records keep source links.
WhatsApp and staff notes
Voice notes, supplier texts, stock photos, owner instructions.
Who said what, what changed, what needs attention.
Identity changes what the Operator does next.
Setup is the product too.
We do not dump a login on the owner. We map the restaurant, set roles, connect priority systems, and launch one recovery loop first.
Connect
Read access first
Elyx starts with the signals that explain missed demand, unpaid money, stock pressure, and margin movement.
Rules
Autonomy rules
Routine loops, write-backs, refunds, payments, and guest messages get clear restaurant rules.
Launch
First recovery loop
One live loop goes first: missed calls, deposits, stock notes, supplier changes, or quiet guests.
Identity changes the action.
Owner, manager, staff member, POS event, payment event, and voice agent are not equal sources. Elyx keeps that difference attached to the memory.
Manager WhatsAppInput
We ran out of wings again.
Stock alert plus menu pressure review.
Payment eventInput
Deposit link failed.
Recovery chase with restaurant context.
POS closeInput
Sales report screenshot.
Daily leakage brief.
No blind write-backs.
Autonomy rules for sensitive moves
Source record attached to each signal
Launch one recovery loop before expanding