Yemeksepeti Integration

Chain and branch: two different identifiers, two different jobs

The Yemeksepeti connection has two identifier concepts, and confusing them leaves the setup half-finished. The chain identifier represents your business as a whole and appears inside every API path; it is required. The branch identifier points to a single location and is needed for pulling orders, listing products and handling categories. The chain identifier establishes the connection, but without the branch identifier the daily flow does not work.

There is also a secret token for order notifications, and you do not generate it: it is created automatically when the connection is established. Seeing it empty on the setup screen is normal.

Grocery operations work differently from a marketplace

The Yemeksepeti grocery side differs from a classic marketplace in a few ways, and those shape the connection. First, there are no variants: grocery products do not carry size or colour, each product is a single item. Second, product submissions are queued and the outcome is fetched separately.

Third, and operationally the most important: stock accuracy matters more in grocery than on a marketplace. The customer expects the order within half an hour; showing an item you do not have means a cancellation and a rating hit. Delayed stock sync hurts more here.

The connection is built around those three realities: products are created through the queue, stock and prices feed from the same pool as your other channels, and a sale on one channel drops stock on the others.