Introduction

Every custom product business has an implicit set of standards. Your experienced team members know how to interpret a customer's customisation notes, what a quality-check pass looks like, and how to handle a design that doesn't match expectations. The problem: that knowledge lives in people, not in your business.

When you hire someone new, they spend weeks absorbing what your experienced team takes for granted. When your best engraver takes annual leave, quality slips. When you're trying to train three people simultaneously to handle a growth surge, you're pulling your experts off production to teach instead of make.

Standard Operating Procedures—SOPs—are the solution. Not the long-winded corporate document kind, but the practical, step-by-step guides that let any trained team member perform any repeatable task to your standard, every time. For custom product businesses on Shopify, SOPs are the difference between a business that scales and one that hits a capacity ceiling it can never break through.

What a SOP Actually Is (And Isn't)

A SOP is a documented, step-by-step description of how a specific task is performed in your business. Its purpose is to transfer knowledge from people to process—so the business doesn't depend on specific individuals to maintain quality and consistency.

A SOP is not:

A mission statement or values document
A list of rules to comply with
A training manual that takes a week to read

A useful SOP is specific, short, and actionable. It describes exactly what to do, in what order, including common decision points and how to handle them. If someone could follow the SOP and produce acceptable output on their first attempt, it's a good SOP.

Why Custom Product Businesses Resist SOPs

Custom work feels, by definition, like it can't be standardised. Every order is different. The artistic and craft elements vary. How do you write a procedure for something that changes every time?

The answer is that what varies in custom work is the specific output—the customer's design, the name being engraved, the material chosen. But the process for delivering that output is largely repeatable:

How you read and verify a customer's customisation requirements
How you set up your equipment for a given material
How you check quality at each stage
How you package a completed order for dispatch

These process steps don't change because the design changed. Standardising the process gives your team a reliable framework within which the creative or craft variation happens.

The SOPs Every Custom Product Business Needs

1. Order Intake and Customisation Verification

This is your highest-impact SOP. Before production starts, someone needs to read the order, understand what the customer wants, check that all required customisation details are present and unambiguous, and flag any issues before the order enters production.

Most rework and customer complaints trace back to this step being done inconsistently. A clear SOP for order intake prevents orders entering production with missing or unclear customisation data—the single biggest source of errors in custom manufacturing.

Your order intake SOP should cover:

Where to find the customisation details for an order
What to check (completeness, legibility, potential ambiguities)
What to do when something is unclear (contact customer, contact manager)
How to confirm an order is ready for production

2. Production Steps by Product Type

Each distinct product type you make needs its own production SOP. This covers the step-by-step process of making the item: setup, materials required, specific technique notes, and quality checkpoints.

Include photos. A picture of what "correctly aligned text before engraving" looks like is worth ten sentences of description. Visual SOPs are faster to create and faster to use than text-only ones.

3. Quality Check

A quality check SOP defines exactly what "done and acceptable" looks like for each product type. Without this, quality check becomes subjective—what your best team member considers acceptable may differ significantly from what a new hire does.

Your quality SOP should include:

What to inspect (visual, dimensional, functional)
What acceptable tolerances look like (ideally with reference photos)
What to do when an item fails (rework criteria, who to inform)
How to record quality check outcomes

4. Packing and Dispatch

Packing is frequently treated as a low-skill task that needs no documentation. It often contains more customer-facing variables than any other step: unboxing experience, personalisation presentation, included inserts, correct labelling.

A packing SOP ensures that every order that leaves your workshop presents consistently to the customer, regardless of who packed it. For a custom product, the unboxing is part of the experience—getting it wrong on a handcrafted item is a significant let-down.

5. Problem Handling

What happens when a machine jams mid-run? When a material is out of stock after production has started? When a customer emails to change a customisation detail after production has begun?

Problem handling SOPs define decision trees for common exceptions so your team doesn't have to escalate every non-standard situation to a manager. "If X, do Y. If Y isn't possible, do Z and notify [person]." Clear escalation paths reduce the management overhead of running a custom production environment significantly.

How to Write a SOP That Gets Used

Most SOPs fail not because they're wrong but because nobody uses them. The reasons are usually:

Too long to read during work
Too abstract to follow practically
Not accessible at the point of use
Not kept up to date

To write a SOP that gets used:

Make it short. If a SOP for a single task runs more than one page, it's probably covering too much. Break it into smaller, task-specific SOPs.

Write it at the point of use. Ask the person who currently performs the task best to walk through it step by step while you document. The result is grounded in what actually happens, not what should theoretically happen.

Use photos and videos where possible. For physical craft tasks, a short video is often more valuable than a written SOP. A 60-second video of "correct machine setup for brass engraving" can replace two pages of written description.

Store it where it's needed. A SOP that lives in a Google Drive folder somewhere gets used when onboarding new staff and never again. SOPs should be accessible at the workstation where the task is performed—on a tablet, a laminated sheet, or a digital display.

Review and update. A SOP that doesn't reflect current practice is worse than no SOP—it creates confusion and reduces trust in the documentation. Review each SOP when the process changes, and do a full SOP audit at least annually.

Getting Your Team on Board

"We're going to write SOPs" is not always met with enthusiasm. Experienced team members may see it as bureaucracy, micromanagement, or an implication that their knowledge isn't trusted.

Reframe it: SOPs exist to protect the business from being dependent on any single person—including the business owner. They make the knowledge the business has built portable. They protect experienced staff from being the bottleneck for every question. They make onboarding new colleagues easier, which means experienced staff get better colleagues faster.

Involve your best people in writing the SOPs. They become the authors of the standard, not the subjects of it.

SOPs and Your Production System

SOPs describe what to do. Your production system is where the doing gets tracked. The two work together.

When your production pipeline has defined steps for each order, and those steps are backed by SOPs, your team knows exactly what to do at each stage without ambiguity. The checklist in your pipeline tool is a live reference to the SOP. Completing a step means the SOP was followed.

Route to Ship supports this with checklist-type steps inside each department's workflow — alongside simpler start/stop steps and approval/rejection steps where appropriate. A team member working a checklist step ticks each item off in order, rather than relying on memory or experience to know what to check. The pipeline tool itself isn't a SOP document store; the value is making the SOP visible at the moment of work, with the checklist standing in for what would otherwise be a laminated sheet on the bench.

Conclusion

SOPs are not a bureaucratic overhead. They're the infrastructure that lets a custom product business grow beyond the capacity of its most experienced people. They reduce error rates, speed up onboarding, make quality consistent, and protect the business from knowledge walking out the door.

The custom businesses that scale successfully are the ones that take the time to document what they know while it's still a manageable task—not after they've hired their tenth employee and the chaos has already set in.

Start with your order intake SOP. It will return more value than any other operational document you create.

References

[1] E-Myth Revisited, Gerber, M. (1986). HarperCollins.
[2] Shopify. How to Create Business Processes and SOPs for Your Ecommerce Store. Available at: https://www.shopify.com/blog/business-processes
[3] ASQ. What is a Standard Operating Procedure (SOP)?. Available at: https://asq.org/quality-resources/standard-operating-procedures