HepsiJet

HepsiJet is part of Kambloo's launch catalog. It connects through a REST API and reports status changes by webhook, which puts it in the same technical group as MNG. The adapter is an Internal Module. You ship under your own HepsiJet agreement and Kambloo charges nothing for the connection.

How it works with Kambloo#

Shipment creation is a single call from the order. Kambloo sends the recipient and parcel details to HepsiJet and receives a label, barcode, and tracking number. The PDF is stored in your bucket for single or batch printing, and the tracking number is saved on the order and sent to the customer with a link through the notification channel you configured.

Status tracking is push-based. HepsiJet posts each event to the central webhook endpoint for your store. Kambloo resolves the store from the URL, verifies the signature, records the raw event under a unique ID, and returns 200 in under a second. Processing happens in a queue job that updates the shipment and the order timeline. A delivered event closes the order and starts the return window. The tracking job still runs as a backstop, so a lost webhook cannot leave a shipment without a status.

Every outbound request to HepsiJet carries an idempotency key. A retry after a timeout does not create a second shipment. Failed jobs retry with backoff and, after the final attempt, show up on the integration health screen with the last error so your team can act.

Cash on delivery follows the platform pattern: the amount is passed at creation, stock is deducted firmly at order time, and collection is confirmed against HepsiJet's report. Cart prices come from your uploaded HepsiJet rate table using desi or real weight and the origin and destination provinces.

Requirements#

• A HepsiJet customer agreement with REST API access.
• A live store domain reachable by HepsiJet webhooks.
• Your rate table as CSV and product dimensions for pricing.