No growth-hacking. Just how the operational side of a Shopify business actually works, written by people who have done the fulfilment shift.
Team chat · Teams · Operations · Inventory · Comparison · Agencies · Launches · Fulfilment
Every Shopify plan caps staff accounts. What the cap actually restricts, the four ways teams work around it, and which of those are safe.
A second location doubles the staff and more than doubles the coordination. The four things that break first, and the structure that prevents most of it.
Most team tool frustration is a sorting problem, not a tool problem. Three questions that tell you where something belongs before you pick where to put it.
An alert everybody ignores is worse than no alert, because it looks like coverage. How to tell whether yours have crossed that line, and how to fix it.
New tools rarely fail on features. They fail in the fortnight where half the team has moved and half has not. How to get through it.
Offboarding catches the people who leave. It misses everyone whose role changed, whose project ended, or who was added for one afternoon in March.
Your store trades while nobody is working. What genuinely needs a response overnight, what can wait until morning, and how to cover the difference.
Most operations advice assumes a team big enough to need it. What actually matters when there are two of you, and what to ignore until there are four.
Wholesale orders look like retail orders in your admin and behave nothing like them. Where the retail process misroutes them, and what to do instead.
Every problem suggests an app and every app adds a place to check. A test for whether a tool earns its place, and the smallest stack that works.
Most fulfilment problems are ownership problems wearing a logistics costume. A step-by-step map of who decides what between a paid order and a delivered parcel.
A third-party warehouse is an operations team you cannot see. What has to flow each way, at what cadence, and what to do when the portal disagrees with reality.
The question is not which is cheaper per order. It is which failure mode you would rather manage, and what each choice does to your team's day.
A parcel stops moving and nobody notices for four days. A simple detection rule, a routing decision, and what to do before the customer emails you first.
Your reorder point is only as good as the lead time you feed it. Why the number suppliers quote is usually wrong, and how to build one that is not.
Who can commit money, what a PO has to contain, and where it lives so that the person receiving the delivery knows what was supposed to arrive.
Most inventory accuracy problems are created on the loading bay, not on the shelf. What to check, what to record, and who to tell when the numbers disagree.
When you never touch the stock, your supplier is your operations team. What to agree before the first problem, and what to tell a customer when you do not know.
App affiliate programs are the most overlooked revenue line in an agency. How they work, what separates a good one from a bad one, and how to build referrals into delivery.
What the Shopify Partner Program actually pays app developers, what changed with the revenue share, and the part that trips people up: app affiliate programs are something else entirely.
Slack and WhatsApp are good at messages. Store staff do not have a message problem, they have a context problem. What that costs, and how to fix it.
Two completely different products share a name. One talks to customers, one talks to your team. Picking the wrong one wastes a budget cycle.
Most stores have one channel doing four jobs badly. Splitting them takes an afternoon and stops the two failure modes that actually cost money.
An honest decision guide, including the cases where the answer is no and you should keep the tool you have.
The argument for keeping the conversation where the orders are, and the honest trade-offs of doing it.
A fair look at the realistic options, including the case for staying on Slack, which is stronger than most vendor blogs admit.
It is the most-adopted team tool in retail and the least examined. Four problems worth knowing about before your team gets bigger.
You do not need a board, a sprint, or a methodology. You need three fields and a habit.
A fixed number for every product is why your alerts get ignored. Here is a threshold rule that adapts to how fast things actually sell.
The permissions conversation most stores have after something goes wrong. Worth having before.
Written for stores without a war room, a duty rota, or anyone whose only job is coordination. Start it in September.
Five lines, same order every time. A template you can copy, plus the reasoning behind each line.
Seven questions worth asking before you install anything, each tied to a specific thing that goes wrong when the answer is no.
An honest teardown of the Slack and Shopify combination, including the parts that work well enough that you should probably keep them.
Less about features, more about process. How to build a shortlist, run a trial that tells you something, and avoid the evaluation that never ends.
Teams is close to free if you already pay for Microsoft 365, which makes it the default for a lot of stores. Whether that default is right depends on three things.
One group chat works beautifully for four people and badly for twelve. The failure is mathematical rather than cultural, and it arrives on a schedule.
Discord is free, fast and excellent at voice. It is also built for communities rather than operations, and that difference shows up in specific places.
Access is two decisions: what someone can change in the admin, and how much of the conversation they see. Collapsing them is how over-permissioning starts.
The answer depends on one thing: whether your work arrives as a plan or as an interruption. Most store work arrives as an interruption.
Everyone knows the group chat is not the right place for this. Everyone keeps using it. The reason is not laziness, and understanding it changes what you do about it.
A migration plan built around the two things that actually kill migrations: parallel running, and the belief that you need to bring everything with you.
Free tiers are genuinely good now. The question is which limit you hit first, and whether hitting it costs more than the subscription would have.
Three fixed points in the day, about twenty minutes total. Built for teams too small to have a manager and too busy to have meetings.
A one-page ownership map that takes an hour to build and prevents the most common category of dropped work. Includes a starter grid you can adapt.
Most standups fail because they are status theatre. Three questions, a hard time limit, and an async version for teams that never overlap.
Not what an escalation should say, but who is allowed to decide what. A decision-rights map for teams where the owner is not always reachable.
Most SOPs are written for the author, not the reader. How to write one for the moment it gets used, which is always a bad moment.
Privacy has a real cost that nobody prices in: everyone outside the room loses context. A default and four cases where breaking it is right.
You have four hours and they start Monday. What to teach, what to leave as reference, and the access decisions to make before they arrive.
Not a metrics dashboard. Four questions that catch the slow problems a daily routine is structurally unable to see.
The engagement ends, the invoice is paid, and the access stays live for years. A checklist and the reason this specific task is always the one that slips.
A flagged order is a decision, not an emergency. A procedure that gets you to hold, verify or fulfil without guessing and without insulting a real customer.
Assume the sale has already gone wrong and work backwards. Forty-five minutes before a promotion that prevents the failure everyone repeats.
Most alert fatigue is an audience problem rather than a threshold problem. Route by who can act, not by who might be interested.
What the indicators mean, which ones deserve weight, and why the location signals produce most of the false positives you are cancelling on.
Every vague delay message creates support work. What to say, when to say it, and the one number customers actually want.
Four numbers turn reordering from a judgement call into arithmetic. Most stores already have three of them.
The engagement ends and the relationship goes quiet, then a problem arrives cold nine months later. What to set up at handover so that call is not the first contact.
Adding a contractor to everything is the fast path and the one that creates the problem. How to set up a boundary that takes two minutes and survives the engagement.
Clients hear insurance, agencies mean capacity, and the two never quite meet. A framing that makes the conversation shorter and the arrangement last longer.
Hiring is not always available. What to do when the volume is coming and the headcount is not, without simply asking everyone to work harder.
Most retros produce a document nobody opens in eleven months. Four questions, one page, and the one habit that makes the findings survive until they are needed.
The wave arrives about a week after the holidays and lasts a month. What to decide in December so January is a process rather than a surprise.
Pre-orders move cash forward and move risk onto your operations. The four commitments that cause the trouble, and how to word them so a slip is survivable.
Someone has to answer the messages between Christmas and New Year. How to cover a quiet-but-not-closed period without one person silently absorbing all of it.
If an alert cannot be acted on within five minutes of arriving, it is a report, not an alert. Here is how to tell them apart and where each one belongs.
Twelve items, each with a named owner. Copy it, cut what does not apply, and never rebuild it from memory again.
Most escalations fail because they are a forwarded email. Four things to include so the person receiving it can decide immediately.
A flat threshold across the catalogue guarantees you get alerted too late on fast movers and constantly on slow ones. Set it by velocity instead.
Store ops is a judgement job, not a process job. Three interview questions that reveal whether someone has it.
Scoped channels beat weekly status calls. How agencies run client comms on the narrowest Shopify access the work needs.
The best post, the notable releases, and nothing else. Unsubscribe in one click.