A mapping table per platform
Product, size, category and modifier: each of the four dimensions is paired with that platform's own code. You keep the scope to one branch or widen it to the whole chain.
Product mapping227/24518 unmapped
ProductGetirTrendyolYemeksepeti
Pizzas
MargheritaMargherita PizzaGTR-10482MargaritaTY-88213MARGHERITAYS-4471
Sucuk pizzaSucuklu PizzaGTR-10486SucukluTY-88219Map
Drinks
Ayran 300mlAyranGTR-20031Ayran 300 mlTY-90114AYRANYS-5120
The codes come from each platform's own catalogue. A mapping is kept per platform.
Integrations
Platform Integrations
Getir Yemek, Trendyol Go, Yemeksepeti, Migros Yemek and Fuudy in one dashboard. Each platform keeps its own catalogue and its own product codes, so the mapping is held per platform — and the panel tells you which platform supports what.
Getir YemekTrendyol GoMigros Yemek
5
Connected delivery platforms: Getir Yemek, Trendyol Go, Yemeksepeti, Migros Yemek, Fuudy
4
Mapping dimensions: product, size, category, modifier — each with its own remote code
4
Order steps: accept, prepare, hand over, complete — the same on every platform
24/7
Support, two hours to an answer on average
The boundary
The platform writes the menu; we map it and hold up the mirror.
Each platform keeps its own catalogue and its own product codes. Dasvio pulls that catalogue, maps it to your products, and writes back a short list of fields. No endpoint anywhere creates a product on a platform; saying otherwise would promise a button that does not exist.
01
Two directions
Inbound: the catalogue, categories, options, orders and reviews. Outbound: price, product status, availability, whether the restaurant is open or closed, busy mode, working hours and preparation time. That is the whole list.
Getir YemekDasvio
InboundPlatform Dasvio
CatalogueCategoriesOptionsOrdersReviews
OutboundDasvio Platform
PriceProduct statusAvailabilityOpen / closeBusy modePrep timeMenu creation· no endpoint
The menu is authored in the platform's own panel. We pull the catalogue, map it, and write back only the fields above.
02
Five platforms, not the same features
Price updates exist on Getir, Trendyol and Migros Yemek; Yemeksepeti has no pricing endpoint. Reviews are read on Getir and Trendyol, and answered on Trendyol alone. Busy mode and courier control belong to Getir and Yemeksepeti.
What each platform carries
PriceReviewReplyClaimReportBusyCourierHoursStock
Getir YemekChain menu
Trendyol GoSupplier
Yemeksepetino price API
Migros YemekBranch + menu
Fuudyno price API
A filled square means the platform has it; a dash means it does not. The gaps belong to the platforms' APIs, not to ours.
The empty cells are the platforms' API limits, not gaps in ours. Knowing what a platform carries before you connect it is better than finding out afterwards.
Mapping recordScope: branch
DasvioMargheritaGetir YemekMargherita Pizza
product_id#4820
The Dasvio product
remote_product_idGTR-10482
The platform's own code
remote_product_nameMargherita Pizza
Its name over there
platform_price₺239
The price on that platform
is_available_on_platformtrue
On sale there
Mapping
Not once — once per platform.
The mapping table is kept per platform: each one has its own product code, its own name and its own price, and they do not merge into a single shared record. Widening the scope carries a mapping to your other branches — not to the other platforms.
- Product, size, category and modifier: four mapping tabs, four separate remote fields
- Scope is branch or chain; moving from one to the other settles each conflict by hand
- Bulk matching suggests candidates by name and does not run at all before the catalogue is fetched
AllUnmapped18Price differs
Unmatched Getir products
Fırın SütlaçDessert₺95
Ayran 1LDrink₺48
Pizza Menü 2Combo₺420
LimonataDrink₺75
They exist on the platform and have no counterpart here. None is created on its own.
Price and status
What we write back is a short list.
Everything we send to a platform goes through an endpoint of its own: price, a product's open, busy or closed state, item availability on Yemeksepeti, opening and closing the restaurant itself, busy mode, working hours and preparation time. The menu is not on that list.
- The pricing sheet shows one platform: product, current price, new price, discounted price
- Product status has three steps: open, busy, closed
- If you hit the platform's request limit the panel says so and a refresh countdown starts
The mapping record
A mapping is five fields.
This is what gets written when you bind one of your products to its counterpart on a platform: our product, the platform's code, its name over there, its price over there, and whether it is on sale over there. The record moves nothing by itself; it says which product is which, and you start the transfer afterwards.
Getir YemekPrices are updated through the chain menu
ProductCurrentNew ₺Discount ₺
Margherita₺229₺239—
Sucuklu Pizza₺249₺249₺219
Ayran 300ml₺32₺36—
Sezar Salata₺185₺185—
Changes are sent in one batchSave (2)
The scope chip says where the record was written: to this branch alone, or to the whole chain.
- remote_product_idThe platform's own product code. It is not minted here; it comes from that platform's catalogue.
- remote_product_nameThe same product's name over there; the panel shows you this rather than the code.
- platform_priceThe price on that platform. It is independent of your dine-in price and does not change it.
- is_available_on_platformWhether the product is on sale on that platform — one platform at a time.
Capabilities
Everything Platform Integrations ships with, end to end.
An integration is four jobs: building the mapping, seeing what is unmatched, writing a price back, and knowing what each platform carries.
The four jobs of an integration
All four are part of the same connection; none of them is bought separately.
Unmatched items stay visible
A product with no counterpart is listed rather than blocked. Bulk matching suggests candidates by name; you approve the record.
A platform price, by that platform's rule
Price updates exist on Getir, Trendyol and Migros Yemek, and each writes them a different way: chain menu, supplier level, branch plus menu.
What each platform carries
Reviews are read on Getir and Trendyol and answered on Trendyol alone. Busy mode and courier control belong to Getir and Yemeksepeti.
FAQ
Frequently asked questions
How does the Yemeksepeti integration work?
Yemeksepeti orders land straight in the Dasvio dashboard and on the kitchen printer — no separate tablet to watch. Menu, price and stock changes sync from the dashboard back to Yemeksepeti, and you open or close the restaurant with one toggle.
Is there a Getir integration?
Yes. Getir orders flow into the same order list as every other channel, route to the kitchen automatically and report by channel at the end of the day. You can update prep times from the dashboard during a rush.
How are Trendyol orders and claims handled?
Orders collect in one dashboard; you approve or reject Trendyol claims (refund/dispute requests) from the inbox inside Dasvio, and reply to platform reviews from the same place.
Is Migros Yemek supported?
Yes. You map your catalogue once; products, prices and availability stay in sync across every connected platform, Migros Yemek included.
Can I run different prices per platform?
The platforms are not alike in this, and the panel knows it: separate prices can be written for Getir Yemek, Trendyol Go and Migros Yemek. On Yemeksepeti the price is managed in that platform's own panel; what Dasvio controls there is item availability and the restaurant's open state.
Do integrations cost extra?
The Starter plan includes one platform integration; Pro and above include them all. There is no per-order integration fee.
Get started
Let us connect your platforms together.
Which platforms you sell on, which credentials each one needs, how your catalogue will be mapped — we set all of it up with you. The average business goes live in 14 days.
No brand lock-in — it runs on the hardware you already haveLive in 14 days on average, from a single site to a chain24/7 Turkish-language support, included on every planGİB compliant, KVKK compliant — no add-on module needed
- Support hotline
- 24/7
- Average setup time
- 14 days
- Uptime guarantee
- 99.9%
Keep exploring