1. Define the dish target before writing parameters
A machine program needs a clear target: flavor, texture, color, moisture, portion size and serving scenario. If the target is vague, the program may repeat the wrong result consistently.
Recipe Digitization
Use this guide to understand how a chef's dish becomes a repeatable machine program with dish targets, heat stages, seasoning checkpoints, validation records and store deployment.
Short answer
The useful starting point is not a written recipe alone. Buyers should prepare dish photos, current chef process, batch size, ingredient order, sauce timing, texture target and service scenario. YAO MASTER then evaluates whether the dish can be converted into a repeatable program for YG-B01 or YG-B01-Pro.
A machine program needs a clear target: flavor, texture, color, moisture, portion size and serving scenario. If the target is vague, the program may repeat the wrong result consistently.
Experienced chefs describe actions like hot wok, quick toss, reduce sauce or finish until glossy. Digitization turns those ideas into ingredient order, heat stage, timing, rotation, seasoning amount and sauce checkpoints.
A recipe should not be deployed only because it runs on the machine. It should be tasted, adjusted, versioned and approved so operators know which program is official and which version is still in testing.
Workflow
Use this as a checklist before sending your menu for automation review.
| Step | What is structured | Buyer should prepare |
|---|---|---|
| Dish target | Flavor, texture, color, portion and plating goal. | Dish photos, benchmark taste and serving scenario. |
| Ingredient order | When each ingredient enters the pot and why. | Ingredient list, prep size and batch quantity. |
| Heat and motion | Heat stage, timing, rotation and cooking rhythm. | Current chef process, key sensory cues and bottlenecks. |
| Seasoning checkpoints | Sauce amount, timing, dilution and reduction target. | Sauce recipes, premix rules and allergen notes. |
| Chef validation | Taste approval, adjustment notes and official version. | Decision maker, tasting standard and acceptance criteria. |
| Store deployment | Which machines, stores and operators use the approved program. | Pilot store, rollout timeline and feedback routine. |
Common mistake
A written recipe is often missing heat behavior, sauce reduction, ingredient moisture, operator timing and output standard. Real digitization captures the process behind the dish so the same program can be trained, tested and improved.
Dish photos, current chef process and target batch size.
Chef tasting plus repeat runs under the intended kitchen scenario.
Deploy only approved versions and keep test versions traceable.
FAQ
Many dishes can be evaluated, but the right answer depends on dish structure, sauce behavior, batch size, texture target and kitchen workflow. Send the dish for a practical review before assuming fit.
Start with repeatable, high-volume dishes where ingredient prep is stable and the target output is clear. These dishes are easier to test and usually make ROI easier to evaluate.
Not always. Headquarters can keep a standard version while adapting regional taste or store conditions, as long as version control and approval rules remain clear.
Run repeat tests, approve the official version, train operators, deploy to selected machines and collect feedback for future adjustment.
Next step
Share the dish name, photos, current chef process, batch size, sauce details and expected daily volume. YAO MASTER can review model fit and menu test direction.