China Logistics API Integration and Cost Guide: Direct, KDNiao, and Kuaidi100
Compare direct carrier integration, KDNiao, and Kuaidi100 across API pricing and maintenance; understand carrier transport costs and which mini programs need logistics.
Use a logistics integration only when the mini program must fulfil, collect, return, or deliver physical goods. For a small multi-carrier launch, KDNiao or Kuaidi100 is usually the shortest route. Direct carrier integration suits large, concentrated volume and an existing shipping contract. A marketplace often benefits from an aggregator plus direct connections to its core carriers. API charges and the carrier's transportation charges are separate costs.
This guide concerns Mainland China parcel, waybill, tracking, pickup, return, and on-demand delivery integrations. Product and pricing information was checked on 28 August 2026. Promotions and shipping quotes change; planning ranges below are not vendor quotations.
1. Which mini programs need logistics?
| Product | Need | Typical first scope |
|---|---|---|
| Brand store, marketplace, farm produce or retail | Yes | Freight rules, shipment creation, labels, tracking, delivery and returns |
| Multi-merchant or supply-chain platform | Strong need | Account isolation, multiple carriers, push tracking, exceptions and reconciliation |
| Food, flowers, pharmacy or errands | Yes, but use on-demand delivery | Pre-order quote, dispatch, courier location, cancellation and proof of delivery |
| Rental, repair, recycling or trade-in | Usually | Outbound and reverse shipment, pickup, insurance and custody evidence |
| Appointment, membership, course or digital content | Usually no | Scheduling, entitlement, redemption and notifications instead |
The decision test is whether completion depends on a traceable physical item moving from A to B. An occasional manually shipped document may need only carrier and tracking-number entry plus an official tracking link.
2. Separate the capabilities
A production scope can include carrier identification, on-demand tracking, tracking subscription and webhook, electronic waybill, shipment/pickup, price and ETA estimate, interception, proof of delivery, and reverse logistics. Same-city delivery has a different real-time quote and dispatch lifecycle.
The normal parcel flow is:
create/record shipment → store carrier and waybill → subscribe → verify webhook → normalize status → display → route exceptions to operations
3. Direct carrier, KDNiao, or Kuaidi100
| Dimension | Direct carrier | KDNiao | Kuaidi100 |
|---|---|---|---|
| Coverage per integration | One carrier | Aggregated carriers | Aggregated carriers |
| Best fit | Concentrated high volume, existing carrier account, deep after-sales | Multi-carrier tracking and waybills with a fast launch | Multi-carrier tracking, shipment, printing and visibility |
| API pricing | Commonly contract-specific; no universal public per-call price | Free/trial, annual bundles and enterprise plans | Packages or prepaid usage; current amounts shown in account |
| Shipping charge | Paid to carrier under retail, branch or monthly contract terms | Own carrier account or platform shipment product | Own carrier account or platform prepaid shipment product |
| Maintenance | Separate schema, signature and upgrade per carrier | One primary integration | One primary integration |
SF's official open platform exposes shipment, information, tracking push, cloud printing and sandbox capabilities. A direct API may have no separate public call charge, but the merchant still needs verification, a customer/monthly account and payment of every shipment. Confirm special APIs, printing, maps and support in the contract.
KDNiao's current product page advertises promotional annual bundles at RMB 488, RMB 1,288 and RMB 2,288 with different allocations for labels, monitoring, address parsing, ETA and interception. These are promotional bundles, not a universal per-tracking price. Its membership comparison distinguishes free and enterprise coverage, limits, push speed and status detail.
Kuaidi100's real-time tracking documentation says packages are purchased in the enterprise console and repeat queries for the same waybill within 40 days are not charged again. Automated lifecycle updates should use push tracking rather than aggressive polling. Its price-estimation API is prepaid and usage based, with current prices in the account. A shipment API may be free to call while the actual courier charge remains payable.
A hybrid design uses an aggregator for long-tail tracking and direct connections for one or two core carriers. Keep a provider-neutral interface such as createShipment, cancelShipment, subscribeTracking, quote, intercept, and getProof.
4. Compare API costs correctly
Normalize the unit: one HTTP call, one new waybill, one subscription, one imported order, and one de-duplicated waybill window are not equivalent. Record validity, rollover, overage price, failed-call billing, duplicate window, test quota, QPS, callback latency, availability, support, refund and invoice terms.
Direct connections carry engineering and ongoing maintenance for every carrier. Aggregators carry package fees and create a shared dependency. Electronic-waybill API allowance also does not automatically include the merchant's carrier account, physical shipment, printer, consumables or value-added services.
5. Carrier shipping costs
| Carrier/type | Positioning | Cost basis | Obtain the real price |
|---|---|---|---|
| SF Express | Time-sensitive and higher-value parcel | First weight + additional weight; route/product dependent | Official price and ETA tool, then monthly contract |
| JD Logistics | Warehousing, e-commerce and pickup | Product, lane, chargeable weight and extras | Open platform or account-manager quote |
| ZTO | Economy e-commerce parcel | Greater of physical and volumetric weight | Official rules and calculator, then branch/contract quote |
| YTO, STO, Yunda, J&T | Economy e-commerce parcel | First/additional weight, lane, branch and volume | Official channel and local branch/contract quote |
| China Post/EMS | Broad coverage, documents and specialist cases | Product, zone, weight/volume and extras | Official postal channel and contract |
| Deppon/less-than-truckload | Large and heavy goods | Kilogram or cubic measure; chargeable-weight rule | Official calculation followed by weighed invoice |
| Same-city networks | Food, retail and urgent delivery | Distance, time, weather, supply, weight and service | Real-time API quote; SF Intra-city uses a top-up and dispatch flow |
Mainland China has no durable nationwide price card applicable to every merchant. Origin branch, destination, monthly volume, settlement, product, dimensions and negotiation all matter. ZTO, for example, documents use of the greater of physical and volumetric weight and a product-specific rounding rule. Do not reuse one carrier's volumetric divisor for another.
For internal stress testing before quotations, a 1 kg economy parcel may be modelled at RMB 6–18, a premium parcel at RMB 12–30, postal products at RMB 8–25, and same-city delivery from roughly RMB 12–50. These broad figures must never be displayed as carrier quotes. Obtain a matrix for the actual warehouse, top destinations, weight/dimension bands and volume, then validate it with trial shipments.
6. Total fulfilment cost
cost per shipment = base transport + additional/volumetric weight + packaging + surcharges + insurance/extras + return/redelivery + allocated API + support and loss
Budget packaging and labour, remote or oversized fees, stairs/special warehouse delivery, insurance, COD, receipt, address change, interception, refused returns, measured-weight adjustments, tracking/SMS/map/printing services, and exception handling. Customer-facing delivery fees are a pricing policy and should be accounted separately from carrier invoices.
For 10,000 monthly orders at 1.1 shipments per order and 5% additional return shipments, there are 11,550 new waybills. Tracking-subscription cost should be based on those new subscriptions, not page views. Replace planning rates with three months of actual destination, weight, dimensions and return distribution before contracting.
7. Selection and acceptance
- Validation or low volume: choose one aggregator and implement tracking plus push first.
- Multiple carriers and moderate volume: negotiate subscription and label allocations; add exception handling and quota alerts.
- High volume concentrated in one or two carriers: evaluate direct integration and keep the aggregator for the long tail.
- Marketplace: isolate each merchant's carrier account, label balance, origin and billing permissions unless the platform intentionally accepts credit, prohibited-goods, claim and tax liability.
- Same-city: quote every order with an expiry and design for no courier, cancellation, changed address, peak/weather surcharge and manual fallback.
Keep secrets on the server, verify and deduplicate callbacks, use idempotency for shipment creation, preserve original and normalized status, tolerate out-of-order events, mask personal data, monitor callback backlog and inactive shipments, and retain manual entry plus official tracking links during an outage.
Before buying, ask every option to quote the same input: monthly new waybills, carrier mix, origins, destination mix, weight/dimensions, shipment/label/tracking/return capabilities, peak QPS, SLA and overage rule. Only then are API and transportation costs comparable.
This article is for product, engineering, and procurement planning and is not a vendor or carrier quotation. Verify current pages, tests, and signed contracts before implementation.