A build-to-order Frappe app that syncs Trendyol orders, listings, inventory, pricing, shipping, and settlements into ERPNext. ECOSIRE scopes, builds, installs, and supports it around your specific catalog and warehouse setup. Built to order by ECOSIRE for ERPNext v15, v16 — indicative price from $499.00 USD; request a quote for a scoped proposal.

A build-to-order Frappe app that syncs Trendyol orders, listings, inventory, pricing, shipping, and settlements into ERPNext. ECOSIRE scopes, builds, installs, and supports it around your specific catalog and warehouse setup.
现在无需付款。此操作会向我们的团队发送报价请求——我们会通过邮件跟进价格和后续步骤。
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.
New Frappe app `trendyol_connector` installed on your bench, with dedicated DocTypes: `Trendyol Settings`, `Trendyol Product Map`, `Trendyol Order`, and `Trendyol Settlement Line`
Inbound order sync via a `scheduler_events` background job hitting the Trendyol Integration REST API, deduplicated by shipment package ID
Automatic mapping of Trendyol orders to native ERPNext `Sales Order` / `Sales Invoice` with correct customer, item lines, and tax templates
Listing and variant publish: push ERPNext `Item` and `Item Variant` records to Trendyol as products with `barcode`/`stockCode`/`productContentId` mapping
Two-way inventory sync driven by a `hooks.py` `doc_events` handler on `Stock Ledger Entry`, so warehouse moves update Trendyol quantities within your configured window
Two-way price sync from `Item Price` changes to the Trendyol listing price, with configurable price lists per channel
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 2–4 weeks 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.
A Turkish or MENA retailer moving high SKU counts with many size/color variants. Needs ERPNext `Item Variant` records mapped cleanly to Trendyol barcodes and stock codes so listings publish and inventory stays accurate without manual re-keying.
Owns order-to-ship. Wants Trendyol orders landing as native ERPNext Sales Orders and cargo labels attached to Delivery Notes, so packers work from one screen and nothing ships late or twice.
Responsible for month-end close. Needs Trendyol commission and settlement lines imported and matched against Sales Invoices in ERPNext, replacing the reconciliation spreadsheet and its errors.
Runs the bench and cares about maintainability. Wants a proper Frappe app with clean DocTypes, permission roles, Error Log visibility, v15/v16 support, and a git repo they can maintain, not an opaque external script.
在 ecosire.com 上购买许可证并从您的帐户仪表板下载 ERPNext Trendyol Connector 应用程序 ZIP。
将 ZIP 解压到您的 bench 的 apps 文件夹中,或者使用解压缩的应用程序的路径运行“bench get-app”。
运行 `bench --site SITE_NAME install-app APP_NAME`,然后运行 `bench migrate` 以安装 ERPNext Trendyol Connector 并应用其架构。
打开您站点上的 ECOSIRE 许可证设置并激活您的许可证密钥。需要免费的 ecosire_connect 和 ecosire_license_client 应用程序。
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| Trendyol order sync | Native Sales Orders/Invoices, deduplicated, scheduled | Whatever you scope and build yourself | Generic sync, often not Trendyol-specific | |
| Variant & listing publish | Item Variants mapped to barcode/stockCode/productContentId | Possible but you design the mapping | Basic, variant handling often weak | |
| Two-way inventory & price | Stock Ledger Entry & Item Price doc events push to Trendyol | Build your own triggers and queue | One-way or polling, risks oversell | |
| Shipping & labels | Cargo label attached to Delivery Note | Extra integration work | Rarely included | |
| Settlement reconciliation | Settlement lines matched to Sales Invoices in ERPNext | Bespoke reporting to build | Usually out of scope | |
| Fit to your setup | Scoped to your catalog, warehouses, taxes | Fully bespoke by definition | One-size-fits-all config | |
| Maintainability | Proper Frappe app, git repo, roles, Error Log | Depends on your developer's discipline | Closed config, limited access | |
| Support & updates | Post-go-live window + v15/v16 upgrade path | You own all future maintenance | Vendor support tiers, variable |
No. This is build-to-order. It is not an existing Frappe Cloud Marketplace download. After a scoping call we confirm your catalog, variants, warehouse mapping, and Trendyol account, then build and configure the connector for your exact ERPNext environment and hand over the source.
Typical delivery is 2–4 weeks from confirmed scope. Simpler catalogs with a clean variant structure land toward the shorter end; complex multi-warehouse or heavy customization pushes it longer. We agree the timeline in writing before starting and install on staging before go-live.
Every build includes a post-go-live support window (scope agreed up front) for bug fixes and adjustments. Because you receive the full git repository, your team can maintain it, and we offer ongoing support or a Frappe/ERPNext version-upgrade engagement separately when you move between v15 and v16 or when Trendyol changes its API.
We build and test against Frappe/ERPNext v15 and v16. The app follows standard Frappe app conventions — DocTypes, `hooks.py` doc events, whitelisted methods, and scheduler events — so it installs on your bench cleanly and has a documented upgrade path.
No. Order pulls are deduplicated by Trendyol shipment package ID, and inventory pushes are triggered from `Stock Ledger Entry` doc events through queued, idempotent background jobs. Transient Trendyol API failures retry via the Frappe queue and surface in the Error Log rather than silently corrupting data.
We import Trendyol settlement lines into a dedicated `Trendyol Settlement Line` DocType and match them against your ERPNext `Sales Invoice` records, so finance reconciles commissions, payouts, and deductions inside ERPNext instead of exporting spreadsheets from the seller panel.
Yes — the connector authenticates with your Trendyol Integration API key, secret, and supplier/seller ID, stored in the `Trendyol Settings` DocType with access restricted by a dedicated role. During the build we use your staging or sandbox credentials where possible and only wire production keys at go-live.
A build-to-order Frappe app that syncs Trendyol orders, listings, inventory, pricing, shipping, and settlements into ERPNext. ECOSIRE scopes, builds, installs, and supports it around your specific catalog and warehouse setup.