How Kasibeyaz took control of food cost — and got their month back
A Dubai-based restaurant group replaced legacy ERP and spreadsheet-driven processes with EYP Ops to bring purchase, inventory, and finance under one ledger — and stopped finding out about last month's cost problems next month.
Single ledger means no end-of-month reconciliation marathon.
Variance visible the morning after — not three weeks later.
Every delivery automatically matched against PO and invoice.
Append-only stock moves tied to source documents — no silent edits.
“Before EYP Ops, we closed the month on receipts and hope. Now we see yesterday's food cost by 9am.”
Flying blind on food cost across multiple outlets
Kasibeyaz had been running its outlets on Orion ERP for back-office financials, supplemented by a tangle of Excel sheets shared over WhatsApp. Purchasing decisions were made from memory and gut feel. Supplier invoices landed in email, got printed, signed, filed. Matching them to purchase orders happened once a month, by hand.
Month-end reconciliation took weeks. By the time the food cost figure was on the owner's desk, the month being discussed was already in the past. Variance analysis — comparing what was ordered, received, costed into recipes, and actually consumed — was impossible to run with confidence. Different team members maintained different spreadsheets, and the numbers rarely agreed.
The decision to move away from the legacy stack came down to one question: "Why am I finding out about last month's food cost problems next month?" EYP Ops was built from the inside out to answer that question — and Kasibeyaz became its first live multi-outlet deployment.
One ledger, every outlet, every move
Kasibeyaz migrated to EYP Ops in phases over Q1 2026. First came ORDERS — purchase orders, supplier management, and delivery note matching. Within the first weeks, every incoming invoice had a corresponding PO and 3-way match was running on every delivery.
INVENTORY followed: stock moves for every kitchen and bar location, opening balances imported from the legacy system via CSV, recipe costs loaded and validated against real purchase prices. Special attention went to Kasibeyaz's unique cost structure — Turkish coffee condiment recipes, shisha tobacco cost backfill across prior periods, and multi-currency handling for Dubai-based purchases paid in AED with Turkey-sourced suppliers invoicing in TRY.
FINANCE closed the loop: supplier payment aging, invoice approval workflow, and AP reconciliation. From there on, the owner could open EYP Ops each morning and see the prior day's food cost — broken down by outlet, by cost type, compared to recipe targets.
The migration path was deliberate: start with ORDERS (highest immediate pain), then INVENTORY (unlock daily cost visibility), then FINANCE (close the AP loop). Each phase ran in parallel with the previous system before deprecation.
What changed in the first quarter
- Month-end close runs against a single source of truth, not reconciled spreadsheets
- Food cost variance visible the next morning instead of weeks later
- Append-only stock ledger — every move tied to a source document, no silent edits
- Automated 3-way match on every delivery (PO ↔ delivery note ↔ invoice)
- Theoretical vs. actual cost variance per recipe, per location, per day
- Waste, staff meal, and transfers tracked at source with location scope
- Recipe cost captured at post-time and immutable for audit
- Real-time AP aging — supplier balances and overdue exposure visible at a glance
How Kasibeyaz rolled out EYP Ops
- Day 1
Opening count session
First operational session: opening count across all active locations. Modules used: INVENTORY (count session) + ITEMS (catalog).
- Wk 1
Supplier ledger + opening AP balances
Supplier records loaded with opening AP balances. Modules used: ORDERS (suppliers) + FINANCE (AP).
- Mo 1
First period close
First operational month-end: invoices reconciled, period locked, food cost variance reviewed by outlet. Modules used: INVENTORY + FINANCE + REPORTS.
- Mo 3
Variance reconciliation + recipe coverage expansion
Mid-cycle: theoretical-vs-actual variance reconciled, recipe coverage expanded across menu. Modules used: REPORTS (variance) + RECIPES.
- Mo 5+
Active in production since January 2026 close
Live since January 2026 close. Active modules: ORDERS + INVENTORY + FINANCE + REPORTS. Daily food cost visibility, automated 3-way match, append-only audit trail across all outlets.
The roadmap ahead
Outlet expansion
New Kasibeyaz locations rolling out on the same ledger and audit trail — zero additional back-office headcount.
Live POS feed
Moving from daily CSV imports to a live POS integration — recipe cost and COGS calculated in real time as orders close.
Cloud kitchen spin-off
A new dark kitchen brand spun from the Kasibeyaz commissary kitchen will launch on EYP Ops from day one.
Want to see EYP Ops in action?
Book a guided demo and we'll walk you through EYP Ops using your own outlet structure and supplier base — no generic slides.