Marketplaces integration
Hepsiburada
What it does
- Creates products and listings on Hepsiburada through the MPOP API, treating the two as separate objects the way Hepsiburada does.
- Syncs stock and price both ways from Kambloo's single stock pool.
- Pulls orders into your standard order flow and handles the shipping steps Hepsiburada expects.
Provider based in Turkey
Hepsiburada is in Kambloo's launch catalog together with Trendyol. It connects through the MPOP API with a token-based authorisation. The connector implements the MarketplaceConnector contract and is an Internal Module. Kambloo charges nothing for it; Hepsiburada's merchant commission applies to your sales there.
How it works with Kambloo
Hepsiburada separates the catalog product from the merchant listing, and the connector is built around that distinction. A push first creates or matches the product in Hepsiburada's catalog, then creates your listing with price and stock. Mapping covers both layers: categories map to Hepsiburada's tree, and the required attributes for each category map to your product fields. The push is blocked until mapping is complete, and each listing records its approval status and any rejection reason.
Stock and price sync is two-way with Kambloo as the default source. Delta jobs send only changed rows, use an idempotency key per request, and respect the marketplace rate limit. A price that originates on Hepsiburada is stored on the listing as the marketplace price and does not touch your base product. A price rule per listing or category adds a percentage and a fixed amount to cover commission, with your chosen rounding strategy.
Oversell is prevented by the single stock pool. Every channel reserves from the same physical stock, sellable quantity is recalculated at once, and the new figure is pushed to Hepsiburada on a high-priority queue. A per-channel buffer lets you report a lower number than you hold.
Orders are pulled into Kambloo and tagged with the Hepsiburada channel. From there they follow your normal process: stock reservation, carrier label, invoice, and notification. Because Hepsiburada links order handling and shipping in one process, the connector carries out those steps and writes the tracking number back to the marketplace.
Integration health, failed jobs, and rate-limit delays are visible on the health screen.
Requirements
- A Hepsiburada merchant account with MPOP API access.
- Category and attribute mapping for the products you list.
- A price rule that reflects your Hepsiburada commission.
Setup steps
The short version. The screens in your store admin follow the same order.
- Install the Hepsiburada module from the Market. It is free.
- Enter your Hepsiburada merchant credentials under Settings > Marketplaces > Hepsiburada.
- Map categories and required attributes to Hepsiburada's catalog.
- Set a price rule and optional buffer stock.
- List products, verify approval, and enable order pull.
Questions about Hepsiburada
What is the difference between a product and a listing on Hepsiburada?
Hepsiburada keeps a shared product catalog and a per-merchant listing with your price and stock. Kambloo mirrors that: the product push creates or matches the catalog entry, and the listing carries your offer. The mapping screen handles both.
Does my Hepsiburada price change when I run a store campaign?
Only if you want it to. Kambloo pushes your base price through the price rule. A price set on the Hepsiburada side is stored separately on the listing and never overwrites your product.
Do Hepsiburada orders ship differently?
Hepsiburada ties order and shipping into one process. The connector follows those steps, and the order otherwise runs through the same pipeline as a storefront order.