Skip to main content
Shiprocket Aggregator Connector for Odoo — One build-to-order Odoo connector to Shiprocket's 25+ Indian couriers — rate compa — 1/1Illustrative preview

One build-to-order Odoo connector to Shiprocket's 25+ Indian couriers

— rate compare, AWB, labels, pincode checks & COD reconciliation.

What is Shiprocket Aggregator Connector for Odoo?

One build-to-order Odoo connector to Shiprocket's 25+ Indian couriers — rate compare, AWB, labels, pincode checks & COD reconciliation. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $999.00 USD; request a quote for a scoped proposal.

Key Features

One-token Shiprocket API layer (`shiprocket.config` model) authenticating to 25+ couriers — Delhivery, DTDC, XpressBees, Ecom Express, Blue Dart, Amazon Shipping — with automatic token refresh via `ir.cron` before the 10-day expiry
Live rate comparison from every eligible courier shown directly on the delivery order, with the recommended courier auto-selected by your rule (cheapest, fastest, or highest-rated)
Best-courier recommendation engine driven by a computed field (@api.depends on weight, destination pincode and shipment value) that re-evaluates whenever the order changes
One-click pincode serviceability check across Shiprocket's 29,000+ serviceable pincodes, blocking AWB generation for non-serviceable destinations before you waste a pickup
AWB assignment and shipping-label PDF generation pushed back onto `stock.picking` as the courier name, AWB number and tracking URL
Automated pickup scheduling against your registered Shiprocket pickup locations, mapped to Odoo warehouses
Full COD support — collectable amount carried from `sale.order` through to Shiprocket, with a reconciliation view that matches courier remittances back to the originating order
QWeb reports for consolidated pickup manifests and reprintable labels, styled to your branding
Automatic tracking updates via Shiprocket status webhooks (JSON-RPC callbacks) that advance the delivery state and log to the chatter — no manual polling
Weight, dimension and package-count fields on the picking that feed accurate volumetric rate quotes
Return (RTO) and NDR visibility surfaced on the order so your team can act on failed-delivery and undelivered exceptions
Role-scoped security via `ir.model.access.csv` plus record rules — warehouse staff ship, only managers edit API credentials — and full audit logging through the standard Odoo chatter
Multi-warehouse and multi-company aware, so each branch ships from its own Shiprocket pickup location
Built and tested across Odoo 17, 18 and 19 on both Community and Enterprise

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

  1. 1

    You order

    Start with a one-time build price. We scope it with you at kickoff.

  2. 2

    We build & install

    ECOSIRE builds, configures and installs it on your Odoo.

  3. 3

    Go live + support

    You go live in about one working week, with two weeks of go-live support. Defects in the code we deliver are fixed free of charge.

Technical Specifications

Odoo Compatibility
Odoo 17, Odoo 18, Odoo 19
Editions
Enterprise & Community
License
Licence confirmation required
Python Requirement
Python 3.10+
Database
PostgreSQL 12+

About this Product

Stop juggling a dozen courier logins and manual AWB entry. The Shiprocket Aggregator Connector for Odoo is a single, native integration that plugs your Odoo Inventory and Sales flow straight into Shiprocket's network of 25+ Indian couriers — Delhivery, DTDC, XpressBees, Ecom Express, Blue Dart, Amazon Shipping and more — through one authenticated API layer.

This is a build-to-order module, not an off-the-shelf apps.odoo.com download. ECOSIRE designs, codes, installs and supports it against YOUR Shiprocket account, YOUR warehouse pickup locations and YOUR Odoo edition (Community or Enterprise). Because we build it fresh, the connector maps cleanly onto your real dispatch process instead of forcing you into a generic template.

Under the hood it is a proper Odoo addon. A dedicated shiprocket.config model (models.Model) holds your API email/password and issues the Shiprocket auth token, refreshing it before the 10-day expiry via a scheduled ir.cron automated action. New models extend stock.picking and sale.order with computed fields (@api.depends) for recommended courier, quoted freight and COD status, so shipping intelligence lives right on the delivery order your team already uses. Every field, wizard and menu is locked down with ir.model.access.csv plus record rules, so warehouse users see shipments while only managers change API credentials.

From a confirmed delivery order, one click checks pincode serviceability across Shiprocket's 29,000+ serviceable pincodes, compares live rates from all eligible couriers, and surfaces the recommended courier (cheapest / fastest / best-rated per your rule). Assign it, and the connector creates the Shiprocket order, generates the AWB and shipping label PDF, and schedules pickup — writing the AWB, courier name and tracking URL back onto the picking. COD orders carry the collectable amount through to Shiprocket and reconcile remittances back against the sale order, so your finance team stops chasing spreadsheets. Tracking webhooks (JSON-RPC callbacks) update delivery status automatically, and a QWeb-based manifest/label report lets you print consolidated pickup sheets.

You supply the Shiprocket account and pickup addresses; we handle the Odoo engineering, the security model, the QWeb reports, the multi-edition testing (17, 18 and 19) and a proper handover. Typical delivery is one working week depending on how much COD reconciliation and custom-courier-rule logic you need.

What you get

  • Complete, installable Odoo addon (module source with `__manifest__.py`, models, XML/OWL views, `ir.model.access.csv`, record rules and QWeb reports) versioned for your Odoo release
  • Installation and configuration on your Odoo instance (staging first, then production), wired to your live Shiprocket account, pickup locations and warehouses
  • Courier-recommendation rule configured to your policy (cheapest / fastest / rated) and COD reconciliation set up against your accounting flow
  • Technical documentation covering the data model, API/token handling, cron jobs, security rules and every configuration setting
  • An end-user runbook plus a live training session for your dispatch and finance teams (recorded on request)
  • A defined post-go-live support and bug-fix window (two weeks, extendable) covering fixes to the delivered scope
  • Handover of the Git repository / source so the module is fully yours to keep, audit and extend

Who this is for

Indian D2C / e-commerce SMB owner

Ships hundreds of orders a month across couriers and is tired of separate courier logins, manual AWB entry and no single view of freight cost. Wants one Odoo-native workflow that picks the right courier automatically and keeps COD money tracked.

Warehouse & dispatch manager

Lives in the delivery-order screen and needs to check serviceability, compare rates, generate AWBs/labels and schedule pickups without leaving Odoo — plus print consolidated pickup manifests for the courier agent each evening.

Finance / accounts lead

Owns COD reconciliation and cash-flow visibility. Needs collectable amounts to flow through to Shiprocket and remittances to match back to the originating sale order automatically, replacing fragile reconciliation spreadsheets.

How Shiprocket Aggregator Connector for Odoo Compares

CriterionECOSIRECustom BuildCompetitorOdoo Native
Access to 25+ couriers via one integrationYes — single Shiprocket API layer inside OdooPossible, but you build and maintain each courier mapping yourselfVaries — many list one courier per app; aggregator coverage is inconsistentNot included
Best-courier recommendation & live rate compareYes — computed on the order, rule-driven (cheapest/fastest/rated)Only if you code the rate-shopping logic from scratchPartial supportNot included
Fits YOUR dispatch process & Odoo editionBuilt to order for your workflow, warehouses and version 17/18/19Yes — that is the whole point of a custom buildNot includedNot included
Pincode serviceability check (29,000+ pincodes)Yes — pre-AWB, blocks non-serviceable destinationsOnly if implemented and kept currentPartial supportNot included
COD support & remittance reconciliationYes — collectable flows through, remittances match back to the orderBuild it yourself; ongoing maintenance is on youPartial supportNot included
AWB, label & QWeb pickup manifest generationYes — labels and consolidated manifests via QWeb, written back to the pickingRequires custom report developmentPartial supportNot included
Security model (ir.model.access.csv + record rules)Yes — role-scoped, credentials manager-only, chatter auditDepends on your team's disciplinePartial supportPartial support
Source ownership, docs, training & support windowYes — full source handover, docs, live training, two-week supportDepends on your vendor/contractno — closed module, ticket-only supportPartial support

Frequently Asked Questions about Shiprocket Aggregator Connector

How long until the connector is live in my Odoo?

This is a build-to-order module, so it is not an instant download. After a short scoping call we build, test across your Odoo version, and install it — typically one working week. Timing depends mainly on how much COD reconciliation logic and custom courier-selection rules you need. You get a firm timeline before we start, plus staging-first deployment so nothing hits production untested.

What support and updates do I get after go-live?

Every build ships with a defined support window (two weeks, extendable) covering bug fixes within the delivered scope. Because you receive the full source, you own the module and can extend it yourself. We also offer optional annual maintenance to keep it aligned with Shiprocket API changes and to migrate it forward when you upgrade Odoo (e.g. 18 to 19).

Does it work on Odoo Community, or only Enterprise?

Both. The connector is built on standard Odoo framework components — models, fields, views, `ir.model.access.csv`, record rules, `ir.cron` and QWeb reports — that exist in Community and Enterprise alike. We build and test it against your exact edition and version (17, 18 or 19) so it installs cleanly with no Enterprise-only dependency unless you specifically want one.

Do I need my own Shiprocket account?

Yes. You bring a Shiprocket account with your couriers activated and your pickup locations registered; we handle all the Odoo-side engineering. During setup we wire your API credentials into the secure `shiprocket.config` model, which issues and auto-refreshes the auth token via a scheduled cron so your team never re-authenticates manually.

How does COD reconciliation actually work?

When an order is COD, the collectable amount flows from the `sale.order` through to the Shiprocket order at AWB creation. As Shiprocket remits collected cash, the connector surfaces a reconciliation view that matches each remittance back to its originating order and delivery, so finance can confirm what has been collected and what is still pending without a manual spreadsheet.

Can it pick the cheapest or fastest courier automatically?

Yes. On a confirmed delivery order it calls Shiprocket for live rates from every serviceable courier and applies your chosen rule — cheapest, fastest, or best-rated — via a computed field (@api.depends). The recommendation is pre-selected but always overridable, so your team keeps final say while the default does the thinking.

Request a quote

Shiprocket Aggregator Connector

One build-to-order Odoo connector to Shiprocket's 25+ Indian couriers — rate compare, AWB, labels, pincode checks & COD reconciliation.

  • One-token Shiprocket API layer (`shiprocket.config` model) authenticating to 25+ couriers — Delhivery, DTDC, XpressBees, Ecom Express, Blue Dart, Amazon Shipping — with automatic token refresh via `ir.cron` before the 10-day expiry
  • Live rate comparison from every eligible courier shown directly on the delivery order, with the recommended courier auto-selected by your rule (cheapest, fastest, or highest-rated)
  • Best-courier recommendation engine driven by a computed field (@api.depends on weight, destination pincode and shipment value) that re-evaluates whenever the order changes
  • One-click pincode serviceability check across Shiprocket's 29,000+ serviceable pincodes, blocking AWB generation for non-serviceable destinations before you waste a pickup

Request a Quotation

Tell us about your Shiprocket Aggregator Connector requirements and we'll send pricing, licensing options and a tailored proposal — usually within one business day.

No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.