SAP Hepsiburada Integration
For businesses running SAP and selling on Hepsiburada: packed orders are written into SAP, and stock and prices flow from SAP out to Hepsiburada. Onboarding reads only at first.
What is the SAP Hepsiburada integration?
The SAP Hepsiburada integration carries stock and prices from SAP out to Hepsiburada, and Hepsiburada orders back into SAP.
What sets this pair apart is the package. On Hepsiburada an order moves forward at package level: one order can be split into several packages, and its line items can ship separately. The packing step is completed in the panel, and the record written into SAP carries which item went in which package. Because partial packing and split items are tracked separately, the shipping record in SAP lines up with the package on the channel.
Onboarding begins in shadow mode. The system reads only for a while and shows stock and order counts in SAP next to listing statuses on Hepsiburada. Write access opens as you approve it: orders first, then stock, then prices.
What flows in which direction
Orders and packages from Hepsiburada into SAP
A Hepsiburada order is taken with its customer, line items and delivery address, and written into SAP once the packing step is completed in the panel. Split items are tracked as separate packages.
Shipping details from SAP out to Hepsiburada
In the Hepsiburada shipping model a package travels with HepsiJet or a contracted carrier. The carrier and tracking number arrive with the order; when the warehouse despatch is marked in SAP, the channel is updated.
Stock and prices from SAP out to Hepsiburada
Stock in SAP is the source of a single pool, and listings are updated through the seller SKU. The list price in SAP is the base, with a separate selling and floor price defined for Hepsiburada.
Returns and settlements from Hepsiburada into SAP
Return requests appear against the order record; goods arriving at the warehouse are accepted by barcode and reflected into SAP. Settlement records are matched at order level.
How the SAP Hepsiburada integration is set up
Connect
You prepare the access details needed on the SAP side with your partner, then enter your Hepsiburada merchant number and the API user credentials defined for the integration into the panel.
Match
Products and variants in SAP match Hepsiburada listings through seller SKU and barcode. Colour and size variants are linked in bulk in the matrix view, and anything unmatched is listed for you.
Watch
In shadow mode the system reads both sides and writes nothing at all. You compare orders, package splits and listing statuses against the records in SAP.
Hand over
You open write access first for orders and packing, then stock, then prices. An ownership flag decides which products on Hepsiburada are managed by Bulutegra.
Technical summary
| Systems connected | SAP and Hepsiburada |
|---|---|
| Order direction | From Hepsiburada into SAP, once the packing step is complete |
| Stock and price direction | From SAP out to Hepsiburada |
| Matching key | Seller SKU and barcode, at colour and size variant level |
| Shipping | HepsiJet or a contracted carrier; the tracking number arrives with the order and despatch is marked in SAP |
| Needed on the SAP side | Access details prepared with your SAP partner; no custom development expected |
| Invoicing and shipping | Continue unchanged in your own routine inside SAP |
| Onboarding | Begins in shadow mode; write access follows in the order of orders, stock and prices |
Frequently asked questions about the SAP Hepsiburada integration
How is a split Hepsiburada order written into SAP?
The order is tracked at package level. When an order is split into several packages, the record keeps which item went in which package, and it is written into SAP with that distinction.
Where does the packing step happen?
Packing is completed in the Bulutegra panel, and in partial packing the remaining items stay open. Your invoicing and shipping routine inside SAP does not change.
What is needed to connect Hepsiburada?
Your merchant number from the Hepsiburada seller panel and the API user credentials defined for the integration are enough. No extra module is needed on the Hepsiburada side, and the SAP access details are prepared with your partner.
Can I see listing status from the panel?
Yes. Which listing is live, which is awaiting approval and which is closed is visible in the panel. Missing attribute, image and category findings are listed separately in the quality tab.
How is stock split between Hepsiburada and the other channels?
All channels are fed from the single pool in SAP, so a quantity sold on one channel drops on the others without waiting. You can also open only a defined part of the stock to Hepsiburada rather than all of it.
How are settlement differences tracked?
Settlement records are matched at order level. Returns whose commission is not refunded and line items that do not agree are flagged separately in the reconciliation list, each with a status and a note.