A structure for shared and per-store procedures, with a check for catching which store drifted first.
To manage multiple Shopify stores without drift, write the shared decision rules once and keep one SOP per store for the steps that differ. Then re-record each store's task against that store's own SOP, so a change shows up on the store where it happened.
Most advice on running several stores covers logins, app stacks and inventory sync. Those are real problems. They are not the one that quietly costs you money in month four.
The expensive failure is one procedure library covering three stores. Each store moves at its own pace. The document keeps describing whichever store someone happened to record first.
SOP drift is what happens when a written procedure stops matching the work it describes. With one store, that gap opens in one place. With three stores, it opens in three places, and not at the same speed.
Drift shows up three ways. Someone finds a quicker method and passes it along informally, so it never reaches the document. The admin or an app changes its screens, so the SOP's screenshots no longer match. Or a call gets made in chat that overrides the written rule, and the chat message wins because it is more recent.
Running several stores makes the second kind worse. Each store runs its own app stack and meets a platform change on its own schedule.
Our view: a procedure that is 80% right is worse than one that is obviously broken, because people follow it with confidence. On a second store, that 80% is usually the shared part, and the missing 20% is the screen that differs.
Shared steps record a decision: when to refund, when to escalate, what evidence to attach. Store-specific steps name a screen, a rate, a tax setting or an app.
Here is the test. If the step would still be right after you swapped that store's apps, it is a shared rule. If it names where someone clicked, it belongs to that store.
In practice the store-specific steps cluster in five places:
Separate app stacks are also why the per-store steps add up. Each extra store adds one more version to keep honest for every process that touches that app.
Month-end close is the clearest case. The decision rules are shared across stores. The payout reconciliation, the tax handling and the currency are not. The accounting SOP templates for month-end close and AP cover the shared steps for that process, and each store's version adds its own screens.
Point every store-specific step at a named screen. These are the places where multi-store differences actually live.
Markets. Shopify's Markets overview says each market has conditions, which define who it applies to, and customizations, which set the experience those customers get. A customer who matches no active market gets the backup region's experience instead. Name the market in the step, not just the country.
Users. A store role's reach is set with Edit store access, which decides which stores it covers. The same role name can mean different things on different stores.
Organization. Shopify says that when your stores are part of an organization, you can manage them with centralized users and billing. Billing is viewed in one place, but outside Shopify Plus each store is still billed and invoiced separately.
Flow. A Shopify Flow workflow lives on one store. You can export it and import it into another, but from then on each copy can change on its own, so each store's copy needs its own check. Turning on a workflow that uses secrets also needs the separate permission for managing connections and secrets.
The store switcher. The switcher in the admin top bar moves between stores. That convenience is part of the problem: switching stores does not switch the procedure someone is reading.
Shopify's store permissions apply at the store level. Each role covers only the stores you choose, and inside a store you can't limit it to particular orders, products or customers. There are two exceptions: app and channel permissions can be granted for specific apps or channels, and a B2B permission limits a user to the company locations assigned to them.
One area of the admin often needs several permissions before a task works end to end. When you assign a permission that depends on others, Shopify selects those too. Deselect a required permission and everything that depends on it is deselected as well.
Your plan decides who can do any of this:
So a store-specific step names the role, not the person. Who is accountable for the procedure is a separate question: the RACI chart example for a Shopify ops team treats the names on the chart as a starting point, not a standard. The IT SOP templates for access, backups and incidents are a starting point for the access steps on each store.
Try it on one of your own procedures.
Record a process once, AI writes the structured SOP. 3 free SOPs, no credit card.
Use two layers:
Keeping one SOP per store is what makes the re-recording check work. A recording made on one store only shows that store's screens. Compare it against a document that mixes three stores, and the other two stores' steps all look like changes.
The refund processing SOP for Gorgias and Shopify documents that process for a single store. Across stores, its refund rules become the shared standard and each store gets its own copy of the clicks.
Penn State Extension's guide to writing SOPs recommends that every SOP carry a clear title, the person responsible and the date it takes effect, and that businesses with many SOPs use a logical numbering scheme to track revisions. Add one more field for multi-store work: the store each SOP describes, named in the title.
A second location or a new international market changes what the Shopify admin does with every order.
Re-record the task on each store, then compare the recording against that store's SOP. Reading the document can't tell you whether the screens still match, because the document is the thing under suspicion.
Four events should start a re-check on the store where they happen:
Run the check store by store, one task at a time. The question is not whether the library is current overall. It is which store changed, and on which step. If a re-check on one store changes a decision rule rather than a screen, update the shared standard and then check every other store's SOP against it.
Our suggested default, not a Shopify rule: re-check every SOP that touches money or a customer on every store every 30 days. The trigger checks above cover what happens in between.
Name one person as the owner of each store's SOP, not a department and not "ops". When a store's SOP belongs to everyone, its drift belongs to nobody. On a second or third store, that is usually where trouble shows first: whoever runs the step hesitates exactly where the stores differ.
When the stores share almost nothing. If the shared standard shrinks to a line or two, the stores do not really share a process. Drop the shared layer for that process and run separate SOPs.
When nobody re-records. A comparison only covers the tasks you actually re-record. It says nothing about the procedures you did not touch this month.
When the change is in a setting, not a screen. ReccordSOP does not watch your Shopify, carrier, helpdesk or other app settings, so it will not flag that a market changed, a shipping rate moved or a staff role was suspended. Those live in the admin, and someone has to look.
When permissions differ. A step can be correct and still fail because the person running it is missing one of the several permissions that area needs. Test the step logged in as someone with that role, not as the owner.
Pick one process that runs on every store, most likely refunds. Write the shared rules once. Then record the task on each store as its own SOP, named for the store, and put one owner's name and a date on each.
ReccordSOP turns a screen recording into a numbered SOP with a screenshot for each step, so each store's version is faster to capture than to write by hand. Re-record the same task on that store later and it compares the new recording with the existing SOP, flagging which steps changed instead of overwriting it. Version history is kept, and workspace admins get an email once a published SOP passes 90 days without a review or edit.
The free plan covers 3 SOPs in total, enough to record one process on three stores. Team is $19 per user per month, with a 3-user minimum.
SOP drift is the gap between what a documented procedure says and what the team actually does. Across multiple stores, a shared document stays accurate for the store it was recorded on and quietly stops matching the others, as each store changes its apps, markets, rates and staff roles at its own pace.
No. If you have accounts on more than one store, the store switcher in the admin top bar moves between them. Grouping stores into an organization adds centralized users and billing. Custom organization roles need a Plus store or organization, a multi-store organization that is not on Plus, or a Partner organization.
On a single store not on Plus, only the store owner and users with the Administrator store role can manage users and roles. Stores on the Basic or Starter plans cannot add users or assign store roles at all.
Re-record it on a store as soon as something changes there: a screen change in the admin or an app, an app swap, a new market or domain, or a role change. Beyond that, our suggested default is to re-check every procedure that touches money or a customer on every store every 30 days. Reading the document does not count as a check. Only a fresh recording compared against it does.
3 free SOPs to start. No credit card required. See if drift detection keeps your docs honest.
Start for freeI built ReccordSOP after watching too many DTC ops teams lose months to undocumented workflows. These SOPs are battle-tested with Shopify operators running $1M to $50M brands.
Last reviewed November 7, 2026
Seven recurring Shopify ops tasks, one accountable owner each, and the permission every row needs. A chart only holds if the names and the procedures behind them stay current.
A refund starts in your helpdesk and ends in your store. The seam between them is where refund procedures quietly break.
A second warehouse or a new market changes how orders route, which rates show and what customers can buy. Here is what changes, and a four-pass check for the SOPs that stop matching.
We use essential cookies for sign-in and a small amount of analytics to improve the product. Privacy policy.