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.

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.