Module 06 of 06

Storefront Completion & Launch Readiness

Finish a polished, working Shopify storefront, fully translated and reviewed in English and French.

Instructions revised October 23, 2026 · 2026-10-23.3. Keep the same project/chat when possible. In a new Codex or Claude Code chat, attach prior PDFs and their Resume context. Check your setup.

What you'll do

Finish a polished, working Shopify storefront, fully translated and reviewed in English and French.

You'll need

Your Shopify previews, Modules 02–05 results, real website reference, brand assets, policies, and review decisions.

AI helps with

Adapt the reference to your brand, finish the actual store, complete EN/FR content, and test and repair customer journeys.

Your approval

Approve the visual direction, scoped store changes, final EN/FR review, and completion; publication and activation need separate authorization.

Expected result

A visually approved, working EN/FR Shopify storefront with verification evidence and a separate launch status.

Final output

The finished EN/FR Shopify storefront and its Storefront Completion & Launch Readiness Report, only after all required gates pass.

Start the exercise with your AI assistant

Copy the AI instructions and paste them into ChatGPT or your supported assistant. It should begin guiding you through this module, one step at a time. Use your existing project/chat. For a new chat, attach the approved prior-module PDFs, including Resume context and any actual source artifacts. Account access requires a separate authorized connection.

View and manually copy full AI instructions

I am completing Randmar Workbook Module 06: Storefront Completion & Launch Readiness. Prompt revision 2026-10-23.3.

Module URL: https://randmar.io/workbook/store-audit. Use this pasted revision when a cached page disagrees.

Act as my Academy guide and DO this exercise with me now, one focused step at a time. Do not audit or rewrite the Academy website. Use my actual business idea or approved brand; examples are never my identity, account data or approval. If I have no brand name or store yet, help me develop my own brand in Module 02 and follow Module 03’s new-store path when we reach it. Before any account action, confirm the exact business and intended store when one exists. A demonstration store, previous business workspace or currently connected account is never my selected business unless I explicitly identify it. Never rename or overwrite a connected demonstration store to build someone else’s brand.

RECOVER AND PREFLIGHT: Reuse available approved prior outputs and progress. Ask only for missing evidence needed now; never invent cross-chat access. Module 01 is setup only with no PDF. From Module 03 onward, confirm earlier exercise completion and request the relevant PDFs if unavailable. First verify the capabilities needed for the current step: research, account identity/read access, authorized implementation, browser previews and PDF export/review. A connected plugin does not prove all of these. Missing access does not prevent independent interviewing, drafting or research. Give the exact supported next action and location for a missing capability; do not repeat successful setup or approvals. Respect the active module over general onboarding recommendations.

AUTHORIZATION: Read current relevant tool contracts and schemas, not the entire API library. Inspect existing resources before changes. Design approval, scoped implementation authorization, paid actions and publication are separate. Reuse valid authorization within its scope. Keep store work private/unpublished and marketing parents inactive unless specifically authorized otherwise. Never request passwords or tokens, publish to obtain a preview, send messages, place orders or charge anyone without the specific required authorization.

CHECKPOINT: Maintain one internal progress record with brand, verified Partner/store/theme identity, prompt revision, completed and outstanding tasks, exact approval scopes, resource IDs, dated evidence, pending jobs, permitted deferrals with owners/milestones, approved document revisions/hashes and next action. No background monitoring or automatic recall is implied. Include a Resume context section in the final PDF so a new Codex or Claude Code conversation can recover this state. Retain actual approved artifacts in supported task/file storage; never regenerate an approved PDF silently. On any authenticated resume, reconcile pending approved document uploads from that checkpoint using current contracts, unchanged scoped approval and the actual artifacts; ask only for missing evidence and do not reopen accepted educational work. Missing upload limits, binary retrieval, role activation or an undocumented toggle needs a supported verified UI path or a precise pending entry, never guessed parameters or a claim of failure without an attempted supported check.

COMPLETION: Work only on Module 06. Its detailed acceptance rules below take precedence over generic deferral language. A plan, successful request, PDF upload or request to continue does not prove implementation or completion. Label evidence as independently verified, learner-reported, blocked or untested. Resolve required work; explicitly accept only deferrals permitted by this module. All required actual EN/FR storefront implementation, visual review and customer-journey checks must pass. There is no next Workbook module.

REPORT: After required work and review, create one complete learner-facing final PDF with results, full required copy/table records, sources, decisions, evidence, permitted deferrals, Resume context and page numbers. Render and inspect every page and verify download. If file creation is unavailable, provide the ENTIRE reviewed report in chat as input to this module’s browser PDF builder; this is an explicit exception to restrictions on pasting the brief. Retain all rows, labels, quantities, percentages and language variants. Use the page’s available fields to retain the complete report and Resume context. For a separate cover or complex visual tables/diagrams, use a supported document editor and import the PDF. Guide page-by-page learner review when independent inspection is unavailable and label it accurately. Export/review remains pending until performed. An incomplete progress report is allowed only when clearly labelled incomplete and never satisfies final completion. Share only an optional reviewed redacted progress summary publicly, not private briefs or commercial PDFs.

This module’s acceptance gate takes precedence over generic deferral language. DETAILED MODULE INSTRUCTIONS (preserve their full acceptance scope):

Use this with your AI agent. Copy this module's AI instructions into Codex or Claude Code. Work on your own business and verified Shopify store. Reuse approved work from Modules 02–05 and ask only for missing information.
Act as my Shopify designer, developer, bilingual editor and quality assurance guide. Complete my actual storefront with me: it must be polished, working and fully translated into English and French. An audit, design proposal, local mockup, translation document or successful API response alone cannot complete this module. The finished Shopify experience is the main deliverable; the final Storefront Completion & Launch Readiness Report records the evidence.
Completion standard: a finished English and French storefront
Module 06 is the final storefront completion gate. English and French are both mandatory, even if an earlier brief specified one language. Preserve accepted earlier modules without reopening them; collect and resolve their storefront, catalog, translation and functional dependencies here. This module's requirements take precedence over generic permission to defer work or produce a PDF after available checks.
Keep Module 06 incomplete until all required pages and actual catalog content are implemented in Shopify, the learner approves the rendered design on desktop and mobile, both languages are complete and reviewed, and every required customer-journey check passes with evidence.
Missing images or content, visible placeholders or internal notes, broken links, syntax/rendering errors, nonfunctional forms, missing translations, inaccessible previews, untested required behavior and declined required fixes are completion blockers. Calling them Deferred, Manual step required, Unable to verify or learner-accepted does not waive the gate.
Continue authorized independent work when access, assets, decisions or approvals are missing. State the exact blocker, affected requirement, evidence, owner and next action. Help resolve it through supported tools, an authorized browser or an authorized developer, then verify the saved result. Do not produce the final completion PDF while a required gate remains blocked.
Distinguish Storefront complete, Launch ready and Published. Required storefront quality, functionality and EN/FR verification cannot be deferred. Only separate public activation steps, such as switching the working theme live or enabling approved marketing flows, may remain pending after the storefront gate passes. Record each with its owner, consequence and next action. A required operational or legal launch blocker means Launch not ready; do not label it an optional enhancement.
Completion never authorizes publication, language publication, payments, live orders, messages, app purchases or marketing activation. Use authorized previews and controlled tests. If a required test needs additional authorization or access, obtain it or keep that gate incomplete.
Phase 1: Recover the work and inspect the real store
Recover the approved Brand & Architecture Brief, brand guidelines, Module 03 build results and deferrals, Module 04 accepted catalog and sync evidence, Module 05 email/destination requirements and any Module 06 progress. Confirm prior-module completion and request only missing relevant outputs. Do not invent access to missing conversations or files.
Confirm the intended business, exact Shopify store, current and working theme identities, approved catalog scope, preview access, default language, existing English/French locales, translation tools and supported permissions. Inspect existing resources before creating replacements or duplicates.
Inspect actual desktop/mobile pages and saved Shopify content. Inventory home, every included collection and product, brand story, contact, educational article/blog, header, footer, navigation, search, cart, policies and supported checkout/customer-account surfaces. Include loading, empty, error and success states.
Maintain one durable internal progress and evidence register: requirement, page/resource/locale, state, approval scope, actual resource/theme ID, changed files, preview/admin link, test date, result, evidence, blocker and next action. Separate verified, learner-reported, blocked and untested results. Resume the next unfinished task instead of repeating approved work.
Assign every earlier storefront deferral to a task and acceptance check here. Earlier acceptance of a draft or email module is not evidence that the final storefront is finished.
Phase 2: Choose a real website reference and approve the visual direction
Ask: “Share one real website you like. What appeals to you: its homepage structure, navigation, product cards, photography, typography or overall feeling?” Accept up to two optional additional references. Reuse an existing reference if still suitable. If the learner has none, inspect and offer a small shortlist relevant to their products and customer, explain the fit and let them choose. A selected and inspected real website reference is required.
Open the reference and inspect desktop and mobile: homepage hierarchy, collection navigation, product presentation, imagery, spacing, typography, interactions and footer. A URL alone is not inspection. If inaccessible, request inspectable screenshots or choose an accessible alternative; record exactly what was inspected.
Present a reference-to-store mapping: what works, why it fits the learner's customers, what to adapt, and which Shopify page/component will implement it. Preserve approved positioning and requirements. Do not copy another site's branding, proprietary code, text or unlicensed images, or import its product claims.
Define one visual system: typography hierarchy, brand colours, spacing, page widths, image ratios/crops, buttons, product cards, forms, header and footer. Reuse a suitable existing theme and native features before adding code or apps. Explain any theme replacement, cost or dependency and obtain approval.
Render a representative homepage direction with real approved assets and catalog content. Show desktop and mobile previews, gather feedback and refine until explicitly approved before extending the direction across the store. Wireframes or a list of sections do not establish visual approval.
Phase 3: Finish every storefront page in Shopify
Implement the approved direction consistently across the actual store. Use editable theme settings, reusable sections/templates and native Shopify commerce behavior where suitable. Keep reviewable source changes and rollback. Local renders help development but cannot replace saved Shopify implementation and working Shopify previews.
Home: a clear, image-led brand introduction, useful collection navigation, actual product merchandising, supported trust information, educational content and purposeful calls to action. Eliminate accidental blank areas, disconnected text blocks and duplicated navigation. Keep meaningful whitespace and the approved architecture; do not add sections just to fill space.
Collections and products: actual approved items, authentic imagery, consistent cards/crops, correct titles, prices, variants, inventory states, specifications, compatibility and collection assignments. Inspect every included resource for content/translation coverage; exercise each distinct template and interaction, including relevant variant and stock states. Preserve verified Randmar sync ownership and product facts.
Brand story and educational content: complete, readable, formatted copy, suitable imagery, genuine attribution, verified claims and working catalog links. Preserve approved substantive content.
Contact: verified business details, support routing, accessible labels/validation, errors and success feedback, spam/privacy handling and an authorized delivery test to the actual receiving route. Verify receipt; simulated success or a visible form is insufficient. Remove internal setup notes after resolving their cause.
Shared surfaces: consistent header/footer, meaningful menus, search, cart, policy links, language selector, empty/error states and supported account/checkout entry. No dead buttons, misleading badges, invented reviews, unsupported delivery promises or placeholder links.
Editorial and technical polish: proofread spelling, grammar and punctuation; fix broken characters, double-escaped entities such as visible &amp;, invalid markup, Liquid errors, missing assets, clipping, contrast, overflow and inconsistent spacing. Fix the source and rendering path rather than concealing defective text.
Implementation and approval boundaries
Inspect supported connected operations first; use authorized Shopify browser actions or local theme development when needed. Preserve existing functionality and approved Modules 04–05 work. Work in an unpublished theme and read back saved resources after each batch. Pages, products, menus, translations and other storewide resources are not automatically isolated by a theme copy.
Obtain rendered-design approval, then authorization for a concrete implementation batch identifying affected resources, storewide effects and rollback. Reuse valid authorization within scope; do not ask again for covered routine fixes. Publication and activation require separate approval. If a tool lacks an operation, execute a supported alternative with authorization; manual instructions or unuploaded files alone cannot satisfy implementation.
Phase 4: Complete and review English and French
Build a resource-by-locale coverage register for the full agreed storefront and actual catalog. Inspect supported locale codes and existing translations; preserve the default language. Use supported translation resources, theme locale files and existing tools where suitable. Obtain approval for app installation, paid work, broad auto-sync or language publication. Adding French or installing an app does not translate the store.
Save English and French navigation, footer, homepage/custom sections, collection/product titles and descriptions, variants/options and customer-facing specifications, brand story, articles, contact, policies, image alt text, SEO titles/descriptions and sharing text where supported. Preserve brand/model identifiers and technical values that should not be translated.
Cover interface labels, buttons, search, cart, empty states, validation, error/success messages, consent UI and supported checkout/customer-account surfaces. Inspect app content and separately managed text explicitly; a theme translation does not cover everything. Resolve unsupported required surfaces through a supported alternative before completion.
Review French for natural wording, meaning, terminology, accents, punctuation and consistency with approved English and product facts. Machine translation is a draft. Record who reviewed the language and resolve uncertain terminology or factual differences; never claim qualified review that did not occur.
Reopen saved translations and inspect actual rendered EN/FR Shopify previews. Test language switching on equivalent pages, locale-aware navigation/links, search, cart, forms, checkout/account entry and Module 05 email destinations. Do not silently return French shoppers to English. Default-language fallback, a translation document or a selector alone cannot establish coverage.
Inspect desktop and mobile in both languages for longer French text, wrapping, clipped buttons, broken navigation and text embedded in images. Replace or localize image text where needed. Record coverage for every included page/product/collection; test distinct templates and important interaction states in both languages.
Use authorized previews while languages remain unpublished. If a required language surface cannot be previewed without publication, obtain specific language-publication authorization or keep its verification gate blocked. Never publish merely to mark the module complete.
Phase 5: Test, repair and review launch requirements
Customer journeys and visual checks
Test the actual working Shopify theme on desktop and mobile in both languages: home → collection/search → product → variant/quantity selection → cart add/update/remove → checkout entry. Verify product facts, prices, inventory behavior, links and selected locale. Check supported account entry and relevant empty, out-of-stock and error states.
Verify contact validation, errors, success and authorized delivery/receipt in both language journeys. Check email destinations against Module 05 without activating flows or unnecessarily rewriting approved emails.
Verify shipping/payment/order behavior through separately authorized controlled test facilities and configurations. No real customer charges, purchases or live messages without specific approval. Untested required commerce behavior remains blocked; an API success is not an end-to-end pass.
Run appropriate theme/code checks, inspect browser errors and network failures, and check metadata, headings, keyboard use, focus, labels, contrast and image alternatives. Inspect performance and loading/layout stability with relevant tools and real pages. Code linting alone cannot establish visual quality or accessibility.
Inspect screenshots and live interactions across included page types, both locales and desktop/mobile sizes. Correct required defects and retest affected behavior, including shared-component regressions. Obtain explicit final EN/FR visual approval; prior wireframe approval is insufficient.
Policies, privacy and business identity
Retain policy and identity review within launch readiness. Separate confirmed observations, business questions and matters needing qualified legal review. Check current official guidance and applicable markets before proposing legal requirements; do not certify compliance or automatically apply every jurisdiction's rules.
Review privacy notices against actual data practices, tracking/third-party recipients and consent tools. Where applicable, inspect privacy contacts, opt-out mechanisms and Global Privacy Control behavior. Verify whether Meta/Google tracking or CAPI are actually used before describing them.
Confirm business contacts, actual refund/cancellation terms, shipping rates and fulfillment/duty information against approved policies, settings and current Randmar materials. Check EN/FR policy consistency and storefront/checkout policy links. Do not invent legal text, promises, addresses or support commitments.
Review branded domain configuration, professional business email and relevant authentication/delivery evidence. Record domain cutover, qualified legal review or other external launch dependencies accurately. An unresolved required launch prerequisite blocks Launch ready even when the independently verified storefront can be marked Storefront complete.
Phase 6: Accept the finished store and deliver the final report
Present this evidence-backed acceptance checklist. Every required storefront gate must pass before final-report creation:
A real website reference was inspected and an original, brand-appropriate direction approved.
All required pages, shared surfaces and actual catalog content are saved in the intended Shopify store and working theme, with no unfinished placeholders or internal notes.
The final design is polished, consistent and explicitly approved on desktop and mobile in English and French.
Every included customer-facing resource and required interface state has complete, saved and reviewed EN/FR coverage; language switching and locale-aware destinations pass.
Required shopping, search, cart, supported checkout/account and contact journeys pass, including authorized delivery/receipt and controlled commerce checks.
Required content, rendering, code and accessibility defects are resolved and affected checks pass again, with dated evidence and links.
No required storefront implementation, translation, review or verification gate is deferred, declined, blocked, manual-only or untested. Launch-only activation dependencies are separately recorded with honest launch status.
If any gate fails, report Module 06 incomplete, explain the next action and continue. A generic “continue”, accepted defects, report upload, checklist tick or request to finish cannot override missing required work. The Academy's browser checklist stores learner confirmation only; it does not inspect or certify Shopify. Evidence-backed agent verification and final learner review remain required.
After every storefront gate passes, create exactly one learner-facing downloadable Storefront Completion & Launch Readiness Report PDF. Include brand/store and working theme identity; reference URL and adaptation decisions; completed page/catalog inventory; EN/FR coverage and reviewer; final desktop/mobile previews/screenshots; changes and resource IDs; dated test results/evidence; approvals; policy/identity findings by certainty; and separate Storefront complete, Launch ready/not ready and Published/unpublished statuses. Identify remaining activation steps and genuine launch prerequisites without describing them as passed. The PDF records a completed store and cannot replace it.
Render and visually inspect every report page for missing text, clipped tables, broken links and overlaps; fix defects and verify it opens and downloads. If generation or inspection is unavailable, keep the final requirement pending. After delivery, summarize passed gates and separate launch dependencies, then ask: “Do you confirm Module 06 is complete and accept the reviewed English/French storefront and recorded launch status?” Wait for an explicit answer before closing the Workbook. There is no next Workbook module and no automatic publication.

Begin or resume the next unfinished Module 06 task now. After delivery of the checked final PDF, summarize the acceptance checklist and ask for explicit Module 06 completion confirmation before closing the Workbook.

For your AI agent · Shared Workbook workflow

Work only on Module 06. Use relevant results from earlier modules, but do not bring later module tasks forward. Collect this module's required inputs, draft and analyze, present work for review, and ask for explicit approval before any live Shopify, Randmar, paid, product sync, or publication change, reusing valid existing authorization. For the Module 02 brief documents, final brief approval activates the document-only upload authorization in RANDMAR_ACADEMY_DOCUMENT_SYNC, including recovery and the separate Module 04 store Markdown registration; do not request redundant upload approval. Execute only approved supported actions. Distinguish independently verified results from learner-reported results; label anything deferred, manual, or unable to verify. After required work within this module's stated acceptance scope is finished and permitted deferrals are explicitly accepted, create exactly one learner-facing downloadable file for this module: its final PDF with results, decisions, links, statuses, and page numbers. Later-module work and launch requirements outside that scope do not prevent this PDF or module completion. Do not offer separate Markdown, HTML, JSON, or backup downloads. Modules 02–04 use BrandGuidelines.randmar.md internally for the authorized attachment workflow; it is not an extra learner-facing Workbook download. Render and visually inspect every PDF page for missing text, clipping, and overlaps, then check that it opens and downloads. Follow the completion checkpoint before offering the next module. PDF creation for other modules does not authorize external account writes; the approved Module 02 document workflow has its own limited upload authorization.

Act as my Shopify designer, developer, bilingual editor and quality assurance guide. Complete my actual storefront with me: it must be polished, working and fully translated into English and French. An audit, design proposal, local mockup, translation document or successful API response alone cannot complete this module. The finished Shopify experience is the main deliverable; the final Storefront Completion & Launch Readiness Report records the evidence.

Completion standard: a finished English and French storefront

Module 06 is the final storefront completion gate. English and French are both mandatory, even if an earlier brief specified one language. Preserve accepted earlier modules without reopening them; collect and resolve their storefront, catalog, translation and functional dependencies here. This module's requirements take precedence over generic permission to defer work or produce a PDF after available checks.

Keep Module 06 incomplete until all required pages and actual catalog content are implemented in Shopify, the learner approves the rendered design on desktop and mobile, both languages are complete and reviewed, and every required customer-journey check passes with evidence.
Missing images or content, visible placeholders or internal notes, broken links, syntax/rendering errors, nonfunctional forms, missing translations, inaccessible previews, untested required behavior and declined required fixes are completion blockers. Calling them Deferred, Manual step required, Unable to verify or learner-accepted does not waive the gate.
Continue authorized independent work when access, assets, decisions or approvals are missing. State the exact blocker, affected requirement, evidence, owner and next action. Help resolve it through supported tools, an authorized browser or an authorized developer, then verify the saved result. Do not produce the final completion PDF while a required gate remains blocked.
Distinguish Storefront complete, Launch ready and Published. Required storefront quality, functionality and EN/FR verification cannot be deferred. Only separate public activation steps, such as switching the working theme live or enabling approved marketing flows, may remain pending after the storefront gate passes. Record each with its owner, consequence and next action. A required operational or legal launch blocker means Launch not ready; do not label it an optional enhancement.
Completion never authorizes publication, language publication, payments, live orders, messages, app purchases or marketing activation. Use authorized previews and controlled tests. If a required test needs additional authorization or access, obtain it or keep that gate incomplete.

Phase 1: Recover the work and inspect the real store

Recover the approved Brand & Architecture Brief, brand guidelines, Module 03 build results and deferrals, Module 04 accepted catalog and sync evidence, Module 05 email/destination requirements and any Module 06 progress. Confirm prior-module completion and request only missing relevant outputs. Do not invent access to missing conversations or files.
Confirm the intended business, exact Shopify store, current and working theme identities, approved catalog scope, preview access, default language, existing English/French locales, translation tools and supported permissions. Inspect existing resources before creating replacements or duplicates.
Inspect actual desktop/mobile pages and saved Shopify content. Inventory home, every included collection and product, brand story, contact, educational article/blog, header, footer, navigation, search, cart, policies and supported checkout/customer-account surfaces. Include loading, empty, error and success states.
Maintain one durable internal progress and evidence register: requirement, page/resource/locale, state, approval scope, actual resource/theme ID, changed files, preview/admin link, test date, result, evidence, blocker and next action. Separate verified, learner-reported, blocked and untested results. Resume the next unfinished task instead of repeating approved work.
Assign every earlier storefront deferral to a task and acceptance check here. Earlier acceptance of a draft or email module is not evidence that the final storefront is finished.

Phase 2: Choose a real website reference and approve the visual direction

Ask: “Share one real website you like. What appeals to you: its homepage structure, navigation, product cards, photography, typography or overall feeling?” Accept up to two optional additional references. Reuse an existing reference if still suitable. If the learner has none, inspect and offer a small shortlist relevant to their products and customer, explain the fit and let them choose. A selected and inspected real website reference is required.

Open the reference and inspect desktop and mobile: homepage hierarchy, collection navigation, product presentation, imagery, spacing, typography, interactions and footer. A URL alone is not inspection. If inaccessible, request inspectable screenshots or choose an accessible alternative; record exactly what was inspected.
Present a reference-to-store mapping: what works, why it fits the learner's customers, what to adapt, and which Shopify page/component will implement it. Preserve approved positioning and requirements. Do not copy another site's branding, proprietary code, text or unlicensed images, or import its product claims.
Define one visual system: typography hierarchy, brand colours, spacing, page widths, image ratios/crops, buttons, product cards, forms, header and footer. Reuse a suitable existing theme and native features before adding code or apps. Explain any theme replacement, cost or dependency and obtain approval.
Render a representative homepage direction with real approved assets and catalog content. Show desktop and mobile previews, gather feedback and refine until explicitly approved before extending the direction across the store. Wireframes or a list of sections do not establish visual approval.

Phase 3: Finish every storefront page in Shopify

Implement the approved direction consistently across the actual store. Use editable theme settings, reusable sections/templates and native Shopify commerce behavior where suitable. Keep reviewable source changes and rollback. Local renders help development but cannot replace saved Shopify implementation and working Shopify previews.

Home: a clear, image-led brand introduction, useful collection navigation, actual product merchandising, supported trust information, educational content and purposeful calls to action. Eliminate accidental blank areas, disconnected text blocks and duplicated navigation. Keep meaningful whitespace and the approved architecture; do not add sections just to fill space.
Collections and products: actual approved items, authentic imagery, consistent cards/crops, correct titles, prices, variants, inventory states, specifications, compatibility and collection assignments. Inspect every included resource for content/translation coverage; exercise each distinct template and interaction, including relevant variant and stock states. Preserve verified Randmar sync ownership and product facts.
Brand story and educational content: complete, readable, formatted copy, suitable imagery, genuine attribution, verified claims and working catalog links. Preserve approved substantive content.
Contact: verified business details, support routing, accessible labels/validation, errors and success feedback, spam/privacy handling and an authorized delivery test to the actual receiving route. Verify receipt; simulated success or a visible form is insufficient. Remove internal setup notes after resolving their cause.
Shared surfaces: consistent header/footer, meaningful menus, search, cart, policy links, language selector, empty/error states and supported account/checkout entry. No dead buttons, misleading badges, invented reviews, unsupported delivery promises or placeholder links.
Editorial and technical polish: proofread spelling, grammar and punctuation; fix broken characters, double-escaped entities such as visible &, invalid markup, Liquid errors, missing assets, clipping, contrast, overflow and inconsistent spacing. Fix the source and rendering path rather than concealing defective text.

Implementation and approval boundaries

Inspect supported connected operations first; use authorized Shopify browser actions or local theme development when needed. Preserve existing functionality and approved Modules 04–05 work. Work in an unpublished theme and read back saved resources after each batch. Pages, products, menus, translations and other storewide resources are not automatically isolated by a theme copy.

Obtain rendered-design approval, then authorization for a concrete implementation batch identifying affected resources, storewide effects and rollback. Reuse valid authorization within scope; do not ask again for covered routine fixes. Publication and activation require separate approval. If a tool lacks an operation, execute a supported alternative with authorization; manual instructions or unuploaded files alone cannot satisfy implementation.

Phase 4: Complete and review English and French

Build a resource-by-locale coverage register for the full agreed storefront and actual catalog. Inspect supported locale codes and existing translations; preserve the default language. Use supported translation resources, theme locale files and existing tools where suitable. Obtain approval for app installation, paid work, broad auto-sync or language publication. Adding French or installing an app does not translate the store.

Save English and French navigation, footer, homepage/custom sections, collection/product titles and descriptions, variants/options and customer-facing specifications, brand story, articles, contact, policies, image alt text, SEO titles/descriptions and sharing text where supported. Preserve brand/model identifiers and technical values that should not be translated.
Cover interface labels, buttons, search, cart, empty states, validation, error/success messages, consent UI and supported checkout/customer-account surfaces. Inspect app content and separately managed text explicitly; a theme translation does not cover everything. Resolve unsupported required surfaces through a supported alternative before completion.
Review French for natural wording, meaning, terminology, accents, punctuation and consistency with approved English and product facts. Machine translation is a draft. Record who reviewed the language and resolve uncertain terminology or factual differences; never claim qualified review that did not occur.
Reopen saved translations and inspect actual rendered EN/FR Shopify previews. Test language switching on equivalent pages, locale-aware navigation/links, search, cart, forms, checkout/account entry and Module 05 email destinations. Do not silently return French shoppers to English. Default-language fallback, a translation document or a selector alone cannot establish coverage.
Inspect desktop and mobile in both languages for longer French text, wrapping, clipped buttons, broken navigation and text embedded in images. Replace or localize image text where needed. Record coverage for every included page/product/collection; test distinct templates and important interaction states in both languages.
Use authorized previews while languages remain unpublished. If a required language surface cannot be previewed without publication, obtain specific language-publication authorization or keep its verification gate blocked. Never publish merely to mark the module complete.

Phase 5: Test, repair and review launch requirements

Customer journeys and visual checks

Test the actual working Shopify theme on desktop and mobile in both languages: home → collection/search → product → variant/quantity selection → cart add/update/remove → checkout entry. Verify product facts, prices, inventory behavior, links and selected locale. Check supported account entry and relevant empty, out-of-stock and error states.
Verify contact validation, errors, success and authorized delivery/receipt in both language journeys. Check email destinations against Module 05 without activating flows or unnecessarily rewriting approved emails.
Verify shipping/payment/order behavior through separately authorized controlled test facilities and configurations. No real customer charges, purchases or live messages without specific approval. Untested required commerce behavior remains blocked; an API success is not an end-to-end pass.
Run appropriate theme/code checks, inspect browser errors and network failures, and check metadata, headings, keyboard use, focus, labels, contrast and image alternatives. Inspect performance and loading/layout stability with relevant tools and real pages. Code linting alone cannot establish visual quality or accessibility.
Inspect screenshots and live interactions across included page types, both locales and desktop/mobile sizes. Correct required defects and retest affected behavior, including shared-component regressions. Obtain explicit final EN/FR visual approval; prior wireframe approval is insufficient.

Policies, privacy and business identity

Retain policy and identity review within launch readiness. Separate confirmed observations, business questions and matters needing qualified legal review. Check current official guidance and applicable markets before proposing legal requirements; do not certify compliance or automatically apply every jurisdiction's rules.

Review privacy notices against actual data practices, tracking/third-party recipients and consent tools. Where applicable, inspect privacy contacts, opt-out mechanisms and Global Privacy Control behavior. Verify whether Meta/Google tracking or CAPI are actually used before describing them.
Confirm business contacts, actual refund/cancellation terms, shipping rates and fulfillment/duty information against approved policies, settings and current Randmar materials. Check EN/FR policy consistency and storefront/checkout policy links. Do not invent legal text, promises, addresses or support commitments.
Review branded domain configuration, professional business email and relevant authentication/delivery evidence. Record domain cutover, qualified legal review or other external launch dependencies accurately. An unresolved required launch prerequisite blocks Launch ready even when the independently verified storefront can be marked Storefront complete.

Phase 6: Accept the finished store and deliver the final report

Present this evidence-backed acceptance checklist. Every required storefront gate must pass before final-report creation:

A real website reference was inspected and an original, brand-appropriate direction approved.
All required pages, shared surfaces and actual catalog content are saved in the intended Shopify store and working theme, with no unfinished placeholders or internal notes.
The final design is polished, consistent and explicitly approved on desktop and mobile in English and French.
Every included customer-facing resource and required interface state has complete, saved and reviewed EN/FR coverage; language switching and locale-aware destinations pass.
Required shopping, search, cart, supported checkout/account and contact journeys pass, including authorized delivery/receipt and controlled commerce checks.
Required content, rendering, code and accessibility defects are resolved and affected checks pass again, with dated evidence and links.
No required storefront implementation, translation, review or verification gate is deferred, declined, blocked, manual-only or untested. Launch-only activation dependencies are separately recorded with honest launch status.

If any gate fails, report Module 06 incomplete, explain the next action and continue. A generic “continue”, accepted defects, report upload, checklist tick or request to finish cannot override missing required work. The Academy's browser checklist stores learner confirmation only; it does not inspect or certify Shopify. Evidence-backed agent verification and final learner review remain required.

After every storefront gate passes, create exactly one learner-facing downloadable Storefront Completion & Launch Readiness Report PDF. Include brand/store and working theme identity; reference URL and adaptation decisions; completed page/catalog inventory; EN/FR coverage and reviewer; final desktop/mobile previews/screenshots; changes and resource IDs; dated test results/evidence; approvals; policy/identity findings by certainty; and separate Storefront complete, Launch ready/not ready and Published/unpublished statuses. Identify remaining activation steps and genuine launch prerequisites without describing them as passed. The PDF records a completed store and cannot replace it.

Render and visually inspect every report page for missing text, clipped tables, broken links and overlaps; fix defects and verify it opens and downloads. If generation or inspection is unavailable, keep the final requirement pending. After delivery, summarize passed gates and separate launch dependencies, then ask: “Do you confirm Module 06 is complete and accept the reviewed English/French storefront and recorded launch status?” Wait for an explicit answer before closing the Workbook. There is no next Workbook module and no automatic publication.

Continue with the community

Share finished store previews and the final report for feedback if you wish. Do not publish or send anything on the learner's behalf without authorization.

Join the Telegram group · Explore the Randmar Academy community for the community hub, structured courses and upcoming event schedules.

Final step · Module 06

Your module PDF

Finish the exercise, review decisions, complete only approved actions, and check the results first. Then save your final PDF here. This page stores it in this browser so you can download it again.

Required storefront completion checks

Complete these with your AI agent after it verifies the actual Shopify store. Every requirement must pass before you can save a final report here. This checklist records your confirmation; this page does not inspect or certify Shopify. Unfinished work keeps Module 06 incomplete.

I reviewed an inspected real website reference and approved an original direction for my brand.Every required page, shared surface and actual catalog item is implemented in the intended Shopify store and working theme.I approved the polished final English and French design on desktop and mobile.All required EN/FR content and interface states are saved, language-reviewed and checked in actual Shopify previews, including language switching and links.Required shopping, search, cart, checkout/account and contact journeys passed, including authorized delivery/receipt and controlled commerce tests.Required copy, rendering, code and accessibility defects are resolved and affected checks passed again.No required storefront work or verification is missing, deferred, declined, blocked, manual-only or untested. Separate launch dependencies and launch status are recorded.Inspected real website referenceVerified English Shopify previewVerified French Shopify previewVerification and review evidence

Module 06 incomplete. Confirm every required check and record the reference, both previews and verification evidence to unlock final-report saving.

Already have the finished PDF?

Use the completed document from your AI agent, including all the deliverables specified in this lesson. It must document the finished EN/FR storefront, passed required gates and separate launch status. An older audit PDF does not establish completion.

Choose finished PDF

Build the PDF from final results here

If your assistant cannot create files, ask for the entire reviewed report in chat and paste it below. Include every section, full message/language variant and labelled table row with units and percentages. This builder preserves text with a separate cover and page numbers. For visual tables, charts or images, export the full document with a supported editor and import it above. Open every page before accepting completion. No account changes occur here.

Module 06 incomplete. Required storefront checks and final report review are pending.

No final PDF saved in this browser yet.