Shopify Hepsiburada Integration

To sell your Shopify products on Hepsiburada, the two systems need to stay in conversation. Hepsiburada does not publish an official Shopify app, so an integration tool builds this connection. Setup starts with the seller application and closes with the first order. In between, the product, stock, price and order flows are each set up separately, and the points where setup stalls sit inside those flows.

Talk to us about setup See the integration

200+ active brands
growing on Shopify with Nodus Works

Shopify Hepsiburada integration what is it?

The Shopify Hepsiburada integration is the connection that keeps your products, stock counts, prices and incoming orders aligned in both systems. On Hepsiburada a product first lands in the catalog; it moves to the sale list only after matching is approved and a price is written. This two-stage structure is the first point that sets the integration apart from other marketplaces.

Setup starts once your Hepsiburada seller account is approved. You then request integration access from the seller panel, register the tool you use as the integrator, map category and brand, and define your price and stock rules. When category and brand mapping goes beyond the standard template, Nodus Works' Shopify integration and custom app development service takes over this setup. After products are sent to the catalog you have to approve matching; the last step is a trial order with a single product.

Once the connection is live, daily work runs from one place. Orders created on Hepsiburada land in Shopify, stock on a sold product drops on both sides, and shipping and invoice steps move on the same record. Because one order can split into more than one package, the warehouse follows the package, not the order.

WHAT IS SYNCED

Between Shopify and Hepsiburada what stays in sync

Once the connection is live, product data, stock, price, orders, shipping and invoices sit in the same flow. The six headings below cover the questions we hear most often about the Shopify Hepsiburada integration.

Hepsiburada product transfer and sync

After category and brand matching, your Shopify products are sent to the Hepsiburada catalog and then move to the sale list. Every variant needs a barcode and a product code written in capital letters; incomplete rows never enter the catalog.

Shopify Hepsiburada stock sync

When a sale happens on one channel, the other channel's quantity drops as well, so two stores do not sell the same last unit separately. If the product is held in a Hepsiburada warehouse, Hepsiburada manages the quantity and stock is not written to that row from Shopify.

Shopify Hepsiburada price sync

The Hepsiburada price is set with a rule that adds commission and any shipping share on top of the Shopify price. Hepsiburada also applies a ceiling based on the same product's past price, so that cap has to be taken into account when you raise a price.

Hepsiburada order transfer

Orders created on Hepsiburada are written into Shopify, so you work from the same list as the warehouse. Because one order can split into more than one package, the warehouse follows the package, and records whose payment is not complete wait in a separate list.

Creating a Hepsiburada shipping label

The shipping label is produced in the seller panel and you can change the carrier. Delivery information comes to you from Hepsiburada; if you use your own shipping agreement, you also write the status yourself.

Hepsiburada invoice link

The invoice link is given on the package, and packages without an invoice collect in a separate list. The invoice itself is issued in your e-archive or e-invoice system; connecting your accounting software is a separate job.

FEATURES

Bulk updates, matching and multi-store

On Hepsiburada a product is written first to the catalog and then to the sale list, so the number of rows you have to follow by hand doubles. Bulk updates, category matching and multi-store management are therefore part of the setup, not extras.

Bulk stock and price updates

You can filter price, stock and shipping data by category and update it in one pass. Rows that exceed the price ceiling stay out of the update, so that list has to be checked after a campaign.

Bulk price updates
Fast stock changes
Campaign management

Multi-store Hepsiburada management

If you have more than one Hepsiburada store, you can run all of them from a single Shopify stock pool. Each store keeps its own product list, the stock pool stays shared, and you can set a separate price rule for every store.

Control from one panel
Shared stock pool
Central management

Hepsiburada category and attribute matching

Your Shopify category is bound to Hepsiburada's deepest leaf, and attributes are picked from Hepsiburada's prepared list. If the same product is already in the catalog, a new page is not opened; the system asks you to approve binding to the existing page.

Automatic categorization
Attribute matching
Existing product matching

SETUP

How is the Shopify Hepsiburada integration set up?

The six steps below cover the full setup, from the seller application to the first trial order. Most of the work happens in the Hepsiburada seller panel, so you need to sign in with an authorized account; on the Shopify side it is enough that your store is live.

Open your Hepsiburada seller account

The application is filed at merchant.hepsiburada.com with your company details and documents. Categories such as cosmetics, food and toys ask for extra papers, so approval can stretch on those rows.

Request integration access

On Hepsiburada, access does not arrive with the account, so it is requested separately. When you open Integrator Information under Integration in My Information in the seller panel, your seller number and connection key are created there.

Register your tool as the integrator

On the same screen you define your tool as the integrator, because requests sent without a registered integrator are rejected. This is also where you see that some apps do not send products to Hepsiburada and only sync stock.

Map category, brand and attributes

You need to pick the deepest leaf category and write a barcode and a product code in capital letters on every variant. The brand name also has to be approved on the Hepsiburada side; a product sent with an unapproved brand does not enter the catalog.

Approve the match

If the same product already exists on Hepsiburada, the system suggests binding to the existing page instead of opening a new one, and that suggestion waits for your approval. Rows you do not approve stay in the catalog and do not appear in the store; more detail is in the matching section.

Confirm the flow with a trial order

After you set the price rule and check the ceiling, place an order with a single product. When you see that the order lands in Shopify, that stock drops and that the invoice link is written, you can open the rest of the catalog.

Building the connection finishes the same day. Opening products for sale depends on matching approval and category checks, so it can take days; the duration of each stage is in the table in the seller section.

The table below shows which Shopify fields map to which Hepsiburada fields, using the names you see in the panel.

What is in Shopify	Hepsiburada equivalent
Title	Product name
Barcode	Barcode
Product code	Seller product code, capital letters and no spaces
Price	Catalog price
Stock	Sale stock
Image	Product images, at most ten
Category	The deepest category
Brand	Brand name approved in the panel

A catalog record is not a sale list: without matching approval and a written price, the product does not appear in the store. Setup has to follow these two stages separately; otherwise the rows you send stay pending without a signal.

Where are you in the setup?

Tell us about your catalog and current setup, and we will work out how the Shopify Hepsiburada integration should be built for your product structure. You do not need to fill in a form, reach us directly by phone, email or WhatsApp.

Get in touch 0850 888 2815 hub@nodusworks.com WhatsApp

SELLER ACCOUNT

What do you need to become a Hepsiburada seller?

To sell on Hepsiburada you need to own a company, and the integration is also built on this company account. The papers requested change by company type, so following the current list on the application screen is the safest path. Access does not arrive with account opening; it is requested separately.

Documents required to become a Hepsiburada seller

The application runs through merchant.hepsiburada.com and the document headings change by company type. The exact list appears on the application screen, so the papers have to be followed there; missing documents extend the approval time.

Extra documents requested by category

Categories such as cosmetics, food and toys ask for extra papers, and those papers extend seller approval. If you assume the paperwork is complete before you decide which category you will sell in, the application waits at this step.

Brand approval and integration access

A product is not opened until the brand name is approved on the Hepsiburada side, and brand creation runs as a panel process, so it cannot be done from outside. Integration access is a separate request as well; in practice it is met within 1 to 3 business days.

If you will sell a new brand, you need to start brand approval before setup, because this step has to finish before products are sent. The access request follows the same logic: if you expect to connect right after opening the account, the integrator screen looks empty.

Seller approval, the access request and opening products for sale are separate timelines. The ranges below are the values we see in practice.

Stage	How long it takes	Note
Seller application approval	No official timeline is published	Extra category documents extend the wait
Brand approval	Panel process	A brand cannot be created from outside
Access request	1 to 3 business days	Does not arrive with the account
Building the connection	Hours	Longer than the flow on the Trendyol page, because two systems are being bound
Opening products for sale	Days	Matching approval and category check

Setups said to finish in minutes usually count only the connection step. On Hepsiburada there is an access request before the connection and matching approval after it; treating the three as a single duration builds the calendar wrong.

PRICING

What sets the price on Hepsiburada?

There are two mechanisms. The first is commission. The rate changes by category and is visible in your panel. Pushing the Shopify amount as-is lowers the margin. The channel price is set as a rule: commission and any shipping share are added on top of the store price. You set the rule once; it is not pushed product by product by hand.

The second is the price ceiling. Hepsiburada applies a cap based on the same product's past price average. As the price range rises, the allowed deviation narrows. If you write a price far above the category average, the product is not opened for sale and stays with price and stock reset to zero. When a store owner arrives saying they sent the product and the price looks like zero, this is usually why.

The official category commission tariff could not be confirmed, so the value in your panel is the one that counts. Raising a price without crossing the ceiling is as much a part of the work as adding the commission.

MATCHING

What happens if the same product already exists on Hepsiburada?

This is the most visible behavior that sets Hepsiburada apart from other marketplaces. On Trendyol the same barcode binds to the existing product page on its own, while Hepsiburada asks for a separate approval for that binding and the product is not opened for sale until you approve it.

The same barcode does not open a new product page

If the product you send already exists on Hepsiburada, the system does not open a new page; it suggests binding to the existing one. Assuming the product was transferred before this suggestion arrives is a mistake.

The match suggestion waits for your approval

Until you approve the suggestion, the product is not opened for sale: it stays in the catalog and does not appear in the store. If setup does not follow this queue, records can stay pending for weeks.

A rejected match does not open a new page in every category

There is a path to reject the suggestion and open a separate record, but it does not work in every category. Assuming a new page opened after a rejection leads to a second wait.

Competing with other sellers on the same product page

When you bind to an existing page, you compete in the same place as the other sellers on that page. The offer that stands out there is chosen by price and delivery time together; you only write your own offer.

Following product statuses

A record moves through stages such as waiting, missing information, match suggestion, matched and rejected. When these stages are not followed, it becomes invisible which step the products are sitting on.

A catalog record is not a sale list

Catalog and sale list are two separate structures on the Hepsiburada side. Landing in the catalog does not mean price and stock were written to the store; the product becoming open for sale happens in a separate step.

The most common reason for "I sent the product but it is not on sale" is a pending match approval; the second is the price ceiling. A setup that does not follow both leaves a product that is live in Shopify closed on Hepsiburada.

STOCK

How does Hepsiburada stock sync work?

A quantity change does not apply to Hepsiburada instantly; it first enters a queue, and the system saying it received the request does not mean stock was written. Hepsiburada does not publish a reflection time, so the only reliable measure is seeing that the update was actually processed.

Stock updates entering a queue

Receiving the request you sent does not mean the quantity was written to the store. If the old quantity is still showing on Hepsiburada, this queue is the first place to look.

Stock management on HepsiLojistik products

If the product is held in a Hepsiburada warehouse, Hepsiburada manages the quantity; writing stock to that row from Shopify breaks the warehouse figure. There is no such split on the Trendyol side, so the same setup causes trouble here.

Keeping unpaid orders separate

If you write an order whose payment is not complete into Shopify as paid, a cancel leaves you with a record that has no counterpart. These orders wait in a separate list and are not handed to shipping.

Writing stock to a locked product

Sending stock while the product is locked does not open the sale; the lock has to be removed first. That is why writing a quantity to suspended rows does not produce a result.

Writing stock in a multi-location Shopify setup

If the sum of every location is sent, quantity from a closed location also appears on Hepsiburada. Which locations open to the channel is given as a separate decision.

Hiding the last few units from the store

Never showing the last few units to the channel lowers the cancel risk. Sellable stock drops by a small amount, but a cancel and the score loss that follows cost more. This rule is set separately for other channels.

Overselling leads to a cancel, and a cancel hits store reviews. Commission rates and approval processes run differently on Trendyol and n11, so writing the same stock rule to every marketplace leaves one channel exposed. If you will open a second channel next to Hepsiburada, see Station to manage product, stock, price and orders from one panel.

OPERATIONS

After an order arrives, how does the process run?

On Hepsiburada the order runs on a package: the warehouse follows the package, while the customer sees the order number. Delivery information comes to you from Hepsiburada, so this end of the flow is built differently from other marketplaces.

Delivery notices arriving in the reverse direction

Hepsiburada sends the delivery information to you and waits for a reply from your system. If no reply arrives, it sends the same notice again, so setup must not process that notice twice.

The seller writing the delivery status

If you use your own shipping agreement, you write the handed-to-carrier and delivered information yourself. On Hepsiburada's contracted carrier, this information can also be processed by the system.

Shipping label and carrier selection

The shipping label is produced in the seller panel and you can change the carrier on the order. Carrier selection is made from Hepsiburada's own list, so names typed by hand are not accepted.

Writing the invoice link onto the package

The invoice link is given on the package, and packages without an invoice collect in a separate list. The invoice itself is issued in your e-archive or e-invoice software; the accounting program is a separate connection job.

Closing return requests

Hepsiburada does not publish a rule that approves a return on its own after a set time. Requests are closed by hand from the panel or through the integration, so a time rule from another marketplace is not carried here.

Orders waiting for payment

An order whose payment is not complete waits in a separate list. If you write this record into Shopify as paid and ready to ship, a cancel leaves you with an order that has no counterpart.

MISTAKES

The most common mistakes in a Shopify Hepsiburada integration

Most work that stalls in the first week looks like a connection error. The real cause sits in the seller number, the price format or matching approval.

Taking the ledger code for the seller number

The connection does not build. The seller number is the long identity on the integration screen. The ledger code from accounting is not written here.

Not sending the price in the format the channel expects

The record opens with zero price and zero stock. Transferring the Shopify amount as-is produces this symptom.

Writing the product code in lowercase or with spaces

The record is rejected. Hepsiburada wants capital letters and no spaces. The code in Shopify is converted before it is sent.

Sending a variant without a barcode

The product is not opened. Every variant needs a barcode. The stock code in the store does not stand in for a barcode.

Leaving matching approval pending

The product stays in the catalog but does not appear on sale. The sale list does not open without approval.

Writing stock from Shopify onto a HepsiLojistik product

The warehouse figure breaks. Hepsiburada manages the stock of these products. Setup separates them.

Crossing the price ceiling

If you write a price far above the category average, the product is not opened for sale. It stays with price and stock reset to zero.

Not answering the delivery notice

Hepsiburada tries again, Shopify falls behind. Without a reply, delivery is not processed.

Opening the same stock to two channels without a rule

Hepsiburada and a second store can sell the same last unit at the same time. If the stock rule is not set separately for each channel, the cancel is born there.

SCENARIO

Three common problems and how we fix them

The three setup scenarios below show how we handle Shopify Hepsiburada integration problems we have solved in stores we connected.

Treating a catalog product as if it were on sale

Problem6 of the 10 products sent stayed on a match suggestion, and the store owner thought the products were open for sale. On two products, price and stock looked like zero. Half of the rows visible in the catalog did not sell at all for a week.

CauseOn Hepsiburada the catalog record and the sale list run separately; a product does not leave for the store until the match suggestion is approved. On the two products that looked like zero, Hepsiburada's price ceiling had been crossed.

SolutionThe matching queue is followed daily and suggestions are not left pending. The ceiling is checked while the price rule is written. The last 2 units are not shown to the channel, so the cancel risk is closed.

Leaving brand approval for the same day as setup

ProblemThe catalog record was created, but the sale never opened. Part of the products sent were rejected outright, and the prices of 3 models opened for a campaign were reset to zero.

CauseBrand approval was still waiting in the panel; rows sent with an unapproved brand do not enter the catalog. In the rejected group, product codes were written in lowercase. The campaign was dropped only in Shopify, so it hit the ceiling on the Hepsiburada side.

SolutionBrand approval is taken before products are sent. Product codes are converted to capital letters before the send. The campaign is also written into the channel price rule, so both sides update together.

Applying the same stock rule to every channel

ProblemUnsellable stock appeared on Hepsiburada, quantities of products held in the warehouse were broken, and when a second marketplace came online the same product sold twice and produced a cancel. A group of products also stayed closed for sale even though stock had been written.

CauseThe sum of every location was written to the channel instead of the sellable location. Shopify quantities were also sent to HepsiLojistik rows. Writing stock to locked products does not open the sale; the lock has to be removed first.

SolutionOnly the sellable location is opened to the channel, and HepsiLojistik rows are kept out of the stock send. Replies to delivery notices are confirmed. When a second marketplace is added, the stock rule is set separately for that channel.

STATION

Shopify Hepsiburada integration

Station is the tool we built to run the product, stock, price and order flow from one panel. When Trendyol or n11 is added, each channel's rule is set separately.

See the integration Talk to us about setup

FAQ

Frequently Asked Questions

How is the Shopify Hepsiburada integration set up?

A seller account is opened, then access is requested separately. When access arrives, the seller number and service key are taken from the integration screen and the tool you use is registered as the integrator. Products go to the catalog, matching is approved, and price and stock are written. The flow is confirmed with a trial order.

Is there a ready Shopify app for Hepsiburada?

Hepsiburada does not publish an official Shopify app. Names that appear in the App Store belong to third-party tools. At least one of them writes in its own description that it does not push products. If you expect to install your store onto Hepsiburada ready-made from the App Store, you are mistaken.

How does the setup calendar work?

Hepsiburada does not publish an official timeline for seller approval. The access request most often arrives in 1 to 3 business days. The connection takes longer because it is written to two systems. Opening for sale depends on matching approval and can take days.

How is Hepsiburada access obtained?

Access does not arrive with the seller account; it is requested separately. The application is filed from the integrator screen under the integration heading in the seller panel. Once it opens, your seller number and service key sit in the same place. The menu can change; searching for integration inside the panel is the fastest path.

Is a separate fee paid for this work?

Hepsiburada does not charge an extra fee for the connection. The amount paid is the subscription of the tool you use. If you develop the software yourself, the cost shifts to maintenance and development. The commission taken on sales sits outside these.

How does commission enter the Hepsiburada price?

The channel price is built by adding commission and any shipping share on top of the store price. The rate changes by category, and the current value sits in the seller panel. There is also a ceiling: that limit has to be checked when you raise a price.

Which documents are required to become a Hepsiburada seller?

A company is required. The documents requested change by company type, and the exact list sits on the application screen. Cosmetics, food and toys ask for extra papers. The brand you sell also has to be approved in the panel; brand approval cannot be done from outside.

Can it be run at the same time as Trendyol?

It can, but the two markets do not run on the same rule. Hepsiburada writes the product to two systems and asks for approval to bind to an existing page. The price ceiling does not exist on the other market. When the same stock is opened to two stores, stock and price have to be set separately for each channel.

I sent the product and price and stock look like zero. What is the reason?

There are two common reasons. The first is the price not going in the format the channel expects: when the Shopify amount is transferred as-is, the record opens with zero price and zero stock. The second is the ceiling: if the allowed upper limit based on the same product's past average is crossed, the sale is not opened.

What does matching approval mean?

If the product you send already exists on Hepsiburada, the system does not open a new product page; it suggests binding to the existing page. That suggestion waits for approval. Until you approve it, the product is not opened for sale. When you approve it, you start competing in the same store as the other sellers on that page.

My product is visible in the catalog but not on sale. Why?

Sitting in the catalog is not the same as being open for sale. Catalog and sale list are separate. The record may be waiting on matching approval, stuck because of missing information, or taken off sale because the ceiling was crossed.

How is stock managed on HepsiLojistik products?

If the product is held in a Hepsiburada warehouse, Hepsiburada manages the number. Pushing a quantity onto these rows from Shopify breaks the warehouse figure. Setup has to separate these products and not send stock. There is no such split on the other marketplace, so the same logic causes trouble here.

Do return requests close automatically?

Hepsiburada has not published a rule that approves a return on its own after a set time. Requests are closed by hand from the panel or through the integration. A time rule from another marketplace is not carried here.

What happens if the shipping template is left empty?

The label does not come out of the panel and the package cannot be handed to shipping. Carrier selection and the template are filled on the seller side. If you use your own agreement, you also have to write the delivery status yourself.

Is brand approval required?

It is. The brand name has to be approved on the Hepsiburada side; a product sent with an unapproved brand is not opened. Brand creation runs as a panel process. If you will sell a new brand, this step has to be started before setup.