How delivery time is built
The promise on the product page is made of two separate parts that shops often confuse. Handling time is the period between the order arriving and the parcel leaving you: picking, packing, payment checks, and any day the warehouse is closed. Transit time is the courier’s part, and it varies by destination far more than by service.
Add them together, apply the cut-off rule — an order placed after the day’s last collection starts counting from the next working day — and you have the window the customer should be shown. Most shops express it as a range rather than a single date, because the transit half is not fully under their control.
In Nepal the two halves behave very differently. Handling is usually consistent; transit is not, once an order leaves the Kathmandu valley for a district that a courier serves less often. A single national promise hides that variation, and the orders that break it are always the distant ones.
Why delivery time matters
It is a conversion factor before it is an operations metric. A visitor deciding between two shops with the same product and similar prices will usually choose the one that tells them when the parcel arrives, because certainty is worth more to a buyer than speed. A page that says nothing invites the visitor to assume the worst or to leave and check a competitor.
Afterwards it becomes a retention factor. A missed promise generates a support message, sometimes a refund, and a customer who does not come back — which quietly raises the cost of every future sale, because acquisition has to replace them. It also shows up in reviews, where late delivery is one of the most frequently cited complaints in any shop’s ratings.
Where delivery time goes wrong
Optimism is the main failure. Shops quote the best case they have ever achieved and then miss it routinely, which is worse than quoting a longer window and beating it. Second is silence: no estimate on the product page, only a vague line buried in a shipping policy that nobody opens.
The third is inconsistency across surfaces. The product page says one thing, the feed’s delivery attributes say another, the confirmation email says a third, and the courier’s tracking page says a fourth. Google shows delivery estimates in Shopping results using what you declare, so a declared window you do not keep is both a customer problem and a feed problem.
Getting it right
Measure what actually happens before you promise anything: record order time, dispatch time and delivery time for a real period, then set the promise at a level you meet comfortably rather than at your best day. Split the promise by region if the transit half genuinely differs, and state the cut-off in plain words.
Show the estimate where the decision is made — on the product page and in the cart, not only in a policy page — and keep the same numbers in your feed’s delivery attributes as part of routine Merchant Center feed management. When something slips, say so before the customer asks. A proactive message costs one email; a missed date discovered by the buyer costs the order and often the repeat purchase.
