J&T operates differently across markets. Your shipping footprint drives the design.
J&T Express moves millions of parcels across Southeast Asia. Shipping costs and COD data live in their system. Someone's bridging that manually.
Oracle ERP Expertise CertifiedTransparent PricingPost Go-Live Support

The Problem
J&T delivers the parcel, but COD settlements and shipping costs don't flow back to NetSuite without manual work.
J&T Express dominates last-mile delivery across Indonesia, Vietnam, Thailand, and the Philippines. But J&T doesn't sync fulfillment events, delivery confirmations, or COD settlement data to NetSuite automatically. Your team reconciles cash-on-delivery payments against open invoices by hand, and shipping cost accruals lag behind actual spend.

Someone copies order details from NetSuite into J&T's shipping portal to generate waybills. At 200 orders a day, that's a full-time job that shouldn't exist.
When a sales order is ready to ship, the integration pushes shipment details to J&T and pulls back the waybill number automatically. No portal login, no copy-paste.
Customer service looks up each parcel on J&T's website individually. There's no consolidated view and no way to flag stuck shipments before customers start asking.
Delivery milestones from J&T update the fulfillment record in NetSuite. Your team sees in-transit, delivered, and failed-delivery statuses without leaving the system.
J&T deposits COD collections in batches. Finance downloads the remittance report and spends half a day matching amounts to orders, with discrepancies tracked in a spreadsheet nobody enjoys.
Each COD batch from J&T is broken down by order and applied as payment against the corresponding invoice in NetSuite. Fees post separately and discrepancies surface immediately.
A parcel comes back because the customer wasn't home or refused COD. The sales order still shows as fulfilled. Revenue recognition is wrong until someone catches it and reverses the entry.
When J&T marks a delivery as failed or returned, NetSuite updates the fulfillment status and triggers a return authorization or re-delivery workflow based on your business rules.
J&T's invoice covers thousands of shipments as a lump sum. No one allocates costs back to individual orders, so margin analysis treats shipping as overhead rather than a real per-order cost.
Delivery charges from J&T map to individual fulfillment records in NetSuite. Your margin reports reflect actual logistics spend at the order level, not an average.
J&T Express + NetSuite Integration
What We'd Ask Before Scoping J&T Express
J&T operates differently across markets. Your shipping footprint drives the design.
Which J&T markets you ship in (Indonesia, Malaysia, Vietnam, Thailand, Philippines) and your daily parcel volume including marketplace spikes.
Whether waybills and labels generate from NetSuite, if pickup requests trigger from fulfillment creation, and if tracking events push back to NetSuite.
Whether you use J&T's COD service and need collected amounts matched against NetSuite invoices or sales orders automatically.

We can then define the full integration scope for each market you operate in.


ONE Pacific built a custom wholesale portal powered by Workato, allowing distributors to enter order details on their own without involving our staff.
Mattia Lolli
Chief Operating Officer
D1 Milano
J&T Express waybill creation, tracking events, COD remittances, and per-shipment charges integrate with NetSuite fulfillment records, invoices, and cost posting through API calls and batch reconciliation.
Most J&T Express integrations are scoped in one to two weeks and live within 6 to 8 weeks. Let's talk about yours.

Map USPS rate tiers, tracking scans, and SCAN form manifests into NetSuite fulfillment records, with separate handling for Commercial Plus vs Retail pricing.

Ninja Van's API varies by country, so COD remittance cycles, tracking payloads, and return-to-sender flows each need per-market logic inside NetSuite.

Keep NetSuite inventory and fulfillment records accurate across every sales channel by syncing shipment data from ShipStation automatically.

Connect EasyPost to NetSuite for automated rate shopping across carriers, real-time tracking updates on fulfillments, and return label linkage back to RMAs.

Pre-calculate duties at checkout through Easyship, then reconcile what the broker actually charges weeks later against your NetSuite landed cost records.

Book GrabExpress pickups from NetSuite fulfillment records, then reconcile the COD cash Grab collects against individual invoices when settlement arrives days later.
Showing 6 of 16 Shipping & Logistics Integrations
Cost depends on how many of J&T's 13+ markets you're shipping to—each country has its own API endpoint and COD reconciliation rules, especially tricky across Indonesia, Thailand, and the Philippines. Their API handles order creation and tracking well, but you'll need custom work for returns management and failed delivery workflows since J&T doesn't provide those endpoints.
If you're pushing high volumes through NetSuite's rate limits while managing multi-currency transactions and country-specific customs docs, expect more development time. Synkka's pre-built connector can get you running in 5 days for standard shipping, but complex scenarios like cross-border landed costs or real-time webhook tracking still need custom builds.
When J&T marks a parcel as undeliverable or returned, the integration updates the fulfillment record in NetSuite and can trigger a return authorization, inventory adjustment, or re-delivery workflow. The specifics depend on your business rules. Some clients re-attempt delivery automatically. Others route returns through a review queue. We configure the logic during implementation.
Typically 6 to 8 weeks from kickoff to go-live. The first couple weeks cover scoping: mapping your fulfillment workflow, identifying which J&T countries are in play, and defining COD reconciliation rules. Build and testing takes another four to six weeks, including a parallel run where automated records are checked against your existing manual process.
The standard milestones: picked up, in transit, out for delivery, delivered, and failed delivery. Each status update writes to the fulfillment record in NetSuite with a timestamp. For failed deliveries, you can configure automatic workflows like creating a return authorization or scheduling a re-delivery attempt.
J&T's API and data formats differ by country. Indonesia, Vietnam, the Philippines, Thailand, and Malaysia each have their own quirks around tracking IDs, settlement schedules, and invoicing. We handle the normalization so NetSuite gets consistent records regardless of which market the shipment originates from. During scoping, we'll identify which countries you ship through and configure each one.
J&T collects cash from your customers and remits it in batches, typically every few days depending on the country. The integration breaks each batch down by order, matches the collected amount to the corresponding NetSuite invoice, and posts J&T's carrier fees as a separate expense. Discrepancies between expected and remitted amounts are flagged automatically so your finance team catches them in hours, not weeks.
Ready to connect J&T Express and NetSuite?
Our engineers will review your setup, map your systems, and, if it makes sense to move forward, provide a clearly scoped proposal. No pressure.