Leopards Courier Connector for Odoo

ECOSIRE builds a dedicated Leopards Courier connector as a proper Odoo module (__manifest__.py declaring dependencies on stock, delivery and sale), with its own delivery.carrier provider type so Leopards appears as a first-class shipping method. From a confirmed stock.picking, a "Book with Leopards" action calls the Leopards Merchant API over JSON/HTTPS to create the consignment, then writes the returned CN/AWB number, tracking URL and booking status back onto the picking via new fields on a models.Model extension. Credentials (API key, merchant api_password) are stored on res.company or ir.config_parameter, never hard-coded, and every request/response is logged for support. Weight, piece count, origin city and destination city are mapped from the picking and partner, with a compute method (@api.depends) resolving the Leopards city code before booking so mis-spelled cities never reach the API.

Technically, the build spans the layers you would expect from a clean Odoo module: an ir.model.access.csv plus record rules so only the Delivery/Inventory groups can book or cancel; XML/OWL views adding a Leopards tab and status widgets to the delivery order form and a smart button to the sale order; a QWeb PDF report that renders the CN/airway-bill label (barcode included) for the packing station; and a scheduled automated action (ir.cron) that polls Leopards tracking on open consignments and posts status changes to the chatter. COD reconciliation is a first-class feature: when Leopards reports a shipment delivered and remitted, the module matches the COD amount against the linked sale.order/account.move and flags mismatches for review, so your finance team stops living in spreadsheets. Serviceability is checked at quotation or checkout time via the Leopards city/tariff endpoint, so customers in non-covered areas are caught before an order is confirmed.

This is a build-to-order engagement, not an instant download from apps.odoo.com. We start with a scoping call to confirm your Leopards merchant account type, which Odoo edition and version you run (17.0, 18.0 or 19.0), your COD workflow, and any e-commerce/website_sale checkout needs. We then build against your exact requirements, test on a staging copy of your database, run UAT with your team, and deploy to production with a rollback plan. Typical delivery is 2–4 weeks from confirmed scope, depending on complexity and how quickly Leopards API credentials are provisioned. You receive the full module source, documentation, training, and a post-go-live support window — the connector is yours to keep and extend.