Text version of this lessonExpand
Store design should not start with polish. A beginner store first needs buyers to understand the product, trust the promise, know how to order, and not hesitate over specs, price, shipping, or support.
The previous lesson leaves a payment-path acceptance sheet: a candidate route, record requirements for success, failure, refund, and payout, a net-received estimate, and a pause line. It answers where money-path evidence belongs, not whether a buyer understands the product.
That record is reviewable, but it does not prove the product claim, media, variants, reviews, shipping/return wording, or mobile add-to-cart path. Filled page fields still do not show that a buyer can judge fit or reach checkout without confusion.
Enter this lesson only when the payment record is reviewable and product understanding, choice, or promise is the earliest blocker. The output is a product trust and listing checklist: facts, evidence, a mobile path, and a pause action for one primary SKU; it is not payment approval, policy confirmation, or launch release.
Accept the product page by explanation, trust, and purchase clarity
Many pages look fine but behave like spec sheets. They lack usage scene, comparison, sizing, materials, shipping, support, and answers to buying concerns.
This lesson turns design and listing into a product-page trust check: hero image, title, benefits, specs, price, delivery, returns, reviews, and FAQ must support the buying decision.
We will keep using one 20oz commuter tumbler as the example, then walk the page from title and hero, to images and video, specs and variants, FAQ and reviews, and finally mobile add-to-cart. You are not writing a product description. You are helping the buyer make one clear decision at a time.
Decision lens for this lesson
- Sales explanation: How the page answers why to buy, who it fits, how to buy, and what risks exist.
- First SKUs: The small product or variant set used for the first validation round.
- Trust signal: Shipping, returns, payment, reviews, material, warranty, and support information that reduces hesitation.
Lesson output: product-page trust and listing checklist. Use this output to decide whether the lesson is truly complete.
How this connects: product pages return to structure and enter QA
Product listing is not filling images and text. It makes SKU, price, inventory, media, trust signals, and mobile path understandable to users and the team.
- Structure route: Shopify store setup to confirm PDPs, collections, navigation, and cart do not fight over boundaries.
- QA route: launch checklist and QA to put first SKUs through public page, checkout, and email tests.
Product-page launch evidence sheet: align media, SKU, promises, and pre-checkout state
Product listing is not finished when title, media, and price are entered in Shopify. A launch-ready PDP connects Shopify admin fields, media assets, page promises, policy pages, inventory, and pre-checkout state. CRO, Feed, Image tool, ad creative, and support should all reuse the same facts.
| Evidence module | Fields to record | Storefront acceptance | Reused by | Stop before it passes |
|---|---|---|---|---|
| Shopify product admin | product handle, title, vendor, product type, tags, collections, status, sales channels | Product URL, collection entry, onsite search, and featured block point to the same product fact | SEO, onsite search, collection page, Feed fields | Do not send traffic to the PDP |
| SKU and variants | SKU, barcode / GTIN status, option name, variant name, price, compare-at price, inventory, weight | Buyer can understand Black, White, Bundle, and Gift Box differences within 30 seconds | Merchant Center, Meta Catalog, order support, inventory sheet | Do not add more variants in bulk |
| Image and video files | file name, alt text, main/detail/lifestyle/size media role, source, authorization state, compressed version | Mobile buyers can judge scale, material, cup-holder fit, bundle contents, and use boundaries without zooming | Image tool, ad creative, product-page hero, email assets | Do not keep changing the theme or adding motion |
| Page promises | hero claim, specs, material, use limits, included items, FAQ, review source, support questions | Buyer can answer “Is it for me, why is it worth it, and what happens if something goes wrong?” without leaving the PDP | CRO, FAQ, support-response guidance, ad landing page | Do not add discounts or countdowns |
| Policy and price trust | Shipping Policy URL, Return Policy URL, order email template version, first support reply template, warranty / return boundary | PDP, policy page, order email, support script, and pre-checkout message do not contradict each other | Launch QA, payment review, support, email notifications | Do not enter real-order testing |
| Mobile add-to-cart path | hero SKU, variant choice, quantity, discount display, shipping message, error state, pre-checkout URL / state | On mobile, title, media, variants, price, policy, and button are readable from first screen to pre-checkout | Launch checklist, CRO funnel, GA4 / Pixel event QA | Do not start ads or add more SKUs |
Minimum completion line
Each hero SKU needs one admin field record, one media-role set, one variant / price / inventory field set, one policy URL set, and one mobile add-to-cart path record. If any part is missing, do not call the PDP launched.
Full product page sequence: title, media, specs, FAQ, then add-to-cart
Keep the 20oz commuter tumbler in mind. A buyer does not read the full spec sheet first. They ask practical questions in order: what is it, does it fit me, which version should I choose, why should I trust it, and can I add it to cart without confusion. The PDP sequence should follow that judgment.
| Page position | Buyer question | What to write for the 20oz tumbler | Proof needed | Stop before it passes |
|---|---|---|---|---|
| Title and hero promise | What is it, and why does it fit me? | 20oz leak-resistant commuter tumbler for car cup holders and all-day office hydration. | Capacity label, cup-holder image, price, and first-screen use case. | Stop theme motion and premium visual polish. |
| Images / video | Can I understand size, material, lid, and included items? | Main image, hand-scale image, lid detail, car cup-holder image, package list, and a 5-8 second clip. | Real scale, detail media, short video, and mobile crop check. | Stop scaling ad creative. |
| Specs and variants | What is different between black, white, straw-lid, and gift-box versions? | Variant name, SKU, inventory, price difference, included items, and fit scenario. | Variant comparison image, SKU sheet, stock state, and price rationale. | Stop adding more SKUs. |
| FAQ / reviews / policies | Will it leak, is it dishwasher-safe, when will it arrive, and can I return it? | FAQ answers pre-purchase doubts, reviews provide real proof, and shipping/return links sit near the decision point. | FAQ, policy URLs, review source, and support questions. | Stop countdown discounts and inflated compare-at pricing. |
| Mobile add-to-cart | Can I choose the right version, see shipping cues, and reach pre-checkout? | Use a real SKU, real discount, and a US address to reach the step before payment; record button, variant, cart, and error states. | Mobile screenshots, pre-checkout state, discount, and shipping message. | Stop launching ads or increasing spend. |
This sequence prevents you from overworking one local area. A clear title without proof media still creates doubt. A long FAQ with confusing variants still creates wrong choices. A mobile path that was never checked can waste every explanation above it.
Media and variant evidence builder: turn images, videos, variants, FAQ, and mobile add-to-cart into one evidence record
This builder turns the full PDP sequence into one SKU-level record: what the buyer doubts, which image or video to add, which Shopify fields to sync, how FAQ and reviews should be written, how the mobile add-to-cart path should be checked, and what media to bring into the Image tool. If you have not chosen the weakest layer yet, use the Product Listing QA Card in this lesson, then return to this record.
| Evidence task | Buyer doubt | Media to add | Shopify fields to sync | FAQ / review copy | Mobile add-to-cart QA | Image tool input |
|---|---|---|---|---|---|---|
| Size and fit proof | Will a 20oz cup fit a car cup holder, feel too large in hand, or leak in a backpack side pocket? | Hand-scale image, car cup-holder fit image, backpack side-pocket image, and a 5-8 second tilt clip. | Options, variant image, alt text, dimensions, weight, package size, and metafields. | FAQ states fit boundaries; reviews only cite real fit feedback. | Capacity, dimensions, fit, and non-fit boundaries are visible before add-to-cart. | Send hero, scale, and fit images to the Image tool for WebP/AVIF compression, file-size notes, and mobile crop checks. |
| Variant choice proof | What is different between black, white, bundle, and gift-box variants, and will a wrong choice affect gifting or stock? | Variant comparison image, bundle flat lay, gift-box unboxing image, and default variant hero image. | Option name, variant title, SKU, price, compare-at price, inventory, and variant metafield. | FAQ explains variant differences; reviews stay attached to the right variant. | Changing variants updates price, image, inventory, and the add-to-cart button instantly. | Create same-size hero images for key variants and record compressed versions so collection pages and ad catalogs crop consistently. |
| FAQ and review proof | Are the reviews real, is FAQ only positive wording, and who owns cleaning, accessories, and support responsibility? | Real-use images, cleaning step image, package accessories image, and support entry screenshot. | Review app mapping, FAQ block, policy links, support email, and warranty metafield. | FAQ answers pre-purchase doubts first; reviews provide evidence but do not replace policy promises. | FAQ, reviews, and policy entry are reachable before or immediately after add-to-cart on mobile. | Compress FAQ images and review screenshots while keeping text readable, then record review source, permission, and disclosure boundary. |
| Mobile add-to-cart proof | Can the button be tapped, does the discount apply, and will shipping or payment issues appear only at checkout? | Mobile hero screenshot, variant selector screenshot, cart screenshot, and pre-checkout screenshot. | Product status, sales channel, inventory policy, discount rule, cart note, and payment setting. | FAQ states shipping, payment, and discount limits; reviews do not replace checkout rules. | Use a real SKU, real discount, and a US address to reach the step before payment, not only the preview page. | Compress and archive mobile screenshots with format, file size, and hero-load risk, then write them into copyable lesson notes. |
The copyable lesson notes should include the current evidence task, Image tool input, media to add, fields to sync, and mobile add-to-cart result. If proof is missing, add proof before hiding the problem with discounts, countdowns, or more SKUs.
Collection boundary: keep only the entry this PDP must support
The PDP is the main battlefield in this lesson, not full collection-page design. The collection page only needs to route buyers to the right SKU and expose hero picks, differences, and filter language; deeper collection conversion, filtering architecture, and SEO internal links belong to CRO or SEO lessons.
| Do here | Confirm collection cards, hero image, price, stock, and filters route buyers to the right PDP. |
| Do not expand into | Full collection design, filtering systems, heatmaps, A/B tests, or SEO content maps. |
| Next route | Route collection-choice friction to CRO, search intent and internal links to SEO, and feed fields to Product Data. |
Product Listing QA Card: check fields, media, price, inventory, and SEO before launch
This card is not another abstract product-page principle. It connects Shopify admin fields, buyer judgment, and launch QA. Work through title and hero, media proof, variant inventory, price and offer, policy FAQ, and SEO/data in order; if you can only do one thing, pick the weakest layer first, then decide which field, image, or promise must be fixed.
| QA layer | Check first | What the buyer needs | Pass line | Write back to copyable notes |
|---|---|---|---|---|
| Hero promise | Product title, SEO title, handle, hero image, hero subtitle | Understand what it is, who it is for, and why it is not generic within 5 seconds | Title, media, price, and hero benefit tell the same story | Rewrite as product type + key spec + use case + one verifiable proof point |
| Media proof | Media gallery, file names, alt text, video, compressed version, usage rights | See scale, material, package contents, use method, and not-fit boundaries | Hero, detail, lifestyle, size/scale, and variant comparison media each answer one question | Add the media most likely to reduce returns first |
| Variant inventory | Options, variant name, SKU, barcode/GTIN, price, inventory, weight | Know which version to choose, whether stock is real, and what happens after a wrong choice | Variant names are natural, default choice is not misleading, and stock state is clear | Fix variant naming, default choice, and inventory state first |
| Price and offer | Price, compare-at price, bundle, discount, shipping threshold | Understand why the price makes sense, whether the offer is real, and whether extra cost appears before checkout | Value proof, shipping/return summary, and bundle differences sit near price | Write the price rationale beside the price |
| Policy FAQ | Shipping/Return Policy URL, FAQ, warranty note, support entry, order email | Know arrival time, delivery coverage, return conditions, and support path | PDP, policy pages, pre-checkout note, order email, and support script are consistent | Align shipping and return wording |
| SEO and data | SEO title, meta description, URL handle, product category, product type, tags, collection, image alt, variant image, availability, price, GTIN/brand/item_group_id, and structured data | Search, collection pages, Feed, ad catalogs, and support read the same product facts | SEO/feed fields match visible page content instead of copied old descriptions, and GTINs are not guessed | Align SEO/feed fields with the SKU fact sheet first |
Define SKU, checkout, and first-batch listing before QA
These three terms appear across product-page work, mobile QA, ad tests, and copyable lesson notes. Define them first so you do not confuse weak design with unclear buyer judgment.
| Term | Plain meaning | Where you see it | What breaks |
|---|---|---|---|
| SKU | Your store-owned code for separating products and variants. | Shopify products, inventory sheets, orders, support records, and ad creative sheets. | Images, price, stock, refund reasons, and ad feedback get attached to the wrong version. |
| checkout | The path from cart to address, shipping, and payment. | Shopify checkout, payment gateways, GA4 funnels, ad conversion events, and mobile QA. | A clear PDP can still lose buyers at shipping cost, payment methods, policy access, or button visibility. |
| first-batch SKUs | The small product or variant set used to validate page, media, price, and fulfillment. | Listing sheets, homepage feature blocks, collection pages, ad tests, and launch QA. | Too many launch SKUs make templates, media, and support promises harder to control, and buyers struggle to choose. |
Use a 20oz tumbler to see how a product page should launch
Assume the first batch has four 20oz commuter tumbler SKUs: black, white, straw-lid bundle, and gift-box bundle. The page should not start with premium styling. It should first help buyers judge capacity, cup-holder fit, insulation, leak risk, delivery timing, and return conditions.
What this page should do
Validate one PDP template first: hero copy explains commute-safe, cup-holder fit, and 20oz capacity; media shows hand scale, car cup-holder fit, lid detail, and package contents; price sits near shipping, returns, and payment trust; FAQ answers dishwasher use, straw lid, insulation time, and leak boundary.
What goes wrong
If you list 30 tumblers at once and every page only has mood images plus premium-quality copy, paid visitors will ask the same questions, stall before checkout, and support or returns will reveal the missing explanation first.
PDP before/after launch builder: move from blank page to launch-ready page
This 20oz tumbler does not need a new theme first. It needs a product page that moves from vague draft to something buyers can judge, support can cite, and launch QA can verify. Each block should answer one purchase question: what is it, which version should I choose, what proof exists, when will it arrive, and what happens if there is a problem?
| Page block | Blank-page version | Launch-ready version | Proof needed | QA check |
|---|---|---|---|---|
| Title and hero promise | 20oz tumbler - premium, stylish, and great for daily use. | 20oz leak-resistant commuter tumbler for car cup holders and all-day office hydration; hero shows capacity, lid, leak boundary, and price together. | Capacity label, car cup-holder photo, lid detail image, price, and primary use case. | On mobile, the buyer can explain what it is, who it is for, and why it is not a generic cup within 5 seconds. |
| Image and video proof | Only three white-background renders; the tumbler looks nice, but scale, lid structure, and usage are unclear. | Main image shows full tumbler; detail images show lid, anti-slip base, and interior; lifestyle images show hand scale, car holder, and desk; short video demonstrates opening and leak boundary. | Hand scale, car-holder proof, lid opening, package contents, cleaning method, and not-for-inversion boundary. | Every asset answers one buying question instead of only looking good. |
| Variant and SKU choice | Black, White, and Bundle show only option name and price; buyers cannot tell straw lid, gift box, and standard version apart. | Variant names become Black / White / Straw Lid Bundle / Gift Box Bundle, with a comparison table for contents, fit case, stock, and return boundary. | SKU for each variant, contents photo, stock state, price-difference reason, and wrong-choice return rule. | Buyer can choose the right version in 30 seconds and understand the not-fit case. |
| FAQ and buying doubts | FAQ only has generic shipping, returns, and contact questions, with no answer on leak risk, dishwasher use, or hot drinks. | FAQ answers leak resistance, dishwasher use, insulation time, straw-lid difference, car-holder fit, return terms, and support entry. | Support questions, return reasons, use instructions, cleaning note, and matching Shipping/Return Policy paragraphs. | Buyer can resolve most pre-purchase questions without leaving the PDP. |
| Shipping, returns, and promises | Page says fast shipping / easy returns, but policy page and order email do not use the same promise. | US orders usually process within 2 business days; standard shipping is about 5-8 business days; unused items can request returns within 30 days under policy, with remote-area and holiday delays possible. | Shipping Policy, Return Policy, order email, support first reply, and pre-checkout shipping state record. | PDP, policy page, checkout, order email, and support script do not contradict each other. |
The point of this builder is to move the page from pretty but vague to verifiable by buyers, support, payment testing, and launch QA. Payment tests and launch checks only matter after the product page can explain the offer.
Start by correcting one common mistake: a pretty store is not automatically a selling store
Many new stores spend too much time chasing a premium look, while buyers care about a different set of questions: what is this, who is it for, why is it worth buying, when will it arrive, and what happens if it does not work out? In other words, design is not there to show that you can decorate pages. It is there to reduce confusion and purchase anxiety.
What store design is actually supposed to solve
- Comprehension cost - Can the buyer understand what you sell within seconds?
- Trust cost - Does the buyer feel safe placing the first order?
- Decision cost - Are the key benefits, specs, price, and policies easy to find?
- Action cost - Are add-to-cart, checkout, and support paths smooth enough?
Build structure first, then style
For an early-stage store, the highest-leverage design work is not choosing colors first. It is defining the page structure first. Without structure, design is mostly decoration. With structure, even an official Shopify theme can become a store that sells.
The core information architecture for a new store
Homepage design: tell buyers who you are, what you sell, and why they should trust you
The homepage does not need to contain everything. It needs to guide the buyer into the right next step. In the early stage, the homepage only needs to do three things well: define the offer, surface the main products, and establish baseline trust.
Hero positioning
One clear value statement, one strong visual, and one clear CTA. Do not make visitors guess what you sell.
Featured products
Do not push too many SKUs at once. Show the products or collection that best represent the business.
Trust support
Shipping timing, return clarity, payment methods, reviews, or a concise brand story all help reduce resistance.
Suggested homepage sections for a new store
- Hero: one-line positioning + image + primary CTA
- Best Sellers or Featured Collection
- Three or four core benefit icons
- Reviews or a trust section
- FAQ / Shipping / Return shortcut block
Product pages are the main conversion battlefield: do not turn them into spec sheets
Most weak product pages do not fail because they lack information. They fail because the information appears in the wrong order. Buyers do not start by looking for a size table. They start by asking: what does this do for me? A good product page sells the value first, supports it with evidence, then removes risk and confusion.
A better product-page content order
Product Page Trust Gap practice: when the page looks good but buyers hesitate, add proof first
Do not blame every product-page problem on theme, color, or polish. If buyers still ask about size, reviews, price, and variant differences, the page is missing buying proof, not decoration. Identify the gap first, then write the proof back to the right page area.
| Page signal | Do not fix it this way | Priority fix | First evidence | Write-back / QA |
|---|---|---|---|---|
| Images look polished, but buyers keep asking whether a 15-inch laptop fits | Keep replacing hero images or write large capacity | Add a size diagram, packed-use photo, and fit/not-fit note | Measured dimensions, fit list, 15-inch laptop packing photo, return or support-request records | Media set, spec table, FAQ, variant note; on mobile, buyers can judge fit without zooming |
| Many five-star reviews appear, but they lack use context and source clarity | Add more positive reviews or vague avatars and one-liners | Show only real, explainable, compliant feedback, then add product facts and use boundaries | Review source, order/use relationship, permission status, disclosure, and whether negative reviews are filtered | Review section, FAQ, proof note, support review loop; buyers can judge trust even without star ratings |
| Price is higher than competitors, but the page only says premium, durable, and well designed | Discount immediately, add a countdown, or use inflated compare-at pricing | Place material, durability boundary, package contents, warranty/returns, and use-case proof near the price | Material detail image, structure note, package list, warranty rule, competitor difference table | Price area, benefit proof, bundle note, shipping/return summary, and FAQ |
| Too many colors, sizes, or bundles make buyers choose the wrong version | List every variant and let buyers figure it out | Add variant naming, comparison image, use case, availability state, and return boundary | Variant SKU, option name, stock state, support questions, and wrong-purchase/return reasons | Variant selector, product media, spec table, FAQ, collection filters, and order confirmation email |
Images and video: media quality determines whether your value proposition is understandable
Shopify's current official product-media documentation gives clear limits
(refreshed against Shopify Help Center on 2026-06-29):
images can be up to 5000 x 5000 px and 20 MB;
video can be up to 1 GB, 10 minutes, and
4K; 3D models in GLB and USDZ are
also supported. But the real question is not how large can the file be? It
is whether different media assets are being used to do different jobs.
The media mistakes that create the most friction
- Only a main image, no explanation images - The buyer can see the product but not understand the value
- Only mood shots - Attractive visuals with little useful information still leave hesitation in place
- No size and package clarity - These often turn into after-sales problems and avoidable returns
Titles and copy: lead with value, then support with keywords
Many tutorials treat product titles like SEO exercises. On an independent store, the first job of the title is still clarity. Keywords matter, but not at the expense of readability. The strongest titles usually balance product name, core differentiator, and use case or audience.
Title and description checklist
- The title is understandable before it is optimized
- The first screen of the description answers why buy this?
- Short paragraphs, bullets, and subheads reduce reading friction
- Specs, dimensions, material, and package contents are separated clearly
- Do not promise performance or benefits that the page cannot support
Listing rhythm: do not flood the store with SKUs at the start
The most effective early listing strategy is not more products. It is launching a small batch of SKUs with complete quality standards around media, copy, and pricing logic. A large number of weak product pages usually makes the store harder to manage and less trustworthy, not stronger.
Recommended first-batch listing rhythm
Price presentation: profitability is not the whole story
Price is both a financial number and a communication signal. When a buyer sees the price, they are also asking whether it feels fair, whether it looks risky, and whether the value is justified. Product pages should therefore present price together with proof and reassurance, not as an isolated number.
Better price presentation rules
- If you show a compare-at price, make sure the discount logic is real
- Place shipping, return, or payment-safety reassurance close to the price area
- Higher-ticket products need stronger proof, reviews, and support clarity
- Your pricing signal should match your product positioning and brand presentation
Trust information: many stores do not lose on traffic, they lose on hesitation
For a new brand, trust information matters as much as the product promise. First-time buyers are often not rejecting the product itself. They are unsure whether the site is real, reliable, and safe enough to try.
Payment and checkout trust
Make accepted payment methods, secure checkout, and refund-policy entry points easy to find.
Shipping and after-sales trust
Put delivery timing, shipping regions, and return rules where buyers actually look for them.
Reviews and proof
Real reviews, user photos, comparison visuals, and FAQ answers all lower purchase anxiety.
Tool strategy: install only what improves conversion or efficiency directly
Tools are not better just because there are more of them. In the early stage, the best additions are usually the ones that improve page speed, review credibility, behavior visibility, and email capture readiness. Decorative app stacking often slows the store before it improves anything meaningful.
A practical execution path for early-stage operators
If you are just getting started, the priority is not to build the most beautiful store possible. The priority is to build the first version that can sell, iterate, and scale later. Get a small number of products right before expanding volume.
Recommended execution order
Product pages must explain facts before visual polish
Shopify product documentation treats product information, price, variants, and availability as maintained store data. FTC review guidance also warns marketers against fake or non-transparent reviews. For a new store, trust comes from complete facts, not from a crowded page.
Mobile add-to-cart failure example
A shopper clicks an ad for the 20oz commuter tumbler. The hero shows the cup, but color options sit below the second screen, Shipping and Returns hide in the footer, Add to cart opens a drawer saying the discount is invalid, and the cart finally says the address cannot ship. Do not change the theme or add countdowns first. Fix variant state, shipping coverage, discount rule, policy access, and cart message together, then prove the mobile path from hero to pre-add-to-cart with screenshots.
Copyable lesson notes: product-page launch record
If buyers still need to ask about material, size, delivery time, and return rules after reading the page, the problem is not visual polish. The sales explanation is incomplete. The choices you made in the Product Page Trust Gap practice, media role review, SKU rhythm, and mobile QA should flow into these copyable lesson notes.
Your copyable notes should include these 6 fields
- Current pressure: Where buyers are stuck now: size, reviews, price, variants, checkout trust, or fulfillment promise.
- First evidence: From the current trust-gap choice: the next image, review check, mobile path record, or support question to collect.
- This-week action: The one primary SKU, PDP section, or pre-checkout friction point to fix this week.
- Stop action: What to pause before page explanation and mobile QA pass: more SKUs, theme changes, discounts, or ad spend.
- Review window: When to review: before launch, after mobile QA, after 7 ad days, or after first support questions.
- Next route: Bring first SKUs, product-page template, media gaps, trust signals, pricing/shipping rules, and mobile path records, plus the practice write-back location, into launch QA.
- Step 1: Choose one primary SKU and place its title, specs, variants, price, and policy entry in the same fact record.
- Step 2: Read the hero, media, choices, FAQ, and pre-add-to-cart prompts in buyer order, then mark the first place a buyer still has to guess.
- Step 3: Run that path on mobile. Pass condition: a buyer can judge fit, price, and the next action without leaving the PDP; If it fails: repair the first missing proof, then pause new SKUs, discounts, or theme work. A common mistake is to change the theme before that proof exists.
Before the next lesson, you should have one primary SKU template, core claims, media gaps, trust signals, pricing/shipping rules, and mobile path records, plus the trust-gap repair location you selected.