Shipping and Returns Pages: Organize the Right Information

A shipping or returns page should help a buyer answer a concrete question: can this order reach me under acceptable conditions, and what happens if something goes wrong? Putting every rule in a long footer document makes that answer harder to find. Repeating the entire document on every product page creates another problem: copies drift apart.

A more manageable approach is to maintain complete policies in clear destinations, show short relevant summaries along the buying path, and identify exceptions where they matter. The structure below is an editorial recommendation for organizing verified business terms. It does not supply those terms or establish legal compliance.

Give each policy a clear job

Use the shipping page to explain destinations, available services, how charges are determined, timing assumptions and the process for delivery problems. Use the returns page to explain eligibility, request steps, applicable windows, condition requirements, fees and what happens after a request is accepted.

These can be two pages or clearly labeled sections within one destination. The useful test is whether a customer can reach the right answer without reading unrelated material. A link labeled “Shipping information” should land near shipping information, rather than at the top of a general terms document.

Google recommends placing the business’s shipping-policy information on a single page, with organization-level ShippingService markup where appropriate. Its return-policy guidance makes a similar recommendation for MerchantReturnPolicy. These are structured-data recommendations, not requirements to use a particular visual layout. See Google’s shipping-policy and return-policy documentation.

Separate preparation from carrier travel

“Delivery takes five days” leaves several questions unanswered. Does the period begin when payment arrives, artwork is approved, production finishes or the carrier receives the parcel? Does it include weekends? Does it apply to the destination the buyer selected?

Build the explanation around the actual sequence:

• What must happen before preparation or production can start?
• What preparation or handling period can the business support?
• When does the carrier’s transit estimate begin?
• Which destination, service and business-day assumptions apply?

Google’s shipping schema distinguishes handling information from transit time, including conditions related to destinations and order characteristics. That distinction is useful for the visible explanation too. A supported estimate should remain an estimate; do not turn it into a guaranteed arrival date. Our custom-product fulfillment guide explains the underlying stages.

Put exceptions beside the affected choice

A business-wide rule may not describe every product. A particular destination might require a different service, while a personalized item might have different return conditions from a standard item. Record the actual exception and its scope before writing a summary.

Consider this hypothetical architecture:

Information	Complete explanation	Relevant buying-path summary
Standard shipping process	Shipping policy	Link near the delivery estimate
Destination restriction	Shipping policy’s destination section	Notice when the affected destination is considered
Product-specific return exception	Clearly identified return-policy section	Notice on that product before the buying decision
Artwork approval dependency	Product or ordering instructions	Explanation beside the customization step

Google supports product-specific return information under an Offer when a product has a nonstandard policy, although offer-level supported fields are a subset of the organization-level fields. The return-policy documentation explains that distinction. Public wording and any markup must reflect the approved exception; a schema example is never a ready-made commercial policy.

Write the return route as a sequence

A statement such as “contact us for returns” can leave customers unsure what to send or what happens next. Explain the request channel, information needed to identify the order, applicable conditions and the next step. State who arranges a label or pays return shipping only when the business has confirmed that responsibility.

Keep the return window’s starting event clear. Distinguish a request deadline from any separate period for sending an accepted return. Where the business treats damaged or incorrect goods differently from change-of-mind requests, explain the verified routes without suggesting that a general exclusion removes applicable consumer rights.

For example, a hypothetical customer receives the wrong apparel size. The page should help them distinguish “the item differs from the order” from “I ordered this size but want another.” The business needs to decide and validate the rules for each situation before the writer can describe them.

Check every place that repeats the promise

The website may not be the only place Google receives shipping or return information. Google’s documentation describes precedence among account settings, Merchant Center or Search Console settings, product-level markup and organization-level markup. A stronger configuration can override the website’s organization-level policy data. Review the relevant shipping and returns precedence guidance.

Keep a small register with the rule, approved wording, affected products or regions, source configuration and review owner. When a fee or condition changes, use that register to find the affected summaries. Our product-data consistency guide provides a broader comparison method.

Test one realistic customer question

Before publishing, follow one actual scenario from the product page to the appropriate policy section. Check that the destination is covered, the estimate’s starting point is understandable, any exception is visible, and the issue-reporting route works on a phone.

For a quote-led project, explain which shipping details the quote will confirm instead of inventing fixed checkout charges. Correct policy structure and markup can improve clarity and eligibility for search features; they do not guarantee rankings or a rich result. If you are planning custom merchandise, send the product, quantity and destination so the project-specific delivery details can be discussed.