Build-to-order Odoo connector syncing Trendyol products, orders, stock, price, cargo labels & Turkish category taxonomy. Odoo 17/18/19. One-time license from $499.00 USD for Odoo 17, 18, 19 — includes 12 months of updates and support.

Build-to-order Odoo connector syncing Trendyol products, orders, stock, price, cargo labels & Turkish category taxonomy. Odoo 17/18/19.
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
Sell on Trendyol and run everything from Odoo. This is a build-to-order Trendyol Marketplace Connector that ECOSIRE designs, develops, installs and supports for your specific catalog, warehouses and cargo setup. It is not an off-the-shelf apps.odoo.com download — after purchase our engineers scope your Trendyol seller account, build the module against your Odoo instance, and deliver a tested, production-ready integration in roughly 2-4 weeks.
Publish products and variants to Trendyol from Odoo with structured listing payloads, then track approval/rejection status back on the product record
Import Trendyol orders into Odoo as sale orders with customer, line, tax and shipping data mapped automatically
Two-way order package/shipment status sync (Created, Picking, Invoiced, Shipped, Delivered, Cancelled) reflected on the Odoo order
Per-store stock synchronization pushing available quantities from chosen Odoo warehouses/locations to each Trendyol store
Per-store price and list-price updates, including sale/discount price fields, pushed on a schedule or on change
Trendyol cargo-provider integration: request shipment labels and store the tracking number and carrier on the delivery
Under the hood the connector is a proper Odoo add-on. A dedicated __manifest__.py declares dependencies on sale, stock and product; new models (models.Model) hold your Trendyol store credentials, listing state, order mappings and cargo tracking, with computed fields driven by @api.depends for margins and sync status. Every model is locked down with ir.model.access.csv access rules plus record rules so warehouse staff, listing managers and finance each see only what they should. Backend screens are standard Odoo views (XML/OWL) with a Trendyol dashboard, and QWeb reports produce packing and reconciliation documents. Scheduled ir.cron jobs and automated actions pull orders and push stock/price on the cadence you choose.
The integration talks to the Trendyol Marketplace API and exposes an Odoo XML-RPC/JSON-RPC surface so your other systems can read the same data. It maps Trendyol's Turkish category and attribute taxonomy to your Odoo product attributes, tracks listing approval status, imports orders with live package/shipment status, keeps stock and price aligned per store, and generates Trendyol cargo-provider labels with tracking numbers. Works on Odoo 17, 18 and 19, Community or Enterprise — we confirm edition-specific behavior during scoping so nothing depends on a module you don't have.
You get clean, documented, upgrade-safe code (no core overrides that break at the next Odoo upgrade), configuration tuned to your account, admin and end-user training, and a support window for the shakeout period after go-live. If Trendyol changes an API endpoint or you add a new store or warehouse, we handle it under the agreed support terms.
A Turkey-based merchant whose Trendyol order volume has outgrown the seller panel and spreadsheets. They need orders flowing straight into Odoo, stock and price kept in sync automatically, and cargo labels generated without re-keying — so the team stops firefighting overselling and mispricing.
A brand already selling in the region and now onboarding to Trendyol as it expands beyond Turkey. They want one Odoo source of truth across channels, correct Turkish category/attribute mapping so listings get approved, and a repeatable publish-and-sync process for a growing catalog.
The person accountable for accurate stock and on-time dispatch. They need per-warehouse stock pushed to the right store, shipment status mirrored between Trendyol and Odoo, and role-scoped access so warehouse staff see only fulfillment data — not pricing or finance.
The in-house admin or partner responsible for the Odoo instance. They want a clean, documented, non-hacky add-on that survives upgrades, respects ir.model.access.csv/record rules, exposes data over XML-RPC/JSON-RPC, and has a support path when Trendyol changes an endpoint.
Buy the license on ecosire.com and download the Trendyol Marketplace Connector (Turkey/MENA) module ZIP from your account dashboard.
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Activate Developer Mode, open Apps, click Update Apps List, search for Trendyol Marketplace Connector (Turkey/MENA), and press Install.
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Trendyol product, order, stock, price and cargo sync out of the box | Yes — built and tested end-to-end for your account | Only what you spec and can build in-house | Varies; often partial (e.g. orders only) or generic | |
| Turkish category/attribute taxonomy mapping to your catalog | Mapped to your live products during setup | You must research and implement the taxonomy yourself | Generic mapping; may need manual rework per product | |
| Fit to your warehouses, stores and cargo providers | Configured to your exact multi-store/warehouse setup | Fully custom but you own all the effort | Fixed assumptions; limited to what the vendor coded | |
| Odoo 17/18/19, Community & Enterprise, upgrade-safe | Supported and confirmed during scoping | Depends entirely on your team's discipline | Often lags new Odoo versions; upgrade risk | |
| Installation, training and go-live support included | Install + docs + training + post-go-live support window | You do it all yourself | Usually download-only; support is extra/limited | |
| API-change handling when Trendyol updates endpoints | Covered under agreed support terms | Your team must monitor and fix reactively | Depends on vendor's release cadence | |
| Time to production | ~2-4 weeks, delivered ready to sell | Weeks-to-months of internal build + testing | Fast to install, slow to make actually fit | |
| Code quality & security (ir.model.access.csv, record rules, no hacks) | Clean models, proper access rules, XML-RPC/JSON-RPC exposed | Only as good as your in-house standards | Unknown; some rely on core overrides that break upgrades |
No. This is a build-to-order engagement, not an instant apps.odoo.com download. After purchase, ECOSIRE scopes your Trendyol account and Odoo setup, then builds and installs a connector tailored to your catalog, warehouses and cargo configuration. You receive a tested, production-ready module — not a generic package you self-install blindly.
Typical delivery is 2-4 weeks depending on catalog size, number of stores/warehouses and any custom mapping needs. The flow is: kickoff and scoping call, we collect Trendyol API credentials and Odoo access, we build and test in a staging environment, then install to production and run go-live validation with your team. We confirm a firm timeline during scoping before development starts.
Every build includes a post-go-live support window for bug fixes and adjustments during the initial shakeout. If Trendyol changes an API endpoint, or you add a new store, warehouse or product type, we handle those changes under the agreed support terms. Because the code is clean and upgrade-safe (no destructive core overrides), moving between Odoo 17, 18 and 19 is straightforward. Ongoing maintenance and SLA options are available.
It supports Odoo 17, 18 and 19 on both Community and Enterprise. The connector depends only on standard modules like sale, stock and product. During scoping we confirm anything edition-specific to your instance so nothing silently relies on a module you don't have.
Scheduled ir.cron jobs and automated actions run at intervals you choose — separately for orders, stock and price. Stock is pushed per store from the Odoo warehouses/locations you select, prices (including sale prices) are pushed on change or on schedule, and orders are imported with live package/shipment status mirrored back. All runs are logged with retry handling for API rate limits, so you can audit exactly what synced and when.
Yes. The connector's models are exposed over Odoo's XML-RPC/JSON-RPC API, so BI tools or external systems can consume the same order, stock and listing data. Access inside Odoo is governed by ir.model.access.csv plus record rules, so listing managers, warehouse staff and finance each see only the data appropriate to their role.
Getting listings approved depends on correct category and attribute mapping against Trendyol's Turkish taxonomy. We map your Odoo product attributes and values to the required Trendyol categories and mandatory attributes during setup, and the module tracks each listing's approval or rejection status so you can fix and re-submit quickly.
Build-to-order Odoo connector syncing Trendyol products, orders, stock, price, cargo labels & Turkish category taxonomy. Odoo 17/18/19.