Anatomy of a Kitchen Ticket: What Should It Show?

What should appear at the top of a kitchen ticket?

The top of the ticket identifies the order before the kitchen reads the food. Put the order number first, then the order time, order type, channel, and table or delivery marker. A cook should know whether the ticket is for table 12, pickup, delivery, or a third-party channel without searching through the item lines.

Keep these markers visually separate from the menu lines. A large table number helps the runner. A clear delivery label helps the packing station. A channel label helps the manager trace a missing item without asking the kitchen to remember who placed the order.

How should the item lines be ordered?

Put the quantity and item name on the first line. Put the important preparation choices directly underneath. Put special instructions after the modifiers, with enough visual space to prevent them being mistaken for a standard option.

The numbers below are an illustrative example, not a client's actual figures.

Do not bury modifiers in a long sentence. A line cook scans the ticket while handling heat, pans, and timing. Use one modifier per line when the order has several choices. Print removals with a clear label such as Remove, Without, or No, rather than relying on a blank option.

The kitchen ticket should show the preparation sequence, not the checkout sequence. If a meal includes a main item, side, and drink, group the lines in the way the branch assembles the order. A category-based printer setup can send selected menu categories to the relevant printer group, such as kitchen, bar, or cashier.

Which modifiers deserve priority?

Modifiers that change cooking or packing deserve priority over preferences that do not affect production. A removal, allergy note, cooking temperature, portion change, or required side should be visible before a general customer comment.

1. Cooking changes, such as well done or no salt.
2. Removals, such as without onions or no sauce.
3. Paid additions, such as extra cheese or double meat.
4. Required choices, such as bread type or side dish.
5. Packing instructions, such as separate sauce.
6. General notes, such as gift message or delivery comment.

A modifier should stay attached to its parent item. If three burgers have different sauces, print the sauce below each burger. A shared note can sit at the bottom, but only when it applies to the whole order. This prevents the common mistake of applying one customer's preference to every item.

Nexara's menu supports products, categories, modifiers, and modifier groups. Its visual menu builder lets the restaurant define the choices once, then use the same catalogue across the website, app, table QR, and supported order channels. See the guide to menu modifiers and add-ons for the setup decisions behind the printed lines.

How should Arabic and English appear together?

Most kitchens we work with print Arabic only on the hot line and bilingual on the pack station. An Arabic ticket can carry English on the same printout when the team is bilingual or a product name is commonly recognised in English. Keep both languages on the same item line or on two directly connected lines.

Arabic thermal printers commonly lack Arabic fonts. Nexara's printing engine renders Arabic correctly for ordinary ESC/POS thermal printers, and the same ticket can include English. A year went into the printing engine alone, so an Arabic receipt never turns to gibberish and a kitchen never goes dark.

Keep labels consistent. If the ticket uses Remove for a removal, do not use a different label for the next item unless the kitchen has been trained on both. A small vocabulary reduces hesitation during service.

What should the footer tell the kitchen?

The footer should carry information that applies to the whole order: a customer note, delivery or pickup marker, payment context when useful to the branch, and a reprint indicator. Avoid repeating the full menu or checkout totals on a kitchen ticket. The kitchen needs production facts first.

• Order-wide note, clearly labelled.
• Table, pickup, or delivery destination.
• Channel marker, such as Website, Call Center, Talabat, or Careem food orders.
• Reprint label when the ticket was sent again.

Nexara receives orders from the call center, branded website and app, table QR, Talabat, and Careem food orders into one live order queue. Tickets can then print in Arabic or English through the branch printer setup. Orders queue while the branch connection is down and print when the connection returns; the order board itself needs a connection.

The printer does not need to be a proprietary Nexara terminal. Nexara drives standard ESC/POS thermal printers over USB or network through its Windows print agent. If a printer fails, the ticket stays on the board, the restaurant can re-route its categories from the dashboard, automatic failover can send work to a configured backup printer, and any ticket can be reprinted by hand once the printer is back.

Read the deeper explanation in how Nexara's kitchen printing engine works before choosing printers, categories, and backup routing.

How can you build a ticket template?

Build the template around the questions your line asks during a busy service. Start with one branch and one printer group. Print test orders that include Arabic names, English names, several modifiers, a removal, a table number, and a delivery marker. Then ask a cook to read the ticket without help.

1. List every field the kitchen must know before starting.
2. Place order number, time, type, channel, and destination at the top.
3. Print each item with quantity before the name.
4. Place modifiers under the matching item.
5. Separate removals and special notes from standard choices.
6. Choose Arabic, English, or bilingual lines for the branch.
7. Assign categories to the correct printer group.
8. Test a normal order, a complicated order, and a reprint.
9. Ask the line which field still causes questions.
10. Change the template, then test it again before service.

Nexara includes a visual template builder for kitchen tickets and receipts. Templates can be assigned per printer, with Arabic and English support. The order layer sits beside the till, so the cashier can handle the day's sale and reconciliation while the kitchen receives a ticket built for preparation.

Nexara has a free plan plus paid plans per branch in Jordanian dinar. Current rates are available on request.