What is a Yemeksepeti integration and how do you set one up? A step-by-step guide for restaurants
Delivery is now as important to many restaurants' revenue as the dining room. It is also where a busy evening hurts most: the order is on a tablet, the cashier is at the till, and the kitchen ticket is handwritten. A Yemeksepeti integration collapses those three screens into one — the order lands on your POS and the kitchen ticket prints the moment you accept it.
This guide explains what an integration is, how it works behind the scenes, how to set it up, and the questions to ask before choosing one. If you want to see ari adisyon's version straight away, head to the Yemeksepeti integration page.
What is a Yemeksepeti integration?
A Yemeksepeti integration automatically passes orders placed on Yemeksepeti into the restaurant's own order/POS system. The order appears on the screen the waiters and cashier already use — not on the platform's tablet — and accept, reject, ready and handed-over updates flow back to the platform from there.
Technically, it is a secure connection between the Delivery Hero infrastructure behind Yemeksepeti and the POS software. The order arrives at the POS as a request; the POS sends your decision (accept, reject, ready) back as a request. For the restaurant the visible part is simple: the till rings, you decide.
The journey of a Yemeksepeti order with an integration: app to till, till to kitchen, kitchen to rider.
What you lose without an integration
In a restaurant without an integration, Yemeksepeti orders usually live on a separate tablet. That works on a quiet afternoon; the trouble starts at peak time:
- Missed orders. The tablet rings in a corner while the cashier is busy with a table. Orders that run out of acceptance time are cancelled by the platform.
- Double entry. An order accepted on the tablet has to reach the kitchen separately — handwritten or re-keyed into the till. Every re-typing is a chance for a mistake.
- Scattered revenue. Delivery sales are missing from the till report and have to be added up from two places at close.
- Two menus. A sold-out item has to be switched off on the till and in the Yemeksepeti panel separately.
The real win of an integration is not speed, it is one source of truth: orders, menu and revenue in one system.
How the integration works
1. The order lands on the till
The moment the customer orders, the order is passed to the POS. A good integration brings a new order to the front whichever screen the cashier is on and keeps sounding until it is accepted. The time left to accept is shown as a countdown.
The new-order card in ari adisyon: short order code, time left to accept, prep-time chips and one-tap accept.
2. Accept: you choose the prep time
When accepting, you choose when the order will be ready. That time goes to the platform; for orders delivered by a Yemeksepeti rider, the rider is planned around it. If you cannot fulfil the order, you pick a rejection reason from the list — choosing the right reason also matters for your reports on the platform side.
3. A tab opens and the kitchen ticket prints
An accepted order opens a table-less tab on the POS. Items are split by station (kitchen, bar) and tickets print with the customer's item notes and extras. The delivery ticket carries the short order code and delivery type — the rider asks for the order by that code.
4. Ready and handed over
When the food is ready you tap "Ready"; if a Yemeksepeti rider is coming, the platform is told. When the rider picks the order up, or your own driver delivers it, the tab closes and the sale goes into the end-of-day report.
Order types: who delivers?
Yemeksepeti orders are delivered in three ways and an integration should handle each one:
- Yemeksepeti rider: The platform's rider collects from the restaurant. The restaurant does not need the customer's address.
- Restaurant's own driver: Address and phone arrive with the order and print on the delivery ticket. Cash-on-delivery is recorded at the till.
- Pickup: The customer collects; you mark it as handed over.
Setting it up, step by step
In ari adisyon you set it up yourself, without waiting for support. The only step on the Yemeksepeti side is sending the connection code to your account manager:
- Enterprise plan: The Yemeksepeti integration is part of the Enterprise plan. See the plans.
- Management → Yemeksepeti → Connect: Pick your branch; the system creates a branch-specific connection code (Remote ID).
- Send the code to Yemeksepeti: Copy the ready-made message on screen and send it to your Yemeksepeti account manager.
- First order: Once Yemeksepeti links your restaurant, the first order lands on the till and the connection card turns "Active".
- Settings: Choose a default prep time, turn on auto-accept if you want it, and push your menu.
A short checklist before going live.
8 questions to ask when choosing an integration
Not every "Yemeksepeti integration" does the same job. When choosing a POS system, ask:
- Where does the order appear — in a separate tab only, or on top of every screen?
- Does the sound keep going until the order is accepted?
- Does the kitchen ticket print automatically on accept, split by station?
- Do the rejection reasons match the platform's reasons one-to-one?
- Does a cancellation on the platform side reach the till and the kitchen?
- Does marking an item sold out also switch it off on Yemeksepeti?
- Are delivery sales in the same end-of-day report as the dining room?
- How long is the customer's personal data kept?
For a detailed look at these questions, see our guide to choosing delivery order software.
Security and data protection
An integration touches customer data, so security cannot be an afterthought. In ari adisyon every incoming request is verified by signature; for orders delivered by a Yemeksepeti rider the customer's personal data is never stored, and for orders delivered by your own driver the name, phone and address are erased automatically 30 days after the order closes. The sale itself is kept as a legal record.
Frequently asked questions
Do I still need the Yemeksepeti tablet?
Not for accepting and managing orders; you do that from the till. The platform's own panel is still where you handle campaigns, reviews and payouts.
I have several branches — is each one connected separately?
Yes. Each branch gets its own connection code and its orders land only on that branch's till.
Is auto-accept safe?
If your kitchen comfortably handles every order, auto-accept saves time: the order is accepted the moment it arrives, with the default prep time, and goes to the kitchen. Where volume swings, leaving acceptance to the cashier gives more control.
Conclusion
A Yemeksepeti integration puts delivery on the same footing as the dining room: one screen, one menu, one report. The biggest gain is that missed orders and re-typed tickets disappear at peak time. See how it looks on our Yemeksepeti integration page, or get in touch.