If you sell on Trendyol and run ERPNext, the daily reality is a browser tab and a spreadsheet stitched between them. Someone re-keys marketplace orders into Sales Orders, watches for oversells across your Trendyol stock and your ERPNext Bin quantities, manually pushes price changes, downloads shipping labels from the Trendyol seller panel, and at month-end tries to reconcile Trendyol's commission and settlement statements against what ERPNext thinks you earned. ERPNext core has no concept of Trendyol — no marketplace connector, no barcode-to-stockCode mapping, nowhere to store a Trendyol order number against a Sales Order — so every one of these steps is human glue. That glue is where oversells, late shipments, and reconciliation gaps come from.

We build a proper Frappe app (trendyol_connector) installed onto your bench alongside ERPNext, not a fragile external script. It ships new DocTypes — Trendyol Settings (supplier ID, API key/secret, seller ID, environment), Trendyol Product Map (linking each ERPNext Item and its variants to a Trendyol barcode/stockCode/productContentId), Trendyol Order, and Trendyol Settlement Line — so every marketplace object has a real home you can report on. Inbound Trendyol orders are pulled on a scheduler_events background job through the Trendyol Integration REST API, deduplicated by shipment package ID, and mapped into standard ERPNext Sales Order / Sales Invoice documents with the correct customer, taxes, and item lines. Because they are native documents, your existing accounting, delivery, and reporting flows just work.

Two-way inventory and pricing keep the marketplace and ERPNext honest with each other. A hooks.py doc_events handler on Stock Ledger Entry (and on Item Price for price changes) enqueues a background push so that when stock moves in any ERPNext warehouse, the corresponding Trendyol quantity and price are updated within your configured window — no cron-scraping, no double-selling. Whitelisted methods (@frappe.whitelist()) expose actions like "publish listing", "resync order", and "fetch settlements" to authorized users, and a bundled Client Script adds those buttons straight onto the ERPNext form. Shipping is wired end-to-end: we generate the Trendyol shipment package, retrieve the cargo label, and attach it to the ERPNext Delivery Note so packers work from one screen. Commission and settlement lines are imported and matched against invoices so your finance team reconciles in ERPNext instead of a spreadsheet. Access is gated by a dedicated Role and Role Profile, and errors land in the Frappe Error Log with retry, so failures are visible, not silent.

This is build-to-order, and we are direct about that: this is not an existing Frappe Cloud Marketplace app you download today. After a short scoping call we confirm your catalog structure, variant model, warehouse mapping, tax setup, and Trendyol account details, then build and configure the connector for your exact environment. Typical delivery is one working week from confirmed scope. We install on a staging bench first, run UAT against your real Trendyol account with a rollback plan, then go live and hand over the git repository. It is built for Frappe/ERPNext v15 and v16, with a documented upgrade path.