Shipment
The Shipment object encapsulates comprehensive shipment details including required tracking number and URL, label information, shipment status, estimated pickup and delivery times in Unix milliseconds, estimated provider charges as integer minor units, and optionally package details and a breakdown of charges.
Shipment Object
The Shipment object contains details about a shipment, including tracking information, label, package details, status, estimated times, and charges.
Properties
- trackingNumber (
string, required): Provider tracking number. - trackingUrl (
string, required): Shipment tracking URL. - label (Label, required): Shipment label details.
- package (Package, optional): Package details of the shipment.
- status (Order Statuses, required): Status of the shipment.
- estimatedPickupTime (
integer, required): Provider estimated Pickup Start Time. Unix time in milliseconds (e.g., 1500616800000). - estimatedPickupTimeEnds (
integer, required): Provider estimated Pickup End Time. Unix time in milliseconds (e.g., 1500616800000). - estimatedDeliveryTimeEnds (
integer, required): Provider estimated Delivery End Time. Unix time in milliseconds (e.g., 1500616800000). - amount (
integer, required): The estimated amount that the provider will charge. Amount as integer minor unit (e.g.,1295indicates12.95). - chargeDetails (
array, optional): Provider's breakup of charge, if provided.
Related
Get Order by External ID
The "Get Order by External ID" API allows retrieval of an order using a unique external ID, optionally forcing an update to fetch the latest order details from the provider (if supported), returning the order data with possible error information, and uses HTTP status codes 200, 400, or 404 to indicate success or failure.
Edit Boundary
The "Edit Boundary" API requires a unique integer boundaryId and an array of boundary objects with a mandatory status field set to either "active" or "inactive" to modify a specified boundary, returning a 200 status code on success or 400 on error.
Why Your Customer's Post-Purchase Behavior Is Crucial For Your Business
The article emphasizes the critical importance of managing the post-purchase customer experience—covering everything from order confirmation to delivery and beyond—to meet modern expectations for immediate, personalized, and transparent communication, thereby enhancing customer satisfaction, fostering brand loyalty, and driving repeat sales and long-term business growth.
Create Order
The "Create Order" API request requires parameters such as order type (delivery, in-store pickup, curbside, or shipping), a required unique storeExternalId and orderExternalId, orderValue, deliveryContact, and deliveryAddress (except for pickup types), with optional fields like groupId, tips, pickupTime, dropoffTime, and package details to facilitate accurate delivery estimates and provider selection.
Elevate Your Brand Experience with End-to-End Tracking
The branded post-purchase tracking platform offers customizable email and SMS notifications, integrated end-to-end tracking with real-time visibility, multi-carrier support for split shipments, marketing and upselling opportunities, simple integration options, and feedback collection to enhance customer communication, operational efficiency, and brand loyalty after purchase.
Mastering ETA Delivery Accuracy: Best Practices for Real-Time Delivery Tracking
The article emphasizes the critical importance of real-time ETA accuracy in modern retail delivery, highlighting best practices such as leveraging precise GPS tracking for improved location accuracy and route optimization, and showcases how DeliverySolutions' platform uses advanced algorithms and real-time data integration to provide customers with reliable, up-to-date delivery predictions that enhance customer satisfaction and operational efficiency.