Melba andCtuit / Restaurant365 — better together
What is Ctuit / Restaurant365?
Ctuit was founded as a restaurant business intelligence and analytics platform, built specifically for multi-unit US operators who need consolidated visibility across dozens or hundreds of sites. Restaurant365 acquired Ctuit in 2019 and has since folded its capabilities into a broader restaurant ERP. Today the combined R365 platform covers:
- Sales and labor performance dashboards fed directly from POS systems (Toast, Square, Aloha, Micros, NCR Voyix, and others)
- Inventory and food cost reporting — theoretical vs. actual variance, depletion analysis, period-over-period comparisons
- Recipe costing and menu engineering analytics tied to purchasing and invoice data
- Multi-unit financial reporting — P&L by location, by region, by brand — with GL, AP, and AR integrations (QuickBooks, Sage Intacct, and others)
- Labor scheduling, tip management, and payroll exports
- Franchise and multi-concept operators: consolidated brand-level reporting with site-level drill-down
R365 is a serious platform with deep roots in US foodservice finance and operations. Its target audience is restaurant groups with multiple locations, a dedicated finance or controller function, and a US-centric POS stack.
R365 owns the reporting layer. Melba owns the kitchen layer.
Recipe costing from Melba feeds R365's theoretical food cost analysis
HACCP, traceability, and EU compliance — handled in Melba
Ctuit / Restaurant365 is a proven platform for US multi-unit restaurant finance and analytics. Melba is a proven platform for kitchen production, recipe management, and food safety. If your operation runs R365 for its financial backbone and you are looking for a dedicated kitchen layer — for recipe costing, production planning, HACCP, or European compliance — Melba is designed to sit alongside R365 as the kitchen-side complement, not to replace it.
Frequently asked questions
Yes — and this is the configuration that makes the most sense for multi-unit groups that already rely on R365 for financial reporting and labor analytics. The two platforms operate at different layers: R365 handles the back-office and POS data layer (P&L, AP, labor scheduling, sales reconciliation), while Melba handles the kitchen production layer (recipes, food cost, batch production planning, HACCP documentation). There is no functional overlap that forces a choice between them. Running both means your finance team keeps the R365 dashboards they already know, while your kitchen teams get a dedicated tool built around how they actually work.
There is no native connector between Melba and Restaurant365 today. R365 does expose an API for sales and inventory data, and Melba supports CSV imports for recipes, ingredients, and cost data. The practical workflow most operators use is a periodic CSV export of recipe costs from Melba into R365 to update theoretical food cost baselines — typically once a week or whenever a major price change hits a key ingredient. A direct API integration is on the roadmap; if this is a priority for your group, mention it when you book a demo so our team can flag your use case.
Three operator profiles benefit most. First, US multi-unit groups that run R365 for finance but manage recipes in spreadsheets — Melba replaces the spreadsheet layer with a purpose-built recipe and cost engine that feeds cleaner data back into R365's variance reports. Second, restaurant groups with European sites (or expanding into Europe) who need HACCP documentation, EU allergen labelling, and CIQUAL nutritional data that R365 doesn't provide. Third, central kitchen operators — commissary kitchens, ghost kitchen networks, catering groups — who need production batch planning and traceability at the production level while the parent group's financials live in R365.
