Transport & TMS

Courier APIs: labels, tracking and COD reconciliation

Carrier capabilities and access conditions vary. Build around the actual services required: shipment creation, labels, tracking, cancellation and settlement.

Illustrative concept: Courier APIs: labels, tracking and COD reconciliation
ASHA TECH Illustrative concept · Sample data

This is the English briefing. The full Thai guide includes additional examples and checklists. ไทย ↗

The practical takeaway

Normalize addresses and package data, while retaining carrier-specific requirements. Save the booking reference before retrying an uncertain request.

Define the records and rules

Normalize addresses and package data, while retaining carrier-specific requirements. Save the booking reference before retrying an uncertain request.

Connect the operational workflow

Keep internal shipment status separate from the carrier event code. Handle delayed events, duplicate webhooks and unsuccessful delivery attempts.

Checks before implementation

COD delivery confirmation does not mean money has reached the merchant. Reconcile carrier settlement records and fees against the expected collection.

Further reading from primary sources

These references support the standards and integration topics discussed. Workflow examples and figures illustrate system design.

Sources checked: 11 October 2026. Confirm current API access and requirements before implementation.

Start with your idea

What you want your business to do
starts with a conversation today.

Have an idea or a task a system could help with? Tell our team—no technical vocabulary needed.

ASHA TECH · DIGITAL ASSISTANT

Asha, your tech assistant

Automated assistant • Available around the clock

YOUR IDEA. OUR NEXT BUILD.

Tell me your idea
Asha is here to help

Web, apps, ERP or IoT
Start a conversation anytime

Automated assistant
Ready for your next idea

What shall we explore?

Pick a topic to start
Answers from our service information • Automated assistant