Logo Hepsiburada Integration
For sellers who want their Hepsiburada store to follow the same routine as Logo: the catalogue link between listing and product is built first, packaging is then completed in the panel, and the order lands in Logo. Quantities and prices are fed from Logo.
What is the Logo Hepsiburada integration?
The Logo Hepsiburada integration ties the two ends together: an order raised on Hepsiburada moves into Logo, and the stock and prices kept in Logo reach the listings through the catalogue link.
What sets the pace in this pairing is the catalogue. A listing reaches your product through Hepsiburada's own catalogue, so the first piece of work is building that link from the merchant SKU and barcode held in Logo. A stock or price update sent before that link exists has no listing to land on, which is why matching comes ahead of every other step here.
The second thing that makes this pair its own is packaging. The step is completed in the panel rather than the seller screen, partial packaging and split lines each keep their own record, and the order reaches Logo with its customer and line items. Invoicing and dispatch carry on inside Logo as they do today, and onboarding starts in shadow mode.
What flows in which direction
Orders and packaging from Hepsiburada into Logo
The order reaches the panel with its lines, its buyer and the delivery address together. Packaging finishes here, each line split out of a partial pack keeps its own record, and the order is written into Logo once that step is done.
The catalogue link by merchant SKU
A listing is bound to the product in Logo through merchant SKU and barcode, at colour and size variant level. Until that link exists an update has no listing to reach, so unmatched items are listed for you first.
Stock out to Hepsiburada, listing status back
A quantity has one source: the stock held in Logo. The moment a shop sale or a warehouse movement happens, the Hepsiburada figure is refreshed in batch requests, and whether a listing is live, awaiting approval or closed is read off the same list.
HepsiJet and the carrier flow
A package moves with HepsiJet or a contracted carrier. Carrier, tracking number and label details come with the order, and once dispatch is marked on the Logo side the Hepsiburada record is updated.
Returns, exchanges and settlements
A return request sits under the order it belongs to; goods reaching the warehouse are received by barcode and an exchange order opens in one step where needed. Settlement lines are matched to orders, and anything that does not agree is gathered under its own heading.
How the Logo Hepsiburada integration is set up
Connect
Your merchant ID and the API user credentials defined for the integration are taken from the Hepsiburada seller panel, entered in the panel, and the connection is tried on the same screen. For the Logo end, you work the access details out with your Logo partner.
Match
In the panel a Hepsiburada listing finds its Logo product by merchant SKU and barcode. This step is finished ahead of the others, because an update without the catalogue link has no listing to reach; variants are linked in bulk from a matrix view.
Watch
In shadow mode the system reads only and writes nothing. You compare orders and listing statuses against the figures in Logo.
Hand over
Write access opens first for orders and packaging, then for stock and prices. Which Hepsiburada listings the panel drives is set product by product with the ownership flag.
Technical summary
| Systems connected | Logo and Hepsiburada |
|---|---|
| Order direction | From Hepsiburada into Logo; packaging is completed in the panel before the order is written |
| Stock and price direction | From Logo out to Hepsiburada, once the catalogue link is in place |
| Matching key | Merchant SKU on the Hepsiburada side, stock code and barcode on the Logo side; an update has no listing to reach before the catalogue link is in place |
| Fields carried on an order | Customer, line items, delivery address, carrier, tracking number |
| Update timing | The moment a sale happens; there is no queued batch job and no polling hour |
| Needed on the Hepsiburada side | Merchant ID and the API user credentials defined for the integration; no extra module required |
| Needed on the Logo side | Access details defined by your Logo partner; nothing new is built inside Logo |
| Invoicing and shipping | Unchanged; they keep to the Logo routine you run now |
| Onboarding | Starts in shadow mode; write access opens for orders and packaging first, then stock and prices |
Frequently asked questions about the Logo Hepsiburada integration
How is the catalogue link to my Logo products built?
Matching runs on merchant SKU and barcode and is linked at colour and size variant level. An update sent before that link exists has no listing to reach, so unmatched items are listed and corrected first.
Where is the packaging step done?
In the panel, without going back into the seller screen a second time. Partial packaging and split lines keep their own records, and the order is written into Logo after that step.
How do carrier and tracking details flow?
A package moves with HepsiJet or a contracted carrier, and carrier, tracking number and label details come with the order. As soon as dispatch is marked in Logo, it shows on the Hepsiburada record.
Does my invoicing routine change?
No. Whoever raises invoices and arranges dispatch in Logo keeps doing it; the integration does not step into those two.