How Metafoodx Works: From Food Scans to Production Decisions
A food scan becomes useful when it changes a kitchen decision. Metafoodx connects measurement, operational review, service decisions, and forecasting through a repeatable sequence: Measure → Understand → Act → Predict → Prevent.
This walkthrough follows the product workflows shown in our How It Works series. The graphics illustrate screens and features; their displayed quantities, recommendations, and projections are not presented as verified customer outcomes.
Measure: Give Each Food Record a Place in the Service
Start before service by recording preparation losses, spoilage, and unserved food. During service, record the food moving onto the line. After the meal, capture returned food separately. These stages answer different questions: what was prepared, what remained unserved, and what came back on plates.
The scanner workflow shows a recognized menu item and choices for Service, Compost, Donate, and Reuse. Selecting the correct destination helps preserve the meaning of the record. Donated food should not be reported as discarded food, and a compost destination does not explain why the food was left over.
Keep item names and units consistent. Follow the site's container-tare procedure, correct recognition errors, and check for missed records. Good coverage matters: an apparent fall in waste means little if the team stopped scanning part of the service.
Understand: Identify the Items That Deserve Attention
The weekly Menu Item Insights screen in the series compares items with high consumption and high overproduction. Its visible tables show weight and how frequently items appear among the top five. Those measures help the team distinguish a recurring pattern from an unusual service.
Weight is only one way to prioritize. Apply item-specific food costs to identify the financial impact. A costly protein may warrant attention even when its discarded weight is lower than that of an inexpensive side dish.
High consumption and high overproduction can occur together. A popular dish may still be prepared in oversized batches. Review demand, batch timing, and leftovers together before deciding to reduce the menu item.
Act: Decide Whether to Cook Another Batch
The mobile view gives operators a way to review consumption and overproduction during service. The decision is practical: prepare another batch, prepare a smaller batch, or hold off while checking remaining demand.
For an illustrative lunch service, suppose 80 portions have been prepared, 60 have been served, and 20 remain available. If the team expects another 15 guests and each is expected to choose one portion, another full batch is not yet supported by those assumptions. If arrivals or selection rates change, the chef can reassess. This is a simplified planning example, not a Metafoodx forecast or customer result.
Record the decision and what happened afterward. Track guest demand, remaining portions, substitutions, and stockouts alongside waste so that a smaller production quantity is evaluated against service quality.
The series also shows a freshness timer to support rotation decisions. Teams should interpret the timer within their established operating procedures; a displayed timer alone does not establish that food is safe.
Predict: Use Consumption History to Plan the Next Service
The breakfast forecast graphic shows planned quantities by menu item, preparation costs, and a recommendation to adjust prep. Its displayed 18% recommendation is an example from the graphic, not a promised reduction for every kitchen.
Before adopting a recommendation, the operator should review expected attendance, menu changes, special events, service requirements, and how representative the underlying consumption history is. Convert the forecast into an initial production plan and a clear rule for reviewing additional batches.
For catering, the series shows event tracking by banquet event order, or BEO. Keeping an event's records together provides context for planning a comparable future event. Compare guest counts, menus, and service formats before carrying a past quantity forward.
Prevent: Check Whether the Decision Reduced Overproduction
Prevention is demonstrated through a comparison. Select comparable services, document the baseline, make a defined change, and measure what happens next. Review overproduction or discarded weight per meal, item-level food cost, and service availability.
For example, if discarded ingredient cost falls from $0.60 to $0.40 per meal across comparable services, that is a $0.20 reduction per meal. At 1,000 meals, it represents $200 less discarded ingredient cost. This hypothetical calculation does not establish net savings: verify avoided purchases or production costs, then subtract the relevant project costs.
Keep environmental reporting equally clear. The sustainability graphic in the series is labeled Projected Annual Overproduction Prevention. Annual projections and CO2e, water, or car-mile equivalents should be described as estimates based on stated assumptions and conversion factors, rather than completed, independently verified savings.
Make the Workflow Repeatable for the Team
Assign responsibility for three moments: capture during the shift, review after service, and planning before the next comparable service. The scanner's English and Spanish options shown in the series can support staff using either language; onboarding should still explain item correction, destinations, and the site's recording procedures.
Begin with one station or meal period. Review missing records, choose one recurring overproduction issue, document the action, and compare the next service. Once the team can connect a record to a decision and an outcome, it has a workflow worth repeating.
