Yandex Eda: connection and order handling

Until the connection is activated, enter orders from the marketplace dashboard manually using the workflow below. This lets the kitchen, Expo and records in cenaly.ge see the order.

What you need to get started#

To prepare the integration, you need:

• Owner access to location settings and a Premium or Enterprise plan.
• A location whose country is Russia, Belarus, Kazakhstan, Armenia, Kyrgyzstan or Uzbekistan. These countries determine card visibility, not guaranteed activation by Yandex.
• A menu with items assigned to the correct location.
• For a future live connection: a Place ID supplied by Yandex and an agreed location connection.

Manual entry does not require an integration. Staff need access to order creation and POS, with the kitchen and Expo configured. An owner or manager sets up an own payment method beforehand.

If you have several locations, check the selected location first: each has its own connection and payment method list.

Prepare a location connection#

The purpose of this step is to save settings and obtain the address for future marketplace onboarding.

1. Open App Store → My apps → Connections by location.
2. Select Yandex Eda and the required location. The Yandex Eda POS integration block opens.
3. Enter the Place ID.
4. Expand Advanced settings, review the settings below and click Connect.
5. Copy the address under Webhook URL for Yandex Eda onboarding (share with Yandex Eda team): to share with the Yandex team during onboarding.

The former store layout used a “Per location” tab; the current interface places these settings under “My apps”.

Result: the card stores the selected location’s settings. In test mode it displays a warning that Yandex access has not been activated.

If the card is missing or fails to load, check the location country and plan access. For a loading error, click Retry.

Prepare the menu and prices#

The operations below currently run in test mode. A success message on the card does not prove that the menu has been published to the live marketplace.

1. Check the dishes, prices, variants and add-ons in the location’s menu.
2. Set Price markup, % for a general price adjustment.
3. For individual differences, use Channel menu overrides: set an item’s price, name, description or photo; hide items or categories you do not want to send.
4. Click Save & sync to save overrides. This starts a menu push.
5. After changing the main menu, click Push menu to Yandex Eda: those changes are not automatically pushed again.
6. Open Sync log and check the operation result.

An empty override price applies the channel markup. Other empty fields use the main menu values. Variants and add-ons are sent as item modifier options.

For the reverse direction, use Import menu from Yandex Eda. It creates new items and skips duplicates; before confirming, make sure you are importing into the correct location.

In Channel commissions, enter your contractual percentage and fixed amount per order. These are internal commission calculation settings, not changes to your marketplace agreement. Do not substitute an estimated market rate.

Result: the channel menu and prices are prepared, and the push attempt is recorded in the log. If an operation fails, use the troubleshooting table below.

Check order handling and pause controls#

To test the internal workflow, click Create test order on the connection card, then Go to Orders.

1. Find the order in Orders and check its contents and location.
2. Check that it appears on the configured KDS. When source display is enabled, the ticket shows Yandex Eats.
3. After preparation, check the order on Expo, which has a Yandex Eda channel badge.

Result: you have checked the test order’s journey inside cenaly.ge. This does not test receipt of a live order from the Yandex app.

Orders has no dedicated panel for sending Yandex Eda order actions to the marketplace. Do not expect the same buttons as for Wolt or Glovo. Actions sent to Yandex through the integration are currently owner-only; an internal readiness update does not replace confirmation in the marketplace dashboard.

KDS and POS provide Pause order intake controls for managing workload:

• Busy +N min adds preparation time.
• Pause 30 min, Pause 60 min or Until end of day stops intake for the selected period.

The shared mechanism also passes pause and additional preparation time to the Yandex Eda connection. This is currently test exchange: control the real location’s availability in the Yandex dashboard.

Marketplace orders without integration#

Use this workflow for any marketplace without a connection, including while Yandex Eda activation is pending. The order first arrives in the marketplace dashboard, and a staff member creates a copy in cenaly.ge.

Prepare a payment method#

1. At POS, open POS appearance, find Own payment methods · Buttons in the payment window and click Set up.
2. Click Add method and enter Yandex Eda in Name.
3. Under For the fiscal receipt, select the payment type agreed with your accountant.
4. Make sure the method is enabled for display at the register and save the changes.

Result: you can select a separate “Yandex Eda” method at POS payment and distinguish those payments by name in the shift report. If the button is missing, check the location and whether the method is enabled for display.

A marketplace courier collects the order#

1. Open the order in the marketplace dashboard and make sure it has not already been entered in cenaly.ge.
2. In Orders, open New order and select Pickup: your location’s part ends when you hand the order to the marketplace courier.
3. In Customer name, enter Yandex Eda courier. In Phone, enter the current marketplace support number from your dashboard.
4. Copy the items, quantities, variants and add-ons. Set Pickup time if a time has been agreed; leaving it empty means as soon as possible.
5. Compare the contents and total with the marketplace dashboard, then click Create order.
6. At POS, find the created order in Open tabs. When recording payment, select your own Yandex Eda method if the marketplace collected the money and your accountant has agreed this procedure.
7. The kitchen prepares the order; staff at Expo check that it is complete and hand it to the courier.
8. For a pickup order, complete handoff with Handed to customer. A delivery order uses Handed to courier.

Result: the order passes through the kitchen and Expo, and payment is recorded using the selected method. Staff update marketplace dashboard statuses separately: manual entry does not send them to the marketplace.

If the marketplace order is cancelled or changed, make the corresponding changes in cenaly.ge separately. Do not create a second copy instead of correcting the first.

Your own courier delivers the order#

1. When creating the order, select Out for delivery — the delivery type in this form.
2. Enter the guest’s actual name and phone number, address and delivery details from the marketplace order.
3. Add the items and create the order; assign your courier using the normal delivery workflow.
4. If the marketplace collected payment, use the agreed “Yandex Eda” method at POS. If your courier collects the money, record the guest’s actual payment method.
5. After assembly, hand the order to the courier and complete delivery once it reaches the guest.

Result: this is a regular delivery order with your own courier. Managing the order in the marketplace dashboard remains a separate staff task.

Limitations#

• The Yandex Eda integration is still in test mode; live orders and marketplace exchange are not verified.
• Marketplace promotions, including gifts and “1+1”, cannot be configured in cenaly.ge. Manage them in the Yandex dashboard.
• There is no integration with Market Delivery (formerly Delivery Club).
• There are no integrations with EdaSakhalin, Chibbis or Kuper; use manual entry.
• Orders has no dedicated Yandex Eda action panel; marketplace actions are restricted to the owner.
• Main menu changes require a manual push. A full push ignores the separate stop list.
• You cannot select “Yandex Eda” as a manual order’s source. The guest name and own payment method do not turn it into a marketplace-channel order: distinguish these payments by payment method, not by channel in reports.
• An own payment method does not disable the fiscal receipt. A manually entered order has no automatic link to the marketplace dashboard.

Troubleshooting#

Frequently asked questions#

Do I need to enter a Client ID and Client Secret?#

No. The location form asks for a Place ID. There are no user-facing OAuth secret fields here; this does not mean that partner access has already been arranged.

Can I send only part of the menu?#

Yes. Channel menu overrides can hide individual items or whole categories. Saving starts synchronization; in the current mode it is a test operation.

Does adding a payment method connect the marketplace?#

No. It helps record payment under the marketplace’s name. Staff still enter the order, changes and statuses manually.

Can I work with several marketplaces?#

For manual records, create separate payment methods to distinguish payments. Each marketplace and location has independent integration settings; having a card does not guarantee live exchange.

Related sections#

• Delivery with your own courier
• Order handoff at Expo
• Kitchen display system
• POS
• Delivery and marketplace receipts on cenaly.ru
• Integrations