A useful policy states what the store can actually do about returns, delivery, data and support. Start with one promise already visible to a buyer, find its operating evidence, and compare the product page, checkout, email, ads and support. Keep the promise, evidence, version, repair and any wording that must remain paused.
16 parts · 7 checkpoints
Show all 16 parts
- 01Read policy evidence through one product
- 02Find the first mismatch across five surfaces
- 03Separate facts you can record from boundaries to verify, has a checkpoint
- 04Connect five page types with real admin evidence
- 05Scan shipping, returns and reviews separately
- 06Follow one promise through four surfaces
- 07Rewrite vague templates into specific rules
- 08Pause the wrong claim before repairing the chain
- 09Give six evidence areas a responsible reviewer
- 10Keep a reconciliation record for each change
- 11Read the rule from four perspectives
- 12Separate return, delivery and duty responsibilities
- 13Connect privacy copy with actual tools and choices, has a checkpoint
- 14Review product claims and market scope separately
- 15Route the next action to the weakest evidence, has a checkpoint
- 16Leave policy promises and review records
Key point Verify the promise before polishing the template
A complete-looking policy may still be wrong for the product or market. Statutory consumer rights, an extra store return offer, a platform template and actual execution are separate layers. Completing this lesson’s record does not establish legal compliance or publication.
Tumbler store
- Capacity (oz)
- 20
- First-batch SKUs
- 2
Consider an English-language store preparing to sell a 20oz tumbler to US buyers in USD. Its first two SKUs have standard and straw lids. The page promises leak resistance, 30-day worry-free returns and worldwide shipping, while a Meta Pixel and email-discount popup are installed. These are inputs to investigate, not evidence of entity eligibility, lawful processing or completed earlier lessons. The later Canadian-English, non-EU placeholder is a separate scope; do not combine the markets into one conclusion.
A SKU is an inventory code for a specific product or variant; PDP means product detail page. The standard and straw lids are separate SKUs, so check each return or delivery promise against the relevant variant. Sharing a tumbler design does not establish identical conditions.
Continues from: Shopify Product Listings: Pages, Variants, and Mobile Add-to-Cart
Connect product-page copy with the rules after purchase
A product-page review should leave facts for one primary SKU, page evidence, a mobile path and an action to pause. Use that record if it exists; otherwise begin with this tumbler. Understanding a product and reaching add-to-cart proves nothing about whether refunds, shipping, duties, privacy or support can honor the words. Use this lesson when a public promise is the earliest unresolved gap.
Questions to work through
Read policy evidence through one product
Policies explain the store’s public rules for buying, using its services and resolving problems. They shape buyer expectations and can be checked by support or during disputes. They help a team use consistent rules, without guaranteeing ad approval, dispute outcomes or conversions. Define four evidence terms before deciding which page to edit.
Four evidence terms
- Promise version
The current wording of the same promise across surfaces, such as PDP saying 7-day delivery while policy says delivery within 15 days.
Where you see it You will see it on PDPs, checkout, Shipping Policy, Refund Policy, order emails, support snippets, and ad creative.If misread If promise versions conflict, buyers, support, payment disputes, and ad review read different rules.- Admin evidence
Admin records that prove the policy promise is real, such as shipping zones, return rules, order email samples, support snippets, and page screenshots.
Where you see it Common surfaces include Shopify Settings, Markets, Shipping and delivery, Notifications, Customer events, order records, and support tools.If misread Without admin evidence, the policy looks complete, but refunds, duties, privacy, or dispute issues become hard to prove later.- Consent surface
The place where a buyer sees and chooses data use, such as cookie banner, signup form, checkout checkbox, unsubscribe link, and privacy request path.
Where you see it You will see it in Customer Privacy, Customer events, cookie banner, email footer, signup popup, and support privacy replies.If misread If consent surfaces and privacy policy disagree, pixels, email signup, and support privacy requests become weak points.- Policy exception
Not every order can use the same policy line. Custom items, opened goods, remote addresses, clearance products, regulated goods, or different markets may need exceptions.
Where you see it Common surfaces include Refund Policy, Shipping Policy, PDP FAQ, order email, support replies, and return forms.If misread If exceptions appear too late, buyers assume the broadest promise, and support, disputes, and returns must repair it after the fact.
If the PDP says 7 days and the policy says 15, you have a promise-version conflict. A shipping setting supports only part of the explanation: product, address, stock and the rule at purchase also matter. A policy exception is not permission for a merchant to remove statutory rights.
Conflict — Refund Policy excludes opened straw lids, Shipping Policy says duties are buyer responsibility, Privacy Policy does not explain pixel or email use, and ads turn leak-resistant into an absolute guarantee.
Repair — Pause strong claims like worry-free returns, no extra fees, and leakproof guarantee, then sync PDP, policies, checkout message, order email, ad creative, and support snippets.
Evidence — Keep the SKU, conflict sentence, first screenshot, surfaces to fix this week, pause line, review window, and next route in the policy review record.
Excluding opened straw lids, engraved products or final-sale goods is a proposal in this store’s draft, not this lesson’s legal conclusion. Check market and product applicability, then distinguish a voluntary return offer from statutory rights. Keep what was public, when it changed and what the buyer could read at purchase.
Find the first mismatch across five surfaces
A buyer usually sees the product page before the full policy. If the page offers carefree returns and support first mentions an exclusion after a request, the conflict already exists. Choose the surface closest to the problem, capture its exact wording and find the evidence behind it. Do not begin by rewriting every template.
Choose the surface carrying the promise
- What to check
- Check price, shipping, returns, effect, material, limits, and use case.
- Common conflict
- Product page says 5-8 days, while Shipping Policy says 15-20 days.
- Evidence
- Keep screenshots of product hero, shipping/return block, and matching policy paragraphs.
- What to check
- Check shipping cost, duties/taxes, regions, discounts, payment methods, and unshippable areas before purchase.
- Common conflict
- Policy says duties are buyer responsibility, but checkout gives no signal.
- Evidence
- Use a test order to capture cart, pre-checkout costs, and region limits.
- What to check
- Check whether privacy, refund, terms, shipping, and contact are real, findable, and non-conflicting.
- Common conflict
- Refund says 30-day returns, support says custom goods are never returnable, but product page never warns.
- Evidence
- Policy URLs, update date, review lead, quotable clauses, and mobile footer access.
- What to check
- Check whether signup, discount, abandonment, and post-purchase emails explain purpose, opt-out, and real promises.
- Common conflict
- Popup only says get a discount, but silently enters the buyer into multiple marketing flows.
- Evidence
- Signup form, unsubscribe link, email footer, and matching privacy paragraph.
- What to check
- Check whether support uses the same public rule for refunds, lost packages, duties, and cancellations.
- Common conflict
- Policy says one thing, while support improvises a different promise to calm the customer.
- Evidence
- Put frequent issues, policy clauses, and reply snippets into one support standard sheet.
Selection locates a question. Record its line, URL or screenshot and first evidence, then compare the other surfaces. Fix the misleading summary buyers encounter first and sync the rest. One screenshot does not establish the whole policy.
Separate facts you can record from boundaries to verify
Name the market, product and promise in this review. Confirmed handling facts, return entry points and tool inventories can be recorded directly. Unresolved consumer rights, consent, safety or entity responsibility need a documented question and suitable professional review. A “subject to local law” footer cannot do that work.
Choose this review’s policy category
- Facts you can record
- Write handling time, delivery range, return entry point, item condition, costs, and support path that the store can actually carry out. A template is not the fact source.
- Verify
- Verify against the current selling market, product type, custom or non-returnable exceptions, carrier reality, and checkout display. Do not carry one market’s window or exception into every market.
- Professional-review trigger
- For cross-border returns, exclusions that may conflict with consumer law, subscriptions, or higher-risk categories, record the question and seek suitable professional review.
- Pause condition
- When the return window, custom exception, or duty responsibility is not verified, pause absolute public claims such as “worry-free returns” or “zero-risk purchase.”
- Facts you can record
- Write the forms, email, pixels, analytics, or support tools actually used, plus a findable unsubscribe and privacy-contact path.
- Verify
- Verify enabled apps, third-party scripts, regional settings, banners, forms, and notifications. Do not read only the privacy page and ignore the real data flow.
- Professional-review trigger
- For multiple markets, sensitive data, unresolved consent paths, or data-request handling, keep evidence and route it to suitable professional review.
- Pause condition
- When it is unclear what a pixel, form, or automation collects or where it goes, pause new traffic or marketing claims through that touchpoint.
- Facts you can record
- Write the public support entry point, actual handling path, current brand or store identity information, and communication promises the team can keep.
- Verify
- Verify against the entity, market language, footer access, order emails, and checkout-adjacent reality. Having a translation does not mean content is suitable for every market.
- Professional-review trigger
- For entity disclosures, mandatory information in different markets, dispute terms, or responsibility language operations cannot confirm, log an escalation and seek suitable review.
- Pause condition
- When public contact, entity wording, or localized versions still conflict, do not treat that market as ready for external promises.
- Facts you can record
- Write only product features, limits, and use cases supported by facts, instructions, testing, authorization, or traceable records.
- Verify
- Verify the current SKU, packaging, page, reviews or creator assets, and target-market or category boundary. Do not reuse old assets or reviews from a different product.
- Professional-review trigger
- For children, cosmetics, health-adjacent, food-contact, electronics, safety-related goods, or strong performance claims, record the evidence gap and seek suitable professional review first.
- Pause condition
- Without checkable evidence or a clear market and category boundary, pause strong efficacy, certification, absolute safety, or claims of global applicability.
Returns and delivery is the opening reading choice. All six review gates start empty. A tick records your manual review step; it does not establish an admin change, customer consent, lawful policy or publication authority. The separate prechecked privacy example cannot satisfy these gates.
Review steps recorded this time
Six steps recorded; no compliance or publication proof
One check remains unticked
Two checks remain unticked
Three checks remain unticked
Four checks remain unticked
Five checks remain unticked
Hold
Six checks remain unticked
The four official starting points answer different questions. Collect evidence for the current market and action, recording source and date. Translation, automated generation or one template example does not establish applicability to your business.
| Official starting point | Scope | Use |
|---|---|---|
| Shopify policy pages | Use it to check current Shopify policy pages and supported policy types. It does not replace review of store operations or market requirements. | Bring policy URLs, version, and page access back into the consistency scan. Do not treat a template as proof that the policy works. |
| Shopify customer privacy settings | Use it to review enabled privacy settings, regions, and tool boundaries. Shopify states that automated settings are not legal advice and merchants still need ongoing review. | Compare real pixels, forms, notifications, and data paths against the privacy page instead of reading one page alone. |
| Shopify localization and translation | Use it to check current language, market, theme, and app boundaries. Translation coverage needs separate readback for different themes and apps. | Put market scope and localized versions on the same version card. Do not equate “translated” with “applicable.” |
| EU consumer withdrawal information | Use only as an official starting point when the store actually serves relevant EU consumers and goods. The page explains common withdrawal rights and exceptions; the current scope still needs verification. | Use it to spot when a return window or exception cannot be copied from a template and route the question to suitable review. |
This page has seven independent record groups. Save, restore, clear and JSON export affect the current group only. The first two groups import the old boundary category, checks, decision and six texts. Reading choices, privacy examples and work notes are new save scopes. The quick self-check remains transient: answer it again after a fresh load; no record saves it.
The old textareas were unbounded. Each current text field allows 2,000 characters, combined text-field limits are capped at 10,000 per group, and storage also has a 32KiB ceiling. Keep a complete original of longer old notes; short-fixture success does not prove arbitrary-length preservation. Records stay in this browser or a download you control and do not write to Shopify. Exclude customer, order, payment, account, identity, complete legal-document and restricted-product information.
Boundary decision
Self-check not answered
Reason for the selected decision
Hold
Unanswered: no answer is inferred
Separate operating facts, open verification and professional review; the record is not legal advice or release.
A footer disclaimer fixes neither conflicting facts nor applicability to every market and product.
Review ticks are not certification; admin, market and publication evidence still need their own checks.
Connect five page types with real admin evidence
Privacy, Refund/Return, Shipping, Terms and Contact are this lesson’s starting set, not a complete legal list for every market or category. Shopify also supports legal notices, subscription policies and other information. Ask what each page tells a buyer and whether support could use it in a concrete case.
Inspect each page’s job
- What to clarify
- What data is collected, why, who receives it, and how users contact or opt out.
- How to review
- Matches real data flows from Shopify, GA4, pixels, email, support, shipping, and payment tools.
- What to clarify
- Return window, conditions, exclusions, cost responsibility, refund path, and timing.
- How to review
- Support can handle a real order with page rules, without inventing policy on the fly.
- What to clarify
- Processing time, transit time, regions, tracking, duties/taxes, delays, and lost-package handling.
- How to review
- Matches logistics setup, product pages, order notices, and checkout cost expectations.
- What to clarify
- Orders, payments, cancellations, pricing errors, liability, disputes, and site usage rules.
- How to review
- Does not conflict with checkout flow, support language, or pricing-error handling.
- What to clarify
- Email, form, support path, response time, and required information for order issues.
- How to review
- Users can find a real support path in mobile footer, near product decisions, and in order emails.
The selector starts on Refund so the tumbler conditions are easy to inspect. Open the other pages as well: contact details must agree, entity wording must fit the business, and buyers must find return and shipping conditions before ordering. A linked empty page is not completion.
Use the current English admin as a locator. Automation, template availability, buttons and theme menus may differ. Here you prepare a review path, without editing or publishing a real store. An authorized operator should preserve existing text and translations before changing settings.
Four steps from policy to storefront
Find policies and the prior version
Open Settings > Policies and inspect Written policies, URLs, edit dates and market scope. Review Privacy, Refund/Return, Terms, Shipping and Contact against the business. Preserve the prior version before removing placeholders.
How to confirm
The “Use automated policy” control can replace custom copy and translations in languages with an automated template. Back up first and review every language after switching.Find the operating evidence
Compare Return/refund policy with actual return rules, PDP copy and support snippets. Compare shipping with Settings > Shipping and delivery, order email and checkout costs. Review privacy through Settings > Customer privacy, Customer events and installed services.
How to confirm
Keep a URL, admin field or order/email/support evidence location for each promise. If its factual support is missing, retain an open question and pause action.Check menus, mobile and support access
Use Content > Menus to add policy links to the relevant menu, then verify which menu the current theme uses in its footer. Find one support path from mobile PDP, footer and order email. /pages/contact is common, but open the actual store URL.
How to confirm
Default policy links in checkout do not establish storefront-footer access. Inspect destination content, language, return navigation, email, form and response expectations.Review before routing the work onward
Align returns, shipping, duties, privacy, reviews and claims, then manually open each page. Pass the evidence, confirmation lead and paused promise to fulfillment, support or launch QA.
How to confirm
A controlled test order, refund path and cancellation example can be rehearsed where permitted. Real orders, charges, refunds, email and publication need their own authorization; this lesson performs none.
Another person should be able to find the same record. Publication, return conditions, shipping/duties, consent and product claims each have a place to inspect. An admin path locates evidence; it does not establish that the action occurred.
| Review job | Admin or site path | Record and first repair |
|---|---|---|
| Publication | Settings > Policies; storefront footer menu | Name, URL, edit date, entry and market. Repair access and version first. |
| Return conditions | Return/refund policy; PDP return note; support template | Window, SKU/category, item condition, cost and request path. Replace vague carefree-return wording first. |
| Shipping/duties | Settings > Shipping and delivery; policy; checkout method; email | Rate name, handling/transit times, duty arrangement and test record. Clarify responsibility before all-inclusive claims. |
| Privacy/consent | Settings > Customer privacy; Customer events; forms and email footer | Purpose, frequency, unsubscribe, policy paragraph and tool use. Verify behavior before adding touchpoints. |
| Reviews/claims | Review app, ad library, PDP, packaging/manual and support FAQ | SKU mapping, source, collaboration, test file and conditions. Pause unsupported claims. |
Scan shipping, returns and reviews separately
Inventory and fulfillment can differ between SKUs of the same tumbler. In this example, stocked items are estimated at 7–10 days and straw-lid replenishment at 15–20. These are estimates, not shipping commitments from this lesson. On day 8, the buyer asks for tracking. Compare the visible promise, actual setup and reply instead of adding another “Fast shipping” badge.
Choose a promise to scan
- Visible promise
- PDP says "7-10 day delivery", the hero says "Fast shipping", and Shipping Policy says transit may take 15-20 days.
- Rule to verify
- Split the rule into handling time, transit time, tracking update timing, remote/holiday/customs exceptions, then align PDP, policy page, order email, and support replies.
- Buyer question
- The buyer asks: It is day 8, why did the page say 7-10 days? Where is tracking? Was this promise misleading?
- Example input
- The 20oz tumbler first batch uses warehouse stock plus replenishment transfer. In-stock SKUs can arrive in 7-10 days, but straw-lid SKUs actually need 15-20 days.
- Evidence to keep
- PDP shipping block, Shipping Policy paragraph, checkout shipping method, order confirmation email, carrier tracking screenshot, and out-of-stock SKU flag.
- Repair order
- First change PDP to "in-stock SKUs usually arrive in 7-10 days; replenishment SKUs usually arrive in 15-20 days", then sync policy, order email, and support template.
- Pause before sync
- Before sync, pause strong claims such as "Fast shipping" and "7-day delivery" in ads and hero banners.
- Visible promise
- PDP says "30-day worry-free returns", while Refund Policy excludes opened straw lids, engraved custom items, and final-sale items.
- Rule to verify
- Return promises must clarify window, item condition, exclusions, cost responsibility, request path, and refund timing.
- Buyer question
- The buyer asks: I bought because returns looked worry-free. Why can an opened item not return? Who pays return shipping? Can support make an exception?
- Example input
- The standard tumbler lid can be resold, opened straw lids raise hygiene and accessory-completeness issues, and engraved custom items cannot return to saleable inventory.
- Evidence to keep
- SKU/variant list, PDP return note, Refund Policy, support first-reply template, return request form fields, and photo requirements for opened items.
- Repair order
- First change "worry-free returns" to "eligible items can request returns within 30 days", then place exclusions in PDP trust block, Refund Policy, FAQ, and support template.
- Pause before sync
- Before sync, pause "zero-risk purchase" and "no-condition returns" claims.
- Visible promise
- PDP shows five-star reviews, ads use creator trial screenshots, and email asks buyers for reviews, but sampling, incentives, material ties, and negative-review handling are unclear.
- Rule to verify
- Reviews and endorsements must clarify source, incentive, fit to the current product, and whether genuine negative feedback can appear.
- Buyer question
- The buyer asks: Were these reviews bought? Did the creator receive product or payment? Does this review match the SKU I am viewing?
- Example input
- The 20oz tumbler imports 48 reviews from an older model. 12 came from sampled creators, and 6 actually refer to the old lid, so they should not appear on the new straw-lid PDP without context.
- Evidence to keep
- Review source, SKU mapping, sampling/incentive record, creator permission, review display rule, and record of hidden or rejected reviews.
- Repair order
- First remove SKU-mismatched reviews, then label sampling or collaboration context, then write review collection, display, and support language into the policy promise consistency map.
- Pause before sync
- Before cleanup, pause claims such as "all real buyers love it" or unprovable doctor/creator endorsements.
The three scans cover shipping differences, return exceptions and review provenance. Of 48 imported reviews, 12 have sampling relationships and 6 refer to an old lid. Investigate those dimensions separately; the sets may overlap, so do not calculate a usable review total by subtraction. Preserve records and pause false attribution or unsupported endorsements, then plan the sync.
Follow one promise through four surfaces
One rule travels through PDP, checkout, order email and support. Other examples have PDP 5–8 days versus policy 15–20, and policy 7–12 versus PDP 5–8 and support within 15. They are separate conflict examples, not numbers to average into a new estimate. Choose a diff and trace where the wrong expectation first appears.
Trace one line across surfaces
- PDP
- PDP says “5-8 days delivery” but does not explain processing time.
- Checkout
- Checkout only shows standard shipping with no waiting range.
- Order email says “ships soon,” so the customer does not know when tracking appears.
- Support
- Support improvises, which can conflict with the policy page.
- Repair
- Use one line: processing time + transit time + remote/holiday exceptions, then sync PDP, shipping policy, order email, and support snippets.
- PDP
- PDP says “worry-free returns” without window or conditions.
- Checkout
- No return access before checkout; buyers ask after purchase.
- Shipping email does not explain how to start a return.
- Support
- Support saying only “see policy” feels evasive.
- Repair
- Clarify return window, item condition, cost responsibility, exclusions, and request path.
- PDP
- PDP does not mention import charges, so buyers assume price is the full cost.
- Checkout
- Checkout tax display conflicts with the policy page.
- Shipment email does not say who handles customs or duties issues.
- Support
- Support cannot promise “we cover everything” unless the business truly does.
- Repair
- Clarify duty/tax responsibility by market and align PDP, checkout, shipping policy, and support lines.
- PDP
- Popup and signup collect emails, but privacy policy does not explain use.
- Checkout
- Checkout opt-ins, cookie banner, and marketing subscription boundaries are unclear.
- Mixing transactional and promotional emails hurts trust and deliverability.
- Support
- Support needs a clear line for unsubscribe, data requests, and privacy contact.
- Repair
- Sync cookies, pixels, email signup, unsubscribe, and privacy-request paths across policy, banner, forms, and support.
The repair should become one conditional rule. Fix the buyer-facing summary, then policies, email and support. Changing only the ad or hiding the policy leaves the conflict. For an existing purchase, retain the version at purchase and use the applicable rules and authorized process; editing today’s page cannot erase an earlier promise.
Rewrite vague templates into specific rules
Clearer does not mean stronger. Each rewrite keeps the buyer’s missing information and the places to update in view. The 1–3 business-day handling range, 7–15 business days after shipment and 30-day return request are examples to verify against operations and applicable law, not templates every store should publish.
Keep the question; clarify conditions and actions
Shipping timing
- Original copy
- We process orders as soon as possible. Delivery depends on the carrier.
- What is missing
- The buyer cannot see handling time, transit time, when tracking appears, or whether holidays, remote regions, or customs checks may add time.
- Example rewrite
- Orders usually take 1-3 business days to process. After shipment, delivery usually takes 7-15 business days. Remote regions, holidays, and customs checks may add time.
- Sync targets
- PDP shipping note, Shipping Policy, order confirmation email, and support replies.
Return path
- Original copy
- We accept returns according to our policy.
- What is missing
- The customer does not know the request window, item condition, start point, cost responsibility, or what support will do next.
- Example rewrite
- Proposed example: request a return through Contact with your order number within 30 days of delivery for unused goods in original packaging; support will give next steps. Use only after checking applicability. This voluntary offer does not restrict statutory rights or make opening a box an automatic exclusion.
- Sync targets
- Refund / Return Policy, PDP return note, shipping email, and support standard sheet.
Marketing consent
- Original copy
- By subscribing, you agree to receive updates.
- What is missing
- "Updates" is too vague. The buyer cannot tell whether it means discounts, new arrivals, abandoned-cart emails, order emails, or how to unsubscribe.
- Example rewrite
- Enter your email to receive this discount and occasional store emails. You can unsubscribe from any marketing email. Order emails are still sent for purchases.
- Sync targets
- Signup popup, footer form, Privacy Policy, email footer, and support privacy replies.
The marketing example explains purpose and opt-out, but an email address or a paragraph of copy does not establish valid consent. The real form, market, choice records, follow-on flows and withdrawal behavior must agree. Review order notifications separately from marketing; a purchase is not blanket permission for every campaign.
Pause the wrong claim before repairing the chain
Choose the closest conflict: return exclusions, surprise duties, vague consent or unsupported claims. Every branch retains the signal, tempting mistake, safer repair, first evidence, update targets and pause line. Pause outward wording that expands the misunderstanding, while continuing to help existing buyers.
Decide what pauses first
- Signal
- The PDP says “carefree returns,” but the refund policy excludes custom, intimate, or opened goods. Support has to explain after the request arrives.
- Tempting wrong move
- Add a stricter exclusion line only in the refund policy while keeping “carefree returns” on the PDP and ads.
- Safer repair
- Sync the return window, item condition, exclusions, cost responsibility, and request path across PDP, refund policy, FAQ, order email, and support snippets.
- First evidence
- PDP return note, refund policy paragraph, order confirmation email, support first-reply template, and one real SKU return-condition screenshot.
- Update targets
- PDP trust block, Refund Policy, FAQ, support standard sheet, and launch QA policy check.
- Pause condition
- Pause “carefree returns” or “zero-risk purchase” claims in ads and hero banners until the surfaces match.
- Signal
- Shipping Policy says duties may be buyer responsibility, but PDP, cart, and checkout-adjacent copy give no expectation.
- Tempting wrong move
- Wait until the buyer receives the duties notice, then have support say the policy already mentioned it.
- Safer repair
- Confirm DDP/DDU/DAP or unpaid-duties handling by primary market, then sync responsibility across Shipping Policy, PDP shipping note, checkout message, and support template.
- First evidence
- Primary-market test order, checkout total screenshot, Shipping Policy duties paragraph, label or carrier service, and support duties reply.
- Update targets
- Shipping Policy, PDP shipping note, checkout-adjacent message, order email, and support exception path.
- Pause condition
- Pause “all fees included” or “no extra charges” wording until duties responsibility is clear.
- Signal
- The popup only says get a discount, but the email enters welcome, abandonment, and promo flows; privacy policy and email footer do not explain opt-out.
- Tempting wrong move
- Raise the discount to increase signup rate without fixing the form, privacy policy, or email footer.
- Safer repair
- Put signup purpose, marketing frequency, order-email boundary, unsubscribe path, and privacy contact into popup, footer form, Privacy Policy, and email footer.
- First evidence
- Popup screenshot, footer form, Klaviyo or email-flow entry rule, email footer, and Privacy Policy data-use paragraph.
- Update targets
- Signup popup, footer form, Privacy Policy, email footer, and support privacy-request reply.
- Pause condition
- Pause new retargeting, SMS sends, or more aggressive popup tests until consent and opt-out paths are clear.
- Signal
- Ads and PDP say “cures,” “100% safe,” “doctor recommended,” or “best in class,” with no testing, certification, study, or authorization file.
- Tempting wrong move
- Add a disclaimer in Terms while letting PDP and ads keep strong claims.
- Safer repair
- Rewrite strong claims into material, spec, use case, limits, instructions, and checkable evidence; downgrade or remove claims without support.
- First evidence
- PDP claim screenshot, ad creative, packaging or manual, certification or test file, and support FAQ.
- Update targets
- PDP, ad creative, FAQ, Terms, support high-risk claim sheet, and launch QA.
- Pause condition
- Pause health, safety, guaranteed-result, authority, and absolute claims in paid media until evidence is ready.
Duties must be reconciled with the actual carrier and import arrangement. Legacy DDU wording, DAP/DDP in a contract or an unpaid-duties label cannot alone establish that all charges are covered. This lesson sets no tax rate or importer responsibility. Match market-specific checkout total, service, label, policy and support reply before restoring “no extra charges.”
Incoterms allocate delivery responsibilities in a trade contract. Under DAP (Delivered at Place), the buyer handles import clearance and related duties and taxes; under DDP (Delivered Duty Paid), the seller does. 1 Identify the buyer and seller in that contract before assuming the store’s end customer is responsible for import clearance.
The older DDU term means Delivered Duty Unpaid. Its ICC 1990 definition excludes import duties, taxes and clearance from the seller’s obligations unless the contract adds them. 2 Use these terms to ask the supplier and carrier who handles import and who receives the bill. Then answer the customer’s practical question: what additional charges could still arrive after checkout?
Give six evidence areas a responsible reviewer
An evidence checklist assigns confirmation to someone who can find the record; it is not another legal checklist. Support and operations review returns, finance confirms the actual refund path and costs, fulfillment supplies carrier/cost evidence, and data, email and support verify their respective privacy processes. Read all six areas.
Choose the weakest evidence area
- Evidence
- Refund Policy URL, return window, excluded SKUs/categories, cost responsibility, return request path, refund timing, and support first-reply template.
- Cross-check
- Check whether PDP trust block, order email, support template, and return request form use the same rule.
- Confirmation lead
- Support lead and operations lead sign off together; finance confirms refund path and fee impact.
- Weak signal
- Page says worry-free returns, but support must improvise opened, custom, final-sale, and international-return cases.
- Evidence before proceeding
- Launch only after one real SKU has examples for returnable, non-returnable, merchant-fault exception, and buyer-remorse return.
- Job
- Refund policy must be executable by support at SKU level, not only a footer template.
- Evidence
- Shipping Policy URL, processing time, transit time, tracking update timing, DDP/DDU/DAP or unpaid-duties logic, and test-order screenshots.
- Cross-check
- Check Shopify rates, checkout cost, PDP shipping note, order confirmation email, and duties support reply for consistency.
- Confirmation lead
- Fulfillment lead provides carrier and test-order evidence; support lead confirms delay, no-tracking, refusal, and duties-dispute snippets.
- Weak signal
- Policy says duties may apply, but PDP, checkout, and ads still imply no extra fees or fast customs.
- Evidence before proceeding
- Write shipping promises only after checkout screenshots for primary, remote, and heavy-order addresses show consistent duties responsibility.
- Job
- Shipping policy must connect to real rate and duties evidence, or it becomes support and chargeback risk.
- Evidence
- Terms of Service URL, payment confirmation, cancellation window, pricing-error handling, dispute path, subscription or preorder note.
- Cross-check
- Check checkout, order confirmation email, payment admin, support cancellation snippet, and Terms for consistency.
- Confirmation lead
- Operations confirms order rules; payment lead confirms capture, refund, dispute evidence; support confirms cancellation and pricing-error snippets.
- Weak signal
- Terms says the merchant may cancel orders, but support, payments, and order email do not explain when or how buyers are notified.
- Evidence before proceeding
- Plan a controlled test order, refund path and cancellation case with state, notices, owner and Terms reference, within an available permitted test scope. Live charges, refunds, email or publication need separate authority; unexecuted work remains unverified.
- Job
- Terms must connect to order, payment, and support actions, not stand as a legal wall.
- Evidence
- Contact URL, support email, form fields, response time, required order information, auto-reply, and escalation path.
- Cross-check
- Check mobile footer, PDP area, order email, policies, and support entry for the same real contact path.
- Confirmation lead
- Support lead owns entry and first-response SLA; operations confirms mobile and email access.
- Weak signal
- Contact page has only a form, without email, response time, order-information requirements, or escalation path.
- Evidence before proceeding
- Find the support path once from mobile PDP, footer, and order email; move to launch QA only after all work.
- Job
- Support entry must be findable by real users on mobile and in order emails.
- Evidence
- Product-page claim URL, ad creative ID, review source, certification/test file, packaging instruction, use limitation, and strong words to remove.
- Cross-check
- Check ads, PDP, reviews, FAQ, packaging, support template, and policy page for claims beyond evidence.
- Confirmation lead
- Content lead collects page and creative; product lead provides evidence; ad lead pauses risky creatives.
- Weak signal
- Terms has disclaimers, but PDP and ads keep using absolute, health, safety, or authority endorsement claims.
- Evidence before proceeding
- Downgrade unsupported claims into material, spec, use case, and limitation language; advertise strong claims only after evidence is complete.
- Job
- Product claims need evidence and limits; Terms disclaimers cannot carry them alone.
Start with the weakest area without calling the whole set complete. Retain returnable, proposed-excluded, merchant-fault and buyer-remorse cases for one SKU. Keep core-US, remote and heavy-order shipping examples under controlled valid addresses and consistent market, stock and shipping setup. A geographic label proves no carrier coverage. Real customer or transaction work uses a separate authorized process.
Keep a reconciliation record for each change
The promise ledger records the template gap, proposed line, supporting evidence, sync targets, review trigger and pause condition. Maintain distinct entries for returns, shipping/duties, privacy/signup and claims/reviews. New SKUs, carriers, markets, pixels or imported reviews provide concrete reasons to reopen it.
Choose the promise to maintain
- Template gap
- The template says "30-day worry-free returns" but does not define excluded SKUs, opened-item handling, return shipping cost, or support evidence.
- Proposed promise
- Customers can request returns for eligible items within 30 days after delivery; item condition, exclusions, cost responsibility, and request path must be clear.
- Reconciliation evidence
- Use the 20oz tumbler to check proposed rules: standard lids may be eligible, while the draft excludes opened straw lids and engraved items. Verify market, statutory rights and the version at purchase. Keep SKU, page line, refund-policy paragraph and support snippet; a draft exclusion is not a legal conclusion.
- Sync targets
- PDP return summary, Refund Policy, FAQ, order email, return request form, and support first-reply template.
- Review trigger
- Recheck when adding SKUs, changing return window, running final sale, adding custom products, or seeing repeated refund disputes.
- Pause condition
- Before reconciliation is complete, pause "worry-free returns," "zero-risk purchase," and "no-condition refund" in ads, hero banners, and emails.
- Job
- Return policy is not a template sentence; it must reconcile at SKU level.
- Template gap
- The template says "worldwide shipping, duties may apply," while PDP says fast shipping, checkout gives no duties signal, and support cannot explain DDP, DDU/DAP, or unpaid duties.
- Proposed promise
- Write handling time, transit time, tracking update timing, duties responsibility, and exception handling by primary market; do not use one global promise for all countries.
- Reconciliation evidence
- Keep checkout screenshots, rate name, Shipping Policy paragraph, order email, and support duties reply for a core US address, remote address, and heavy order.
- Sync targets
- PDP shipping block, Shipping Policy, checkout-adjacent message, order confirmation email, tracking email, and support delay/duties snippets.
- Review trigger
- Recheck when adding markets, changing carriers, changing free-shipping threshold, entering EU/UK, scaling promos, or seeing repeated duties/delay tickets.
- Pause condition
- Before reconciliation is complete, pause high-promise lines such as "no extra fees," "7-day delivery," and "sitewide free shipping."
- Job
- Shipping policy must reconcile with checkout cost, order email, and support replies.
- Template gap
- The template says "we may collect information," while the site actually uses Pixel, GA4, signup popups, abandoned-cart emails, retargeting, and support tools.
- Proposed promise
- Define what is collected, why, which tools read it, how marketing emails can be unsubscribed, and where privacy requests go.
- Reconciliation evidence
- List cookie banner, Privacy Policy, signup form, email footer, Customer Events, Pixel/GA4 tool list, and unsubscribe path.
- Sync targets
- Privacy page, cookie banner, popup, footer signup form, checkout opt-in, email footer, and support privacy reply.
- Review trigger
- Recheck when adding ad pixels, email tools, support tools, SMS, cookie banner, or entering markets with stricter privacy expectations.
- Pause condition
- Before reconciliation is complete, pause aggressive popups, SMS sends, retargeting scale, and vague signup incentives.
- Job
- Privacy policy must reconcile with real tools, not only a generic disclaimer.
- Template gap
- Terms has disclaimers, but PDP, ads, reviews, and creator assets keep strong lines such as "guaranteed result," "all real buyers love it," or "officially recommended."
- Proposed promise
- Rewrite strong claims into material, spec, use case, limits, review source, and evidence location; downgrade unsupported claims first.
- Reconciliation evidence
- For each claim, keep PDP URL, ad creative ID, review source, SKU mapping, sampling/collaboration record, certification or test file, and packaging note.
- Sync targets
- PDP, ad creatives, review app, FAQ, packaging/manual, support template, Terms, and policy promise consistency map.
- Review trigger
- Recheck when importing old reviews, sampling for reviews, changing SKUs, changing ad creatives, or entering health, beauty, children, or safety-related categories.
- Pause condition
- Before reconciliation is complete, pause absolute, medical/health, safety guarantee, authority endorsement, and unproven review claims.
- Job
- Product claims cannot rely on Terms alone; each one needs evidence.
The 30-day offer and lid exclusions remain draft rules in the example. Verify the market, version applicable at purchase and statutory rights before treating them as usable copy. Preserve old wording and dates rather than presenting today’s edited page as past evidence. A complete record still decides no dispute outcome.
Read the rule from four perspectives
Reread a rule through four lenses: ad work checks claims and their sources, payment disputes need transaction evidence, support needs a quotable handling rule, and buyers need the condition most likely to be misunderstood before ordering. These are teaching perspectives, not promises about Meta, Google or payment-provider review algorithms.
Keep the screenshots, emails and support threads below in a separate file for human review; record only nonsensitive summaries and locations here. The current launch-scanner form takes the store URL, platform, launch stage and manual confirmations based on your own checks. It does not upload or parse those materials. Compare its report with the evidence yourself; ticking a confirmation does not make the tool verify the underlying order, consent or support action.
Choose a reading perspective
- Reader
- Use an advertising-review lens for claims, PDP, reviews, privacy choices and refund promises in Meta, Google or creator work. Verify the actual platform/account rules and review scope separately; this exercise does not predict a review algorithm.
- What to find
- It looks for unsupported performance claims, misleading reviews, before/after framing, health or safety superlatives, data tracking, and marketing consent explanation.
- Weak signal
- Privacy page has generic cookie text, while ads use retargeting, creator endorsement, and "real buyers all love it" without consent and evidence context.
- Evidence
- Ad creative ID, PDP claim screenshot, review source, collaboration or sampling record, Privacy Policy data-use paragraph, and unsubscribe path.
- Evidence for human review
- Keep the ad creative URL/ID, PDP URL, privacy URL, review-module screenshot, consent note and claim to pause separately, for a person to compare with the scan report.
- Repair line
- Downgrade the ad claim first, then add PDP evidence and privacy consent. Do not ask policy pages to rescue ad creative.
- Job
- Review claims, reviews, consent and policies together; pause the creative when evidence is weak and verify the actual platform review scope separately.
- Reader
- Prepare traceable transaction evidence across page promises, policy at purchase, order email, logistics and support. Verify submission, deadlines and decisions against the actual provider, dispute reason and applicable process.
- What to find
- It checks refund window, non-returnable exceptions, duties responsibility, shipping time, billing descriptor, cancellation rule, and whether support followed public terms.
- Weak signal
- Refund Policy says 30-day easy returns, PDP lacks opened/custom exceptions, and support later refuses refund ad hoc; evidence conflicts during disputes.
- Evidence
- Refund Policy URL, PDP return note, order confirmation email, delivery proof, support thread, refund/reship decision, and billing descriptor screenshot.
- Evidence for human review
- Keep the policy URL, order-email screenshot, support thread, logistics proof, billing descriptor and current dispute-risk note separately, for a person to check the transaction evidence.
- Repair line
- Turn refund, shipping, duties, and cancellation rules into quotable lines, then make support templates cite the same line; do not improvise.
- Job
- Payment-risk reviews rely on the evidence chain, not a polished template; order, logistics, support, and policy must match.
- Reader
- Support is not a passive reader. After launch, support uses policies for refunds, delays, duties, address errors, privacy requests, and claim challenges.
- What to find
- It looks for quotable lines, evidence required from buyers, response time, escalation timing, and forbidden promises.
- Weak signal
- The policy page is long, but support cannot find what photos damage needs, when no-tracking escalates, or where privacy requests go.
- Evidence
- Support macros, FAQ, policy paragraph, form fields, order lookup path, escalation lead, and first-response SLA.
- Evidence for human review
- Keep the Contact URL, support email, auto-reply, policy paragraph, support template and first-response SLA separately, for a person to check the contact and handling paths.
- Repair line
- Convert long policy into support-quotable lines: condition, evidence, next step, and forbidden promise.
- Job
- Support needs quotable lines and escalation paths, or policy pages become an unused text wall.
- Reader
- Buyers do not read the full policy word by word. Before ordering, they want to know delivery timing, returns, duties, data use, and who to contact if something breaks.
- What to find
- It checks whether hero, PDP FAQ, checkout-adjacent copy, footer policies, and Contact answer the same questions in plain language.
- Weak signal
- Footer links exist, but PDP and pre-checkout have no summary. Buyers learn only after purchase that custom items are non-returnable, duties are unpaid, or tracking may delay.
- Evidence
- Mobile PDP screenshot, FAQ summary, pre-checkout cost note, footer policy entry, Contact entry, and order-email sample.
- Evidence for human review
- Keep the PDP URL, checkout screenshot, policy-entry screenshot, Contact URL and the promise buyers are most likely to misunderstand separately, for a person to check the pre-purchase explanation.
- Repair line
- Move the most misunderstood rule near PDP FAQ or checkout first, then keep the full policy link.
- Job
- Buyers read pre-purchase summaries; policies carry full rules, but key risks must be surfaced earlier.
A support snippet can name the condition, requested evidence, next action and promise staff must not make. Put the most easily missed condition near PDP FAQ or checkout and retain the full policy link. Footer access alone is insufficient. Buyers need delivery, returns, duties, data use and a contact path before purchase.
Separate return, delivery and duty responsibilities
Separate the extra service a store chooses to offer from rights already provided by applicable law. Your Europe describes a usual 14-day withdrawal period for distance purchases, generally from delivery for goods, with exceptions. A custom 30-day offer does not replace that review. GOV.UK separately states that sale items retain the same refund rights and that opening a box to inspect an item does not automatically remove rights. Do not carry a US example or one store’s exclusion into EU/UK markets.
| Rule | What to establish | Bad signal |
|---|---|---|
| Return window | State whether the window starts from delivery, receipt, or purchase date, and whether it is 14 days, 30 days, or another period. | Only says returns are accepted, without start point, end point, or exceptions. |
| Return condition | Separate the voluntary store offer from statutory rights, then record condition, packaging, accessories and the specific applicability of proposed custom, hygiene/intimate, perishable or digital-content exceptions. Do not automatically exclude opened, sale, faulty or misdescribed goods. | Ads promise carefree returns while policy excludes most products. |
| Cost responsibility | Separate buyer remorse, wrong item, damage, loss, and delay; explain who pays shipping and replacement cost. | Support improvises every exception, so each buyer receives a different promise. |
| Shipping timing | Separate processing time, transit time, tracking update timing, remote regions, and holiday delays. | Only says 7-15 days, without explaining handling versus transit. |
| Duties and taxes | Clarify buyer/merchant responsibility, DDP/DDU, import tax, and destination fees before checkout surprise. | Policy mentions possible duties, but product and checkout create no expectation. |
Unused/original-packaging conditions, opened hygiene items, personalised goods, perishables and digital content need product- and market-specific review. An exclusion cannot remove applicable remedies for faults, wrong items or misdescription. If the 30-day example applies, state its starting point, request path, costs and refund process; do not hide important limits behind “eligible.” Verify actual refund state and bank arrival by payment method rather than promising one unsupported number of days.
For refunds, record whether and how funds return through the original payment method. Verify refund status, expected timing and bank arrival against the actual provider and payment method; mark unverified steps as open. Shipping rules should also list countries or regions not served, and the handling, costs and responsibility for loss, delay, an incorrect address or a delivery attempt with no recipient available.
Another handling-time conflict is a PDP saying it ships in 3 days while the policy says 7. Check what “ships” means in each place and which admin and fulfillment records support it, then align page, email and support. Keep handling and transit time separate.
Connect privacy copy with actual tools and choices
List data, purpose and recipients first. Orders, email, phone, address, device, browsing and purchase behavior may pass through payment, shipping, support, analytics, advertising and email tools. Collect only what the business actually needs and offer a real path for requests. Device storage/access through cookies or pixels, subsequent personal-data processing and email-marketing choices are not one universal permission.
For applicable access, correction, deletion, marketing-unsubscribe and privacy-contact requests, state who receives them, where to submit them and what needs escalation. Verify rights and deadlines for the actual market; do not present one process as a global rule.
Inspect signup forms and discount popups for prechecked marketing, strong inducements or unclear purposes. Receiving a discount or subscribing once does not mean agreeing to every marketing flow. Check how the actual choice, refusal and withdrawal take effect, then align the form and privacy explanation.
The five rows retain the original 2/5 opening example: data and third parties checked, the rest unchecked. They are editable manual reading states, not findings about actual use, consent, opt-out handling or law. They cannot satisfy the independent six gates above. Review each explanation and its evidence, then change its state; the count describes these five rows only.
Current five-row state count
Shopify currently says its banner governs Shopify-specific tools. Manually added third-party pixels or apps may need further integration or logic; mismatched consent regions can allow non-essential processing before a choice. In applicable regions, inspect actual behavior before choice, after accept, after reject and after withdrawal, alongside forms, unsubscribe and request handling. A visible banner or link does not prove those actions work.
For UK online-advertising storage/access, the current ICO guidance requires consent: funding the business through ads is not a strictly-necessary exception. Other purposes have their own narrow conditions; the statistical exception is not a pass for every analytics tool. Recheck when markets, purposes, third parties or choices change. This UK boundary is not a global rule.
Attribution asks which platform receives credit. Incrementality asks how much business would be missing without that advertising. These are different questions, so platform-reported revenue alone cannot establish actual growth. A tracking tool or a reported value does not answer that counterfactual question or establish permission to use that data.
Review product claims and market scope separately
Materials, specifications and use cases must also be true. Replacing “cures” with “may improve” does not fix a page that still implies the same unsupported health effect. FTC health-product guidance examines express and implied messages, the overall impression and appropriate support. An unrelated certificate, testimonials or a Terms disclaimer cannot supply that evidence.
Inspect claim risk
- High-risk wording
- Cures, treats, no side effects, permanent results, guaranteed improvement.
- Safer wording
- Describe use case, materials, design logic, limits, and verified product facts.
- Evidence
- Without testing, certification, study, or checkable evidence, do not make strong conclusions.
- High-risk wording
- 100% safe, never breaks, fastest, cheapest, zero risk.
- Safer wording
- Use conditional language: fit, scenario, expected improvement, and limitations.
- Evidence
- Use FAQ, fit/not-fit, spec limits, and real reviews instead of overpromising.
Keep certificate number, matching model, authorization scope, packaging instructions and limitations. Health, cosmetics, children, food-contact, electronics and safety-related goods need earlier market/category review. The tumbler is food-contact too; calling it an everyday item does not remove applicable requirements.
| Scope | Concern | First action |
|---|---|---|
| United States | Marketing claims, refund disputes, state consumer protection, privacy, chargebacks, and substantiated product claims. | Align ad, product page, policy page, and support promises first; strong claims need evidence. |
| UK / EU | Privacy, cookies, consumer information transparency, returns, product safety, and responsible-party expectations in some categories. | List primary market and high-risk categories; run dedicated review before entering rule-heavy markets. |
| Higher-risk categories | Children, cosmetics, health-adjacent, food-contact, electronics, safety-related, or function-heavy goods. | Do not launch with generic templates; prepare labels, instructions, evidence, limits, and a review lead. |
The four boundaries concern Shopify policy responsibility, EU GPSR, EU withdrawal and FTC reviews. GPSR has applied since 2024-12-13, with scope, exclusions and interaction with sector-specific rules. It is not the only requirement for every product, nor a rule to copy unchanged across the whole UK. The FTC rule’s 2024-10-21 start date likewise does not put every review or creator question under that rule alone.
Four official boundaries and review triggers
Shopify templates are not a liability shield
- Official boundary
- Shopify currently supports return, privacy, terms, shipping, legal notice, contact-information and subscription policies, with automation for supported policies. Merchants remain responsible for accurate published policies and following them; templates and automation do not guarantee legal compliance.
- Use in this lesson
- Turn templates into a promise-consistency map: policies, PDP, checkout, email, and support need one real rule.
- Recheck when
- Recheck whenever returns, shipping, subscriptions, privacy tools, footer menus, or market language changes.
EU GPSR is a product-safety boundary, not footer copy
- Official boundary
- GPSR has applied since 2024-12-13 and concerns safety, traceability and an EU responsible economic operator for products within scope. Exclusions and sector-specific legislation matter; GPSR alone is not sufficient for every product or a rule to assume across the whole UK.
- Use in this lesson
- Beginners do not need to memorize regulation. High-risk categories do need documented labels, instructions, a responsible contact, claim evidence, and conditions for pausing EU entry.
- Recheck when
- Recheck before entering the EU, adding children/cosmetic/food-contact/electronic/safety-related SKUs, or changing packaging instructions.
EU returns cannot be only a custom refund window
- Official boundary
- The official EU consumer page explains that distance purchases usually have a 14-day withdrawal period; for goods it usually starts from delivery, with exceptions.
- Use in this lesson
- Split returns into the return window, item condition, exclusions, return cost, refund timing, and support entry so carefree-return copy does not conflict with the policy page.
- Recheck when
- Recheck when opening EU/EEA markets, changing return windows, adding non-returnable categories, changing return address, or changing return cost.
Praise cannot be filtered into trust
- Official boundary
- The FTC explains that the Consumer Reviews and Testimonials Rule took effect on 2024-10-21 and addresses fake, false, or deceptive reviews and testimonials.
- Use in this lesson
- Connect reviews, UGC, creators and claims to their source records. Do not condition incentives on praise; disclose applicable material ties, check SKU mapping, preserve moderation reasons and avoid misleading suppression. Honest non-sentiment-conditioned incentives, sorting and moderation still need contextual review rather than a blanket ban.
- Recheck when
- Recheck when enabling review apps, importing old reviews, using creator assets, sampling for reviews, or changing review display rules.
The FTC does not prohibit every incentive for an honest review, but a reward conditioned on positive sentiment cannot be cured by disclosure. Material connections, display, product matching and endorsements still need the applicable guidance. Sorting or moderation is not automatically unlawful either: preserve genuine reasons, treat cases fairly and avoid misleading suppression. The 48/12/6 review case is not institutional research data.
Route the next action to the weakest evidence
When the PDP says 7 days, the policy 7–15 and support usually within 20, do not select the most attractive figure. Establish real handling and transit conditions, align the rule and check whether imagery, ads, packaging or support still imply more. The quick check holds the current answer only; explicitly answer it again after reloading.
Shipping-conflict check
Self-check not answered
Reason for the selected decision
Hold
Unanswered: no answer is inferred
Hiding a policy makes rules harder to find and leaves the promise unresolved.
Align PDP, policy, email and support around one real rule before proceeding.
Changing only the ad leaves the page and support conflict unresolved.
Route the next action
- Next-action reason
- Continue into fulfillment, tracking, duties, and exceptions so Shipping Policy has operational support.
- Related lesson
- Set up fulfillment
- Next-action reason
- Turn refunds, loss, delay, duties, and cancellations into support snippets and escalation paths.
- Related lesson
- Build support
- Next-action reason
- Return to payment acceptance and complete test order, refund, payout, and dispute evidence.
- Related lesson
- Review payments
- Next-action reason
- Enter launch QA and verify policies, pages, payments, notifications, data, and mobile path together.
- Related lesson
- Start launch QA
Unstable delivery, duties or tracking points to fulfillment. Unusable return replies point to support. A broken transaction-evidence chain points back to payments. Move to launch QA when these records can be reviewed together. This lesson releases no later configuration, legal conclusion or publication.
Leave policy promises and review records
These 19 work entries cover action, alignment, review and specific rules. Write the promise most likely to mislead and its first evidence, then this week’s main repair, pause condition and review window. “Policies complete” is not a substitute. Rechecking pages after 48 hours and support/refunds after 7 days is an example cadence, not a legal deadline or service promise.
New Store Launch Self-Check
Free accountEnter the store URL, platform, launch stage and confirmations based on your own checks to locate public-page gaps. Keep policy URLs, footer/checkout evidence, email samples, paused claim, reviewer, source date and next review separately for human review; they are not uploaded to the Scanner. Compare its report with page, trust, checkout, tracking, SEO and mobile evidence yourself. Login, interactive flows, real transactions and data permissions still need their own checks; a scan is not legal certification or release.
No checkpoint finished in this lesson yet. Start with “Go to the exercise”.
Self-check not answered
Common questions
- Are five footer pages enough to launch?
- No. They are a starting review set. Check real contacts, URLs, dates, market/language, mobile access and matching promises across PDP, checkout, email, support and ads. Templates can be drafts, but cannot establish business facts, statutory rights or professional review.
- How do I find the promise to pause first?
- Choose one SKU and one public line. Use scans and diffs for shipping, returns, duties, privacy, reviews and claims. Record the wrong move, first evidence, sync targets and pause condition. Stop expanding unsupported carefree returns, no-extra-fee, 7-day or 100%-safe claims before repairing the surfaces.
- What belongs in return and shipping rules?
- State window/start, condition, proposed excluded SKU, cost, request path, photo needs, refund process and timing still to verify. Separate handling, transit, tracking, regions, holidays/customs and exceptions. The 30-day store example cannot replace EU withdrawal or other applicable remedies; review opened/custom/final-sale goods by market. Duties cannot be hidden in the footer or inferred solely from DDP/DAP or legacy DDU wording.
- How do privacy, cookies, email and Contact fit together?
- Inventory actual Pixel, GA4, Customer events, email, payment, shipping and support uses. Check form choices, banner behavior, refusal/withdrawal, marketing opt-out and privacy requests. Keep order notices separate from marketing. PDP, footer, email and policies should reach the same real email/form with requested information, response expectation and escalation.
- What do the evidence checklist, ledger and four-reader review add?
- Six evidence areas identify URLs, admin facts, screenshots, cross-checks, confirmation leads and conditions to proceed. The ledger keeps the template gap, proposed promise, sync targets, review trigger and pause. Four readings check ad claims, transaction evidence, support-quotable rules and the buyer summary. None guarantees approval or a dispute outcome.
- How should old reviews, samples, creators and claims be handled?
- Keep SKU mapping, source, sampling/collaboration, permission, display and moderation reasons. Do not condition incentives on praise, misattribute product reviews or misleadingly suppress criticism. The FTC rule and other applicable guidance have separate scopes. Pause unsupported cure, guarantee, absolute-safety and authority claims; specifications and limits still need to be true, and Terms cannot rescue them.
- When should official or professional review happen again?
- Recheck after changing markets, SKUs, final sale/custom products, carriers, return address, tracking/email tools, reviews, packaging or claims. EU GPSR concerns product safety, not just a footer. Review EU/UK, children, health, cosmetics, food-contact and electronics within their actual scope. Keep source, date, version at purchase and confirmation role.
- How do I save the work and choose what comes next?
- Save/restore/clear/JSON apply to the current group, and the shipping-conflict self-check remains transient. Keep policy URLs, footer/checkout evidence, email samples, paused claim, reviewer, source date and next review separately for human review. Enter only the Scanner's store URL, settings and checked manual confirmations, then compare its report with your evidence. Go to fulfillment for unstable delivery, support for replies, payments for transaction gaps, then launch QA when evidence agrees.
Continue from the remaining evidence gap
Use the Shopify setup lessons for field-by-field policy, privacy or event checks. When returning to the product page, repair its summary against the same policy version. Fulfillment is the next regular series step; the earliest actual gap still determines the work order.