Hepsiburada in the Zervanor Engine: Orders, Claims and Stock

Hepsiburada sellers know where the hours go: copying every new order into the accounting app, cutting the e-Fatura by hand, entering cargo numbers one by one, and answering the same customer questions all day. None of it is selling — it’s the cost of selling.

Zervanor is the automation engine behind vertical SaaS products, and Hepsiburada is modelled in it as a versioned connector pack. That means the grind above is expressible as workflows a product can run on its customers’ behalf. Here is what the engine covers.

What the Hepsiburada connector does

The Hepsiburada connector covers the real seller surface — verified against the official Marketplace Integration API, 49 actions and 6 triggers:

• Orders & shipping: List Orders, Get Order Line Items, Create Packages, Update Cargo Number, Change Line Item Cargo Company, Send Invoice Link.
• Returns & claims: List Claims, Create Claim, Accept Claim, Reject Claim.
• Listings: Update Price, Update Stock, Update Listing Inventory, Create Product, Update Product.
• Customer Q&A & finance: List Questions, Answer Question, List Invoices, List Transactions.
• Triggers that start a flow: Order Created / Updated, Return Claim Created, and Customer Question Created.

Each of these is also callable by an AI agent as a tool — so an agent can read an order, decide what to do, and act; it doesn’t just move data.

4 automations worth building

1. New order → e-Fatura → customer SMS. When Order Created / Updated fires, normalize the order, cut the matching e-Fatura in your accounting app, and text the customer the invoice link — zero manual steps.

2. Return claim → return invoice + notify. When Return Claim Created fires, cut the matching return invoice and let the customer know — closing the loop accounting usually chases by hand.

3. Customer question → AI-drafted answer. When Customer Question Created fires, let an AI step draft an accurate answer from your product data and post it with Answer Question — the same reply quality, in seconds.

4. Cross-marketplace stock protection. When stock changes anywhere, keep Hepsiburada in sync with Update Stock / Update Price — never oversell a product that’s gone.

What the engine already runs

The full order chain is modelled and validated end to end:

• Hepsiburada Order → Paraşüt e-Fatura → Netgsm SMS — connect Hepsiburada, Paraşüt and Netgsm, and every new order becomes an invoice and a customer text automatically.

The return, Q&A and stock-sync flows above are not modelled as templates yet — and we won’t pretend they do. Instead, describe the exact flow in plain language (“when a Hepsiburada return claim is created, cut a return invoice in Paraşüt and text the customer”) and Zervanor assembles a real, validated workflow from your actual connectors — showing every step before it runs. If a piece isn’t available yet, it tells you honestly and routes it to the build queue rather than faking it.

Why sellers move automation to Zervanor

The whole chain runs as a single workflow execution, and the agents that handle the reading, judging and drafting run in the same runtime as the workflow itself.

See the full Hepsiburada connector reference for all 49 actions and 6 triggers, or start with the template above.

FAQ

Does it work with my accountant’s software? Yes — Paraşüt, Nilvera and more are live e-invoice connectors, and templates ship with ready alternatives. If yours isn’t listed, Chat-to-Build says so honestly and routes it to the build queue.

Do I need to write code? No. Deploy the template or describe the flow in chat. Any step is editable in the visual builder if you want to open it.

How does Zervanor connect to Hepsiburada? Through Hepsiburada’s official Seller / Marketplace Integration API with credentials you connect once — no scraping, no unofficial access.