Demand Intelligence
Restaurant demand forecasting that turns into ingredient requirements.
Neumas uses a canonical demand model for restaurants, hotels, and catering, then translates menu-item demand through active recipe versions into ingredient requirements.
1. Explainable baseline
Forecasts start with recent moving average, day-of-week seasonality, weighted historical demand, trend, and explicit event or promotion uplift where signals exist.
2. Confidence
Confidence is calculated from history depth, recent forecast error, signal quality, data freshness, and variance, with evidence persisted for operator review.
3. Evaluation loop
Forecasts can be compared against actual sales or usage after the period, persisting MAE, MAPE where safe, bias, and confidence calibration.
Frequently asked questions
- What does autonomous procurement mean in Neumas?
- It means Neumas observes demand and inventory evidence, recommends purchasing actions, evaluates policy, routes approvals, creates traceable actions, and verifies outcomes. External supplier execution is only enabled through real provider adapters.
- How is Neumas different from inventory software?
- Inventory software tracks stock. Neumas connects stock to recipes, demand forecasts, supplier offers, purchase orders, receiving, invoices, policy, and margin outcomes.
- How does Neumas control food cost?
- Neumas calculates theoretical food cost, tracks supplier and invoice variance, records waste, reconciles purchases, and attributes margin leakage only where evidence exists.
Start with the public overview, then try the product.
Neumas keeps core company and product information public while private dashboards remain authenticated and protected.