One instruction should not accidentally change every dish.

Choose between a menu variant, a paid extra and a note

Start with the restaurant’s approved menu. A regular coffee and a large coffee are distinct choices when they have different portions or prices. An extra item that carries a charge needs the supported billable entry. A free-text preparation note describes an instruction; typing a price into it does not establish that the bill includes the charge.

Keep the kitchen instruction and the amount check separate. If the guest requests an additional paid item, verify its quantity and amount on the saved order, then verify the kitchen receives the corresponding instruction. Do not use a note as a substitute for a configured product or pricing rule without demonstrating the intended workflow.

Find out whether the note belongs to an item or one unit

The reviewed captain ordering code provides an item-notes entry and stores notes against the product in the cart. That is source evidence of an entry workflow, not proof that two units of the same product can retain separate instructions in every installation. Ask the demonstrator to show the exact behaviour when the same dish is added again.

Use three fictional coffees: two with the restaurant’s usual preparation and one with sugar served separately. The intended result is still three drinks. Ask the operator to represent that distinction using the supported procedure, then reopen the cart or saved order. If the screen has a single quantity-three line with one note, the cook must still be able to explain which one drink differs. Do not assume a note automatically creates a separate line or seat assignment.

If the installed workflow cannot preserve the required distinction, record that limitation and agree a clear supported method with the supplier before live use. Repeatedly adding the same product or creating duplicate menu records without review can make the result harder to reconcile.

Ask the kitchen to read back the three-drink order

Run the test outside service with fictional records and no food preparation. Give the kitchen reader the actual output from the proposed setup, without first telling them the expected answer. Ask for the order reference, total number of drinks, number with the special instruction and number with the usual preparation.

The expected answer is one identified order containing three drinks: one with sugar separately and two with the usual preparation. Record the actual words and quantities shown. A total of three alone is insufficient: all three carrying the special instruction has the right count but the wrong meaning.

Check the channel staff will actually use. A readable note on the captain’s phone is not evidence that it reaches the paper KOT or kitchen display. The reviewed voice-announcement code speaks names and quantities, not item notes. A spoken order therefore cannot replace reading and acknowledging the written instruction. Demonstrate the chosen printer or display separately.

Add a second round without carrying the old note forward

Now add one more coffee with the usual preparation to the same training order. The intended current total is four coffees: one with sugar separately and three with the usual preparation. Inspect the new entry before sending it. Existing cart notes or configured descriptions may be offered again in a notes workflow; confirm what the actual screen contains rather than trusting an empty-looking entry step.

After saving, ask the kitchen reader to identify the one newly requested coffee and its preparation. A full-order printout must not become a request for four additional drinks. Keep the original order and the second-round evidence together so a later shift can distinguish the current order from what is new.

Treat a late instruction change as a kitchen handoff

In a separate practice case, discover a mistaken note after the kitchen has received the order. First establish whether preparation has started. Ask the operator to demonstrate how the correction is saved, how the kitchen learns about it and who acknowledges the current instruction. Editing text at the counter does not establish that a cook has seen the revision.

Record the previous instruction, the corrected instruction and the affected quantity against the same order reference. Keep dish quantities unchanged unless the guest actually changes them. Do not submit a second order simply to transmit a note. If a fresh print or manual handoff is required, explicitly identify it as a correction to existing work.

The exercise concerns ordinary preparation preferences. Do not treat a free-text note or this rehearsal as an allergy-management procedure. Use the restaurant’s established staff process for requirements that need separate confirmation.

Keep a small acceptance record for the Chennai demo

Bring two common dishes, one ordinary preparation request, one priced extra and the printer or display details you intend to use. Record the staff role, order reference, item quantity, note wording and each output checked. Use sample data; customer names and telephone numbers are unnecessary for this exercise.

Mark each result as demonstrated, unresolved or not tested. Check that a note correction did not change the amount or create another item, that the paid extra did change the bill as intended, and that a new round did not inherit the earlier instruction unexpectedly. Ask a second staff member to repeat the readback rather than accepting only the operator’s explanation.

DeccanPro’s restaurant software is Rs.6,000 per year with unlimited use and no setup or hidden software fees. Confirm your particular instruction workflow in the demonstration; this guide does not promise separate per-unit notes, structured modifier pricing or a special receipt layout. Equipment and third-party services are separate.

• One instruction has a clear affected quantity.
• The saved order, kitchen output and readback agree.
• The next round retains the intended preparation.
• A paid extra is verified as a charge, not just text.
• Late corrections have an explicit kitchen acknowledgement.