How Kasibeyaz took control of food cost — and got 2 weeks of their month back
A Dubai-based restaurant group replaced a legacy ERP and spreadsheet-driven processes with EYP Ops — and within a quarter, month-end close dropped from a two-week ordeal to a two-day routine.
[Placeholder metrics — Eyüp will confirm exact figures and time period before publish]
“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 two outlets
Kasibeyaz had been running two outlets — Downtown and Marina — 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 two weeks. By the time the food cost figure was on the owner's desk, the month being discussed was almost three weeks 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 Orion 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 two weeks, every incoming invoice had a corresponding PO, and the 3-way match rate hit 100%.
INVENTORY followed: stock moves for every kitchen and bar location, opening balances imported from Orion 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. The team was trained over approximately one week. From week two onward, 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 had a one-week parallel run before the previous system was deprecated.
Measurable from the first month
[Placeholder — Eyüp to confirm all figures and measurement period before publish]
- Month-end close reduced from 2 weeks to 2 days
- Food cost variance visible daily — not after a 2-week lag
- Zero ledger mismatches in 3 months of live operation
- 100% invoice to PO 3-way match on delivery
- ~2–3 percentage points food cost improvement
- Waste and staff meal tracked at source, per location
- Recipe cost captured at post-time — immutable for audit
- AP aging visible in real-time; late payments eliminated
The roadmap ahead
Third outlet rollout
Expanding EYP Ops to a third Kasibeyaz location — same ledger, same 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 demo or try the sandbox at demo.eypops.cloud. We'll walk you through EYP Ops using your own outlet structure and supplier base — no generic slides.