Features
Ten modules. One production date.
Every screen hangs off a date and a site. The number sales promised is the number the kitchen cooks, the vans carry and finance bills.
Sales and quotation
Quote with the margin on screen, not in a spreadsheet after
Every inquiry from the website, ads, social, phone and email lands in one queue with the source recorded. The pipeline runs new, qualified, menu proposed, negotiation, confirmed.
The proposal builder starts from a template or an ad hoc menu. A live cost panel shows material, labour, overhead, packaging and transport per head as you add dishes. Quotes below the floor margin go to a manager for approval.
- Alternative dishes by cuisine, budget and preference
- Availability check on every line before the quote leaves
- One click on confirmation creates the order, work orders, requisition and proforma
Live cost
Material22.85
Labour5.03
Overhead2.74
Packaging and transport2.08
Cost per head32.70
Price per head45.00
Margin 27.3%, above the 22% floor
Inventory and procurement
Buy exactly what the schedule needs
Requirement planning explodes confirmed orders into gross demand by item and date, nets off stock on hand and open purchase orders, and respects lead time. Requisitions group by supplier and cycle.
Daily, weekly and ad hoc cycles run side by side. A phone buy is recorded in under a minute. Goods receipt checks temperature and quality, creates the batch and runs a three-way match against the supplier invoice.
- Live availability on every proposed dish
- Direct-to-site or central kitchen routing per item
- Supplier records, price lists, on-time and quality scores
Capacity
A date is sellable only when all four constraints clear
Equipment hours by section, labour hours by section, storage volume and vehicle trips are evaluated for every date. The binding constraint is named and the headroom is a number, not a feeling.
The forward calendar shows open, filling, tight, committed and blackout states. Urgent requests above capacity are blocked with the reason, alternative dates proposed, and an override needs two named approvals.
- Weekday and weekend volume profiles
- Staffing requirement derived from production hours
- Equipment conflicts flagged before they reach the kitchen
Kitchen and HACCP
Batch sheets by section, scaled and timed
Work orders are generated per date, meal period and section from the locked schedule. Each line carries the scaled ingredient list, the site breakdown and packing instructions. Yield and wastage are captured at the station.
Critical control points, temperature logs, retained samples, cleaning schedules and hygiene declarations are recorded where the work happens. Every container label traces back to the batch, the goods receipt and the supplier lot.
- Kitchen tablet works offline for a full service day
- Non-conformance from a complaint to the lot in under a minute
- Audit packs for Dubai Municipality on demand
Chicken thigh63.6 kg
Basmati rice42.4 kg
Onion, fried8.5 kg
Yoghurt6.4 kg
Biryani masala1.06 kg
Saffron water0.42 l
Batch 2 of 3
424
portions, start 09:10
Core temp 76 C
CCP pass, 09:52
Label L2609000412
Aster Mankhool, 40 portions, use by 15:00
Logistics
Twenty vehicles, three meal runs, every container scanned
Trips are planned per meal period and temperature class, clustered by zone with delivery windows and vehicle capacity respected. Loading is in reverse drop order so the first stop is at the door.
The driver app shows the route, the load check and proof of delivery with signature, photo and location. Sites see the ETA. Direct-to-site supplier deliveries and returnable assets are tracked in the same place.
- Vehicle breakdown reassigns the remaining stops
- Fleet register with insurance, registration and service dates
- Driver app in English, Arabic, Hindi and Malayalam
- 1Aster Mankhool06:30delivered
- 2Aster Al Qusais06:55delivered
- 3Medicare Al Safa07:20arrived
- 4Gulf Marine HQ07:45pending
People
Staff the shifts the production plan demands
The staffing requirement comes from standard times and a productivity factor, by section and date. Rostering assigns people with the right skills and certificates, respecting rest hours and weekly maximums, and shows the gap.
Attendance by biometric or geofenced app, leave, swaps and document expiry alerts at 90, 60 and 30 days. Approved hours export to payroll.
- Visa, Emirates ID, food handler and health card expiry alerts
- Call-in list of off-shift staff with the right certification
- Payroll boundary: hours out, no salary calculation inside
Thursday gap
Need 296 hours, rostered 272
4 certificates
Food handler cards expire in 30 days
Point of sale
Entitlements, subsidies and cash at the same counter
Staff entitlement by badge, subsidised sale, cash sale, mess count, group dining, pre-order and department bulk. Weight-based pricing with a scale, UAE VAT receipts, and a shift close with cash variance.
The terminal serves from a local cache when the network drops. Transactions queue and sync, and offline entitlement exposure is capped so the risk is bounded.
- Every sale becomes a consumption record for billing
- Resale items reduce site stock
- Android terminal or Windows till with standard peripherals
Simplified tax invoice
Mise Demo Catering LLC
TRN 100987654300003
Chicken biryani18.00
Raita3.00
Water 500 ml1.00
Subtotal22.00
VAT 5%1.10
Total23.10
Badge 48211 entitlement18.00
Hospital subsidy 50%2.55
Card2.55
Recorded offline, queued for sync
Finance
Invoices from what was confirmed and what was consumed
Six billing models: per meal, fixed monthly, minimum guarantee plus variable, per event, cost plus fee and rate card. Each invoice carries a backing statement by date, site and payer, with approved variations and credits.
Receivables ageing, VAT at 5% with zero-rated and exempt codes, bilingual tax invoices and native connectors for Zoho Books, QuickBooks, Xero, Tally and a generic REST and CSV path.
- Proforma raised on quote confirmation
- Contract profitability with food, labour, transport and overhead
- VAT return working file by period
Subtotal
965,760
VAT 5%
48,288
Posted to Zoho
1,014,048
Reporting
Forecast, variance and capacity are the spine
Role dashboards for executives, sales, chefs, procurement, operations, finance and site supervisors. Thirteen core reports with drill-down to the transaction, CSV export and scheduled email.
Meal count forecasting from contracted headcount and weekday profiles, corrected by actuals, holidays and the Ramadan calendar, with accuracy tracked. Food cost variance split into price and usage. Menu engineering by popularity and margin.
- Custom report builder over published fields
- Read-only API for your own BI tool
- Compliance pack on demand
Forecast error
2.1% MAPE
Food cost
31.4%
Oven utilisation
82%
Security and hosting
Your data stays in the UAE
Hosting, residency, backup and security as the RFI asks for them, section 19 of the PRD.
Hosted in the UAE
Production runs in AWS Middle East (UAE) or Azure UAE North. Primary data, backups and replicas stay inside UAE borders. Private cloud or on-premise is available if your policy requires it.
Backup and recovery
Continuous transaction log backup with point-in-time recovery. Daily snapshots kept 30 days, weekly 12 weeks, monthly 7 years. RPO 15 minutes, RTO 4 hours, second availability zone for failover, DR test reported yearly.
Encryption
TLS 1.3 in transit and AES-256 at rest. Session timeout and device policy are configurable per organisation.
Identity and access
Role-based access with site and client scope. Multi-factor authentication for privileged roles, optional for everyone. Single sign-on through SAML 2.0 or OIDC against your identity provider.
Audit and data protection
An immutable audit trail on every data change. Aligned to UAE Federal Decree-Law 45 of 2021 on personal data protection, with a documented breach notification procedure.
Assurance
ISO 27001 aligned controls, annual penetration test with a summary shared with you, 99.9% monthly uptime target and planned maintenance outside service hours with 7 days notice.
Implementation
Live in 16 to 20 weeks, value from week 7
Sales and the menu core go live first. Phases 1 and 2 start while discovery finishes, which is how the 16 week floor is reached. The 20 week figure assumes full HR and multi-site POS.
- 0
Discovery and design
Weeks 1 to 3
Process mapping, configuration workshops, data templates issued, integration design signed off
Signed design document
- 1
Foundation
Weeks 4 to 7
Item master, recipes, costing engine, menu templates, client and contract setup, user roles
Costed recipe library live, quotes priced on real data
- 2
Sales and planning
Weeks 8 to 11
CRM pipeline, proposal builder, live costing, menu cycles, production schedule, capacity calendar
Sales quoting in the system, schedule generated
- 3
Supply and kitchen
Weeks 12 to 15
Inventory, procurement, goods receipt, work orders, batch tracking, HACCP records
Kitchen working from the system, procurement schedule-driven
- 4
Logistics, POS and HR
Weeks 16 to 18
Routes, dispatch, driver app, POS at one pilot site, employee records, rostering
Pilot site served end to end through the platform
- 5
Finance and rollout
Weeks 19 to 20
Accounting integration, billing cycle, POS at remaining sites, reporting suite
Full operation live, first invoice generated from system data
- 6
Hypercare
Weeks +4 weeks
On-site support, tuning, issue burn-down
Handover to standard support
Training
Delivered in English and Hindi or Malayalam as the workforce requires. A train-the-trainer track builds internal capability.
| Audience | Format | Duration |
|---|---|---|
| Sales team | Classroom plus live quoting practice | 2 days |
| Executive and section chefs | On-site, hands-on at the station | 3 days |
| Storekeepers and procurement | On-site with real receipts | 2 days |
| Operations and dispatch | Classroom plus shadowing | 2 days |
| Drivers | 45-minute app session, in groups, in the language they use | 45 min each |
| Site supervisors and POS staff | On-terminal at the counter | 1 day |
| HR and finance | Classroom plus integration walkthrough | 2 days |
| System administrators | Configuration, user management, troubleshooting | 3 days |
Support
Phone hotline, email, in-app ticket and a dedicated account manager with quarterly reviews. Business hours Sunday to Thursday 08:00 to 18:00 GST, critical cover from 04:00.
| Tier | Coverage | Response | Resolution |
|---|---|---|---|
| Critical, service stopped | 24x7 | 30 minutes | 4 hours |
| High, major function impaired | 24x7 | 2 hours | 1 business day |
| Medium, workaround exists | Business hours | 4 hours | 3 business days |
| Low, cosmetic or query | Business hours | 1 business day | Next release |
Cutover
A one month parallel run on the billing cycle, so the first system invoice is checked against the manual one. Opening stock by physical count on the cutover weekend. A rollback point at every phase.
Change management
A named sponsor, a fortnightly steering committee, departmental champions from phase 0, a communication plan before each go-live and a feedback channel with published response times.
Releases
Minor releases monthly, major quarterly, security patches as needed. Notes 7 days ahead, breaking changes 30 days ahead, never during your service hours.
RFI traceability matrix
Every requirement, mapped to a section you can read
All 24 mandatory requirements are met natively. No mandatory item requires custom development. Section numbers refer to the Mise product requirements document.
Section 4 requirements
M is mandatory, D is desirable.
| RFI ref | Requirement | Priority | PRD section |
|---|---|---|---|
| 4.1.1 | Consolidate inquiries from web, ads, social, phone | Mandatory | 6.1 |
| 4.1.2 | Generate proposals from templated or ad-hoc menus | Mandatory | 6.4, 7.3 |
| 4.1.3 | Live food cost while building a menu | Mandatory | 6.5, 7.2 |
| 4.1.4 | Invoice generation on quotation confirmation | Mandatory | 6.7, 14.2, 14.6 |
| 4.1.5 | Share finalised menu with kitchen and operations | Mandatory | 6.7, 10.1 |
| 4.1.6 | Propose alternative dishes by cuisine, budget, preference | Mandatory | 6.6 |
| 4.2.1 | Reusable menu templates linked to daily production | Mandatory | 7.3, 7.5 |
| 4.2.2 | View and select from the menu scheduled for a date | Mandatory | 7.6 |
| 4.2.3 | Rotating 4 to 5 week cycles across meal periods | Mandatory | 7.4 |
| 4.2.4 | Searchable database of 1,000 to 1,200 items including unscheduled | Mandatory | 7.1, 6.6 |
| 4.2.5 | Kitchen staff upload and maintain recipes | Mandatory | 7.8 |
| 4.2.6 | Similar menus across adjacent dates | Desirable | 7.7 |
| 4.2.7 | Recipe-level costing to raw material and portion cost | Mandatory | 7.2 |
| 4.3.1 | Real-time stock check on proposed dishes | Mandatory | 8.3 |
| 4.3.2 | Daily, weekly and ad-hoc procurement cycles | Mandatory | 8.4 |
| 4.3.3 | Direct-to-site versus central kitchen routing | Desirable | 8.5, 11.6 |
| 4.3.4 | Supplier records, pricing, purchase history for 1,000 to 1,200 SKUs | Mandatory | 8.6 |
| 4.4.1 | Forward capacity visibility by date | Mandatory | 9.1, 9.2 |
| 4.4.2 | Upcoming dates with guest counts, staffing, equipment | Mandatory | 9.3, 12.5 |
| 4.4.3 | Support 8,000 to 9,000 meals with weekday and weekend variability | Mandatory | 9.5, 19.2 |
| 4.4.4 | Dynamic linked view across all planning dimensions | Mandatory | 9.4 |
| 4.5.1 | Delivery scheduling and routing for ~20 vehicles | Mandatory | 11.2, 11.3 |
| 4.5.2 | Track kitchen-to-site and supplier direct-to-site deliveries | Mandatory | 11.5, 11.6 |
| 4.5.3 | Driver-facing mobile view | Desirable | 11.4 |
| 4.6.1 | Staffing records for ~270 employees across locations | Mandatory | 12.1 |
| 4.6.2 | Link catering volume to staffing and equipment planning | Mandatory | 12.2, 12.5 |
| 4.6.3 | Shift and roster scheduling aligned to production | Desirable | 12.3 |
| 4.7.1 | Accounting integration for automatic invoicing | Mandatory | 14.2, 14.6 |
| 4.7.2 | Open API for accounting, HR and fleet | Mandatory | 18.2, 18.3 |
| 4.7.3 | Multi-entity and multi-site reporting across segments | Desirable | 5.3, 14.5, 15.2 |
Section 5 vendor questions
Where the answer comes from.
| RFI ref | Question topic | PRD section to answer from |
|---|---|---|
| 5.1.1 | Company overview and client count | Company profile document, not this PRD |
| 5.1.2 | Purpose-built for contract catering or adapted | 2.3, 5.2, 9.1 |
| 5.1.3 | Reference clients of comparable scale | Reference sheet, not this PRD |
| 5.1.4 | Cloud, on-premise or hybrid, data residency | 19.1 |
| 5.2.1 | Inquiry to proposal to quotation to invoice to work order in one workflow | 16.1, 6.7 |
| 5.2.2 | Date-based menu templates linked to live production | 7.3, 7.5, 7.6 |
| 5.2.3 | Recipe-level real-time costing and cost inputs | 6.5, 7.2 |
| 5.2.4 | Reusing similar menus across adjacent dates | 7.7 |
| 5.2.5 | Forward capacity planning and committed-date flagging | 9.1, 9.2 |
| 5.2.6 | Live inventory check and procurement flagging | 8.2, 8.3 |
| 5.2.7 | Native fleet and delivery scheduling | 11.1 to 11.5, native |
| 5.2.8 | HR and staff scheduling native or integrated | 12, native with payroll export |
| 5.2.9 | Multiple business lines in a single instance | 5.3 |
| 5.2.10 | Reporting for meal forecasting, cost variance, capacity | 15.2, 15.3 |
| 5.3.1 | Native accounting integrations | 14.6 |
| 5.3.2 | Documented API | 18.2, 18.3 |
| 5.3.3 | Data migration support | 18.4 |
| 5.3.4 | Mobile capability and offline mode | 10.7, 11.4, 13.3, 19.5, 19.7 |
| 5.3.5 | Uptime SLA, backup, disaster recovery | 19.2, 19.3 |
| 5.4.1 | Implementation timeline at this scale | 20.1 |
| 5.4.2 | Training and change management | 20.3, 20.4 |
| 5.4.3 | Post-go-live support model | 20.5 |
| 5.4.4 | Release cadence and communication | 20.6 |
| 5.5.1 | Pricing model and indicative cost | Annexure A, not this PRD |
| 5.5.2 | One-time implementation fees | Annexure A, not this PRD |
| 5.5.3 | Contract term and data export at exit | Commercial terms, data export covered by 18.2 |
Want the matrix as a document for your response? Ask us and we will send it.
Stop planning 9,000 meals in a spreadsheet
A 45 minute walkthrough with your own menu, your own sites and your own numbers. We bring the sample data, you bring a real date.