Shopify HepsiJET Integration
Almost everyone who writes about HepsiJET describes it as Hepsiburada's shipping, and leaves the most asked question unanswered: if you do not sell on Hepsiburada, can you work with HepsiJET? The answer sits on the firm's own application form. The form does not ask for a Hepsiburada store identity or a seller number; it offers website and social media as sales-channel options. So an independent Shopify store can apply directly. The application is made from a form, integration credentials come by email instead of from a panel, you produce the barcode at this firm, and the neighborhood field is solved separately on the Shopify side.
growing on Shopify with Nodus Works
Shopify HepsiJET integration what is it?
The Shopify HepsiJET integration is the connection that declares store orders as shipments to the carrier, prints the label, writes the tracking number on the order and reads delivery status back. HepsiJET does not publish its own Shopify app; an integration tool builds the bridge using your corporate account credentials.
Setup starts with an application, not with writing code. The become-a-customer form on the firm's site is a single page and does not require a branch visit; company title, tax or identity number, sales channel and monthly package count are requested. After approval the integration credentials are sent by the integration team by email. To speed up this manual process and build the connection correctly, you can take support from Nodus Works' Shopify integration and custom app development service.
Once the connection is live, daily work runs from one screen: the order is declared, the barcode is produced, the label is taken as a document in a separate step and printed, the customer notification goes out when the tracking number is written on the order, and the order closes on its own when delivery status is read back.
What a HepsiJET integration actually does
Once the connection is live, shipment declaration, barcode, label, tracking, delivery status and collection become parts of the same flow. The six headings below cover the questions asked most often about the Shopify HepsiJET integration.
Creating and declaring a shipment
The order address is declared with the data on the order instead of being typed into the carrier by hand. Because the address is three-level on the HepsiJET side, this step is also a test of your address data; district and neighborhood are expected as separate fields.
Producing the barcode number
At this firm the sender produces the barcode, not the carrier: it is formed by joining the short code the firm gave you with your order reference, and this number is expected on the physical label. The reverse of the layout at other shipping firms.
Taking the label in a separate step
The label does not come back during shipment creation; after creation is complete it is pulled as a document in a separate step. That is why bulk printing is the job of the tool you use, and one of the questions to ask when choosing a tool.
Writing the tracking number on the order
When the tracking number is written on the order, the customer notification goes out from Shopify's own email and the order closes on its own when delivery status is read back. If the number is not written, the customer sees nothing.
Cash-on-delivery flow
On a cash-on-delivery order the amount to collect is read from the order total and written on the shipment. At this firm cash on delivery needs to be assumed as cash; collection by card is not a confirmed fact.
Return shipments
On the return side the flow looks less like giving the customer a code and sending them to a branch, and more like you opening the return shipment: the shipment type is chosen as return and it is created like a normal shipment. Return scope is incomplete in app listings.
I do not sell on Hepsiburada, can I work with HepsiJET?
This is the question asked most often. The answer sits on the firm's own application form: marketplace selling is not asked.
The application form does not ask about marketplace selling
The firm's become-a-customer form asks for name, city, district, phone, email, company title, sales channel, tax or identity number and monthly package count. A Hepsiburada store identity or seller number does not appear at all.
Website can be chosen as the sales channel
The form offers website and social media as sales-channel options. So a seller who only has a Shopify store can also apply directly as an independent sender; this is a result that comes from an official source.
The carrier application is a completely different thing
There is also a carrier application on the site, but that is for vehicle owners who want to do distribution in the firm's name. It has nothing to do with becoming a sender. The mistake made most often is thinking these two are the same.
A sole proprietorship can also apply
The number field on the form accepts an identity number next to a tax number, so the application is not closed to legal entities only. Because an acceptance criterion and document list are not published, we do not count conditions here.
A marketplace shipment and your own shipment are two separate jobs
Using HepsiJET as the marketplace's carrier when you sell on Hepsiburada and opening a shipment on your own agreement are not the same thing: in the first the label comes from the marketplace and the fee is cut from your payout, in the second you produce the label and the invoice comes to you.
The split also appears in the shipment type
On the integration side the shipment type is chosen: retail, marketplace, express and return. So your Shopify order and your marketplace order leave from the same connection as different types; the split is not conceptual, it is inside the flow.
If you also sell on Hepsiburada the two flows run in the same warehouse but do not mix: marketplace packages leave with their own label, store orders go on your agreement. You can find the rules on the channel side on the Shopify Hepsiburada integration page.
How do you set up Shopify HepsiJET integration?
The six steps below cover the whole setup, from the application to printing the first label. The second step is specific to HepsiJET: credentials come from the integration team by email, not from a panel.
Submit your become-a-customer application
The become-a-customer form on the firm's site is a single page and does not require a branch visit: company title, sales channel, tax or identity number and monthly package count are sent through hepsijet.com. Do not mix it with the carrier application on the site.
Request your integration credentials
This firm has no public developer portal; credentials come from the integration team by email and the process can take days. Sending your request together with the application is the most practical path; also saying the name of the tool you will use makes the other side's work easier.
Collect the whole identity set that arrives
At this firm a username and password are not enough. Company title, short code, sender-address identity and transfer-hub code are also given; the four are required fields of the integration. When email correspondence starts again for a missing piece of data, setup loses days.
Build the connection and define your barcode layout
The credentials go into the tool you use and the barcode layout is defined: it is produced by joining your short code with your order reference. Also confirm in this step that the label does not come back in the shipment-creation response, it is taken as a document in a separate step.
Define the address, desi and payment setup
Make address line 2 required at checkout and rename it to district. Because Shopify has no neighborhood field, decide whether this field will go empty or be derived from the open address. If you will use cash on delivery, also set the manual payment method on the Shopify side.
Confirm the flow with a test shipment
Create a shipment from a single order and check that the barcode is produced, the label arrives in a separate step and is printed. Then confirm that the tracking number is written on the order, the customer notification goes out and delivery status is read back.
The table below shows which Shopify data maps to which counterpart on the carrier side.
| What Shopify has | What the carrier uses |
|---|---|
| Order | Shipment declaration |
| Order number | The second piece of the barcode |
| Shipping address | Open address |
| City | A separate field |
| Address line 2 | District, a separate field |
| Phone | The number the notification message goes to |
| Weight | One side of the chargeable weight |
| Package definition | Source of the desi calculation, on single-line orders |
| Payment status | Amount to collect on cash on delivery |
| No Shopify field | Neighborhood; short code; sender-address identity; transfer-hub code; shipment type; delivery window |
The last row of the table is longer at this firm than at others, and the reason is that the identity set is crowded. Neighborhood does not exist in Shopify at all; short code, sender-address identity and transfer-hub code live only on the carrier side and are defined as fixed values in the integration.
Tell us about your catalog and current setup, and we will work out how the Shopify HepsiJET 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.
Where do you get HepsiJET integration credentials?
The answer to this question is different from other shipping firms and directly affects your setup calendar: there is neither a self-service panel nor a public developer portal. Credentials come from the firm's integration team by email. Two independent sources say the same thing: the request is sent and a few days are waited, and in some cases the time can stretch to weeks. So the most uncertain line in your setup plan is this wait; sending the request at the same time as the application is the most practical path.
The second detail is that the incoming data set is more crowded than at other firms. Next to username and password your company title, a short code, your sender-address identity and your transfer-hub code are given. Because the short code is the first piece of the barcode it cannot be changed later; sender-address identity and transfer-hub code define your origin. Stores that start setup expecting a username and password to be enough get stuck exactly here, and when email correspondence starts again for missing data, days are lost.
The third is that this firm has no option to open a shipment by hand from your own panel. At the other three large shipping firms a panel is given to the corporate customer and the integration automates that panel's work; here the path for creating a shipment appears to be the integration directly. The site has only shipment tracking and the application form. The practical result is this: when the integration does not work you have no backup plan of opening a shipment by hand for a while, so doing the test shipment before going live is more important here.
There is also the question of who the agreement belongs to. Apps do not provide a shipping agreement; you sign it in your own company's name and the invoice comes from the carrier. The alternative is stores without their own agreement shipping on an intermediary's bulk rate; in that case the fee is paid to the intermediary. The two models must not be mixed, because who the invoice comes from and who sets the rate both change.
Why do you produce the barcode number?
The general rule of shipping integrations is that the carrier defines the barcode. HepsiJET is the exception to this rule, and setups that do not know this produce a label that will not scan.
The sender produces the barcode
The barcode is formed by joining the short code the firm gave you with your order reference, and this number is expected on the physical label. At other firms the carrier gives the number; here the layout runs in reverse.
The short code does not change later
Because the short code is the first piece of the barcode, changing it after setup produces a mismatch with past shipments. Recording this code together with your identity set makes your work easier when you change the tool or the vendor.
The label does not come back in the shipment response
When the shipment is created the label does not arrive; after creation is complete it is pulled as a document in a separate step. One app listing calls this the firm's official document label. That is why bulk printing is the tool's job.
A barcode and a tracking number are not the same thing
The barcode you produced is the reference the firm uses to recognize the package. The tracking number is assigned after the package enters the flow. That is why the tracking number is written on the order after the package enters the system, not at once.
If the tracking number is not written, the customer sees nothing
Shopify's notification chain starts when the tracking number is written on the order. When the number is not written, the customer cannot learn that the package has left, and the support load comes back to you.
Label size decides whether the barcode will scan
The common size in ecommerce is a fifteen-by-ten-centimeter thermal label. Printing a label that arrives as a document on large paper shrinks the barcode until it will not scan; at this firm the label size and print format need to be confirmed in setup.
If the order is cancelled, the declaration must be cancelled as well; if the address changes, the declaration is cancelled and created again. Because you produce the barcode, opening a second shipment with the same reference can produce a clash, so the recreate-after-cancel layout needs to be defined from the start.
What are HepsiJET's own service headings for?
The service headings the firm lists on its own application page are not a delivery-time promise, they are service names that can be chosen; they directly affect your campaign-period plan.
Scheduled delivery
A delivery where the customer chooses an hour window. On the integration side this sits as a window chosen at shipment level. Offering this choice to the customer in Shopify is not built in; checkout setup or an extra app is needed.
Same-day and next-day delivery
Same-day and next-day delivery are listed as separate service names and correspond to separate product codes in the integration. We do not give a time promise here: these are service names, and which city and district they are valid in depends on your agreement.
After-hours delivery
A delivery that falls in evening hours sits as a separate heading. For stores whose customer base is not at home during the day this is a concrete option that lowers the rate of packages that are not accepted.
Unlimited quota in a campaign period
One of the headings the firm lists is that no quota is applied in campaign periods. For stores that hit a shipment-count limit in discount periods this is the clearest point of difference against other firms; you need to confirm the conditions in your contract.
Live tracking
Live tracking of the shipment is listed as a separate heading. The store-side counterpart is delivery status being read back by the integration and written on the order; the information shown to the customer comes from this data.
Air cargo
It sits as a separate service heading for long-distance shipments. Whether you can use it depends on your product type and your agreement; you need to ask size and content limits in the meeting.
All of these headings open depending on the agreement. Saying which ones you will use in the application stops you from going back to another meeting after setup. A delivery-time promise is not given for any of these services; times and scope are the information written in your agreement.
What you need to confirm before setup
Because this firm has no public seller document, many topics are only clear in your contract and in the information the integration team gives. The nine headings below are what you should ask before setup.
Is there collection by card on cash on delivery
News based on the firm's own explanation gives the service name as cash-on-delivery cash payment; collection by card could not be confirmed. Promising the customer payment by card produces a package that cannot be delivered, so you need to assume cash and confirm the condition in your contract.
How many days the collected money takes to arrive
No official statement was found for the transfer time. Some shipping firms write this time on their own page; here it is not written. If you will tie your cash flow to cash on delivery you should learn the time from the start.
How the return flow will be set up
There is no source on whether the return code is fixed or one-time. On the technical side a return is opened like a normal shipment by choosing shipment type return; so the flow looks less like giving the customer a code and more like you opening the return shipment. Settle this before setup.
Can the customer leave a return at a point
Some shipping firms publish a consumer-facing point network. No branch-search tool or point list was found on this firm's site; a return at marketplace points runs with the marketplace's own return flow. Access for an independent-store customer could not be confirmed.
Is a corporate panel given
No self-service panel for the sender was found, so when the integration does not work there may be no backup of opening a shipment by hand. If such a panel is given, learning its name and access eases your hand during setup.
How you will call the courier
No courier-call form for the sender was found on the site. You need to ask in the meeting how a pickup plan is set for a regular outbound, what the daily last hour is and whether there is a weekend outbound.
How many sender addresses can be defined
In the identity set, sender-address identity and transfer-hub code are given as separate fields, so more than one origin is split at the identity level. How many addresses can be defined could not be confirmed; if you will ship from two warehouses, ask from the start.
At which size the label will be printed
That the label arrives as a document was confirmed, but its size and printer-language support could not be confirmed. If you will buy a thermal printer you need to ask this question to the provider of the tool you will use.
Is HepsiJET an extra-fee module in the tool you chose
Some panels offer this firm as an optional and paid extra module; other carriers on the same panel can be in the standard scope. When choosing a tool you need to ask both the scope and the extra cost.
How is cash on delivery set up in Shopify?
Cash on delivery is set up separately on both sides: as a payment method on the Shopify side, and as a shipment layout on the carrier side. At this firm you need to be careful about the payment type.
The Shopify counterpart is a manual payment method
In Settings, under payments, cash on delivery sits as a ready manual payment method. On such an order, payment opens as pending and is marked paid after collection happens.
Assume cash, do not promise payment by card
News based on the firm's own explanation gives the service name as cash-on-delivery cash payment, and collection by card could not be confirmed. Promising payment by card on your checkout creates an expectation the courier cannot meet and leads to the package not being delivered.
Reconciliation is the integration's job
The amount to collect is read from the order total and written on the shipment, and the order is marked paid when the money reaches the account. If this match is not set up, every order is marked by hand and at month end which collection belongs to which order is lost.
Cash on delivery is not in every tool
This firm's app listings offer different scopes: cash on delivery is in one, it does not appear in the other. If cash on delivery is part of your business model, tool choice starts from this question.
Region and amount limits are not built in
Restricting cash on delivery by region, setting an amount limit or adding a cash-on-delivery fee do not come as ready settings in Shopify. Those are solved with rate setup or an extra app.
Cash on delivery changes the return rate
Collecting payment at delivery raises the rate of packages that are not accepted, and every package that comes back means a two-way carriage fee. The cash constraint raises this rate further, so unaccepted shipments need to be watched separately.
There is no neighborhood field, how is address data solved?
At this firm the address is three-level: city, district and neighborhood. Because Shopify has no neighborhood field at all, the shared district problem is one level deeper here.
The address is expected as three levels
City, district and neighborhood are requested as separate fields; the open address sits outside these. Because Shopify has no neighborhood counterpart, what this field will be must be decided in setup.
Neighborhood can be left empty
One of this firm's app listings writes clearly that neighborhood can be left empty. So it is not required; having neighborhood information inside the open address still makes the work easier on the distribution side.
District must be a separate, recognizable value
On plans other than Plus you cannot add city and district pickers at checkout. The path used in the field is one: address line 2 is made required and renamed to district by editing the checkout language. The second path is taking an address confirmation after the order.
Desi is volume turned into a charge
The invoice is issued on whichever is larger, weight or desi. Package volume is found in cubic decimeters, divided by three on a domestic shipment and the result is compared with kilograms.
The data to calculate desi is not on the order
The Shopify product card has no length, width or height field; dimensions live only on the package definition, and a multi-line order uses the store default package. That is why some integrations declare the shipment with a fixed desi.
The firm measures the real desi, the difference hits the invoice
If the declared value and the measured value differ, the invoice is issued on the measured value. The shipping charge you took from the customer stays fixed while your invoice changes, so the difference comes straight out of margin.
Defining your package standards and declaring shipments on their real dimensions also lets you set the shipping rate at checkout to that real cost. If you have marketplace channels your shipping cost also splits: marketplace shipping sits on the payout report, your own agreement sits on the monthly invoice. To run the two flows in the same warehouse without mixing them, look at Station.
The most common mistakes in a Shopify HepsiJET integration
The nine headings below are the mistakes met most often in setup. At this firm half of them come from thinking other shipping firms' rules are also valid here.
Mixing the carrier application with the customer application
The carrier application on the site is for vehicle owners who want to do distribution in the firm's name. The form a store that wants to become a sender should fill is the become-a-customer form; sending the wrong form loses weeks.
Assuming a username and password will be enough
At this firm the identity set is crowded: company title, short code, sender-address identity and transfer-hub code are also given. A setup that starts with missing data restarts the email correspondence.
Waiting for the carrier to produce the barcode
Here the sender produces the barcode: the short code and your order reference join. A setup that applies other firms' rule tries to create a shipment without a barcode and the label cannot be printed.
Looking for the label in the shipment response
The label does not come back in the creation response, it is pulled as a document in a separate step. Setups that do not know this cannot take a label even though the shipment was created, and look for the error in the wrong place.
Thinking the neighborhood field is required
The address is requested as three levels but neighborhood can be left empty. Thinking this field is required and adding an extra field at checkout slows the customer for no reason.
Going live without fixing the district field
Orders with an empty district or a district buried in free text fail at the declaration step. Turning address line 2 into district should be part of setup.
Promising the customer payment by card at the door
The service is defined as cash-on-delivery cash payment and collection by card could not be confirmed. Writing payment by card at checkout creates an expectation the courier cannot meet and leads to the package coming back.
Choosing the tool without asking about returns and cash on delivery
This firm's app listings offer different scopes: cash on delivery is in one and not in the other, return scope is not complete in any of them. Choosing the tool without asking the scope means running the return process by hand.
Skipping the test shipment
No panel where you would open a shipment by hand was found at this firm, so when the integration does not work you may have no backup plan. Doing a test shipment before going live is more critical here than at other firms.
Three common problems and how we solve them
The three setup scenarios below show how we handle Shopify HepsiJET integration problems we have solved in stores we connected.
The application stayed unanswered for weeks
ProblemA seller who only had a Shopify store wanted to work with HepsiJET. They filled the form on the site and waited weeks for an answer; in the meantime, because of content they read on the internet, they started thinking they were not accepted because they were not a Hepsiburada seller.
CauseThere were two separate things. The form they filled was the carrier application, the form for vehicle owners; the form a store that wants to become a sender should fill is different. Also there was no condition of being a marketplace seller: the become-a-customer form accepts website as the sales channel.
SolutionThe correct form was filled and the integration-credential request was also sent in the same email. After approval the credentials came from the integration team; sending the request together with the application closed the wait in one pass and setup was completed the same week.
The shipment is created but the label cannot be printed
ProblemSetup looked complete: shipments were being created, no error was coming back. The warehouse team could not take a label on any order, though, and packages were waiting. The team spent half the day looking for where the error was.
CauseTwo rules specific to this firm had been skipped. The sender produces the barcode, not the carrier, and the barcode is formed by joining the short code the firm gave with the order reference. Second, the label does not come back in the shipment-creation response; it is pulled as a document in a separate step.
SolutionThe barcode layout was turned to the correct form built with the short code, and the label was defined to be taken in a separate step. Bulk printing was also tied to the same step, so the warehouse team started printing the whole day's labels from one screen.
Cash-on-delivery packages coming back
ProblemAfter the store turned cash on delivery on it saw a clear rise in the rate of packages that were not accepted. Because every package that came back brought a two-way carriage fee, the extra sales cash on delivery brought were not covering the cost that formed.
CauseThe cash-on-delivery option at checkout had been described as if payment by card could also be done. At this firm the service is defined as cash-on-delivery cash payment and collection by card is not a confirmed fact; a customer waiting for a card at the door was not accepting the package.
SolutionThe checkout text was corrected so it clearly says cash collection, and the same information was added to the order-confirmation email. Writing the amount to collect on the shipment was also ensured, so reconciliation stopped being a job done by hand; the unaccepted-shipment rate was put on a separate watch.
Station is the tool we built to run order, label, tracking and collection flow from one panel. If you also sell on marketplaces, their shipping flow stays separate, so seeing the two side by side makes the work easier.
Frequently Asked Questions
How do you set up Shopify HepsiJET integration?
I do not sell on Hepsiburada, I only have a Shopify store. Can I work with HepsiJET?
How do I apply to HepsiJET, do I have to go to a branch?
Is the carrier application on the site this one?
I am a sole proprietorship, can I apply?
HepsiJET is already used on my Hepsiburada orders, do I need a separate agreement for Shopify?
Where do I get my HepsiJET integration credentials?
What are short code, sender-address identity and transfer-hub code?
Do I produce the barcode number?
Why does the label not arrive when I create the shipment?
Can I change my short code later?
The address field asks for neighborhood, Shopify has no neighborhood field. What should I do?
How is a district field added at checkout?
Does HepsiJET have its own Shopify app?
Which integration tool should I choose?
Can I open a shipment by hand from a corporate panel?
Can I set up the integration without an agreement?
Does Shopify's own shipping label work in Turkey?
Can checkout show a live shipping rate?
When is the tracking number added to the order?
If the tracking number never arrives, what should I check?
If I cancel the order, is the shipment cancelled too?
Is there cash on delivery at HepsiJET?
When does the money reach my account on cash on delivery?
How is cash on delivery set up on the Shopify side?
How do I manage return processes?
Can my customer leave a return at a pickup point?
Can I let the customer choose scheduled delivery at checkout?
Is a shipment quota applied in a campaign period?
Can I use same-day or after-hours delivery?
Can I ship from two warehouses?
Why did my invoice come in higher than I expected?
Does the app set the shipping price?
BİZİ TERCİH
EDENLERİN ARASINDA
YER ALIN...
Herkes için Shopify çözümleri üretiyoruz.
Yeni bir Shopify mağazası kurmak, mevcut mağazanızı geliştirmek, özel entegrasyonlar yapmak veya hız problemlerini çözmek mi istiyorsunuz? Biz, teknik işleri sizin yerinize çözen uzman bir Shopify partneriyiz.

Dossha
#shopify

Les Benjamins
#shopify

Nocturne
#shopify

Fellas
#shopify

Mai
#shopify

Karaca
#shopify

Milagron
#shopify

Kiğılı
#shopifySeo

Şölen
#shopify

Adell
#shopifyB2B

Ohora
#shopify

Rendrea
#shopifyBooking

Babeskin
#shopify

The New Lab
#shopify

DTF Town
#shopify

Eczaclick
#shopifySeo

Termos Dünyası
#shopify

Halı.net
#shopify

Blend-r
#shopify

Oioi
#shopifySeo

Nowshopfun
#shopify

Marie Claire
#shopify

Gaziburma
#shopify

Dünyada Kitap
#shopify
NEDEN BİZİMLE
ÇALIŞMANIZ GEREKTİĞİNİ
SİZE ANLATMAK İSTERİZ
Shopify'ı çok iyi anlıyoruz; Türkiye'de her segmentin karşısına biz olarak çıkıyoruz :)







Sadece Shopify konuşanlardan oluşan bir takım

Hey!
Bannerlarım kesik gözüküyor :(
Yardım eder misiniz, kampanya dönemindeyim.
Selam Elif!
2 dakikaya çözüyoruz.





.webp)
.webp)


