Must Restaurants Follow Manufacturer Cooking Instructions?

Under the 2026 FDA Food Code model, a restaurant or retail food establishment should not treat every packaged product as ready to heat and serve. If the package bears cooking instructions, the food generally should be cooked before it is offered as ready-to-eat food unless the manufacturer says it may be eaten without cooking. Foods identified as not processed to control a pathogen, and raw meat or poultry bearing federal safe-handling instructions, have more specific model cooking requirements.

The FDA Food Code is a model, not an automatically effective nationwide rule. State, local, tribal and territorial authorities decide whether and how to adopt it. Confirm the current retail food code and any amendments for every establishment before describing a 2026 provision as a legal requirement.

What does the 2026 FDA model say?

Section 3-401.15 of the 2026 Food Code separates three situations. That separation matters because “there are directions on the box” does not explain why the directions exist or what the operator must control.

• Food not processed to control an identified pathogen: when a food-processing plant provides information under 21 CFR 117.136 that the food was not processed to control the identified hazard, the model says the packaged food must be cooked using a time and temperature appropriate for that hazard before it is offered as ready-to-eat food or for consumption.
• Raw meat or poultry with federal safe-handling instructions: packaged food bearing instructions required by 9 CFR 317.2(l) or 381.125(b) must be cooked according to those directions or the applicable Food Code cooking section before service.
• Other packaged food bearing manufacturer cooking instructions: the new paragraph 3-401.15(C) says it should be cooked before it is offered as ready-to-eat food or for consumption, unless the manufacturer specifies that it may be consumed without cooking.

The 2026 change is especially useful for packaged plant foods. Section 3-401.13 now cross-references section 3-401.15 when plant food is cooked for hot holding. This prevents an operator from assuming that reaching the ordinary plant-food hot-holding threshold completes a separate manufacturer-directed cooking step.

This is model language. A jurisdiction may still use an earlier Food Code edition, adopt only part of the 2026 text, change the wording or set a later effective date. Record the authority and code edition for the site rather than relying on the date printed on FDA’s national model.

How can an operator read the label correctly?

Start with the product’s status, not the appliance setting. A label may describe a food as fully cooked, ready-to-eat, ready to heat, partially cooked, raw, or not processed to control a named hazard. Those terms are not interchangeable.

For each packaged food prepared at the site, check:

• the exact product and supplier item number;
• whether the label says fully cooked, ready-to-eat or safe to consume without cooking;
• whether it says raw, partially cooked, not ready-to-eat or not processed to control an identified hazard;
• the cooking method, starting condition, time, internal temperature and any required standing time;
• whether the directions differ for an oven, microwave, fryer, grill or other equipment;
• whether the site’s intended use is direct service, inclusion in another recipe, or hot holding; and
• whether the equipment and batch size used at the site can follow the directions consistently.

Do not rely on the front of the package alone. The useful safety information may appear in the cooking panel, a safe-handling box, product specification or documents accompanying the food. “Heat until hot” on one product and “cook to 165°F” on another describe different controls even when both products arrive frozen and look similar.

When the supplier substitutes a product, treat the replacement as a change. Compare its ready-to-eat status, allergens, cooking instructions, portion size and equipment method before staff use the old procedure. A purchasing substitution should not silently become a food-safety substitution.

Is 135°F enough before hot holding?

Not necessarily. In the 2026 model, plant food cooked for hot holding must reach at least 135°F, or be cooked as specified under section 3-401.15. The cross-reference means the operator needs to check whether the packaged product has a separate cooking instruction that governs before hot holding begins.

For example, a packaged plant food may bear directions intended to complete a pathogen-control step. Warming it only until it reaches 135°F could satisfy the ordinary hot-holding threshold while failing to complete the required cooking process. The site should finish the applicable cooking step first, verify it as its procedure requires, and only then use hot-holding equipment to maintain the food.

Likewise, a food that is fully cooked and supplied ready-to-eat may need only reheating or hot holding under the locally adopted rules and the site’s procedure. Do not invent a cooking requirement that the product does not carry. Product status and intended use drive the decision.

How is this different from FSMA?

The reference to 21 CFR 117.136 can make this section look like a new FSMA rule for every restaurant. It is not. Part 117 regulates covered food manufacturing and processing facilities. Section 117.136 describes circumstances in which a manufacturer or processor may rely on a customer or later entity to control an identified hazard, supported by disclosures and assurances.

The 2026 Food Code model uses information flowing from that manufacturing framework to tell a retail food establishment how the packaged food should be handled before consumption. One provision concerns the upstream manufacturer’s preventive-control system; the other is model retail-food language for the downstream establishment. They should not be presented as the same legal duty.

Federal meat and poultry labeling requirements are another layer. The Food Code model cross-references the safe-handling instructions required for specified USDA-regulated products. The package instruction is not optional merely because the restaurant also uses a local cooking chart.

A multi-site operator may therefore need to track:

• federal information and safe-handling instructions attached to the product;
• the retail food code adopted for the establishment;
• local amendments or regulator instructions; and
• the operating procedure and record used to apply those requirements.

What should the site procedure cover?

A workable procedure should turn the label into a repeatable task. It should identify the product, approved equipment, maximum batch or loading arrangement, cooking method, required time and temperature, thermometer location, standing time where applicable, record and corrective action.

For each controlled product, define:

1. Receiving decision: confirm that the correct product arrived and keep the current label or specification available to the people setting the procedure.
2. Storage and starting condition: state whether the product begins frozen, refrigerated or thawed and how any thawing step is controlled.
3. Cooking method: name the approved appliance, settings, portion or load and required preparation steps.
4. Verification: record the actual result needed to show the process was completed; a tick without a measured result is weak where temperature is the control.
5. Transfer to holding or service: prevent delay and cross-contamination after cooking.
6. Corrective action: explain what staff must do when the instruction, time, temperature or equipment condition is not met.

Train staff on the difference between cooking, reheating and hot holding. A direction such as “cook from frozen” should not be translated into “leave it in the hot case longer.” Where the label is unclear, the product has been repacked or the site cannot follow the stated method, pause use and obtain reliable information from the supplier or the appropriate regulatory authority.

What should happen when the instruction was not followed?

Do not overwrite the result or assume extra time in the holding unit repairs the process. The immediate response should protect consumers and preserve the facts needed for a decision.

1. Stop service or sale of the affected batch and identify any food already transferred to a display, recipe or customer order.
2. Confirm the product and instruction, including its ready-to-eat status, hazard statement, starting condition and required cooking method.
3. Record what actually happened: equipment, times, temperatures, batch or lot, quantity, locations and person responsible.
4. Apply the approved corrective action. Depending on the product, process and local rule, this may permit completing the cooking step or may require disposal. Do not improvise a recovery method where safety cannot be established.
5. Escalate wider exposure if the product was served, used at several locations or prepared under the same faulty procedure.
6. Fix the underlying cause, such as an incorrect product setup, unread label, unsuitable appliance, excessive batch size, supplier substitution or outdated work instruction.

A useful corrective-action entry explains the failed limit, the food decision and the preventive follow-up. “Cooked longer” is not enough if it does not show the final verified result or whether any product had already been served.

How should multi-site operators control product differences?

Central teams can maintain an approved-product register that links each supplier item to its status, current instructions, intended use and site procedure. Local teams still need to confirm that the product, equipment and adopted food code match the central setup.

Useful fields include:

• supplier, product name, item number and current specification date;
• ready-to-eat or requires-cooking status;
• identified hazard or safe-handling statement where supplied;
• approved cooking method, time, temperature and standing time;
• approved equipment and maximum batch;
• record and corrective-action route;
• sites using the product;
• local code edition, authority and effective date; and
• the owner and date of the most recent review.

Review the setup when a supplier changes the product, label, formulation, package size or instructions; when equipment changes; after a failed cooking check; and when a jurisdiction adopts or amends its food code. A strong central standard can support consistency, but it does not replace checking the law that applies to each location.

TapTick can help teams schedule cooking checks, record actual results, surface exceptions and keep corrective actions visible across locations. It does not determine whether a Food Code provision has been adopted or replace the product manufacturer’s instructions. See TapTick features for the current product scope.

Primary sources

• FDA: Food Code 2026
• FDA: 2026 Food Code PDF — see sections 3-401.13 and 3-401.15 and the definition of ready-to-eat food in section 1-201.10.
• FDA: Summary of Changes in the 2026 Food Code
• FDA: The FDA Releases 2026 Food Code (September 17, 2026)
• FDA: Adoption of the FDA Food Code by state and territorial agencies
• FDA: State retail and food-service codes and regulations
• eCFR: 21 CFR 117.136, manufacturing and processing preventive-control circumstances
• eCFR: 9 CFR 317.2, meat-product labeling
• eCFR: 9 CFR 381.125, poultry safe-handling labels

Important: This article describes the 2026 FDA Food Code model and federal source material available on November 3, 2026. The Food Code does not take effect nationwide on publication. Confirm the current code edition, amendments, effective date and regulator instructions for each establishment.