How to use Shopify theme detector | Checkout Club¹⁰¹

The pass

Paste the store URL. Open Shopify theme finder and do it in this order.

Paste the store URL, not a screenshot of the theme list. The finder reads the public storefront.
Note the theme name and whether it is Theme Store or custom. A name like “Copy of Dawn” should still resolve to Dawn.
If it is a Theme Store theme, open the product template in the theme editor and see which sections sit above the product form. That is the work, not a rebuild.
If it is custom, ask for the theme files before you estimate. The finder cannot see how heavily the sections were edited.

The mistake that wastes the pass

Quoting a custom rebuild because the theme was renamed. Read the finder before the proposal, not after the call.

How you know it worked

The name you put in the proposal is the name the finder returned, including when the merchant had renamed the theme. If you wrote “custom” and the finder says Dawn, the pass failed.

Open the named theme on the product template

Start in Shopify admin, then Online Store, then Themes. Find the theme whose public name matches the detector, not merely the nickname in the list. Click Customize. Open the product template dropdown and choose the template assigned to pet grooming glove. If you are unsure which template the product uses, open the product in admin and read its theme template field before you wander the dropdown. Editing the default template while the stand uses another one is the most common wasted hour after an otherwise correct theme name.

Stay on that template until you can see the product form. Select it. Confirm it shows title, price, variant picker, and buy buttons, or write down the app block that replaced it. Then scroll the section list from top to bottom and type the order into a note. Include sections that are disabled only if you might turn them on. A disabled section is still part of the theme. It is not part of the buyer page until you enable it.

Do this on the published theme when you want to know what buyers see. Do it on an unpublished duplicate when you want to try a change. Say which copy is which at the top of the note. A screenshot without the theme name and the template name becomes useless the day someone duplicates the theme again. Put both names in the filename if you save images.

If the detector said Theme Store, you may open a fresh install on a development store later to see the original section list. That comparison is optional and manual. The detector already finished its work. If the detector said custom, skip the fresh-install comparison against Dawn unless you are deliberately considering a move to Dawn. Comparing a custom build to Dawn section names will invent gaps that are really just different names for similar regions.

What to write down before you change anything

Write five lines before you drag a section. Line one: public theme name, and Theme Store or custom. Line two: the admin nickname, so the next person can find the row. Line three: published or unpublished. Line four: product template name, and the product you opened. Line five: whether the product form is the theme form. These lines are dull. They are also the difference between a brief someone can execute and a chat message that says the product page feels off.

Add a sixth line for the job you actually want. For pet grooming glove, that line might be "add a materials section under the gallery" or "stop stacking a second price near the form." A job without a block name turns into a theme argument. A block name without a theme name turns into edits on the wrong copy. Keep both.

Write what you will not do in this pass. Examples: you will not publish a different theme, you will not edit Liquid, you will not install an app to create a heading the theme already has, you will not treat the result as a speed test. Constraints keep a helpful coworker from "improving" the shop while you are only trying to record it. Constraints belong in the note, not only in your head.

Store the note where the person who edits the theme will see it next week. A slide deck that nobody opens is not a record. A sentence on the product in an internal doc, next to the template name, is a record. If a freelancer will touch the theme, send the five lines before the call so the call is about the section, not about rediscovering Dawn.

Check the form, then the sections around it

On the product template, read the price the form shows and match it to the product in admin. For a listing at 24, a mismatched price means you are previewing the wrong product, the wrong market, or a draft. Do not restyle a preview that is not the offer. Choose a variant if the product has finishes or sizes. The picker should change the available choice without losing the buy button. If it does not, the form is the problem to document, and a new hero section is a distraction.

Then walk outward. Note the section directly above the form and the section directly below it. Those two neighbors decide whether the buyer sees the price next to a photo or next to a wall of badges. If you want a materials note, see whether an existing rich text or collapsible section can hold it. Adding a section is allowed. Duplicating the same words in three sections is how the template gets long without getting clearer.

Look at the mobile preview inside the editor before you leave. Theme editor desktop view hides stacking problems. The form, the variant labels, and the buy button should remain obvious without a hunt. You are not scoring the page. You are checking that the four form jobs are still visible after the section order you intend. If you have not changed anything yet, this preview is your baseline. Save it.

If a section is an app block, write the app name beside the section name. You still do not need the full app list to finish a theme note, but an unnamed app block will confuse you when it disappears after a theme duplicate. The app name in the section list is enough for this pass. A fuller storefront list is a different session.

Recheck embeds when the theme copy changes

After you duplicate a theme, open the duplicate, open theme settings for app embeds, and read which embeds are on. Compare that list to the published theme. Turn on only the embeds the duplicate needs for an honest preview. Then reload the product preview. If the preview gains a review strip, a chat bubble, or a banner you did not add as a section, an embed did that. Note it so you do not redesign around a ghost that only exists on one copy.

After you publish a theme, repeat the embed check on the theme that is now live. Visit the product URL in a normal browser, not only inside the editor. Editor preview and the live URL can disagree when an embed is off on the published theme or when you are logged in as staff. The buyer path is the live URL. The form should still show title, price, variants, and buy buttons there.

If an embed you expected is missing, confirm the app is still installed, then enable the embed on this theme. Installation without the embed is a normal Shopify state, not a broken detector result. The theme detector never claimed to carry embeds across themes. Your note claimed you would check. This is that check.

When an embed hurts the layout, disable it on the theme you are editing and reload. Do not uninstall the app in the same minute unless you already know the shop can live without it. Disabling on one theme is reversible and local. Uninstalling affects the shop. The theme pass prefers the reversible move until someone who owns the app agrees.

How you know the theme note held up

The note held up when another person can open the same theme, the same template, and the same product, and see the same form and the same section order you described. Ask them to do that without you on the call. If they land in the right place, the names were specific enough. If they land on the homepage or on the wrong theme copy, the note failed and the fix is more precise names, not a new detector run.

The change held up when the live product URL for pet grooming glove shows the section edit you wanted and the form still sells. Pick a variant. Read 24. Confirm the buy button is the button you expect. Look once on a phone-width window. You are looking for agreement between the note and the URL, not for a lift you did not measure. If you want to know whether the edit helped orders, that is a later comparison of periods you define yourself. Do not invent that comparison here.

The migration held up, if you did one, when the published theme name matches the theme you meant to publish, embeds you still need are on, alternate templates are assigned, and the product form is intact. Run the public theme check again after publish if you want the nickname and the public name side by side in the record. A match to the theme you just published is the success condition. A prettier homepage with a missing variant picker is not.

Stop when the written names, the editor, and the live URL agree. More screenshots will not make them agree. If they disagree, fix the pointer: wrong theme, wrong template, or unpublished preview. Only then discuss taste. Taste conversations on top of the wrong template feel productive and change nothing buyers see.