← All features SOPs & checklists

The procedure, next to
the exception to it.

Start from a library of retail procedures, turn the repeating ones into checklists that record who did what and when, assign them to people, and export or print the finished run as a PDF. Included on every plan.

LIBRARYStore openingStore closingGoods-in checkShift handoverReturnsRUN · TUESDAY 08:02Count cartonsM08:02Check sealsM08:05Photograph damageD08:11Book in to locationAFTERPDFPrintKeptassigned

Start from a template, not a blank page

The hardest part of writing a procedure is the empty page, which is why most stores never get past intending to. The template library is there so the first version of a procedure is an edit rather than an act of authorship.

Templates cover the recurring retail procedures: store opening and closing, shift handover, click-and-collect pickup, sales-floor replenishment, order fulfilment, returns and exchanges, receiving inventory. They are grouped by category, so you browse Inventory or Customer service rather than scrolling one long list, and filtered by whether you want an SOP or a checklist.

Every one is a starting point rather than a standard. Preview it, take it, then change it until it describes your store, because a procedure adopted verbatim from a library is one nobody follows for long.

TEMPLATE LIBRARYSearch templatesSOPAll categoriesRetail OperationsStore openingPreviewRetail OperationsStore closingPreviewRetail OperationsShift handoverPreviewOrder fulfilmentOrder fulfilmentPreviewInventoryReceivinginventoryPreviewCustomer serviceReturns andexchangesPreview
The template library, filtered by type and category.

Why these sit next to the conversation

Most stores keep procedures somewhere else: a shared doc, a folder, a tool somebody set up once. That arrangement works until the first time reality does not match the procedure, which is roughly every week.

When the exception arrives, the conversation about it happens in one place and the procedure sits in another, and neither updates the other. So the document slowly stops describing what the team actually does, and people stop opening it, and the fact that it is out of date becomes invisible because nobody is looking.

Keeping both in the same workspace does not magically fix that, but it removes the friction that causes it. The person who worked out the exception is one click from the page that should record it, and the page is where people already are rather than somewhere they have to remember to go.

SOPs are documents, not notes

An SOP page has a real editor: headings, formatting, images, the structure you need to write a procedure somebody can follow under pressure. It is a document rather than a long message, because a procedure without structure is one people read once and never return to.

Pages are internal only. Nothing written here is visible to customers, and nothing is published to your storefront.

The useful discipline is to keep SOPs to things that stay true. A page that mixes permanent policy with last Tuesday's decision teaches the team that documents are unreliable, and once they believe that about one page they stop trusting all of them. Time-sensitive things belong in a room; durable things belong here.

Checklists are templates that spawn runs

A checklist is defined once and started whenever it is needed, and each start creates a separate run. Monday's stock count is its own record, distinct from last Monday's, rather than the same list being wiped and reused.

That distinction matters more than it sounds. A checklist you tick and reset holds only the current state, so the question "did we actually do the Friday close last week" has no answer. A checklist that spawns runs keeps every one of them, and the answer is a record rather than a recollection.

Each item records who completed it and when. So a finished run is evidence: it says this was done, by this person, at this time. That is what makes a checklist useful for anything with a consequence, such as a goods-in check or a shift close.

GOODS-IN CHECKRun started 07:58, TuesdayCount cartons against the POMira08:02Check seals and outer damageMira08:05Photograph anything damagedDev08:11Book in to the right locationDev08:24Flag discrepancies to purchasingEach tick carries a name and a time.
A run in progress: who ticked each item, and when.

Where this fits against tasks

Tasks and checklists overlap enough to be worth separating clearly, because teams that confuse them end up with a board full of things that are not tasks.

A task is one piece of work with an owner and a due date. It happens once. Chase the supplier about PO 4471, photograph the damaged pallet.

A checklist is a sequence that repeats. Opening the store, closing the till, receiving a delivery, onboarding a new starter. The sequence is the same each time and the run is what varies.

The practical test: if you would write it out again next week, it is a checklist. If it is a one-off, it is a task. Putting recurring work on a task board means recreating the same items forever, which is the most common reason a board gets abandoned.

Assigning, exporting and printing

SOPs and checklists can be assigned to a named person, which is the difference between a library and a system. A manager sets who owns the store opening and who owns goods-in, and the assignment is recorded rather than remembered.

A finished run exports as a PDF, with the names and times intact. That matters more than it sounds for anything with a consequence: a goods-in check that produced a discrepancy, a closing routine on the night something went missing, a receiving record a supplier disputes. The export is the evidence, and it reads the same in six months as it did on the day.

Checklists also print, blank, for people who work away from a screen. A packing bench or a stockroom wall is a perfectly good place for a checklist, and pretending everyone works from a laptop is how operational tools lose the people who do the physical work. Print it, work through it, and record the run afterwards.

ASSIGNEDMMiraStore openingDDevGoods-in checkSSofiaReturns and exchangesWho owns which procedure, recorded.WHEN IT IS DONEDownload as PDFthe run, with names and timesPrint itfor the bench or stockroomKeep the recordevery run stored, not wiped
Assigned to named people, and three ways a finished run leaves the app.

On every plan, including Free

SOPs and checklists are available on every plan, including the free tier for up to five people. That includes the template library, assignment, and PDF export. They are not a reason to upgrade, because a procedure nobody can read is not much of a procedure and gating documentation behind a paid plan makes the tool worse at the job it is for.

What changes on paid plans is everything around them: message history beyond 30 days, private rooms and categories for scoping who sees what, and custom roles on Business+ for giving a seasonal hire or an agency exactly the part of the workspace their work needs.

answers

Common questions

Can I write SOPs in Store Huddle?

Yes. SOPs are rich document pages with a real editor, supporting headings, formatting and images, written for procedures somebody has to follow rather than for long-form prose. They are internal only and never visible to customers.

How are checklists different from tasks?

A task is one piece of work with an owner and a due date, and it happens once. A checklist is a reusable template for a sequence that repeats, and starting one creates a fresh run. If you would write it out again next week, it is a checklist.

Does a checklist keep a record of who did what?

Yes. Each item records the person who completed it and when, and each run is kept separately, so a finished checklist is evidence of what was done rather than a list that was ticked and reset.

Are SOPs and checklists on the free plan?

Yes, on every plan including Free for up to five people. Paid plans add unlimited message history, private rooms and categories, and custom roles on Business+.

Can I attach an order or product to an SOP?

Shopify resources attach to messages and tasks. An SOP describes how something is done in general rather than referring to one specific order, which is the distinction between a procedure and the conversation about a particular case.

Can I download an SOP or checklist as a PDF?

Yes. SOPs export as PDF, and so does a completed checklist run with the names and times against each item. That is what makes a finished run usable as evidence rather than only as a status.

Can checklists be printed?

Yes, blank for people working away from a screen, and again as a PDF once the run is finished. A packing bench is a reasonable place for a checklist and the app does not assume everyone has a laptop open.

Can I assign an SOP or checklist to someone?

Yes, to a named person, and the assignment is recorded. That is what lets a manager set who owns the store opening and who owns goods-in without relying on anybody remembering.

Are there ready-made templates?

Yes. The library covers the recurring retail procedures, grouped by category such as Retail Operations, Order fulfilment, Inventory and Customer service, and filtered by whether you want an SOP or a checklist. Take one and change it until it describes your store.

Does this work in Shopify POS?

No. Store Huddle runs inside Shopify admin. If your staff follow checklists from a till rather than a desk, a POS-native tool fits that better and we would rather say so than imply otherwise.

See it inside your own admin.

Free for teams up to five, and about two minutes to connect your store.