How to write a delivery and returns page Indian shoppers trust

A delivery and returns page is most useful when it answers the awkward questions before checkout: where do you deliver, when should a customer expect an update, what if a parcel arrives damaged, and how does a return actually start? For a small Indian business, accuracy matters more than impressive-sounding promises. Write the page from the steps your team can consistently follow.

Separate processing from delivery

Explain the difference between the time your team needs to prepare an order and the carrier’s transit time. State which locations you currently serve and how a shopper can check whether their PIN code is included. If delivery times vary by product, destination or courier, say so and describe how the estimate is shown before payment. Do not call an estimate a guarantee unless your business can honour it.

Be precise about charges. Show whether delivery fees are calculated at checkout, vary by location or depend on order size, and identify any conditions that affect them. Mention how tracking is shared and what a customer should do if an update has not appeared. If the business sometimes ships in multiple parcels, explain that one order can have more than one tracking update. Keep the information consistent across product pages, checkout, confirmation messages and the policy page.

Make the return rules easy to scan

Use headings or a small table to explain which products are eligible, the allowed time window, the condition required, and who pays for return shipping. If a product is made to order, perishable, customised or otherwise treated differently, describe that only when it reflects your actual policy and applicable requirements. Avoid blanket wording such as “no returns under any circumstances” without checking the rules that apply to your business.

Spell out the steps: how to contact support, what order information is needed, whether the customer should wait for approval before sending anything, and how to package an item. For a parcel that arrives damaged or incorrect, tell the customer how soon to notify you and what evidence helps your team investigate. Ask only for information needed to resolve the issue; do not request passwords or payment-card details.

Explain what happens next

Tell shoppers how you confirm a request, how they can check its status, and what happens after a return is accepted. Distinguish the inspection step from the refund or replacement step. If the refund goes through the original payment method, bank processing time may vary; state your own processing step separately rather than promising a date you cannot control. Give a monitored support channel and a realistic response window only if staff can meet it.

Before publishing, ask someone outside the business to find the delivery estimate and start a sample return from a phone. Check that every promise matches your actual order workflow, then review the page whenever your delivery area or process changes. If you are commissioning a new store or revising its policy pages, compare website building companies in India against the same written scope for checkout, policy content and ongoing updates. Do not hand over policy wording without checking it against your real operations and current requirements.

Disclosure: I work with MGTech Labs. This is practical writing guidance, not legal advice; confirm the policy against the rules that apply to your business.