Map ecommerce operations before you install another app

TL;DR: Map your ecommerce operations on one page before you install another app. List each stage from supplier to returns, score it for pain and frequency, and fix one problem properly. Forthsuite starts every engagement this way: scope the workflow first, then decide what to fix, automate or outsource.

Last updated: November 2026

Most small Shopify stores I talk to have between 15 and 30 apps installed. When I ask which ones they'd notice if they disappeared tomorrow, the answer is usually four or five. The rest were installed to fix a problem that was never really written down.

I made the same mistake with my own stores. Every time something broke, I went looking for an app. What I should have done first was spend an afternoon drawing the whole operation on one page. This is the method I use now, and it works for a one-person shop as well as a team of ten.

List the stages a product actually goes through

The real stages of your operation, from idea to after the customer has the product, belong on the page before you touch another app. For most physical product stores the list looks like the one below.

1. Find and vet a supplier
2. Forecast demand and decide how much to order
3. Raise a purchase order and pay
4. Receive stock, into your own space or a 3PL. If fulfilment is already outsourced, watch the 3PL from your Shopify data
5. Pick, pack and ship orders
6. Handle customer questions and delivery problems
7. Process returns and exchanges
8. Deal with slow stock and dead stock

Your list might be shorter. Dropshippers skip receiving. Print on demand skips most of it. That's fine, just write your real stages.

Fill in five columns for every stage

For every stage, a named owner, a tool, a trigger, weekly time, and the last two failures tell you more than a process diagram. Make a row and answer each of the five prompts below.

• Owner. Who actually does it. A name, not "the team."
• Tool. Where it happens: an app, a spreadsheet, email, WhatsApp, someone's head.
• Trigger. What starts it. "Stock drops below 40 units" is a trigger. "When I remember" is also a trigger, and an honest one.
• Time per week. Rough hours. Guess, then check it for one week.
• What goes wrong. The last two times this stage failed, what happened and what did it cost.

The "what goes wrong" column is where the value is. People are usually surprised by how specific it gets. "We ran out of the black medium in March because the reorder spreadsheet hadn't been updated since January" is far more useful than "inventory is a problem."

Mark the hand-offs between tools

Most operational mess lives in the gaps between tools, not inside them. Draw an arrow between each pair of stages and ask what information has to cross it.

Forecast to purchase order needs quantities and dates. Shipping to customer service needs tracking numbers. Returns to inventory needs to know whether an item can be resold.

Every hand-off that depends on someone copying data from one place to another by hand is a likely failure point. Circle those in red.

Score pain and frequency, then pick one problem

Score each stage from 1 to 5 for pain and for frequency, multiply them, and pick one candidate to fix — not three. Anything at 15 or above is a candidate, and one problem fixed properly beats three half-installed apps.

Decide whether to fix, automate, outsource or leave it

For the stage you picked, the choice is fix the process, automate it, outsource it, or leave it with a checklist.

• Fix the process. Often the answer is a clearer trigger or a single owner. Free, and it's surprising how often this is enough.
• Automate it. Worth it when the step is repetitive, rules-based and happens weekly or more. Reorder points and return labels are good examples.
• Outsource it. Worth it when the step needs skills you don't have and don't want to build, like warehouse work or reading supplier records in Chinese.
• Leave it. If it scores low and happens twice a year, a checklist is fine.

Before buying anything, write down what "fixed" looks like in a number. "Stockouts on top 20 SKUs drop from four a quarter to one" gives you a way to tell whether the change worked.

Watch for four common mapping mistakes

Map what actually happens, count your own time, and revisit the page every six months.

• Don't map the process you wish you had. Map what actually happens, including the workarounds.
• Watch for single points of failure. If one person is the only one who knows how purchase orders get raised, that's a risk even if it works today.
• Count your own time. Founders tend to price their hours at zero. Use a real hourly rate, even a modest one.
• Revisit it every six months. Stores change. A map from last year is out of date.

Where this method comes from

This mapping exercise is how I start every engagement at Forthsuite, the custom supply chain operations service I founded. We scope the workflow first, agree what's in and out, and only then quote and build — it's custom work, not a packaged software bundle, and often the map alone shows a merchant they need a better process, not more tools.

You don't need anyone's help to do the first version, though. Get a big sheet of paper, block out an afternoon and fill in the five columns. You'll probably uninstall a few apps by the end of it.

If you want a second pair of eyes on the map, start with an operations audit.

Frequently Asked Questions

Do I need another Shopify app before I map my operations?

No. Map the workflow first. List each stage, score pain and frequency, and pick one problem. Only then decide whether to fix the process, automate it, outsource it, or leave it. Installing an app before the map usually just adds another tool to a problem you haven't written down.

How long does this operations mapping exercise take?

An afternoon is enough for a first version. Write the stages, fill in owner, tool, trigger, weekly time and recent failures, then mark the hand-offs. You can refine the scores after you watch the process for a week.

What should I do after I score the stages?

Pick one. Multiply pain and frequency, treat anything at 15 or above as a candidate, and fix that one properly. Write down what "fixed" looks like as a number before you buy a tool or hire help.

Is Forthsuite a Shopify app I can install?

No. Forthsuite is a custom supply chain operations service. We scope your workflow first, agree what's in and out, and only then quote and build. The mapping method in this article is the starting point, and you can do the first version yourself.