SE-Asian and MENA merchants running ERPNext live and die by their last-mile carrier, and J&T Express is one of the biggest — but ERPNext core has no idea J&T exists. Out of the box you get a Shipment DocType and Delivery Note, yet no way to push a consignment to J&T, print a compliant AWB, book a pickup, or pull a scan event back. Teams end up keying orders into the J&T merchant portal by hand, copying tracking numbers into spreadsheets, and — worst of all — reconciling COD remittances manually against hundreds of parcels. Every rekeyed address is a misdelivery, and every unreconciled COD parcel is cash you can't see in Payment Entry.

ECOSIRE builds a proper Frappe app (its own module, not a pile of Custom Fields) that makes J&T a first-class carrier inside ERPNext. We add a J&T Settings single DocType holding per-country API credentials, customer code, and the private key J&T uses to sign requests, plus a J&T Shipment DocType that mirrors each consignment and its lifecycle. Booking is driven from your existing documents: a hooks.py on_submit doc event (or an explicit "Create J&T Shipment" button backed by a @frappe.whitelist() method) reads the Delivery Note, maps items and package weights, calls the J&T order-create endpoint, stores the returned AWB/tracking number back on the source document, and renders a label through a Frappe Print Format so your packers print straight from the desk — no portal round-trip.

COD is treated as a real accounting problem, not a checkbox. The connector flags COD consignments, captures the collected amount J&T reports, and gives you a reconciliation view that matches carrier remittance files against Sales Invoice / Payment Entry so finance can see exactly which parcels are paid, pending, or short. Pickup booking is a whitelisted method against J&T's pickup API with the response persisted for audit, and a Frappe Scheduler Event polls (or receives, where J&T supports webhooks) tracking milestones and writes them to a timeline on the shipment so support and customers see live status. Multi-country serviceability is baked in: routing rules pick the correct J&T endpoint, credentials and label template per destination, with graceful fallbacks and a Frappe Error Log entry whenever the carrier rejects a booking, so failures are visible instead of silent.

Because this is build-to-order, nothing is pre-listed for instant download. We start with a short scoping call to confirm your J&T country accounts, the exact documents you dispatch from, your COD and returns policy, and your ERPNext version. From confirmed scope, typical delivery is 2 to 4 weeks: we build against a staging bench, run UAT with your real order and COD data, and hand over installable source, a git repository, technical and user documentation, a training session, and a post-go-live support window. You get software shaped to your operation and warranted by the team that wrote it.