Thursday afternoon, 3:40 pm. A seller is going back and forth between two screens. One is the Hepsiburada seller panel: 38 packages that have to go out today. The other is the panel of their own sales channel: 25 orders waiting since morning. The Hepsiburada packages' shipping and labels are handled in one place; the orders from their own site go through another tool and another flow.
Around 6 pm someone notices that two Hepsiburada labels were printed twice and one package was never handed to the carrier. They'll find out tomorrow morning, when that order is already a day late.
Many sellers on more than one channel know this day. The problem isn't one mistake. It's running a deadline-driven job by hand, in two panels, at two different rhythms.
This guide covers how Hepsiburada shipping really works, why running it from the seller panel gets harder as volume grows, and how to ship Hepsiburada orders in one queue with your own sales channels. We also write down plainly what we do and don't do.
We made the same argument for Trendyol in our Trendyol order and shipping management guide. If you sell on several channels, the multichannel order management guide draws the full picture.
Why Is Hepsiburada Shipping Different From Your Own Sales Channel?
When you ship from your own sales channel you choose the carrier, the service and the timing. On a Hepsiburada order some of those aren't in your hands:
- Hepsiburada assigns the carrier. Each package gets a carrier. You can switch to another one, but Hepsiburada decides which carriers you can switch to. You can't apply your own contract to a marketplace order.
- The time is written to you. Hepsiburada calculates the seller score from eight parameters; customer reviews, cancellation and return rates, response time to customer questions, complete delivery of invoices and not sending missing, wrong or damaged items are among them. One of them is on-time shipping. Hepsiburada doesn't disclose how much each parameter weighs.
- Lateness has a price. Orders not shipped on time can bring a score drop and a penalty calculated on the order value. Repeated delays can carry consequences for visibility and commission. Because deadlines and rates can change, confirm the current values in the rules in your seller panel.
So on Hepsiburada, shipping is less "which carrier is cheaper" and more "did this package leave in time". As volume grows, that turns the job into an organization problem.
Why Change the Way You Do It?
The seller panel is fine on days of 10-15 packages. As volume grows, three things break:
- There are more places to look. Hepsiburada, your own sales channel's panel, maybe another marketplace. Each has its own queue and its own label flow. "How many packages today?" has no single answer.
- Doing it one by one produces errors. Taking labels one by one and checking carriers one by one turns, on a fifty-package day, into a label printed twice or skipped. As we noted in our guide to scaling shipping operations, in manual processes this kind of mistake starts around 30 orders.
- The marketplace order jumps the queue. Hepsiburada packages with a deadline go out first and your own sales channel drops to second place. The channel where your margin is usually better ends up in the shadow of the noisy one.
Why Shipink?
When you connect your Hepsiburada sales channel in Shipink, your ready-to-ship packages land in the same queue as the orders from your own sales channels. The day goes like this:
1. Connect once. You connect the sales channel with your Hepsiburada seller details. A Hepsiburada carrier account is opened for you automatically when you do.
2. Packages land in the queue. Your Hepsiburada orders appear on the same screen next to your other channels. You look in one place for the order count.
3. Pick the carrier there. When you create the shipment you pick from the carriers Hepsiburada allows (HepsiJET, Aras, Yurtiçi, Sürat, MNG, PTT and others). You don't have to go back to the Hepsiburada panel. The tracking number becomes the number of the carrier you chose.
4. Take labels in bulk. When you select packages and print labels in bulk, a fifty-package afternoon comes down to minutes. If a label isn't ready right away, the system retries it automatically so you don't have to follow it.
5. Track from one place. Every shipped package, Hepsiburada or not, reports its status in the same view. You see a stuck package before it shows up in your score.
The test is simple: can you finish a whole shipping day without opening the Hepsiburada seller panel once, even for one package? If so, you're working above the panel.
You can look at the connection steps on the Hepsiburada sales channel page.
The Honest Limits
This flow doesn't take over everything. What you should know:
- Carrier choice is limited to Hepsiburada's list. You can't attach your own contract to a Hepsiburada order. Your own contracts are for orders from your own sales channel.
- Shipping cost follows the Hepsiburada agreement. You won't save by comparing prices between carriers on this channel; the gain comes from speed and order.
- Orders don't land instantly. On this channel Shipink pulls packages at regular intervals instead of receiving instant notifications; a new package enters the queue at the next pull.
- Invoice delivery isn't done from Shipink. Hepsiburada asks for the invoice as an e-archive invoice link and Shipink doesn't send it. Because complete invoice delivery is part of the score, keep this step in your existing flow.
- The return decision is in Hepsiburada. Approving or rejecting return requests stays on the Hepsiburada side; in Shipink the requests are read-only.
- Deleting a shipment in Shipink doesn't undo the package. The package lives on in Hepsiburada. If a cancellation is needed, it's done on the Hepsiburada side.
- Micro-export packages are out of scope. The flow for these packages runs on the Hepsiburada side.
These limits also show the point: not to change Hepsiburada's rules, but to run the work inside those rules in one queue, in bulk, without mistakes.
Four Things to Measure
Because Hepsiburada tracks your operation with a score, know your own numbers before the scorecard reaches you:
- Time to hand-off. The time from the order arriving to the package being handed to the carrier. It's one of the score's parameters.
- Delivery performance by carrier. Among the carriers Hepsiburada allows, which one really delivers on time on your routes? The carrier performance tracking guide shows how to follow this.
- First-attempt delivery and exceptions. Wrong addresses and failed attempts hurt on a marketplace too; the discipline in the failed delivery guide applies here as well.
- Return reasons. Separate returns caused by damage and wrong items from product-related ones. The returns management guide explains why.
It also matters to have a backup when a carrier struggles in a region; we covered that in the carrier outage backup plan guide.
Why Now?
The November campaigns are coming. Order volume goes up and packing often takes on temporary people. If you try to set the process up that week, learning and mistakes happen together. In the peak season preparation plan we described how exceptions grow with volume.
Time lost in the campaign is written to your score. Packages that leave late in the rush can bring a penalty and a score drop; the score stays with you after the campaign ends.
You have a few weeks before the campaign. That's enough to set up the connection, get used to the queue and try the bulk label flow. Doing the same in campaign week is expensive.
A Trial You Can Run This Week
- Look at last week's Hepsiburada packages. How many were handed to the carrier within the first day after the order arrived?
- Time one shipping day. How many minutes does going back and forth between the Hepsiburada panel and your own channel, and taking labels, cost you?
- Connect the Hepsiburada channel and try a 20-package day: select from the queue, set the carrier, take the labels in bulk.
- Settle who owns invoice delivery. Hepsiburada expects the invoice from you; does that step still work in your existing flow?
- Write down the current deadline and penalty rules in your panel. Set your target time by that rule.
Work Above the Panel
The cost of shipping Hepsiburada badly is a small visible penalty plus a large invisible loss: as your score drops, fewer people see you. The reason so many sellers struggle isn't carelessness; the seller panel, built around one package one click, wasn't designed for a real shipping operation.
Taking Hepsiburada orders into the same queue as your own channels and shipping them with the same bulk flow is how you hit the deadline by default instead of by heroics. If you'd like to connect your Hepsiburada channel and try it with 20 packages, you can try Shipink for free, look at the operations tools, or write to us to talk through your setup.
