# Restaurant digitisation in Greece: from the handheld order to the receipt

> Digitising a restaurant is not just taking orders on a handheld. It is connecting the whole operation, from the floor and the kitchen through to the till and the tax document. Here is what actually changes in a shift, where the chain breaks today, and what to ask a hospitality platform before you sign.
>
> AI-friendly Markdown version. HTML version: https://wrapp.ai/en/resources/restaurant-digitisation-greece-order-to-receipt
> EL version: https://wrapp.ai/el/resources/psifiopoiisi-estiasis-paraggelioliipsia-apodeixi.md

Most hospitality businesses start digitising with the obvious move: a handheld in the waiter's hand instead of a paper pad. It is the right step, but it is one step. The gain is not in the device, it is in the **connection**: the floor, the kitchen, the till and management all working off the same live picture of the shift.

The end result is practical rather than theoretical: fewer mistakes on the order, faster service, and a clean picture for the owner without waiting for month end to find out what happened. Below is what changes at each level, where the chain breaks today, and what to ask a hospitality platform before you sign.

### Order taking, payment, issuing: three separate levels

We start here, because it is the most common misunderstanding in every supplier conversation. In hospitality the word "POS" is used for two completely different things: the till and the card terminal. These are three separate levels, and none of them replaces the other two.

| Level | What it does | What it does not do |
| --- | --- | --- |
| Order-taking handheld (PDA) and till | Takes the order, sends it to the kitchen, keeps the table's bill open | Does not take card payments, does not issue a legal tax document on its own |
| Card POS terminal | Accepts card and contactless payments | Does not know what the customer ate, does not issue a document |
| Document issuing | Issues the receipt or invoice, marks it and transmits it to myDATA. Done by a cash register (ΦΗΜ) or by a ΥΠΑΗΕΣ provider | Does not take orders, does not manage tables |

Why the distinction matters: when a supplier says "I will give you a POS", ask which of the three levels it covers. Businesses that end up with three systems that do not talk to each other type the same data three times. If you want to see how the card terminal specifically connects, we explain it in the guide on [connecting SoftPOS](https://wrapp.ai/en/resources/connect-viva-softpos).

### What changes during a shift

The difference does not show up in a demo, it shows up on a Saturday night with a full room. The points that matter:

- **Every role on the same picture, in real time.** Management, floor, till and preparation areas see the same state. The order does not get lost between the floor and the kitchen, because it does not travel on paper.
- **Workflows built for your model.** A take-away spot does not work like a table-service restaurant or a business with multiple revenue centers. Configurability is what lets the same software fit both.
- **One change, everywhere.** When a price or a dish changes on the menu, the change propagates centrally to every device without interrupting service for the people already seated.
- **Permissions per role.** A waiter, a shift manager and the owner do not need the same capabilities. Distinct access levels are control and security at the same time.
- **Numbers that answer questions.** What sells, what is left, at what hour, at which point of sale. That is the difference between knowing and guessing.
- **Customer ordering by QR.** Ordering from the table, calling a waiter, live order tracking and electronic payment, without tying up staff to carry information around.

### Where the chain breaks today: the tax document

This is the point that cancels much of the gain, and it usually goes undiscussed while the software is being sold. The order travels digitally from the floor to the kitchen, and then somebody **retypes** the bill into the cash register so a receipt comes out.

Two entries for the same transaction means double the time at close, room for human error on a tax document, and two different truths about the same evening: what the software says and what the till says. At closing time, nobody is in the mood to work out which of the two is right.

The fix is not faster typing, it is removing the second entry. When issuing happens automatically from the system that already holds the order, staff go back to the job they are there for, which is service, and no accounting knowledge is needed to produce a correct document.

### Issuing without a cash register

Issuing through a certified **electronic invoicing provider** (ΥΠΑΗΕΣ) is a legal alternative to a cash register, under article 12 §10 of law 4308/2014 (Greek accounting standards) and the provider framework. The provider marking, meaning the ΜΑΡΚ with a QR code plus real-time transmission to myDATA, substitutes for the cash register marking.

In practice: **no cash register, no marking on a separate machine, no daily Z report**. Watch the scope of the claim though, because this is where mistakes happen: a provider removes the ΦΗΜ. It does not remove the business's obligations towards ΑΑΔΕ, nor the provider declaration.

There is also one document type in the hospitality flow that often gets overlooked: the **Catering Order Note**, myDATA type 8.6. It documents the order before the final receipt, without creating a payable amount. Together with retail receipts, invoices to businesses, credit notes and delivery notes for supplies, the whole flow is covered from one place. The steps for issuing inside the app are in the guide on [how to issue an invoice](https://wrapp.ai/en/resources/how-to-issue-an-invoice), and replacing the cash register with an All in One device is covered in [its own guide](https://wrapp.ai/en/resources/all-in-one-pos-cash-register-replacement).

### The dates that affect hospitality

| What | When |
| --- | --- |
| Mandatory e-invoicing for B2B documents, meaning catering, events, corporate accounts, wholesale | 1 October 2026 |
| End of the transitional period, conditional on a declaration filed on time | 31 December 2026 |
| Digital clientele registry for hospitality | Announced, with no decision, ΦΕΚ or date |

For mandatory e-invoicing, the full timeline, the penalties and the condition attached to the transitional period are in the [guide to 1 October 2026](https://wrapp.ai/en/resources/mandatory-e-invoicing-greece-october-2026).

On the digital clientele registry we hedge deliberately: it has applied to the vehicle sector since 1/7/2025, and extending it to catering, events and hotels has been announced without a decision being issued. Do not plan around a date that does not exist. How the mechanism works today is explained in the guide on [the digital clientele registry](https://wrapp.ai/en/resources/how-digital-clientele-works).

### What to ask a hospitality platform

Seven questions that separate the demo from daily life:

- **Does it fit my model?** Take away, table service, delivery, multiple points of sale. Ask to see it in your own scenario, not in a generic demo.
- **Does it work on every device?** Handheld, tablet at the till, screen in the kitchen, with the same functionality rather than a cut-down version.
- **Is it cloud based?** Access from wherever you are, with no specialised equipment and no installation at each location.
- **Does a change propagate centrally?** Test the obvious thing: change a price and see how fast it appears, and where.
- **Does it have per-role permissions?** And can you change them yourself, without calling support.
- **Does it issue the document, or do you type it somewhere else?** The only question on this list that also has a tax dimension. Ask explicitly whether issuing goes through a certified ΥΠΑΗΕΣ provider and whether transmission to myDATA is automatic.
- **What happens when you grow?** A second location, a second point of sale, catering. The answer should not be "a second installation from scratch".

### How it works in practice: Coquo

[Coquo](https://coquo.gr) is a hospitality management platform that covers the order-taking flow of any venue, with a different interface per device type, central configuration and immediate synchronisation, per-role permissions, statistics and reports, plus QR Ordering with waiter calling and electronic payments.

Coquo connects to Wrapp through the API for issuing and transmitting documents to myDATA automatically. The process runs in the background, with no double entries and no extra steps by staff, reducing the additional manual work and the room for human error.

### Where Wrapp fits

Wrapp is a certified ΥΠΑΗΕΣ provider. It takes on the third level, the issuing, so the hospitality platform can do what it does best.

- **Full document coverage:** retail receipts, invoices, credit notes, Catering Order Note, delivery notes, public sector invoices.
- **No cash register**, with ΜΑΡΚ and QR marking and real-time transmission to myDATA.
- **Issuing through the REST API** when the order starts in another system, with a staging environment for testing.
- **The provider declaration to ΑΑΔΕ** filed by us, inside the ten-day window.

If you run a hospitality business, start with a [free account](https://wrapp.ai/en/users/new) or ask your software vendor whether it connects to a provider. If you build software for hospitality, the next step is [integrating through the API](https://wrapp.ai/en/api/becomeapartner), and why issuing cannot stay inside your own stack is covered in the article on [hospitality platforms and myDATA](https://wrapp.ai/en/resources/hospitality-platform-mydata-ypahes-provider).

## Frequently asked questions

### Is an order-taking handheld the same thing as a card POS terminal?

No, and the confusion wastes time in every supplier conversation. The handheld takes the order and sends it to the kitchen and the till. The card terminal takes the payment. Issuing the tax document is a third, separate layer, handled either by a cash register (ΦΗΜ) or by a licensed electronic invoicing provider (ΥΠΑΗΕΣ). All three can work connected to each other, but none of them replaces the other two.

### Do I still need a cash register if I issue through a provider?

No. Issuing through a certified ΥΠΑΗΕΣ provider is a legal alternative to a cash register, under article 12 §10 of law 4308/2014 (Greek accounting standards) and the provider framework. The provider marking, meaning the ΜΑΡΚ with a QR code plus real-time transmission to myDATA, substitutes for the cash register marking. There is no daily Z report. Scope it precisely though: a provider removes the ΦΗΜ, it does not remove your own obligations towards ΑΑΔΕ or the provider declaration.

### How does the receipt get issued when the order starts on a handheld or a table QR code?

Through the API, from the same system that holds the order. The moment the bill closes, the retail receipt is issued, gets its ΜΑΡΚ and QR code and is transmitted to myDATA, with nobody retyping the items into a second device. The customer receives it electronically or printed.

### What is the Catering Order Note?

It is a distinct myDATA document type, 8.6, designed for the hospitality flow: it documents the order before the final receipt without creating a payable amount. Wrapp supports it alongside retail receipts, invoices, credit notes and delivery notes, so one integration covers the full flow of the business.

### Does the 1 October 2026 e-invoicing mandate apply to restaurants?

It applies to the documents you issue to other businesses: catering and events, corporate accounts, wholesale. From 1/10/2026 those are issued through a ΥΠΑΗΕΣ provider. Retail receipts to consumers do not fall under the B2B obligation, though in practice businesses that already have a provider issue both categories from the same place. There is also a transitional period until 31/12/2026, conditional on a declaration filed on time.

### Does the digital clientele registry apply to restaurants?

Today it applies to the vehicle sector, since 1/7/2025. Extending it to catering, events and hotels has been announced, with no decision, no ΦΕΚ and no date. Do not plan around a specific date: follow ΑΑΔΕ or ask your accountant.

### Can the hospitality platform I already use connect to Wrapp?

Yes, if its vendor integrates with our REST API. This already happens with hospitality platforms such as Coquo, where issuing and transmission run in the background. Ask your software vendor for it: a staging environment is available so they can test before going to production.

### What does a hospitality business practically need to get started?

Three things, in this order. First map where every document comes from today: cash register, handwritten book, order-taking software. Then decide whether issuing happens inside the app or automatically through the API from your order-taking system. Finally sign with a provider: the provider files the declaration with ΑΑΔΕ within 10 days and you accept it through myAADE.

Need help? Contact us: https://wrapp.ai/contact