Quick facts
- Price
- $199.00 USD
- Odoo versions
- 17, 18, 19
- Setup time
- 30 min
- License
- One-time perpetual
- Languages
- 11 languages
One-time Purchase
Colissimo Shipping Connector for Odoo
A build-to-order Odoo delivery carrier that connects La Poste Colissimo directly to your warehouse — generating labels, offering pickup-point (point retrait) selection at checkout, quoting live rates and syncing tracking back into Odoo. ECOSIRE builds, installs and supports it for Odoo 17.0, 18.0 or 19.0.
$199.00USD
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
Key Features
Native `delivery.carrier` provider — adds a `colissimo` `delivery_type` with its own settings page rather than a bolt-on wizard, so it behaves like any core Odoo carrier across sales, website and inventory
Live rate calculation via `<provider>_rate_shipment()` against the Colissimo grille tarifaire using real-time weight, destination and service code, returned to the sale order and website checkout
Label generation through Colissimo's `generateLabel` Web Service, storing the returned PDF/ZPL as an `ir.attachment` on the `stock.picking`
Pickup-point (point retrait / point relais) selector as an OWL checkout widget calling the Point Retrait service, with map/list rendering and persistence of the chosen relay ID on the order and delivery
Automatic parcel-number write-back to `carrier_tracking_ref` on `stock.picking` at delivery validation
Tracking synchronisation via `ir.cron` (or an automated action) that polls the Colissimo tracking service and advances shipment status
International and DOM-TOM support with a CN23/customs data model — HS codes, declared value, net weight and content per move line — feeding the international label call
Direct-to-printer output for Zebra/label printers plus a QWeb report action for A4/A6 label sheets and the bordereau de dépôt
Multi-service code support (domicile with/without signature, point retrait, return labels) selectable per carrier or per order
Credentials secured behind `ir.model.access.csv` and record rules so contract number and API password are visible only to shipping and admin roles
Return-label generation for reverse logistics, creating the Colissimo retour parcel and attaching its label to the picking
Full XML-RPC/JSON-RPC exposure so external systems can create Colissimo shipments and read tracking programmatically
Sender account and multi-warehouse configuration so each dispatch location can carry its own Colissimo contract and return address
Structured error surfacing — Colissimo API faults (weight limits, invalid postcode, contract errors) are caught and shown on the picking as a clear message instead of a silent failure
About this Product
French Odoo sellers shipping with La Poste Colissimo hit the same wall: Odoo ships with generic delivery carriers (fixed price, weight-based, and a handful of third-party connectors) but nothing that speaks Colissimo's Web Services natively. Teams end up re-keying every order into the Colissimo Expéditeur portal or Colieco, printing labels by hand, and copy-pasting parcel numbers back into stock.picking. Pickup points — the point retrait / point relais options that a large share of French e-commerce buyers expect — simply do not exist at Odoo checkout, so you lose the cheaper, higher-conversion delivery option entirely. The pain compounds at scale: no live rating, no bordereau, no customs data for DOM-TOM or international parcels, and no automated tracking updates for customers.
Why Choose Colissimo Shipping Connector for Odoo
Native `delivery.carrier` provider — adds a `colissimo` `delivery_type` with its own settings page rather than a bolt-on wizard, so it behaves like any core Odoo carrier across sales, website and inventory
Live rate calculation via `<provider>_rate_shipment()` against the Colissimo grille tarifaire using real-time weight, destination and service code, returned to the sale order and website checkout
Label generation through Colissimo's `generateLabel` Web Service, storing the returned PDF/ZPL as an `ir.attachment` on the `stock.picking`
Pickup-point (point retrait / point relais) selector as an OWL checkout widget calling the Point Retrait service, with map/list rendering and persistence of the chosen relay ID on the order and delivery
Automatic parcel-number write-back to `carrier_tracking_ref` on `stock.picking` at delivery validation
Tracking synchronisation via `ir.cron` (or an automated action) that polls the Colissimo tracking service and advances shipment status
We build a first-class Odoo delivery carrier that plugs into Colissimo's SOAP/REST Web Services. Technically it is a proper delivery.carrier provider: a new delivery_type selection with its own settings (contract number, API password, sender account, product/service codes) stored on the carrier and secured behind ir.model.access.csv plus record rules so only shipping and admin roles can see credentials. The rate step implements <provider>_rate_shipment() to call Colissimo's grille tarifaire live against parcel weight, destination country and chosen service, returning a real price to the sale order and website checkout. On validation of the stock.picking, <provider>_send_shipping() calls the label web service (generateLabel), stores the returned PDF/ZPL as an ir.attachment, writes the parcel number to the picking's carrier_tracking_ref, and can print through a QWeb-wired report action or push straight to a Zebra printer. Compute fields with @api.depends keep totals and label state consistent, and an automated action (or ir.cron) polls the tracking web service to advance shipment status and notify the customer.
The pickup-point experience is built into the checkout flow: an OWL widget calls Colissimo's Point Retrait service, renders nearby relay points on a map/list, and persists the buyer's selected point ID onto the sale order and delivery so the correct 08 service code and relay address flow into the label call. For cross-border and DOM-TOM parcels we add the CN23/customs data model — HS codes, declared values, weights and content descriptions per move line — so international labels generate without manual portal work. Everything is exposed over Odoo's XML-RPC/JSON-RPC API, so your marketplace connectors, TMS or ERP satellites can create shipments and read tracking programmatically.
Because this is build-to-order, you are not downloading a generic app and hoping it fits. After a short scoping call we confirm your Colissimo contract, service codes, printers and volume, then build and configure the module against your exact Odoo edition — 17.0, 18.0 or 19.0, Community or Enterprise (the Enterprise website_sale_delivery checkout integration differs from Community, and we handle both). Typical delivery is 2–4 weeks from confirmed scope. You get the full installable source, UAT on a staging database with a rollback plan, documentation, a training session, and a post-go-live support window — plus the git repository handover so the code is yours.
What you get
- Installable source code for your exact Odoo edition (17.0, 18.0 or 19.0; Community or Enterprise), delivered as a proper addon with a clean `__manifest__.py`
- Installation and configuration on your environment — Colissimo contract/service codes, sender accounts, printers and checkout wiring
- Technical documentation: models, fields, service-code mapping, security rules and the XML-RPC/JSON-RPC integration surface
- User guide plus a live training session for your shipping and e-commerce team
- UAT on a staging database with a documented test plan and a rollback plan before production go-live
- Post-go-live support window for defect fixes and configuration questions
- Git repository handover so the module source is fully yours to keep and extend
- Odoo version-compatibility notes covering Community vs Enterprise checkout differences for your setup
Who this is for
French Odoo e-commerce manager
Runs a B2C store on Odoo Website and needs Colissimo domicile plus point retrait at checkout to match buyer expectations and lift conversion, without staff re-keying orders into the Colissimo portal.
Warehouse / logistics lead
Owns the `stock.picking` dispatch flow and wants one-click label printing, correct bordereaux, tracking write-back and fewer manual steps as daily parcel volume grows.
Cross-border / DOM-TOM seller
Ships beyond metropolitan France and needs compliant CN23 customs data generated automatically so international and overseas-territory labels don't require manual work in the Colissimo Expéditeur portal.
Odoo integrator / IT lead
Maintains the Odoo instance and prefers a properly-architected delivery carrier — clean models, security via `ir.model.access.csv` and record rules, and an API surface — over a fragile scraper or manual process.
Installation overview
Download from ECOSIRE
Buy the license on ecosire.com and download the Colissimo Shipping Connector for Odoo module ZIP from your account dashboard.
Upload to Odoo
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Install the module
Activate Developer Mode, open Apps, click Update Apps List, search for Colissimo Shipping Connector for Odoo, and press Install.
Configure settings
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Verify & go live
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
How Colissimo Shipping Connector for Odoo Compares
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Colissimo pickup points at checkout | Built-in OWL point retrait selector with relay persistence | Possible but you build the widget and service calls yourself | Sometimes offered, often limited or extra-cost | |
| Live rate calculation | Real-time grille tarifaire quote in cart and sale order | Depends on your own implementation | Varies; some only fixed/weight tables | |
| Label generation | Native `generateLabel` call, PDF/ZPL stored on the picking | You implement and maintain the API integration | Usually included but generic | |
| International / DOM-TOM customs | CN23 data model feeding international labels | Build the customs model yourself | Often partial or unsupported | |
| Fit to your Odoo edition | Built for your exact 17/18/19, Community or Enterprise | Fits, but full build cost and timeline are yours | One-size-fits-all; edition quirks common | |
| Ownership & source code | Full git repo handover — the code is yours | You own it, but carry the whole build | Licensed, typically no source ownership | |
| Support & delivery model | Build-to-order, 2–4 weeks, UAT + support window | Your team's timeline and support burden | Instant download, generic ticket support | |
| Security of credentials | Scoped via `ir.model.access.csv` + record rules | Depends on your implementation discipline | Varies by vendor |
Frequently Asked Questions about Colissimo Shipping Connector for Odoo
+How long does delivery take, and is this an instant download?
No — this is a build-to-order module, not an existing apps.odoo.com download. After a short scoping call to confirm your Colissimo contract, service codes and Odoo edition, typical delivery is 2–4 weeks from confirmed scope. You receive the installable source, staging UAT and a go-live plan rather than a one-click purchase.
+Which Odoo versions and editions do you support?
We build against Odoo 17.0, 18.0 or 19.0, on both Community and Enterprise. The website checkout and delivery integration differ between Community and Enterprise, so we target your exact edition and note the compatibility details in the handover documentation.
+How are updates and support handled after go-live?
Every build includes a post-go-live support window for defect fixes and configuration questions. Because you receive the full git repository, you own the code and can maintain or extend it yourself; we can also quote a separate maintenance arrangement or a version-upgrade (for example 17.0 to 19.0) when you need one.
+Do you support pickup points (point retrait / point relais)?
Yes. We build an OWL checkout widget that calls Colissimo's Point Retrait service, lets the buyer choose a nearby relay point on a map/list, and persists the selected relay ID onto the sale order and delivery so the correct service code and relay address flow into the label.
+Can it handle international and DOM-TOM shipments with customs data?
Yes. We add a CN23/customs data model capturing HS codes, declared value, net weight and content descriptions per line, which feeds the Colissimo international label service so cross-border and overseas-territory parcels generate without manual portal entry.
+Do I need my own Colissimo contract?
Yes — you supply your La Poste Colissimo business contract (contract number, API password and enabled service codes). The module authenticates against your account; we configure your credentials securely behind Odoo access rules during installation.
+Can other systems create shipments through it?
Yes. The carrier is exposed over Odoo's XML-RPC/JSON-RPC API, so a marketplace connector, TMS or external ERP can create Colissimo shipments, trigger labels and read tracking references programmatically.
Related Modules
Request a quote
Colissimo Shipping Connector for Odoo
A build-to-order Odoo delivery carrier that connects La Poste Colissimo directly to your warehouse — generating labels, offering pickup-point (point retrait) selection at checkout, quoting live rates and syncing tracking back into Odoo. ECOSIRE builds, installs and supports it for Odoo 17.0, 18.0 or 19.0.
- Native `delivery.carrier` provider — adds a `colissimo` `delivery_type` with its own settings page rather than a bolt-on wizard, so it behaves like any core Odoo carrier across sales, website and inventory
- Live rate calculation via `<provider>_rate_shipment()` against the Colissimo grille tarifaire using real-time weight, destination and service code, returned to the sale order and website checkout
- Label generation through Colissimo's `generateLabel` Web Service, storing the returned PDF/ZPL as an `ir.attachment` on the `stock.picking`
- Pickup-point (point retrait / point relais) selector as an OWL checkout widget calling the Point Retrait service, with map/list rendering and persistence of the chosen relay ID on the order and delivery