Hepsiburada HepsiJet Shipping and Package Flow Guide

Shipping on Hepsiburada begins the moment an order lands and ends when the package is delivered and the return window closes. At the center of that process is HepsiJet, Hepsiburada's own delivery network. When an order arrives, Hepsiburada assigns the carrier, you create the package and print the label, you hand it to the courier or drop it at a hub, and from then on every status change flows to both the customer and you. This guide walks through each step of that flow and shows where an integration needs to step in. For the marketplace basics, see our Hepsiburada integration overview.

What makes HepsiJet different from a regular carrier

With a conventional carrier you choose the company, sign the contract and print labels from your own carrier account. With HepsiJet all three happen inside the marketplace. At order time Hepsiburada says "this package ships with HepsiJet", the tracking barcode and label arrive with the order record, and a courier collects from you or you drop the package at a hub.

For you this means three things:

• The choice is not yours. Hepsiburada decides which order goes with which carrier. Region, product size and your agreement influence the outcome.
• The label is part of the order record. The shipping label is generated together with the order, not in a separate system. Your integration must be able to print it directly.
• Status flows in both directions. You report that the package was handed to the courier; HepsiJet reports delivery, failed delivery and return. Both directions need monitoring.

These three differences set Hepsiburada operations apart from Trendyol or Amazon. If one warehouse ships to three marketplaces, each one's label and status logic has to be understood separately.

The package flow from order to delivery

The statuses a package passes through on Hepsiburada, in order:

1. Order created. The customer paid and the order appeared in the seller panel. The dispatch clock starts now.
2. Package being prepared. You or your integration marks the order as packed. If items from the same order are ready at different times, the package can be split, and each part gets its own label.
3. Label printed. The HepsiJet barcode is tied to the package. The label must carry the recipient, the order code and the barcode; a wrong label means a package going to the wrong address.
4. Handed to courier. The courier collected the package or you dropped it at a hub. Reporting this step to Hepsiburada is your job; if you do not, the package still shows as "being prepared" and may count as late.
5. In transit. The package moves through the sorting hub to the delivery region. HepsiJet updates these statuses.
6. Delivered. The customer received the package. The return window runs from this date, and settlement is timed from it too.
7. Exceptions. Undeliverable, refused by recipient, wrong address, damaged package. Each calls for a different action.

The most commonly skipped step is the fourth. If the warehouse worker who handed the package to the courier forgets to record it, you look late on Hepsiburada's side and your score drops. Having the integration send that notification automatically when the label is printed or the barcode is scanned removes the risk.

Dispatch deadlines and the operations score

Hepsiburada assigns a dispatch deadline to every order. It varies by product, category and your seller settings; the exact value is shown in your seller panel. A package not handed over within the deadline first gets a warning, then becomes a cancellation candidate and affects your operations score.

Managing the deadline requires three things:

• Seeing the remaining time. Without "hours left" in the package list you cannot prioritize.
• Bulk actions. Scanning barcodes and marking a hundred packages as "handed to courier" at once instead of one by one.
• Holiday and working-hour settings. If the warehouse is closed on weekends and public holidays, set the handling time accordingly; otherwise Monday morning greets you with expired packages.

The operations score covers more than dispatch time: cancellation rate, undeliverable rate and customer complaints also count. We discuss these metrics in marketplace performance reports and KPIs.

Undeliverable packages and returns

Not every package reaches the customer. The HepsiJet courier makes a few attempts and, failing that, brings the package back to the seller. Points to watch in that process:

• Timing of stock recovery. Until the package is back with you, the item is still "sold". The moment it enters the warehouse you should scan it and return it to stock; otherwise sellable goods sit on a shelf.
• Shipping charge. In some cases the shipping cost of an undeliverable package is still deducted from the seller. Track this line separately in the settlement report.
• Customer returns. If the customer opens a return after delivery, HepsiJet collects the package from them and brings it to you. Return acceptance, item inspection and approval happen on your side.

Accepting returns by barcode lets you catch a wrong item or missing part while it is still in the warehouse. The full flow is covered in marketplace return management and the return portal.

Good shipping performance on Hepsiburada depends less on printing labels than on reporting status on time. A package reported late is penalized the same as a package shipped late.

What the integration should take over

Managing all of this by hand is possible at low volume and impossible as you grow. A good integration takes over these jobs:

• Writing the order to the ERP the moment it lands, with carrier information included.
• Pulling the HepsiJet label with the order record and printing in bulk. Printing labels for several marketplaces from one screen is covered in shipping labels and bulk printing.
• Reporting "handed to courier" to Hepsiburada automatically when the barcode is scanned.
• Reading delivered and undeliverable statuses from HepsiJet and writing them to the order record.
• Moving packages near their deadline to the top of the list and raising an alert.
• Reopening stock when an undeliverable package enters the warehouse.

Every item on this list corresponds to a point where Hepsiburada either lowers your score or costs you money.

How it works with Bulutegra

Bulutegra pulls the order through the Hepsiburada API together with the carrier and the HepsiJet barcode, and writes it to your ERP with customer, line items and shipping details. In the Integration Panel, the Hepsiburada tab sorts packages by remaining dispatch time; labels print in bulk, and when the warehouse scans a barcode the "handed to courier" notification goes out automatically. Delivered and undeliverable statuses from HepsiJet land on the order record; a return request coming through the return portal is tied to barcode-based warehouse acceptance and the stock is reopened. Channel monitoring checks the Hepsiburada connection continuously; a channel that goes quiet raises an alert and sends a notification to your phone. A user with the Warehouse role sees only package and return screens.

To see how your Hepsiburada operation runs on Bulutegra, request a demo, or browse the full list of supported channels.