Yemeksepeti menu management: sold-out items, price changes and menu sync
A latte is 95 TL on the till and 90 TL on Yemeksepeti. The kitchen has run out of köfte but the platform is still selling it. Both happen sooner or later in any restaurant that runs its menu in two places. This post explains the idea of running your Yemeksepeti menu from the POS, and how to do it in practice.
Why one menu?
Two menus mean two versions of the truth. When price, name, description and availability are kept in two places, one of them will be updated and the other forgotten. With one menu, the POS owns the menu and the platform is a reflection of it.
A menu should have one owner. A price fixed on the platform will be replaced by the POS price on the next menu push — so always change prices on the POS.
Pushing the menu to Yemeksepeti
In ari adisyon, your branch menu is sent to Yemeksepeti with "Push menu" on the Management → Yemeksepeti screen. Items go with their categories, names, descriptions and prices; Yemeksepeti finishes the import within a few minutes and you see the result on screen.
Menu changes flow one way: from the POS to Yemeksepeti.
How does product matching work?
When the menu is pushed from the POS, each item goes with its own ID. When an order comes in, the item is matched to the POS product by that ID; the kitchen ticket shows your product name and the item goes to the right station. If an item does not match, the order card shows a warning — usually a sign the menu needs pushing again.
Switching off sold-out items instantly
Sold-out items are one of the most common reasons for rejecting an order. When you mark an item sold out on your menu, ari adisyon also switches it off on Yemeksepeti; when you turn it back on, it opens on the platform too. The sold-out badge on the waiter's screen and the platform stay in step.
When sold-out status lives in one place, the contradictions go away.
Publishing price changes safely
- Change the price on the POS menu.
- Batch your changes; push once a day rather than for every small edit.
- Publish with "Push menu" and check the import result.
- Open one or two items in the platform panel to confirm the price arrived.
Think of campaigns and discounts separately: the platform's own campaigns are managed in the platform panel; your till campaigns are for dine-in sales. When a platform discount is partly funded by the restaurant, that share is written to the tab as a separate discount line when the order arrives.
Menu layout tips
- Name categories with delivery in mind: "Mains", "Drinks", "Desserts".
- Add portion and ingredient details to descriptions; you'll get fewer customer questions.
- Rethink items that do not travel well (fast-melting desserts, foamy drinks) for the delivery menu.
- If you list calories and allergens, keep them current.
Per-branch menus
If you have several branches, each one pushes its own menu. An item not sold at one branch does not appear on that branch's Yemeksepeti menu; an item sold out at one branch closes only there. A branch with different prices can run its own menu without affecting the others. For multi-branch businesses, see our multi-branch management post.
If a menu push fails
An import can occasionally fail because of an item name, missing information or a rule on the platform side. The result shows on the Yemeksepeti screen; you fix the problem and push again.
Frequently asked questions
Where do I manage product photos on Yemeksepeti?
Photos and visual edits are made in the platform's own panel. The menu pushed from the POS carries item names, descriptions, categories and prices.
Can I use different prices for dine-in and delivery?
Because the POS owns the menu, the price sent to the platform is the POS price. If you want separate delivery pricing, plan it with your account manager and your menu layout; tracking two prices by hand brings the mistakes back.
How quickly does sold-out status show up?
It is sent to the platform the moment you mark the item sold out. When it appears in the customer app depends on the platform's own update, which is usually quick.
Conclusion
Treat your Yemeksepeti menu not as a separate job but as an extension of your POS menu. Changing prices and availability in one place cuts both mistakes and needless rejections. See the full integration on the Yemeksepeti integration page.