Vendion
    Point of Sale

    Daily order number on the ticket

    6 min read#90

    Previously, Vendion showed a technical ID on the ticket — something like "CD8373". That was a sliced chunk of a unique system ID and had zero value for the kitchen. Nobody yells "Is order CD8373 ready?!" in a stressed kitchen.

    Now there's instead a daily counter: "#047". Simple, clear, and it works the way normal humans expect.

    How it works

    Every day the counter starts at 1 and ticks upward for each new order sent to the kitchen. The first order in the morning becomes #001, the next #002, etc.

    The counter resets automatically when you run the Z-report (end-of-day). After Z, the next day starts at #001 again.

    That means:

    • Yesterday: #001 to #154 (you had 154 sent orders)
    • End of day: Z-report runs, counter resets
    • Today: #001, #002, #003... starting from scratch

    When is the number assigned?

    The number is assigned on the first send-to-kitchen of the order — not when the order is created.

    That's deliberate. If we assigned the number when a new tab was opened, the counter would fill with empty, abandoned orders that never got sent (e.g. the guest who just sat down, opened the menu and left again). The kitchen would report "order 73" but the counter would show 200 — confusing for everyone.

    So: as long as an order is never sent (or if you're just adding items in the POS but haven't sent to kitchen yet), it has no order number. The moment you hit Send for the first time, a fresh number is assigned.

    Same order = same number everywhere

    If a single order has items across multiple destinations (e.g. starter to kitchen + drink to bar), both tickets show the same number.

    That means:

    • The chef in the kitchen yells "#47 ready!"
    • The bartender hears and knows "okay, my drink for 47 should also go out soon"
    • The server picks up and knows starter + drink belong together

    Perfect sync across stations.

    Appearance in the template

    On the ticket template you can control:

    • Whether the order number is shown (toggle "Daily order number")
    • Size (S, M, L) — recommended L so it's visible at a distance
    • Prefix — "#", "Order", "Beställning" or any text

    Default is prefix "#" and size L. Works for most.

    If you change prefix to e.g. "Order " it becomes "Order 047" on the ticket instead of "#047". Small detail, but some kitchens prefer one over the other.

    Order number vs receipt number — important distinction

    Many mix up these two counters. They are completely different and both are needed.

    PropertyOrder number (#047)Receipt number (18234)
    Where it showsOn the ticket (kitchen)On the receipt (guest)
    When it resetsEvery Z-reportNever — it's perpetual
    Starting value1 every day1 + all previous receipts
    PurposeKitchen commsLegal requirement (tax authority)
    Who caresChef yelling "47 ready!"Accounting and audit

    Why two?

    The receipt number must by Swedish fiscal law be a perpetual counter that never resets, never skips and never gets reused. Critical for Skatteverket audits. If your restaurant has 18,234 receipts since launch, the next receipt will be number 18,235 — whether it's January, July or a new owner.

    The order number is instead a kitchen-practical counter. A short, readable number that resets every day so it never grows to four or five digits. It's only for internal kitchen comms.

    Mixing them up would be bad:

    • If the receipt showed "#047" → Skatteverket wouldn't approve your cash register
    • If the ticket showed "18235" → the kitchen couldn't tell 18235 from 18236 from 18237 at a distance

    So we have both. Different counters, different purposes, different places.

    Show receipt number on the ticket (extra toggle)

    If you really want the receipt number also on the ticket, there's a toggle: "Show receipt number when paid". It shows the receipt number as an extra row on the ticket, but only if the order is already paid when the ticket is created (uncommon — usually we send to kitchen before payment).

    Useful in:

    • Takeaway flows where the guest pays first and the kitchen cooks after
    • Historical ticket copies (if you want to link back to a specific receipt)

    In normal seated-guest flows you don't need to turn it on.

    Common questions

    What if I run the Z-report mid-service? The counter resets immediately. Next ticket gets #001 again. In practice Z runs after closing so this rarely happens, but if it does, it's not a disaster — the kitchen sees the number is "low" again and can ask if it's a new order.

    What if we reach #999 in one day? The counter continues to #1000, #1001 etc. The ticket format changes from 3 digits to 4. If you regularly reach numbers that high — congrats, you have an incredibly busy restaurant.

    Can I manually reset the counter mid-day? No, only via Z-report. Deliberate, to avoid human errors.

    Does the order number work for takeaway tickets too? Yes. All tickets from the POS use the same counter — dine-in, takeaway, delivery. Every unique order gets a unique number for the day.

    How does the order number affect Skatteverket? Not at all. Skatteverket cares only about the receipt number. The order number is an internal convenience that isn't reported anywhere.

    Can I disable the order number entirely? Yes. Go into the template, turn off the Daily order number toggle in the Header tab. The ticket prints without a number. But we strongly recommend keeping it on — the kitchen without a readable ID becomes chaos in the evening.

    Summary

    • Order number = daily counter, resets per Z, used by kitchen
    • Receipt number = perpetual counter, never resets, required by law
    • Both exist in parallel and both are needed
    • The order number is assigned on first send-to-kitchen (not on order creation)
    • Same order has the same order number at every destination
    • Configure visibility, size and prefix per ticket template

    This feature is part of Vendion POS.

    Curious how it looks in practice? Read more about the product or book a short demo.

    Was this article helpful?