A kitchen does not need final construction drawings before it can begin looking for a cooking robot. It does, however, need a defined production problem. Without one, model selection becomes a tour of features: a larger drum looks impressive, automatic seasoning sounds convenient, and a four-wok unit appears productive, yet none of those observations establishes whether the equipment belongs in the operation.
Readiness is therefore not the same as being ready to place an order. This checklist is designed to produce four working documents: a production brief, a menu-and-demand file, a site-and-utilities pack, and an operating plan. Together, they should give a supplier enough information to propose relevant equipment and give the restaurant enough structure to challenge that proposal. Recipe trials, final drawings, local compliance review, and contract checks still follow later.
1. Define the production problem
Begin with the reason the kitchen is considering automation. Is the hot line short of skilled wok cooks? Does output fall behind during a particular service period? Is the business trying to reproduce one menu across several sites, or design a new restaurant around a smaller operating team? A prospective distributor has a different question again: which equipment could be supported and sold in the destination market? The intended use changes the shortlist.
Current commercial cooking robots are strongest at repeatable stir-fry work. Other applications have been demonstrated, including shawarma and American barbecue, and some suppliers describe boiling or additional cooking modes. Those claims need to be tested on the intended food. A kitchen built mainly around deep-frying, steaming, constant improvisation, or highly manual finishing should not assume that a stir-fry machine will solve its central production problem.
The output from this step is a one-page production brief. It should identify the country and destination market, restaurant and service format, number of planned sites, the cooking-stage bottleneck, daily and peak demand, normal portion size, budget, and target timeline. If the problem cannot be stated in operational terms, comparing machines is premature.
2. Document the menu and requirements
The next file is the real menu, not the supplier's cloud library. A platform may store more than 1,000 recipes, but a large library says nothing about which dishes a particular restaurant should automate. There is no useful universal target such as ten, twenty, or thirty SKUs. The required number is the number of dishes the operation actually intends to serve through the machine.
List those dishes with their normal portions and expected demand. Identify which ones drive the rush, which require the most skilled wok work, and which are commercially important enough to justify recipe development. The preparation standard does not need to be perfect at this stage, but the buyer should understand that cutting, draining, marination, portioning, and loading will eventually need a repeatable method. A machine program cannot compensate indefinitely for undefined inputs.
Recipe responsibility also belongs in the plan. A buyer may use recipes already developed by a supplier, ask the supplier to digitize existing dishes, or develop programs internally. This choice affects trial time, ownership of the food standard, staff involvement, and what must be completed before opening.
The output from this step is a menu-and-demand file. For every first-phase dish, record the normal portion and expected daily and peak demand, then state whether the recipe will be bought, commissioned, or developed internally. Name the person who can approve taste and food quality during trials; without that decision-maker, a technically successful demonstration can still leave the project unresolved.
3. Check the site, utilities, and working envelope
A specification sheet gives the machine footprint. A kitchen plan needs the complete working envelope. That includes the route through doors and corridors, space for loading and unloading, ingredient staging, operator movement, finished-dish handoff, cleaning access, drainage, and later service access. Photographs, videos, floor plans, utility schedules, equipment lists, and a live video walkthrough can all support an early remote review. They do not replace final verification at the site.
Electricity is an early filter because larger floor-standing equipment may require power that the site does not have. Some designs may offer a gas-heated alternative, but that is a model-specific option rather than a general workaround. Water, drainage, ventilation, and network requirements also vary. For projects in the United States, European Union, and other regulated markets, the supplier and qualified local contractor should confirm electrical suitability, ventilation, permits, installation work, and the required product compliance. Some suppliers have overseas support teams; others rely on third-party engineers.
Human reach can be as decisive as floor area. On some four-wok systems, the upper woks are difficult for shorter operators to reach and remove, particularly when the vessels are heavy. A drawing cannot settle that question. The future operator should test the loading and removal motion with the proposed machine or an accurate physical mock-up.
The output from this step is a site-and-utilities pack: a current floor plan, photographs, door and corridor dimensions, the existing equipment layout, available electrical supply, and the proposed location. Mark the space needed for staging, operator movement, handoff, cleaning, and service. Water, drainage, ventilation, network, any gas alternative, and local compliance can then be confirmed against the exact configuration by the supplier and a qualified local contractor.
4. Assign staff, workflow, cleaning, and supplier responsibilities
The clearest sign that a kitchen needs more preparation is not a missing measurement. It is that nobody has decided where the machine will sit, who will operate it, or how food will move through the new line. Sketch the complete route: washing and cutting, portioning, filling ingredient boxes or loading the wok, starting the recipe, unloading, inspecting, plating, and cleaning. The new station should remove pressure from the kitchen rather than shift the queue into preparation or handoff.
Decide how many people will work around the machine and what kind of staff they will be. Height, lifting ability, language, training, and responsibility for recipe selection all matter. Automatic cleaning is not a readiness requirement. It is a selection choice. A manual-cleaning model can work well if the closing routine and access are practical; an automatic wash cycle still leaves other food-contact parts and the surrounding workspace for staff to clean.
Before a contract is signed, ask the supplier direct questions about installation, operator training, recipe commissioning, warranty, spare parts, remote support, on-site service, and recovery from a breakdown. Answers vary substantially between suppliers and destination markets. Record the answers in the quotation or contract rather than relying on a general promise that support is available.
The output from this step is an operating and support plan. It should show the number and type of operators, the movement of staff and food during normal and peak service, who owns cleaning at the end of a shift, and how the station remains usable by the people assigned to it. The same file should capture the supplier's written scope for installation, training, recipe work, warranty, spare parts, technical support, and breakdown recovery.
5. Review the readiness pack
The checklist is complete when the four documents contain decisions and usable evidence, not merely checked boxes. The table below is a final review of what the project file should now make possible.
A 'ready to shortlist' result is permission to compare and test, not to buy. Exact utilities, recipe programs, installation design, compliance, and commercial terms still need to be verified against the selected machine before a contract is signed.
Back to Planning & ROI