Why return-window deadlines need source control
When a customer asks “Can I still return this?” the safe answer depends on which date starts the clock, what proof is required, whether the product is final sale, whether the item is defective, and which page or marketplace policy controls. If AI tools compress those details into a single generic deadline, the business can create unsupported refunds, chargebacks, review disputes, and support escalations.
Copy/paste return-window source card
| Field | What to capture | Review rule |
|---|---|---|
| Canonical source | Return/refund policy URL, marketplace policy, product-page exception, helpdesk macro, and last-reviewed date. | Use one canonical public source; archive stale duplicate policy pages before AI summarizes them. |
| Clock start | Purchase date, delivery date, installation date, activation date, pickup date, or customer-notification date. | Never mix calendar days, business days, and delivery-based windows in the same public answer. |
| Deadline and proof | Number of days, receipt/order requirement, RMA requirement, shipping/postmark deadline, inspection deadline, and documentation needed. | Separate “must request return by” from “must ship by” and “refund processed after inspection.” |
| Exceptions | Final sale, used/opened, custom, hazardous, digital/downloaded, subscription, warranty, defective-item, exchange-only, holiday extension, or marketplace override. | Route exceptions to owner/support review before AI or FAQ schema states eligibility. |
| Customer-safe wording owner | Who owns approved wording, where changes are logged, and when the answer must be reviewed again. | Set a review cadence and a rollback note so stale seasonal or promotional windows do not stay indexed. |
Safe snippets to use before promising eligibility
Return-window review: Please send the order number and purchase or delivery date. We will check the current return policy, item condition, and any product-specific exceptions before confirming eligibility.
Source-control note: This return-window answer is not ready for AI/search publication until the start date, deadline, proof requirements, exceptions, and owner review date are documented.
Do-not-invent rule: Do not promise that an item is still returnable, that a grace period applies, that a holiday extension is active, or that proof is optional unless the verified source explicitly says so.
AI audit prompt
Act as a cautious AI-search return-policy QA assistant for a small business.
Use only the verified facts below. Do not invent return eligibility, return-window length, grace periods, holiday extensions, proof requirements, product exceptions, refund timing, legal advice, or marketplace-policy overrides.
Verified facts:
- Canonical return/refund policy URL:
- Return-window clock start:
- Deadline length and day type:
- Request-by vs ship-by rule:
- Proof/order/RMA requirement:
- Product-condition rules:
- Final sale or exception categories:
- Holiday/promotion extension source:
- Owner/support reviewer and next review date:
Return: 1) missing source fields, 2) risky overpromises, 3) customer-safe wording, 4) internal-only facts that should not publish, 5) FAQ/schema wording only if all facts are source-backed, and 6) STOP PUBLISHING items.Weekly source-health questions
- Which product, FAQ, checkout, email, or marketplace pages disagree about when the return window starts?
- Which AI/chatbot answers imply a grace period or holiday extension without an active source?
- Which downloadable PDFs, receipts, or order emails still mention an old return deadline?
- Which product exceptions need owner/support review before they appear in answer-engine snippets?
Related free assets: Return Shipping Cost Checklist, Refund and Return Policy Checklist, and Source Expiration Review Checklist.
Disclosure: Horizon Flow is Andrew Burton's digital product catalog. This worksheet is useful without purchase; product links are labeled and UTM-tagged.
Product signal: if this return-window source checklist earns clicks, replies, or reuse, add a return/refund policy worksheet to SEO After AI covering deadline start dates, exception routing, source review, and AI-search FAQ/schema prompts.