Use the template when shipping or return rules change more often than the team can reliably update every public and channel-facing surface from memory.
Ecommerce template
Shipping and Returns Source of Truth Template
Use one policy record to keep storefront, checkout, support, Merchant Center, and structured data changes aligned.
Quick answer
A shipping and returns source of truth should record the standard policy, every exception group, the affected products, the owner, the live page location, channel settings, and the next review date.
Topic, affected product or campaign, current issue, and the decision the team needs to make
A downloadable CSV with columns for policy rule, product scope, public copy, channel setting, owner, status, and review date.
Why this matters in a real store
Shipping and Returns Source of Truth Template matters because ecommerce growth work usually breaks down in the handoff between a number, a platform warning, a campaign idea, and the person who has to make the next decision. A store team may know something is wrong, but still lose time because the issue is not written in a way that connects the symptom to a next action.
Use this page as a practical translation layer. The goal is to slow down the first reaction, name the business risk, and give the team enough context to decide whether the next move is a calculation, a feed change, a campaign QA step, or a page update. The tables and checklists are there to make the work repeatable, but the judgment comes from understanding why the issue appears in the first place.
Columns to keep
| Column | Purpose | Example |
|---|---|---|
| policy_rule | Names the customer promise | 30-day return for unused items |
| product_scope | Defines affected products | All full-price bedding |
| exception_type | Separates standard and special cases | Final sale |
| visible_copy_location | Points to the page or checkout surface | Product page return tab |
| channel_setting | Records Merchant Center or marketplace representation | Return policy configured in Merchant Center |
| owner | Makes follow-through clear | Operations lead |
| review_date | Prevents stale exceptions | 2026-07-15 |
How to use the CSV
Start with a small number of rows. If the team cannot explain the standard rule in one row, the public policy is probably too ambiguous to operationalize cleanly. Once the standard row is clear, add exception rows for product groups that behave differently.
The template is most useful before a promotion or policy change goes live. It gives the feed owner, storefront owner, support owner, and operations owner the same record to work from.
Methodology and limits
Create one row for the standard rule, then one row per exception group. Use the row to drive page copy, checkout QA, support notes, Merchant Center settings, and structured data review.
The template does not decide the policy. It helps the team keep an approved policy consistently represented.
Reusable download
Use the related CSV as a working file for the calculation, checklist, or planning step covered on this page.
Common questions
Should the template include screenshots?
The CSV should link to screenshots or QA notes when a policy launch is high risk, but the core record should stay easy to scan.
How granular should exception rows be?
Use one row per group that has the same customer promise. Split rows when return window, shipping cost, destination, or support handling differs.
Can this replace a help-center article?
No. It is an operating record for the team. The customer still needs clear public policy copy.