Delivery Promises Your Shopify Store Can Actually Keep
An Indian customer adds a product to their cart on your Shopify store and sees: "Delivery by Wednesday." That promise travels through processing delays, courier schedules, pin code routing, and the chance of an RTO (return to origin). Between the promise shown and the package landing on a doorstep sits a chain of decisions that either build trust or destroy it. This guide explains what Shopify actually handles natively, what you need to add, and how to make a delivery promise you can keep.
What does Shopify show customers about delivery?
Shopify's checkout and product page show estimated delivery information when you configure it. According to Shopify's shipping rates documentation, you can "display estimated arrival times at checkout" by configuring your shipping rates and fulfillment settings. The estimate appears as a date range-usually in the format "Delivery by [date]" or "Estimated delivery [date range]"-and it is calculated from two components: processing time (how long before you hand the order to the courier) and transit time (how long the courier takes). Neither component comes pre-filled. Both require your input.
On the product page itself, Shopify themes vary in what they display. Most modern themes show a generic delivery estimate or a link to shipping policy, not a specific date. That specificity lands at checkout, when the customer picks a shipping method and Shopify calculates the promise based on the rate you have configured.
How does Shopify calculate estimated delivery dates?
Shopify uses three pieces of information to build the delivery promise:
- Processing time per product. You set this on each product variant in the admin. It is how many days between order and when the courier picks up. For a D2C clothing brand in Surat handling COD orders, this might be 2-3 days to account for payment confirmation, picking, packing, and label generation. Shopify documentation on product variant setup includes shipping fields where you can set a processing time per item.
- Shipping method. You define shipping rates per origin location and destination zone. Shopify's shipping profile system lets you create different rates for different product types or locations. A flat rate might say "All India Metro: Rs 99, 3 business days." That 3 business days is your second input.
- Delivery profile. This is where the structure lives. Shopify's shipping profiles documentation explains that a profile links products to rates and can set fulfillment time-the window between order and shipment. The profile controls whether this store promises metro areas one delivery window and tier-2 cities a different one. For Indian stores, this is where you split Delhi, Bangalore, Hyderabad rates from pin codes in smaller towns or high-RTO zones.
Shopify adds these numbers: processing time (2 days) + transit time (3 days) = delivery by day 5. That promise appears at checkout.
What information does Shopify show customers after they order?
After checkout, the customer lands on an order confirmation page and receives an email with the order number. Shopify sends a second email when the order is fulfilled (you mark it as shipped in the admin) and it includes a tracking number if you have provided one.
The customer can view their order at any time via the order status page-a URL like `mystore.myshopify.com/orders/[order-number]`. On this page, Shopify shows:
- Order number and date
- Items ordered
- Payment and shipping addresses
- Fulfillment status (unfulfilled, partially fulfilled, fulfilled)
- Tracking information and tracking link if provided
- Estimated delivery date or range, if your shipping rate included it
The estimated delivery date on the status page does not update. If you promised "Delivery by Friday" and the courier hits a backup, the customer still sees "Delivery by Friday." That is not a Shopify limitation; it is how most ecommerce platforms work. The promise is locked at checkout. Real-time updates come from the courier's tracking link, not from Shopify itself.
What do carriers and fulfillment APIs add to the delivery information?
Shopify's native capabilities tell you when to handoff to the courier and when the customer expects delivery. Shopify does not predict if the courier will meet that deadline. That prediction comes from the carrier.
When you integrate with a fulfillment service-such as Shopify's native Fulfillment API or a third party such as Delhivery, Shiprocket or Ecom Express, that service sends back tracking information. According to Shopify's Fulfillment API documentation, tracking data includes the carrier name, tracking number, tracking URL, and current shipment status (in transit, delivered, attempted delivery, etc.). Shopify displays this on the order status page and notifies the customer via email when tracking becomes available.
This flow is what most Indian D2C stores use: Shopify shows the initial estimate, then the courier's API updates the tracking status. The courier does not typically return an updated estimated delivery date into Shopify-that remains the original promise from checkout.
What does Shopify not handle natively, and what needs an app or custom build?
The gap between a realistic promise and a broken one in India often lives here:
Pin code serviceability checks. Shopify's base platform does not check if a pin code is serviceable before showing a rate at checkout. A customer enters a pin code, Shopify looks at the shipping profile, and shows the available rate-even if that pin code is unreliable for returns or is not covered by any courier. Major Indian logistics providers (Delhivery, Shiprocket, Ecomm Express) offer APIs that can check if a pin code is deliverable and at what cost. To use these, you need an app or custom backend that calls the courier API before displaying the shipping rate. Without this, you promise delivery to a pin code that the courier cannot reach, or you over-promise speed in high-RTO zones.
RTO and reverse logistics handling. A return to origin happens when a customer is not available, refuses the order, or the address is incomplete. Shopify does not track or predict RTOs. The courier logs the RTO, the store gets a reduced refund, and the item returns to inventory. Our guide to reducing COD and RTO in Indian Shopify stores covers the operational side of this, but from a delivery promise perspective, a three day promise into a pin code with a poor delivery record is built on an assumption that ignores your own history. A more honest promise acknowledges the zone's reliability. That requires either a custom integration that pulls RTO data into your rates, or manual rate configuration that accounts for high-RTO zones.
Real-time delivery window updates at checkout. Some international D2C brands show a delivery calendar at checkout-pick a date and see the available time window (morning, afternoon, evening). This requires a real-time API call to the courier to check available slots. Shopify's checkout does not do this by default. Building it requires a custom checkout extension or a third-party app that integrates with the courier's slot-booking API. For India, Shiprocket and some hyper-local couriers (Dunzo, Shadowfax) support this, but it needs custom code to surface in Shopify.
Proof of delivery and photo on order status page. International DTC stores sometimes show a photo of the delivered package on the order status page. Indian couriers like Delhivery offer APIs that return proof of delivery images. Shopify does not pull these automatically. To display them, you need a custom frontend that fetches the image from the courier and displays it on the order status page, or an app that does this for you.
How do you set realistic delivery dates so the promise does not cause returns or support tickets?
A delivery promise that is broken creates costs: support tickets, customer refunds, negative reviews, and repeat orders that never happen. A promise that is under-sold leaves money on the table (slower delivery is cheaper, but customers may not accept it). The honest middle is calibrated to your actual performance.
Step 1: Know your processing times by product type. Not all products process at the same speed. Fresh food or made-to-order items need 3-5 days. Pre-packed consumables might be 1-2 days. Apparel with size variants might need 2-3 days due to picking complexity. Set processing times per SKU or per variant, not globally. Shopify lets you do this in the variant edit screen under the Shipping section.
Step 2: Get actual carrier transit times, per zone, from your fulfillment provider. Do not guess. Call Delhivery, Shiprocket, or your chosen carrier and ask: "What is your actual 90th percentile delivery time from my warehouse to Bangalore metro? To tier-2 cities? To high-RTO pin codes?" Use the 90th percentile, not the average. If average is 3 days and some deliveries take 5, show 5. Most carriers publish SLAs (service level agreements) that are guarantees, and that is the number you use at checkout.
Step 3: Create shipping profiles that account for zone difficulty. Do not use one flat rate for "all India." Create separate profiles: metro (3-day SLA), tier-2 city (4-day SLA), tier-3 and high-RTO zones (5-day SLA). Shopify's shipping profiles let you do this by creating different rates for different pin code ranges. Or use an app that calls a carrier API to show zone-specific rates at checkout.
Step 4: Set your processing time conservatively. If your median processing time is 1.5 days, set the product to 2 days in Shopify. This accounts for occasional bottlenecks-payment delays on COD orders, a busy day in the warehouse, or a fulfillment provider pickup delay.
Step 5: Monitor actual delivery performance monthly. Pull fulfillment data from Shopify (via the admin or API) and compare promised dates to actual delivery dates. Track the percentage of orders delivered on time, one day late, and more than one day late. If you consistently beat the promise, tighten it next quarter. If you keep missing it, loosen it or fix the operational cause.
Should you show delivery dates on the product page, or only at checkout?
Product page delivery dates look good but are rarely accurate, because the actual date depends on which warehouse ships, which zone the customer is in, and whether they order today or in 3 days. Most high-performing stores show a generic promise on the product page ("Ships in 2-3 business days from India") and the exact estimate at checkout after the customer enters their address. This avoids the false precision that leads to complaints.
If you want a product page estimate, use a checkout extension or a custom script that looks up the customer's zone (via IP geolocation or manual input) and shows an estimate based on that. Shopify's checkout API supports this via cart and order extensions.
How do you keep the promise honest over time?
Review it against what actually happened. Once a month, compare the dates your store promised with the dates orders were delivered, by zone. A promise that was right in January can be wrong by October, because couriers change routes, volumes rise and your own packing time drifts.
Three habits keep it accurate. Note your real packing time rather than the one you hoped for, including weekends and holidays. Separate metro from smaller cities instead of using one national number. And change the promise when the data says so, rather than when a customer complains.
An honest, slightly longer promise costs you fewer orders than a short one you keep missing. It also costs less in support time, and in the returns that follow a disappointed delivery. If you are reviewing this alongside the rest of your store, our CRO audit guide covers where delivery information sits in the buying decision.
Need a delivery promise audit?
A broken delivery promise is usually caught too late-after customers are complaining. A review of your current setup takes an afternoon and can show where promises are over-optimistic or where pin code serviceability is a blind spot.
Free review. Get in touch or email hello@exactwhy.com with the subject "Delivery promise review", and tell us your store URL and which courier(s) you use. We reply within 4 hours with an audit of what Shopify is showing, what is missing, and what needs fixing before the next peak season. We also send a quick breakdown of which D2C logistics gaps cost you the most in your market.
Implementation and integration. If you want to build pin code checks, set up courier APIs, or improve zone-based delivery estimates, we handle the backend setup and Shopify configuration. When the promise matches what the courier actually does, the questions about where an order is tend to stop arriving.