Check your store before launch | Keepsake documentation

Complete this checklist on your own store before publishing. A theme demonstration and automated theme checks do not prove your catalogue, apps, payments, phone experience or performance. Keep the theme unpublished while making changes and retain a copy of the theme you can return to.

1. Review your real content

[ ] Product titles, prices, variants, availability, descriptions and images match what you sell.
[ ] Materials, dimensions, care, lettering choices and what is included are accurate.
[ ] Making and delivery are explained separately. Shipping, returns and policy information match your real arrangements.
[ ] Example brand text, newsletter promises and sample service claims have been replaced.
[ ] Your logo, favicon, social destinations and sharing image are correct.
[ ] Sample photography has been replaced or intentionally removed. Turn off Theme settings → Sample photography → Show sample photos in empty image sections, then inspect the store again.

Expected result: removing samples does not leave an important product or buying explanation missing. Finish or hide any empty section.

[ ] Header → Main menu and the intended footer menus are selected.
[ ] Every menu item and visible button opens the intended resource. Test menu image cards and the phone menu as well.
[ ] Your story, gift guide, delivery and contact Pages exist, use the intended templates and have real content.
[ ] Each product uses its correct default or personalized template. Editing a template in preview has not been mistaken for assignment.
[ ] #how-it-works and #gift-finder links point to configured, visible sections.
[ ] The default shopping collection and any explicit collection links are correct.
[ ] Search, filters, no-results pages, pagination where applicable and empty bag links are useful with your catalogue.

Expected result: a shopper can reach a relevant product and return to shopping without a broken or misleading link. If assignment options are unavailable while the theme is unpublished, plan that final assignment step using Pages and navigation.

3. Review the visual design with difficult content

[ ] Inspect desktop, tablet-width and narrow-phone layouts using your own longest titles and headings.
[ ] White-background packshots and artwork edges remain visible using the appropriate image fitting.
[ ] Separate phone crops preserve the subject and meaningful lettering.
[ ] Text, input borders and button labels are readable in every color scheme you changed.
[ ] Use the page with a keyboard: menus, dialogs, product choices and bag controls remain usable, with a visible focus indication.
[ ] Check the page with reduced motion enabled. Important information does not depend on an animation.
[ ] Try film playback, pause, retry after a failed source, and the transcript or visual description on the devices you support.

Expected result: the actual content fits, controls remain accessible and film content has a useful fallback. A resized desktop browser does not replace testing on a real phone.

4. Test the complete shopping flow

[ ] Add an ordinary product, change its quantity and remove it. Check an unavailable variant and any minimum/increment rules that apply to your catalogue.
[ ] Try quick shop with a genuinely simple product. Confirm that a personalized product or one needing additional choices reaches its complete product page.
[ ] Submit a personalized product without its required answer and without spelling confirmation when enabled. The form should ask for the missing information.
[ ] Add the longest text you allow, punctuation and two differently personalized copies of the same variant. Confirm each line retains the correct answers.
[ ] Open Edit personalization in the bag, cancel once, then save a correction and inspect the updated value.
[ ] Save changed quantities and the order note with Update bag before continuing to another action. Reopen the bag and confirm the saved values.
[ ] Test both product-page extra rules: One per selection stays one for that selection; One for each item follows its main quantity.
[ ] Remove an extra independently, then remove a main product with its linked extras. Other gift selections should remain intact.
[ ] Add an extra from the bag suggestions and confirm it behaves as an independent product.
[ ] Check every automatic or code-based discount you plan to offer with the same product, gift and quantity combinations.
[ ] Repeat the flows with your installed cart, subscription or personalization apps. Test app-required fields and their payment routes.

Expected result: the bag's products, quantities, properties, extras, discounts and totals agree with your choices. If the bag reports that an update could not be confirmed, review the refreshed contents before retrying. Do not treat an error message as proof that nothing was added.

5. Complete a test order

Use Shopify's documented test-payment method for your payment provider. Do not use a real payment simply to check the theme. Payment test mode affects the store, including its live checkout, rather than only the unpublished theme. Arrange testing accordingly and restore live payment settings afterward. Follow Shopify's test-order guidance.

Prepare an order containing a standard product and a personalized selection with an extra.
Review the bag, then go through checkout with a test shipping address and your intended shipping method.
Complete the test transaction.
In Shopify admin, confirm the purchased variants, quantities, exact personalization, extra relationship, discounts, taxes and shipping.
Confirm that your fulfilment process or supplier receives the information it needs. The theme does not create production files or automatically approve a personalized design.
Remove test data and restore the appropriate payment configuration when you finish.

Expected result: the saved order agrees with the shopper's choices and can be fulfilled using your real process. Test separately any payment, discount or app route that differs from this order.

6. Check real devices and performance

Use at least the actual phone and desktop browsers important to your audience. Try touch controls, the on-screen keyboard, image enlargement, long personalization, bag editing and video. Inspect loading on a normal mobile connection, not only a fast development computer.

Measure representative homepage, collection and product pages with your own images and apps. If a page is heavy, review unnecessary sections, oversized media, third-party scripts and video use before changing design settings at random. These checks are tasks for your store; this guide does not claim that every device, app combination or performance target has already passed.

7. Publish deliberately and verify again

Save your final changes and reopen the editor to confirm they persist.
Keep a recoverable copy of the current theme and note the intended template assignments.
Confirm your store's real policies, customer-contact route and payment/shipping configuration are ready.
Publish the theme when your checks are complete, then finish any template assignments that depended on the published theme.
Open the public store in a fresh browser session. Recheck menus, one standard and one personalized product, the bag, language/market settings you use and the contact route.

Result: you have checked the published store, not just its editor preview. Keep notes of your test products, devices, discounts and app versions so later changes can be checked against the same flows.

If a check fails

Use Troubleshooting to isolate the affected setting or flow. For release changes, follow Updates and apps. A new theme file does not automatically rewrite your saved templates, catalogue or app configuration.