Checkout9 min read

Shopify Store Security Checklist for Merchants (2026)

A Shopify store security checklist for merchants: sign-in and staff access, apps, theme code, scripts and pixels, checkout, domain and email, and a routine to repeat.

In this guide
  1. The checklist at a glance
  2. 1. Sign-in: two-step authentication for everyone
  3. 2. Staff and collaborators: the fewest people with the least access
  4. 3. Apps: uninstall what you don’t use
  5. 4. Theme code: know who changes it and keep a way back
  6. 5. Scripts, app embeds and pixels: list what runs for shoppers
  7. 6. Checkout: settings, payment providers and where checkout ends
  8. 7. Store data: metafields, files, redirects and menus
  9. 8. Domain and email
  10. A routine you can keep
  11. Where Custos: Store Security Scan fits
  12. FAQ

A Shopify store security checklist covers the parts of the store you control, not Shopify’s servers: who can sign in to your admin and how, which apps have access, what code your theme, apps and pixels load into shoppers’ browsers, where your checkout goes, and whether your domain and email records are set up. Shopify runs and secures the platform and its checkout. Everything you add on top of it is yours to check, and the checks are worth repeating on a schedule, because apps and themes change without asking you.

This guide is the merchant-level list: what to check, where to find it in the Shopify admin, and how often. It does not need a developer, although a few steps are quicker with one.

The checklist at a glance

Area What to check How often
Sign-in Two-step authentication on every account, secure sign-in required Once, then for every new user
Staff and collaborators Who has access, with which permissions Monthly, and the day someone leaves
Apps Installed apps you still use, the access each one asked for Monthly
Theme code Who edits it, a copy before every change, unknown scripts After every edit, and weekly
Scripts and pixels Every script, app embed and pixel on the storefront Weekly, or after every app change
Checkout Checkout settings, payment providers, where checkout ends Monthly
Store data Metafields, files, redirects and menu links with code or odd links Monthly
Domain and email HTTPS, redirects, SPF and DMARC on your sender domain Quarterly

The sections below go through each row.

1. Sign-in: two-step authentication for everyone

A stolen password is the shortest way into a store. Every person with admin access should use two-step authentication, with an authenticator app or a security key rather than text messages. Shopify no longer lets you set up SMS as a new two-step method (Shopify Help Center).

The store owner can’t switch two-step authentication on for someone else’s account; each person sets it up for their own login. What you can do is require a secure sign-in method for each user in Settings > Users. Our Shopify staff permissions guide walks through that setting, the Shopify Payments rule on two-step authentication and what happens when you switch an existing user to “required”.

  • Owner account uses an authenticator app or a security key.
  • Every staff account has a secure sign-in method set to required.
  • Recovery codes for the owner account are stored somewhere safe and offline.

2. Staff and collaborators: the fewest people with the least access

Every staff account can do exactly what its roles allow on the live store. The risk grows with accounts that outlive the job and permissions given “just in case”: refunds, payment settings, app installs, theme editing and customer exports deserve the most care.

  • List every user in Settings > Users and remove anyone who no longer works on the store.
  • Give theme editing and app installs only to the people who need them.
  • Review collaborator accounts from agencies and freelancers after each project ends.
  • On the day someone leaves, remove their access before anything else.

The staff permissions guide has a monthly review routine and an offboarding list you can copy.

3. Apps: uninstall what you don’t use

Each app can read or change what its access scopes allow, and many apps also load code into your storefront. An app you stopped using months ago still has that access until you uninstall it.

  • Go through Settings > Apps and sales channels and uninstall apps nobody uses.
  • Before installing a new app, read the access it asks for on the install screen and ask whether the job needs it. Our services team wrote how to check a Shopify app’s security before installing it.
  • After uninstalling an older app, check your theme for code it left behind. App embeds and app blocks go away with the app, but code an app or a developer pasted into theme files stays until someone removes it.

4. Theme code: know who changes it and keep a way back

Your theme is code that runs on every page. Edits by staff, freelancers or apps that write to theme files are the most common way unexpected scripts end up on a store.

  • Duplicate the live theme before any edit, so you can publish the copy if something breaks.
  • Know that Shopify keeps older versions of each theme file in the code editor. If a file changed and nobody can say why, you can compare and restore it.
  • Look for <script> tags that load from sites you don’t recognise, mostly in layout/theme.liquid, snippets and the assets folder.
  • Ask anyone who edits the theme to tell you what they changed and why.

If you find code you can’t explain, our guide on how to find a malicious or injected script in a Shopify theme covers what to search for and what to do next.

5. Scripts, app embeds and pixels: list what runs for shoppers

The code that reaches shoppers’ browsers comes from three places: your theme files, app embeds and app blocks (switched on in the theme editor), and web pixels (under Settings > Customer events). App embed code is served by the app itself, so it can change when the app updates, while your theme file stays the same.

  • In Online Store > Themes > Customize > App embeds, check which embeds are on, and turn off any from apps you no longer use.
  • In Settings > Customer events, check every app pixel and custom pixel, and remove the ones you don’t need. Custom pixels run in a sandbox, but they can collect events on more pages than app pixels, checkout included, and you are responsible for their code (Shopify Help Center).
  • Open your store in a browser, open the developer tools on the Network tab, and note the sites that load scripts on the home page, a product page and the cart. Do it again after any app change and compare.

Doing the last step by hand once teaches you a lot about your store. Doing it every week is where most merchants stop, and it is the part a scan can take over.

6. Checkout: settings, payment providers and where checkout ends

Shopify hosts the checkout, and the card fields are Shopify’s own secure frame. What you control is the checkout configuration, the payment providers and the apps you allow to add to checkout.

  • In Settings > Checkout, check the customizations and checkout apps listed there, and remove any you don’t recognise.
  • In Settings > Payments, check that every active payment provider is one you set up.
  • Place an item in the cart and click Check out. The address bar should show your own domain or Shopify’s checkout, never another site. Apps that send shoppers to a checkout outside Shopify are a known risk; see checkout hijack apps.

If you accept cards and your acquirer asks about the scripts on your payment pages, read PCI DSS 6.4.3 and 11.6.1 for Shopify merchants.

7. Store data: metafields, files, redirects and menus

Code doesn’t only live in theme files. A metafield that holds HTML and is printed by the theme without escaping can put a script on every product page that uses it. A JavaScript file in Content > Files, a URL redirect to another site or a menu link to an unknown domain can do similar damage.

  • In Content > Files, check for .js or .html files nobody uploaded on purpose.
  • In Online Store > Navigation, check menu links that leave your store.
  • In URL redirects, check redirects that point to other sites.
  • Ask your developer whether any metafield that holds HTML is printed without the escape filter.

8. Domain and email

  • Your store loads over HTTPS, and http:// sends visitors to https://. Shopify issues and renews certificates for the domains it serves.
  • If you send email from your own domain, it has an SPF record and a DMARC record, ideally with p=quarantine or p=reject once you know your legitimate senders. Without them, anyone can send mail that looks like it comes from your store.
  • Your domain is not flagged by browser “dangerous site” warnings. Google’s Safe Browsing site status lets you check.

A routine you can keep

Security checklists fail when they are done once. A routine that fits a small team:

  1. Every week: compare the scripts, app embeds and pixels on your storefront with last week’s list.
  2. Every month: review users, apps, checkout settings and store data.
  3. Every quarter: check your domain, email records and recovery codes.
  4. After every change: after a theme edit, an app install or a developer’s work, check the scripts again.

Where Custos: Store Security Scan fits

Custos: Store Security Scan takes over the weekly script check and part of the monthly one. It reads your live theme for scripts from other sites and for code patterns used by card skimmers, lists your app embeds, and walks your store like a shopper: home, a collection, a product, search, the cart, the customer account and checkout up to the payment step. The first scan is your baseline; later scans report what is new, changed or removed, including a checkout that ends on a site that is not your store’s domain or Shopify’s checkout. It also checks metafields, files, redirects and menu links, your pixels and the sites they send data to, HTTPS, security headers, SPF and DMARC.

What it does not do:

  • It does not check your admin. Staff accounts, permissions, two-step authentication and admin activity are outside the scan. Sections 1 and 2 stay manual.
  • It does not change or remove anything. Its access is read-only, apart from one tagged test customer it creates for the walk. You make every fix yourself.
  • It cannot promise to find every kind of malicious code. It reports changes and known risky patterns on the pages it visits; what the scan cannot see lists its limits.

You can install Custos: Store Security Scan from the Shopify App Store and run the first scan in a few minutes. How the scan works explains each step.

FAQ

Is Shopify secure enough without any of this?

Shopify secures its platform, hosting and checkout. It does not choose your staff, your apps, your theme edits or your pixels. Most problems on a Shopify store come from those choices, which is why this checklist covers them.

How often should I review my Shopify store’s security?

Scripts and pixels weekly and after every change, users, apps and checkout monthly, domain and email quarterly. The schedule matters more than the length of the list.

Do I need a developer for this checklist?

No. Every step uses the Shopify admin or a browser. A developer helps with step 4 and the metafield question in step 7, where reading Liquid code makes the check faster.

What should I do if I find a script I don’t recognise?

Don’t delete it straight away. Note where it is and since when, find out which app or person added it, and follow the steps in how to find a malicious or injected script in a Shopify theme.

Does a security scan app make my store compliant with PCI DSS?

No. A scan gives you a record of the scripts on your store and alerts when they change. Whether your store meets PCI DSS is decided with your acquirer or assessor; see PCI DSS 6.4.3 and 11.6.1 for Shopify merchants.