If you came here wondering whether Blue Dart or Delhivery is faster, the honest answer is that no article can tell you: transit time depends on the pickup and delivery pincodes, the service level, the day and the carrier's current performance, and it changes. The better question for a business with an online store is how your website should find out the real delivery time for each customer's pincode and show it before they pay. That is a website-building problem, and it is solved by connecting your store to courier rate and serviceability data, not by picking a winner from a comparison table. This guide explains how to build delivery estimates, courier selection and order tracking into a store, what the integration involves, and what to ask your developer.
We have rewritten this post. An earlier version compared the two couriers using rate and on-time figures that we could not source, and a comparison of carriers is not what our readers need from a web development company. The version below sticks to what a website can and should do. It is written for owners of Indian online stores and the people commissioning their sites.
Why a courier comparison does not help your website
Courier performance is local and time-dependent. A carrier that is quick between two metro pincodes may be slower to a smaller town, and the reverse can be true for another. Rates depend on your contract, volumes, parcel weight and dimensions, cash-on-delivery handling and fuel or surcharge changes. Any table that gives one transit time or one per-kg rate for a whole carrier is a generalisation that your customer's actual parcel will not follow.
What your store needs instead is data at the level of a single order: from your pickup pincode to this customer's pincode, with this parcel weight, which services are available, what will they cost and what delivery window do they promise? Couriers and shipping aggregators expose this through programming interfaces, and a store can call them at checkout.
What a good store shows, and when
| Moment | What the customer should see | Where the data comes from |
|---|---|---|
| Product page | A pincode box that returns "delivery available" or "not available" and an estimated delivery window | Courier or aggregator serviceability and estimate service |
| Cart | The delivery fee, or a clear statement that it is free above a threshold you set | Your shipping rules, or live rates |
| Checkout | The shipping options available for the address entered, with price and estimated date | Live rate and serviceability lookup, or your own rate table |
| Order confirmation | The expected delivery window and what happens next | Stored from the checkout choice |
| After dispatch | Tracking link and status updates by email, SMS or WhatsApp | Courier tracking events, received by your store |
| Delay or failure | A clear message and a way to reach you | Courier status events and your own support process |
Not every store needs every row. A small store that ships a few products to a limited area can use a simple fixed-rate table and a pincode list. A store with many products, weights and destinations benefits from live lookups.
Three ways to connect your store to couriers
1. Direct integration with one courier
Your developer connects the store to a single courier's interface. This gives you the most direct control and is reasonable if you use one carrier for nearly everything. The drawbacks are that every additional carrier means another integration, and that you depend on that carrier's interface staying stable. Each courier documents its own interface and access process, and access usually requires an account with them. Ask the courier for the current documentation rather than relying on a third-party summary.
2. A shipping aggregator
An aggregator is a service that connects you to several couriers behind one interface, so the store integrates once and can offer different carriers. Many Shopify and WooCommerce plugins and apps connect to such services. Aggregators differ in which carriers they cover, how they price, how they handle cash on delivery remittance and what support they offer. We do not rank them here; evaluate them using your own parcels, as described below.
3. A rate table you maintain yourself
For stores with simple needs, the store can use fixed rules, such as flat rates by region or weight band and a manual list of serviceable pincodes. It is the cheapest to build and the easiest to understand, but it goes stale and cannot show real delivery dates. It suits a narrow range of products and destinations.
| Approach | Good for | Watch out for |
|---|---|---|
| Direct courier integration | One main carrier, steady volumes | Extra work for each new carrier; changes to the carrier's interface |
| Aggregator | Several carriers, comparing options at checkout | Your dependence on the aggregator; read its terms on data, fees and support |
| Own rate table | Small catalogue, limited destinations | Rates and pincode lists going out of date |
Choosing between these is a decision about your business as much as your technology. If you are weighing it, our service page on logistics integration describes how we approach it, and the page on checkout systems covers the wider checkout build.
Pincode checks on the product page
The pincode box is one of the most useful and most commonly poorly built elements of an Indian store. A good one:
- Accepts a six-digit pincode and validates it immediately.
- Returns a result quickly, ideally without reloading the page.
- Shows a delivery window, not a precise promise you cannot control, such as "estimated delivery between X and Y".
- Says clearly when delivery is unavailable, and when cash on delivery is unavailable if you offer it.
- Remembers the pincode for the visit, so the cart and checkout do not ask again.
- Fails gracefully. If the courier's service does not respond, the page should show a neutral message and let the customer continue, not break the product page.
Performance matters. Calling an external service on every product page view can slow your store if done carelessly. A developer can cache results for common pincode and product-weight combinations for a short time and load the check only after the visitor interacts with it. See our guide to store speed and Core Web Vitals for why this matters for both customers and search.
Showing honest delivery estimates
An estimate is a promise in the customer's mind, even if your wording is cautious. Build it from three parts: your own processing time (the time between order and handover to the courier), the courier's transit estimate for that route, and a buffer. Show a date range rather than a single date. Make sure the processing time reflects reality on busy days, and let the store adjust it during sales or festival periods. Our article on the festival campaign calendar is a reminder that peak periods are when estimates fail.
State clearly on the product page and in your policy pages what the estimate does and does not cover. If a courier's live estimate is not available, use a conservative default and label it as an estimate.
Checkout: showing shipping options without confusing people
Show the delivery options only after the address or pincode is known. List each option with its name, price and expected window, and pre-select the one you want most customers to choose, which is usually the cheapest reasonable option. If free shipping applies above a basket value, show how much more the customer must add, as this is a recognised way to raise order value; our article on upsells, cross-sells and bundles covers this.
Keep the delivery fee visible from the cart onwards. Customers who meet an unexpected fee at the last step may leave. If you offer cash on delivery, show any extra fee at the same stage rather than after the order is placed. Our guide to checkout forms and guest checkout shows what else to simplify.
Tracking: what the store should do after dispatch
Couriers send status updates through tracking pages and, with proper integration, through notifications to your system. A well-built store:
- Records the tracking number and courier against each order when it is dispatched.
- Shows a tracking link in the customer's account and in the dispatch email. Our guide to order history and reorder in the customer account describes the account area.
- Receives status changes from the courier or aggregator where supported, and updates the order status.
- Sends useful messages at dispatch, out for delivery and delivered, through email and, if you use it, WhatsApp. See transactional emails and our page on WhatsApp Business API for commerce.
- Flags exceptions such as failed delivery attempts or returns to origin, so your team can contact the customer before they contact you.
- Keeps its own record of the key events, so that you can resolve disputes even if the courier's tracking page changes.
Keep the customer's phone number and address accurate and validated at checkout. Many failed deliveries begin with a mistyped pincode or an unreachable number.
How to evaluate couriers using your own data
Because no published comparison will match your parcels, test them yourself.
- Choose a sample. Take your last 200 or so orders, or as many as you have, across your main destinations, including smaller towns and a few remote pincodes.
- Collect quotes in writing. Ask each courier or aggregator for rates for those routes, weights and payment types, including cash on delivery and return charges.
- Run a pilot. Split a small share of real orders between two options for a few weeks.
- Record what you can measure. Pickup on time, delivery date versus estimate, failed attempts, damaged or lost parcels, return handling, how quickly support answered, and the speed and accuracy of remittance for cash-on-delivery orders.
- Decide using your numbers. Choose by route if necessary. Many stores use different carriers for different regions or weight bands, which a store integrated with several carriers can handle automatically with rules.
Keep in mind that the choice of carrier is an operations decision. This post does not rate carriers; it describes how the website supports whichever decision you make.
Reverse flows: returns and failed deliveries on the website
A store should provide a clear returns request flow: the customer selects an order and reason, the store creates a return request, and your team approves it and arranges pickup or gives instructions. The policy text, time limits and conditions are for you to decide and to publish clearly in plain language, in line with consumer rules that apply to you. Our article on consumer protection rules for ecommerce is a starting point. Technically, the store should link each return to the original order and update the order status so that finance and support see the same picture.
What to ask a developer or agency
- Which carriers or aggregators will you integrate, and why?
- Will the pincode check use live data or a maintained list, and how are failures handled?
- How will rates be calculated: live, rule-based or a table?
- How are delivery estimates built, and can I change the processing time during busy periods?
- How will tracking updates reach customers, and through which channels?
- What happens if the courier's service is down during checkout?
- How is cash-on-delivery handled, including fees and order confirmation checks?
- Who holds the carrier accounts and credentials, and who can change them?
- What testing will you do with real pincodes before launch? See our pre-launch testing checklist.
- What does ongoing maintenance of this integration cost, and what happens if a carrier changes its interface?
Common mistakes
- Showing a precise delivery date that the process cannot keep.
- Hiding delivery charges until the last step.
- Letting a slow external call delay the whole product page.
- Integrating one carrier in a way that makes a second one expensive to add.
- Putting courier account credentials in the hands of a single person or developer.
- Forgetting to update processing time and estimates during sale periods.
- Not recording tracking numbers against orders, which forces staff to search manually.
- Copying a comparison table from another website, including figures that were never verified.
Frequently Asked Questions
Which is faster, Blue Dart or Delhivery?
It depends on the route, the service level and current conditions, so no general answer is reliable. Test both on your own pincodes with real parcels, and have your store request a live estimate for each customer's address.
How do I show estimated delivery dates on my online store?
Add a pincode check on the product page that calls your courier's or aggregator's serviceability and estimate service, combine it with your own processing time, and show a date range. Cache results briefly so the page stays fast.
Can my website offer more than one courier at checkout?
Yes, through an aggregator or by integrating several carriers directly. The store requests options for the customer's address and weight and shows them with price and expected window. Rules can also choose a carrier automatically by region or weight.
How do customers track their orders on my website?
Store the courier and tracking number against each order, show a tracking link in the account and dispatch message, and, where the carrier supports it, receive status updates so the order status changes automatically.
Do I need a custom build for courier integration?
Not always. Shopify and WooCommerce have plugins and apps that connect to couriers and aggregators. A custom build or custom connector makes sense when your rules are unusual, your volumes are high, or you want everything inside your own system.
Where to Start
List your last month's orders by destination pincode and note how many reached small towns. That tells you whether a simple rate table is enough or whether live lookups would earn their cost. Then ask your developer the questions in the list above before any work begins.
Govindani Infotech is a website design and development company in Pune, at Landmark Plaza, Satara Road, Parvati Paytha. We build online stores and their integrations; see our ecommerce development service, or contact us or call 092019 58274.
Sources: