J&T Express Shipping Connector for Odoo

Key Features

J&T Express `delivery.carrier` provider type wired into Odoo's native delivery framework so shipping methods resolve against J&T rules

Automated order creation via `send_shipping()` when a `stock.picking` is validated — no double keying into the J&T portal

Airway bill (AWB) number written back to `carrier_tracking_ref` and surfaced on the delivery and sale order

Print-ready J&T label pulled from the API and rendered through a QWeb report for warehouse thermal/A4 printing

Shipment cancellation through `cancel_shipment()` that voids the J&T booking and clears the tracking reference

COD amount mapping from the sale order total onto the J&T booking payload, with a configurable rounding/currency policy

COD remittance reconciliation model matching courier-collected amounts against expected, with a `@api.depends` variance compute

Real-time tracking sync via an `ir.cron` scheduled action that polls J&T and posts status changes to the delivery chatter

Signed webhook controller endpoint for J&T push tracking callbacks where the account supports it, avoiding poll latency

Serviceability and destination-area validation that flags out-of-coverage addresses before a booking is attempted

Encrypted credential storage (customer code, API key, request signing) in a settings model backed by `ir.config_parameter`, with sandbox/production toggle

HMAC/private-key request signing and full request/response logging to a dedicated shipment-log model for audit and debugging

Role-scoped access through `ir.model.access.csv` plus record rules separating shipping-operator and finance visibility

XML-RPC/JSON-RPC exposure so an external OMS, marketplace bridge or storefront can trigger J&T bookings programmatically

Multi-warehouse and multi-company aware configuration so different branches can use distinct J&T customer codes

Built to order, done for you

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

You order

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

We build & install

ECOSIRE builds, configures and installs it on your Odoo.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

If you ship with J&T Express across Southeast Asia, China or MENA, your team is almost certainly living in two systems at once: Odoo for the sale order and delivery, and the J&T merchant portal or a spreadsheet for the actual booking, waybill and COD figures. Every parcel gets keyed twice, tracking numbers are copy-pasted back by hand, and COD amounts collected by the courier never quite reconcile against what Odoo invoiced. Odoo's native stock.picking and the built-in delivery carrier framework give you a carrier_id and a manual tracking-reference field, but there is no J&T API call behind the "Send to Shipper" button — the native flow stops exactly where the real integration needs to begin.

ECOSIRE builds a dedicated J&T Express connector that plugs into that native delivery layer and does the rest. We add a J&T delivery.carrier provider type so a shipping method resolves against J&T's serviceability and rating rules, then implement the send_shipping() and cancel_shipment() hooks to call the J&T Express API directly from the picking. When a warehouse user validates a delivery, the connector creates the J&T order, writes the airway bill number back onto stock.picking.carrier_tracking_ref, and pulls a print-ready label. API credentials (customer code, API key, HMAC/private-key request signing) live in an encrypted settings model backed by ir.config_parameter — never hardcoded — with separate sandbox and production endpoints so we can UAT safely before go-live.

Technically, the connector is a proper Odoo addon: a clean __manifest__.py declaring delivery and stock_delivery dependencies, new models extending models.Model for J&T configuration, shipment logs and COD reconciliation lines, compute fields with @api.depends for landed cost and COD variance, and QWeb reports for the AWB label and a shipping manifest. Access is locked down through ir.model.access.csv plus record rules so only shipping and finance roles touch courier data. Tracking sync runs on a scheduled automated action (ir.cron) that polls the J&T tracking endpoint and posts status changes to the delivery's chatter; where J&T supports push callbacks we expose a signed controller endpoint instead of polling. COD amounts are mapped from the sale order total onto the booking payload and, on remittance, matched back so finance sees a clean collected-vs-expected line. The same connector is exposed to your other automations through Odoo's XML-RPC/JSON-RPC API, so an external OMS or marketplace bridge can trigger a J&T booking without touching the UI.

Because this is build-to-order, nothing ships as a blind download. We start with a short scoping call to confirm your J&T account type, regions, COD workflow and whether you are on Odoo 17.0, 18.0 or 19.0 (Community or Enterprise — the connector targets Community APIs so it runs on both). We then build against your J&T sandbox credentials, hand you a staging environment for UAT, and only after you sign off do we install to production with a rollback plan. Typical delivery is 2–4 weeks from confirmed scope, and you receive the full source, documentation and a post-go-live support window.

What you get

Installable, version-pinned source code for your Odoo edition (17.0, 18.0 or 19.0), delivered as a clean addon

Installation and configuration on your environment, including J&T credential setup and sandbox/production wiring

Technical documentation: model reference, API mapping, cron/webhook setup and configuration parameters

User guide plus a live training session for your shipping and finance teams

UAT on a staging environment against J&T sandbox credentials, with a documented rollback plan before production cutover

Post-go-live support window for bug fixes and configuration adjustments after launch

Git repository handover with full commit history and tagged release for your version

Serviceability, label and COD reconciliation test scenarios validated against real J&T responses during UAT

Who this is for

SE-Asia / MENA online seller

Runs an Odoo-based ecommerce or B2C operation shipping J&T parcels across Indonesia, Malaysia, the Philippines, Vietnam, China or the Gulf, and needs bookings, labels and tracking to happen inside Odoo instead of the merchant portal.

Warehouse / fulfillment lead

Validates dozens to hundreds of deliveries a day and wants one-click AWB generation and label printing off the picking, with cancellation handled cleanly when an order changes.

Finance / COD controller

Owns cash-on-delivery reconciliation and needs collected-vs-expected COD amounts matched automatically so remittances from J&T tie back to invoices without manual spreadsheet chasing.

Odoo operations / IT manager

Responsible for a Community or Enterprise Odoo instance and wants a maintainable, role-secured addon with proper logging and an API surface other systems can call, not a fragile portal-scraping hack.

How J&T Express Shipping Connector for Odoo Compares

Criterion	ECOSIRE	Custom Build	Competitor	Odoo Native
J&T API booking from Odoo	Automated `send_shipping()` on picking validation	Possible, but you design and maintain the integration	Sometimes, if the module targets your J&T region	None — manual tracking field only
AWB label generation	Print-ready label via QWeb from the J&T API	Buildable with in-house dev effort	Varies; often a fixed template	Not available
COD reconciliation	Collected-vs-expected matching with variance compute	Only if you scope and build it	Rarely included	Manual, outside Odoo
Tracking sync	`ir.cron` polling plus signed webhook option	You build and schedule it yourself	Usually basic polling	Manual copy-paste of tracking numbers
Fit to your workflow	Scoped to your regions, edition and COD process	Fully bespoke but you own delivery risk	Generic; adapt your process to the module	Generic carrier framework only
Version support (17/18/19)	Pinned and tested to your exact version	Depends on your team's coverage	Often lags new Odoo releases	Ships with core, no J&T logic
Security and credential handling	Encrypted config, signed requests, role rules	As good as your own review	Unknown; audit required	N/A — no external calls
Support and maintenance	Post-go-live window plus paid upgrades	Your team maintains it	Vendor-dependent, often forum-only	Community/Enterprise support, no J&T scope

Frequently Asked Questions about J&T Express Shipping Connector for Odoo

How long does delivery take?

This is a build-to-order module. After a short scoping call to confirm your J&T account, regions, COD workflow and Odoo version, typical delivery is 2–4 weeks from confirmed scope. We build against your J&T sandbox, hand you a staging environment for UAT, and only cut over to production after you sign off.

Is this an existing app I can download from the Odoo App Store?

No. ECOSIRE builds, installs and supports this connector specifically for your J&T account and Odoo version. There is no instant download — you receive tailored source code plus installation, documentation and a support window after go-live.

Which Odoo versions and editions are supported?

Odoo 17.0, 18.0 and 19.0. The connector is built on Community-level APIs (the `delivery` and `stock` frameworks), so it runs on both Community and Enterprise. We confirm your exact version and edition on the scoping call and pin the release to it.

How are COD amounts handled and reconciled?

The connector maps the sale order total onto the J&T booking as the COD amount using a configurable currency and rounding policy. On remittance, a reconciliation model matches courier-collected amounts against expected values and computes any variance, so finance sees a clean collected-vs-invoiced line instead of a spreadsheet.

How does tracking stay up to date?

A scheduled automated action (`ir.cron`) polls the J&T tracking endpoint and posts status changes to each delivery's chatter. Where your J&T account supports push callbacks, we instead expose a signed webhook controller so status updates arrive in real time without polling.

What about support and updates after launch?

Every build includes a post-go-live support window for bug fixes and configuration adjustments. You also get the full git repository, so your team can maintain it. Beyond the initial window we offer ongoing support and paid upgrades — for example when J&T changes its API or when you migrate to a newer Odoo version.

Are my J&T API credentials stored securely?

Yes. Customer code, API key and signing keys live in an encrypted settings model backed by `ir.config_parameter` — never hardcoded in the source. Requests are signed (HMAC/private key) and logged to a dedicated shipment-log model, and access to courier and COD data is restricted by role through `ir.model.access.csv` and record rules.