The short answer
Hepsiburada Shopify integration is the automatic transfer of products, stock and prices from your Shopify store to Hepsiburada, and of Hepsiburada orders back into Shopify (and from there into your ERP). The connection is built through a middleware layer between Hepsiburada's seller APIs and the Shopify GraphQL Admin API and webhooks.
What sets a Hepsiburada integration apart from other marketplaces is the catalogue structure: a product sold on Hepsiburada often already exists in the Hepsiburada catalogue, and your product is matched to that record before it goes on sale. With an off-the-shelf integrator you can go live in 2–4 weeks; setups with an ERP and channel-specific pricing rules take 6–10 weeks.
This guide draws on the field experience of Byte Digital, a Shopify Plus Partner that has served Shopify brands for 7 years.
Which data is synchronised between Hepsiburada and Shopify?
Products, stock and prices flow from Shopify to Hepsiburada; orders, cancellations and returns flow from Hepsiburada to Shopify.
Data | Direction | Frequency | Shopify side | Hepsiburada side |
|---|---|---|---|---|
Product content | Shopify → Hepsiburada | On new products | Product, ProductVariant, metafields | Catalogue product (category, attributes, images) |
Listing | Shopify → Hepsiburada | On change | SKU, price, stock | Merchant SKU, Hepsiburada SKU, price, stock, dispatch time |
Stock | Shopify → Hepsiburada | Every 5–15 minutes | InventoryLevel | Sellable stock |
Price | Shopify → Hepsiburada | On change | Price or a channel-specific price field | Listing price |
Order | Hepsiburada → Shopify | Every few minutes | Order (with channel tag) | Order and package |
Shipping | Shopify ↔ Hepsiburada | On dispatch | Fulfillment | Package, carrier, tracking number |
Cancellations and returns | Hepsiburada → Shopify | Event-driven | Cancel, Return, Refund | Cancellation and return requests |
Hepsiburada-specific rules: catalogue, listings and SKU matching
On Hepsiburada a product has two identities: the merchant SKU you assign and the Hepsiburada SKU created in Hepsiburada's catalogue (a code starting with HBV). Every record that is on sale, the listing, links these two codes; price, stock, dispatch time and maximum purchase quantity are kept on the listing.
Catalogue matching: If the product already exists in the Hepsiburada catalogue (for example, a branded item with the same barcode), it is matched to the existing record instead of opening a new product. If not, a new catalogue product is created with its category, mandatory attributes and images and goes for approval.
SKU discipline: Stock and price updates are matched through the merchant SKU. The SKU in Shopify and the merchant SKU on Hepsiburada must be identical and must not change later.
Categories and attributes: As with Trendyol, Shopify collections are mapped to Hepsiburada categories and product attributes to category attribute values. For products with variants, variant attributes are mapped separately.
Asynchronous updates: Price and stock updates return a tracking number; whether the operation succeeded is checked separately with that number.
Access: API credentials are obtained from the seller panel; if an integrator is used, it must be authorised from the panel. Brand approval may also be required for your own brand.
Shipping: Orders can be shipped through Hepsiburada's logistics network HepsiJet or contracted carriers; which carrier is used is managed at the listing and order package level.
Hepsiburada Shopify integration methods
An off-the-shelf integrator suits Hepsiburada alone, a multichannel platform suits several marketplaces, and custom middleware is the right choice for ERP-connected setups and custom rules.
Method | When to choose it | Setup time | Flexibility | Ongoing cost |
|---|---|---|---|---|
Off-the-shelf integrator | Hepsiburada only, standard catalogue | 1–3 weeks | Low–medium | Monthly licence |
Multichannel marketplace platform | Several channels such as Hepsiburada, Trendyol and Amazon | 2–6 weeks | Medium | Monthly licence, often per-order fees |
Custom-built middleware | ERP integration, channel-specific pricing, high volume | 6–10 weeks | Highest | Hosting + maintenance |
In the architecture we recommend, Shopify is the single hub: product content and stock are managed in Shopify, Hepsiburada orders land in Shopify with a channel tag, and the ERP takes orders from Shopify. Hepsiburada, Trendyol and the website are all fed from the same stock.
Stock, pricing and commission management
When several sellers offer the same product on Hepsiburada, the featured offer depends largely on price, stock and dispatch time, so all three must be managed correctly by the integration.
Channel-specific price: A Hepsiburada price that covers commission and shipping should be kept in a variant-level metafield or applied in the middleware with a category-based multiplier.
Dispatch time: The dispatch time on the listing should reflect your real warehouse capacity. Short times that are not met lower the seller score.
Maximum purchase quantity: Can be used on campaign products to stop a single order from emptying the stock.
Safety stock: In multichannel selling, keeping a buffer of 1–2 units on critical products lowers the risk of cancellations.
Deactivating: An out-of-stock listing should be kept by setting the stock to zero or deactivating it rather than deleting it, so the catalogue match is preserved.
Hepsiburada Shopify integration step by step: timeline and cost
2–4 weeks with an off-the-shelf integrator, 6–10 weeks with custom development; catalogue matching takes the most time.
Preparation (1 week): Seller account, API or integrator authorisation, brand approvals, carrier preferences.
Catalogue analysis (1–2 weeks): Determine which products already exist in the Hepsiburada catalogue and which will be opened new; complete missing barcodes and SKUs.
Matching and setup (1–4 weeks): Category and attribute mapping, listing creation, stock and price flow, order and shipping flow.
Pilot (1 week): Go live with 20–50 products; review approval results and unmatched SKUs.
Full catalogue and monitoring (1–2 weeks): The remaining products are opened; stock and order errors are tracked daily.
The main cost drivers are the number of products, the share of products already in the catalogue, category variety, an ERP connection such as Nebim, Logo or Mikro, and whether the same integration will also cover other marketplaces.
The 5 most common mistakes in Hepsiburada Shopify integration
Mapping the SKU to the wrong field: The Shopify SKU must match the merchant SKU, not the Hepsiburada SKU (the HBV code). A wrong mapping means stock updates never apply.
Changing the SKU later: A SKU changed in Shopify breaks the link with the Hepsiburada listing and the product stops receiving stock.
Not checking update results: Price and stock updates run asynchronously; if failed ones are not tracked, the product keeps selling at the old price.
Deducting stock through two separate integrations: If Hepsiburada and Trendyol are connected with different tools, the same item can be sold on both channels.
Unrealistic dispatch times: When a short dispatch time is not met, the seller performance score drops and product visibility falls.
Hepsiburada Shopify integration with Byte Digital
Byte Digital is an Istanbul-based Shopify Plus Partner that has provided Shopify setup, Shopify migration and integration services to leading Turkish brands for 7 years. With our Shopify-centred setup, you manage Hepsiburada and other marketplaces through a single stock pool and a single ERP connection.
Share your product count, the ERP you use and the marketplaces you sell on, and we will prepare a free pre-assessment with the right method, timeline and an estimated budget.
Request a free Hepsiburada Shopify pre-assessment →
Frequently asked questions
Can Shopify be integrated with Hepsiburada?
Yes. A Shopify store can be connected to Hepsiburada through Hepsiburada's seller APIs, either with an off-the-shelf integrator or with custom middleware. Products, stock and prices flow from Shopify to Hepsiburada; orders flow from Hepsiburada to Shopify.
How long does a Hepsiburada integration take?
With an off-the-shelf integrator, a standard catalogue goes live in 2–4 weeks. With an ERP connection or channel-specific pricing rules, custom development takes 6–10 weeks.
What is the difference between the Hepsiburada SKU and the merchant SKU?
The merchant SKU is the code you assign to the product; the Hepsiburada SKU is the code of the product in Hepsiburada's catalogue. The Shopify SKU must match the merchant SKU exactly.
What happens if my product already exists on Hepsiburada?
Instead of opening a new product, it is matched to the existing catalogue record and goes on sale with your own price, stock and shipping details.
Can the Hepsiburada price differ from the Shopify price?
Yes. To cover commission and shipping, a channel-specific price is managed with a variant-level field or a category-based multiplier.
