End-to-end Delhivery integration for Odoo: shipment creation, AWB label print, live tracking, pincode check and COD reconciliation. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $249.00 USD; request a quote for a scoped proposal.
アプリマニフェスト
あなたのワークフローに合わせて構築
End-to-end Delhivery integration for Odoo: shipment creation, AWB label print, live tracking, pincode check and COD reconciliation.
自分での設定は不要 — ECOSIRE が構築・インストール・サポートする実働アプリです。
一回限りの構築料金から始めます。キックオフで一緒に範囲を決めます。
ECOSIRE がお客様の Odoo 上で構築・設定・インストールします。
約2〜4週間で稼働し、リリース後のサポート期間が付きます。
The Delhivery Shipping Connector is a build-to-order Odoo module that ECOSIRE designs, builds, installs and supports for your specific instance — it is not an instant apps.odoo.com download. We wire Delhivery's One API directly into your Odoo Inventory and Sales flow so your team stops copy-pasting AWBs into the Delhivery panel and starts pushing shipments straight from the delivery order.
Grounded in real Odoo engineering, the module ships as a proper addon with its own __manifest__.py declaring dependencies on stock, delivery and sale, a delivery.carrier extension that registers "Delhivery" as a native shipping method, and dedicated models (built on models.Model) that store the Delhivery waybill, package dimensions, client-warehouse mapping and COD amount against each stock.picking. Rate, serviceability and tracking calls run through a thin, retry-aware Python service layer talking to Delhivery One over JSON, with credentials stored securely in res.config.settings (staging and production tokens kept separate). Computed fields using @api.depends derive chargeable weight and expected freight, so planners see cost before they book.
Access is locked down the Odoo way: ir.model.access.csv grants and record rules scope Delhivery configuration to shipping managers while warehouse users only create and track shipments. Views are delivered as clean XML/OWL — a Delhivery tab on the delivery order, a serviceability check widget, and a tracking timeline — and the AWB label prints through a QWeb report so your packing station gets a Delhivery-format label with barcode straight from the printer. Automated actions and optional scheduled crons poll Delhivery for status transitions (picked up, in transit, out for delivery, delivered, RTO) and post them to the picking chatter, and everything is reachable over Odoo's XML-RPC/JSON-RPC API if you drive fulfilment from an external OMS or marketplace bridge.
We deliver and validate the connector on Odoo 17, 18 and 19, on Community or Enterprise, matched to your edition and warehouse topology. Because it is built to order, the module fits your exact pincode zones, COD reconciliation workflow and multi-warehouse pickup points rather than forcing a generic template onto your process. Typical delivery is 2–4 weeks from kickoff, and every engagement includes a support and updates window so the integration keeps working as Delhivery's API and your Odoo version evolve.
Runs a growing direct-to-consumer brand on Odoo shipping across India via Delhivery. Needs one-click shipment booking, printed AWBs and automatic tracking so a small team can dispatch hundreds of orders a day without living in the Delhivery portal.
Sells on Amazon, Flipkart and their own store, all fulfilled through Odoo. Needs Delhivery bookings triggered from Odoo (and via XML-RPC from marketplace connectors), correct pickup-warehouse mapping and consistent tracking pushed back to every channel.
Owns cash-on-delivery collections and remittance matching. Needs COD amounts captured on every shipment, RTO handling reflected in Odoo, and Delhivery remittances reconciled against orders so the books stay clean.
Maintains the company's Odoo 17/18/19 instance. Wants a properly structured addon with secure credential storage, role-based access rules and clean upgrade behavior rather than a fragile script bolted onto the database.
| 基準 | エコシエール | カスタムビルド | 競合他社 | オドゥー ネイティブ |
|---|---|---|---|---|
| Delhivery One API shipment booking from inside Odoo | 付属 | 部分的なサポート | 部分的なサポート | |
| AWB label via QWeb report at the packing station | 付属 | 部分的なサポート | 付属 | |
| Real-time tracking synced to the picking (cron + automated actions) | 付属 | 部分的なサポート | 部分的なサポート | |
| Serviceability / pincode check before booking | 付属 | 部分的なサポート | 部分的なサポート | |
| COD capture and remittance reconciliation workflow | 付属 | 部分的なサポート | 含まれていない | |
| Tailored to your warehouses, zones and COD rules (build-to-order) | 付属 | 付属 | 含まれていない | |
| Role-scoped access via ir.model.access.csv + record rules | 付属 | 部分的なサポート | 部分的なサポート | |
| Validated on Odoo 17/18/19, Community & Enterprise, with support window | 付属 | 含まれていない | 部分的なサポート | |
| You own the source and get technical handover | 付属 | 付属 | 含まれていない |
This is a build-to-order module, not an instant download. Typical delivery is 2–4 weeks from kickoff, depending on the complexity of your warehouse setup, COD reconciliation rules and pincode zones. We start with a short requirements call, build against your Odoo version, validate on Delhivery's staging environment, run a live test shipment with you, then install and hand over on your production instance.
Every engagement includes a defined support and updates window covering bug fixes and compatibility maintenance for changes in Delhivery's One API or your Odoo version. Within that window we resolve issues and keep the connector working; afterwards you can extend the support period or, because you own the source, have your own team maintain it. We can also provide an ongoing SLA for high-volume operations.
We build and validate the connector for Odoo 17, 18 and 19, on both Community and Enterprise. It integrates with the standard Inventory (stock), Delivery (delivery) and Sales (sale) apps, extending delivery.carrier so Delhivery appears as a native shipping method — no core code is patched, so your instance stays upgrade-friendly.
Yes. You provide an active Delhivery One (or Delhivery API) account with production credentials and configured pickup locations. During the build we use your staging/test credentials, and we store production and staging tokens separately in Odoo's settings. We do not resell Delhivery services — we integrate your existing account into Odoo.
COD is first-class. The COD amount is captured on the delivery order, passed to Delhivery on booking, and stored for reconciliation. Tracking events including RTO (return to origin) are synced back to the picking and sales order, and we build a reconciliation view or report so your finance team can match Delhivery remittances against the corresponding orders.
Yes. Because the module lives inside Odoo, everything it exposes is reachable over Odoo's XML-RPC/JSON-RPC API. An external OMS, marketplace connector or headless storefront can create shipments, fetch AWBs and read tracking status programmatically, while your team still works normally inside the Odoo UI.
End-to-end Delhivery integration for Odoo: shipment creation, AWB label print, live tracking, pincode check and COD reconciliation.