Choose between a driver job and a carrier shipment
A courier aggregator can mean access to local delivery networks or a multi-carrier parcel platform. Start with what you hand over: a ready meal to a nearby driver, or a packaged shipment entering a carrier network. Local dispatch assigns pickup and delivery work. Parcel shipping selects a carrier service, purchases a label and follows tracking events through the network. A tool that does one does not automatically do the other.
The multi-carrier shipping workflow
Prepare origin and destination addresses, package weight and dimensions, contents and service requirements. A quoted rate depends on those inputs and the eligible carrier account. Check dimensional weight, surcharges, insurance and collection fees before passing a delivery charge to the customer. A quote is not a guaranteed pickup or final invoice.
Shippo documents shipment creation using addresses and parcels to retrieve available rates. Its documentation separates returns from the outbound shipment. Use those as distinct requirements when evaluating a parcel API, rather than assuming a tracking widget buys labels or creates return shipments.
After selecting a service, purchase and print the correct label, attach it to the correct parcel and arrange pickup or drop-off. Record the carrier acceptance event. Label creation alone does not prove the package entered the carrier network. Match the tracking number to the order and expose clear statuses for in transit, exception and delivered; define who investigates missing or contradictory scans.
Returns need a separate operating policy
Decide eligibility, authorization, destination, return-label cost and inspection rules before accepting returns. Distinguish a carrier returning an undeliverable parcel from a customer requesting a product return. Issue refunds only through the agreed payment process after the required checks; a return tracking event is not itself a refund.
Integrate without confusing responsibilities
Map the order ID, shipment ID and tracking number. Define the system that owns addresses, stock, labels, cancellations and refunds. Repeated API calls must not buy duplicate labels. Reconcile webhook events with shipment records, and give support a manual lookup and escalation path when updates are delayed. Test voided labels, partial shipments, failed pickups and returns in a suitable test environment before production.
Ordering.co connects customer channels, merchant operations and local delivery with owned drivers or connected providers. That does not establish a native multi-carrier label, parcel-rate or returns portal. Scope a separate shipping platform and connector when those are requirements. Compare local delivery workflows and shipping versus local delivery, then discuss the system boundaries with your order and package examples.