Check the kitchen printer before the first real order.

Record the exact equipment

Write down the printer make and model, connection type and paper width. Take note of its physical location, available power and which computer or network it connects to. Share those details before installation so compatibility can be checked.

Do not assume every thermal printer behaves the same way. A receipt that fits one paper width may wrap differently on another. Cable reach, network access and printer settings should be reviewed as part of the actual setup.

Compare 58mm and 80mm samples before buying

Ask the supplier for two sample tickets with the same menu and intended text size, each printed on equipment correctly configured for its paper. Compare them at your kitchen pass under normal working light. A longer ticket can be acceptable if each dish and quantity remain easy to match; a compact ticket is not useful if staff must guess where a wrapped item ends.

Check the manufacturer's instructions before changing paper guides or settings. For example, Epson's TM-T82III technical reference warns that after changing from 80mm to 58mm and using the printer, it cannot be changed back because of possible print-head and cutter wear. This is a model-specific restriction, not a rule for every printer. The manufacturer references below describe equipment; they do not establish DeccanPro compatibility.

Run one controlled readability test

Use a training order such as 2 Onion Rava Masala Dosa, 12 Mini Idli Plates and 1 Filter Coffee. These are fictional test items, not a customer order. Ask the cook to identify all three lines and read back 2, 12 and 1 while the cashier checks the saved order. If a name wraps, check that its continuation cannot be mistaken for a fourth item.

Keep the menu wording unchanged while comparing samples. If you change the text size or layout, label that sample and repeat the read-back check. Add your actual Tamil menu items if required and use the linked Tamil print-test guide; a readable English sample does not establish Tamil rendering. Do this away from live service and label the tickets as training material through the supported procedure.

Verify the destination and the next update

Send the training order through the actual application connection. Check that it reaches the intended kitchen, rather than only the counter receipt printer. Record the full hardware variant: Epson India, for example, identifies SKU C31CH51551 as USB + Serial. A familiar model family name alone does not confirm which interface your quoted unit supplies.

Next send an additional item, a changed order and a cancellation using the demonstrated procedures. Compare each printout with the current order. The distinction between these ticket types matters more than a visually attractive sample containing only one item.

Follow one order through an addition and a reduction

Keep the first training ticket from the 2-dosa, 12-idli-plate and 1-coffee example. It represents three item lines and 15 units. Now add one coffee to the same saved order. The current order becomes 2 dosas, 12 idli plates and 2 coffees: 16 units. The kitchen needs to understand that only one coffee is new. A ticket showing the whole current order must not be read as a request to prepare all 16 units again.

Ask the kitchen reader to explain the change from the actual output before the cashier supplies the answer. Record whether your installation prints an addition alone, prints the current order or relies on another demonstrated handoff. This guide does not prescribe a ticket format or claim that every setup marks changes identically.

Next reduce the idli-plate quantity from 12 to 11 using the supported procedure. The saved order now contains 2 dosas, 11 idli plates and 2 coffees: 15 units. The total is back to 15, but the contents differ from the first ticket. An equal total alone cannot prove that the kitchen has the correct instruction. Record the changed item, current quantity and kitchen acknowledgement. Keep this as a no-food training exercise; handling a real dish already in preparation requires a separate kitchen decision.

Agree how staff respond to a missed print

Ask the installer to demonstrate the supported way to inspect or retry a ticket. Before repeating any print, staff should check whether the first copy already reached the kitchen. An unrecognised duplicate can turn one guest order into two preparation requests.

Keep the printer model, connection information and support contact near the counter. Recheck after moving equipment or changing the network. DeccanPro can review your Chennai restaurant's existing printer during the demo; compatibility should be confirmed before you buy a replacement.

Accept the demonstrated workflow, with unresolved checks visible

Use one row per acceptance check: readable item and quantity, correct destination, addition understood, reduction understood and copy handled as existing work. Mark each pass, fail or not tested. Keep the printer model, layout settings, order reference and sample identifier with the result. A clear first ticket cannot compensate for an untested cancellation or a confusing replacement copy.

Before a supported reprint, confirm what the kitchen already received and who will identify the new sheet as a copy of existing work. Check that the saved order has not gained extra items. If the procedure or printed reference leaves staff unsure, keep the check unresolved and ask the installer to demonstrate it again. Do not create a fresh order just to obtain another piece of paper.

When comparing configurations for a Chennai restaurant, keep the test menu constant and label each sample. Record any change in font, layout, connection or printer alongside the paper width. Assign an owner and retest date to failed checks, preserving the failed sample. Accept only the workflow actually demonstrated on the intended equipment; a different model or connection needs its own verification.