Delivery and returns pages for e-commerce: what customers need to know

Treat policy pages as part of the buying journey

Delivery and returns pages answer questions that can stop an order. Customers want to know whether you deliver to their area, what it costs, when the item is likely to arrive and what happens if something is wrong. A vague promise to provide excellent service does not answer those questions. Start with the decisions the buyer needs to make before paying.

These pages also support your team. A clear published process gives customer service a consistent reference and helps staff distinguish an ordinary request from an exception. If the website promises one thing while staff follow another process, rewriting the page alone will not solve the problem. The business needs to agree the process first.

Use this guide as an operational content checklist, not a ready-made legal policy. The final wording must reflect your products, markets and applicable requirements. Shopify itself cautions that policy templates do not guarantee compliance. Have the appropriate business and legal review where needed, especially when selling across borders or handling products with special conditions. Clear language and correct obligations need to work together.

Map the actual delivery process

List what happens between an order being accepted and a customer receiving it. Include payment confirmation, stock checks, preparation, packing, courier collection and transit. Identify which steps your team controls and which depend on a fulfillment partner. This makes it easier to explain the timeline accurately rather than compressing several different stages into one optimistic number.

Record the differences between product groups. Ready-stock goods, personalized products and items supplied from another location may not share the same preparation time. If a basket contains mixed items, decide whether they ship together or separately. The customer needs to understand that arrangement before the order, and staff need to know how it is recorded.

Check the published process with the people doing the work. A marketing estimate can overlook collection days, production capacity or packing requirements. Use actual operating evidence when setting a promise and revisit it when the process changes. A delivery page should describe the service the business can reliably offer, rather than the service it hopes to offer after a future operational improvement.

Explain coverage, charges and exceptions

State where you deliver and how customers can check a location that is unclear. For a Kenya-based store, an area name that seems obvious to the team may be ambiguous to a shopper. Use practical coverage descriptions and make sure the checkout applies the same rules. If a destination needs a manual quote, provide the contact route before the customer attempts payment.

Explain how delivery charges are calculated. The relevant factors might include destination, weight, product type or order value. You do not need to expose every internal courier calculation, but customers should understand what determines the final charge. If a free-delivery offer has conditions, place those conditions near the offer and keep them consistent with checkout.

List meaningful exceptions in plain language. Oversized, fragile or separately fulfilled items may need a different arrangement. Avoid hiding an exception only in a long paragraph after a general fast-delivery headline. Our inventory and SKU guide explains why product-level operational details should be recorded in the catalog, making it easier to keep delivery messages accurate as the range grows.

Distinguish preparation time from transit time

Preparation time is the period before the parcel is handed to the carrier. Transit time begins after the carrier receives it. A customer cares about the combined expectation, so make the distinction understandable without requiring them to calculate from several scattered pages. Shopify's shipping guidance also distinguishes transit time from order processing time.

Use time language carefully. If the business quotes working days, explain relevant operating days and any genuine order cut-off conditions. Avoid publishing a precise arrival guarantee unless the business can support that promise. An estimate can still be clear when it explains the expected stages and what may affect them. Keep exceptional delays separate from the normal process so the page remains useful.

A hypothetical example can help the team test its wording. If an item needs two working days of preparation and a courier estimate is one to three working days, saying delivery takes one to three days omits a material part of the journey. Those numbers are illustrative, not a BrandNerds or courier promise. The content should use the business's verified current timeline and explain product-specific differences where they matter.

Define the customer contact and tracking process

Tell customers what communication they will receive after ordering. Explain whether the business sends an order acknowledgement, payment confirmation, dispatch update or tracking information. Use the names your systems actually use so a shopper can recognize the message. Do not promise automatic tracking if staff send updates manually or the selected service does not provide it.

Give a clear contact route for a delivery problem. State what information helps the team investigate, such as the order number and contact details used at checkout. Avoid asking customers to post private information publicly. Internally, decide who checks the order, contacts the carrier and updates the customer. The page should describe a process the team is prepared to follow.

Include guidance for an incorrect address, missed delivery or a parcel reported as delivered but not received. The exact response depends on your business and provider terms, so do not copy another store's procedure without review. What matters is that the customer knows how to raise the issue and staff know how to investigate it. Keep the tone calm and practical rather than making the page sound like a list of accusations.

Describe returns through a clear sequence

A useful returns page explains how a customer starts a request, what information is needed and what happens next. Separate the request process from the decision about eligibility. Customers should not need to guess whether to send an item back without instructions, especially when a return address differs from the public business address.

Identify the product conditions and exceptions that actually apply, and have them reviewed against relevant requirements. Do not assume every category can use the same blanket rule. Personalized, perishable or hygiene-sensitive items may need specific treatment, but the final wording should be accurate for the business and market rather than copied from a generic template.

Explain inspection and communication. If the team needs photographs to understand a problem, say what is useful without demanding unnecessary personal information. If an item must be physically inspected, describe that stage and how the outcome is communicated. A clear process can reduce repeated messages because the customer understands the next step, while still leaving room to handle unusual cases appropriately.

Separate returns, exchanges, cancellations and refunds

These terms describe different actions. A return concerns an item coming back. An exchange concerns replacing an item. A cancellation concerns stopping an order, and a refund concerns money being returned. They can overlap, but treating them as one process can create confusing instructions for customers and staff.

Explain when a customer should contact the business for each situation. A request before production starts may need a different internal path from a problem discovered after delivery. If the business offers exchanges, clarify how stock availability, delivery arrangements and any approved price difference are handled. Avoid promising an exchange process that the fulfillment team cannot track accurately.

For refunds, use the payment provider's supported process and explain the relevant stages without inventing a universal timeline. The business approving a refund and the customer seeing funds are not always the same event. Confirm the provider terms before publishing a timeframe. Keep staff instructions aligned with the payment record so an ordinary customer-service message does not become mistaken proof that a financial action has completed.

Publish, test and keep the pages current

Make the pages easy to find from the footer and relevant buying areas. Put essential product-specific information near the product and link to the full policy for detail. Customers should not discover a significant restriction only after checkout. Check the links on a phone and confirm that the checkout points to the current pages.

Review consistency across banners, product descriptions, collection pages, checkout and order messages. A free-delivery promotion or a change of courier can create contradictions if only one page is updated. Assign a named role to approve policy changes and keep a dated record of significant revisions. The source of truth should be clear to the team.

Before launch, test a standard order and several exceptions against the written pages. Can staff explain what happens next using the published information? Does the checkout calculate the promised rate? Can a customer find the return contact route without searching the entire site? BrandNerds can help organize the store content and implementation, while the checkout review guide helps connect these pages to a clearer purchase journey.

Include the packing and support teams in sign-off. Their practical questions often reveal a missing exception before that gap becomes a repeated customer problem.