A vase arrives in three pieces. Someone has to make the customer whole, and someone has to work out whether the carrier or the supplier broke it.
In a two-person company, this is easy. One person reads it, replies, ships a replacement, remembers to chase the courier. The whole case fits in one head.
At six people it stops fitting. Support replies and offers a replacement. The warehouse is asked, in Slack, whether there is another vase in stock — and answers four hours later in a thread that has moved on. Someone says they will file the carrier claim. Nobody writes down who. Two weeks later the customer emails again, politely, because the replacement never shipped, and the person who reads that email is not the person who took the original message and has no idea what was promised.
Nothing here is incompetence. It is a system problem: there is no single place where the state of that case lives.
Why everyone reaches for a helpdesk
The obvious fix is to buy software, and the software that markets itself to Shopify merchants for anything involving an unhappy customer is a helpdesk. The pitch is compelling and largely true — one place for customer problems, assignment, history, no more lost threads.
So teams sign up for a helpdesk, connect the inbox, and discover a few months later that the order problems are still slipping. Usually they conclude they configured it wrong.
Often they did not. They bought a tool for a different shape of problem.
What helpdesks are genuinely excellent at
This is worth saying plainly, because a lot of readers should buy one.
A helpdesk solves inbound conversation volume. If customer messages arrive across email, live chat, SMS, Instagram and Facebook, a helpdesk collapses that into one queue, which is transformative and hard to replicate.
It solves shared responsibility for a queue. Assignment rules, agent workloads, response-time targets, saved replies for the sixtieth “where is my order” of the day. If you employ people whose actual job is answering customers, this is the category you want and nothing else comes close.
It solves history against a customer. Every past conversation, in one timeline, when the same person emails a year later.
If you are drowning in inbound messages, stop reading and go buy a helpdesk. This article is not for you.
Why order problems don’t fit that shape
Order issues are a different animal from support conversations in three specific ways.
They are cases, not conversations. A support ticket wants to be answered and closed — the goal is a reply. A damaged-order case wants to be progressed: investigated, evidenced, claimed against, replaced, reconciled. It has stages. It can sit for two weeks legitimately waiting on a supplier while nobody sends a single message. In a ticket queue, silence looks like neglect. In a case system, “awaiting supplier” is a valid state with a date attached.
The people who resolve them often never touch the inbox. The warehouse lead who checks how it was packed. The ops manager who files the carrier claim. The founder who wants to know how often this happens with one particular supplier. These people need to see and update the case. They do not need — and will not use — a customer messaging tool. Asking a warehouse lead to log into a support platform to update one field is a request that quietly never happens.
The pricing model is a red herring. The adoption problem is not. It is tempting to blame per-seat pricing, and on Zendesk, Freshdesk or Help Scout that is a genuine cost — every occasional viewer is another line item every month. But Gorgias, the one most Shopify merchants are actually weighing, charges by ticket volume and states plainly that it is never priced per agent. Free seats do not fix this. The warehouse lead still will not open a customer messaging tool twice a week to update one field, and the answer still stays in Slack. The barrier was never the invoice. It is that the tool is shaped around conversations they are not having.
The result is a well-run helpdesk with an order-issue problem still leaking out the sides of it.
The middle option nobody names
There is a real gap between “order notes and a spreadsheet” and “a full helpdesk,” and most small teams belong in it. The thing that fits there is an internal issue tracker.
It is not a customer messaging tool. Customers never see it. It is an internal board where an order problem becomes a tracked object with an owner, a status, a history and a home — sitting where your orders already are, rather than in a separate application.
Concretely, it is the answer to who owns this and what is it waiting on, asked about a specific order, answerable in five seconds by anyone on the team.
That is a narrower job than a helpdesk does. Narrower is the point. A tracker will not manage your inbox, will not route chats, and has no business trying. It handles the internal half of the problem — the half that helpdesks handle least well and spreadsheets handle only until you have more than one person.
Who should not use one
Worth being direct, because the category is easy to oversell.
If most of your problems arrive as inbound email or chat and you have no shared inbox, get a helpdesk. A tracker assumes the conversation is already handled somewhere. If three people are forwarding messages from a personal Gmail account, the shared inbox is the real gap and no amount of internal tracking fixes it.
If you need customers submitting issues directly with photos, look at a returns portal. That is a genuinely different product category and it does that job better.
If you are one person doing everything, stay on the spreadsheet. Ownership tracking solves a coordination problem. One person has no coordination problem. Spend the money elsewhere.
The order issue log, as a spreadsheet
Every stage, category and closure condition in this guide, already built. Dropdowns for stage and category, a chase-date column, and a monthly review tab that counts your five numbers for you — including the one nobody tracks.
- Highlights any issue where the customer was made whole but the claim was never filed
- Flags an Awaiting row the moment it passes its chase date
- Opens in Excel, Numbers or Google Sheets
If you need SLAs, agent performance reporting and macros, that is a helpdesk. Do not make a tracker pretend.
What to look for if the middle is where you are
Five things, roughly in order of how much they matter.
It lives where the orders live. If your team has to leave the Shopify admin, context-switch, and search an order number to log an issue, they will stop logging issues. Adoption is the entire game, and friction kills it.
Ownership is a required field, not a suggestion. One named person per issue, always, with handoff that is a deliberate action rather than an assumption.
Status is a lifecycle, not a label. Stages that describe what a case is waiting on, so “no activity for nine days” is either legitimate or visible as a problem.
History is append-only. Notes that accumulate rather than overwrite. When a supplier disputes a claim six weeks later, an audit trail is the difference between recovering the cost and absorbing it.
Supplier and carrier claims are tracked separately from the customer resolution. These run on different clocks. Conflating them is how teams make the customer whole and quietly forget to recover the money — the single most common and most expensive mistake in this whole area.
Our own app, IssueDesk, is one example of this category — it lives in the Shopify admin, attaches issues to orders, and gives each one an owner and a status. There are others, and the argument here matters more than the product: work out which of the three shapes your problem actually is before you buy anything. If damaged goods are the bulk of what you handle, the workflow for those specifically is here.
Most teams do not have a helpdesk-shaped problem. They have a nobody knows who has this problem, and those need different tools.
Common questions
Do I need a helpdesk to manage order complaints?
Only if your problem is inbound volume. If messages arrive across email, chat, SMS and social and you need a shared inbox with assignment rules and response targets, buy a helpdesk. If the customer conversation is already handled and what breaks is the internal follow-through, a helpdesk is a lot of machinery aimed at the wrong half of the problem.
What is the difference between a helpdesk and an order issue tracker?
A helpdesk manages conversations and wants them answered and closed. A tracker manages cases and wants them progressed: investigated, evidenced, claimed against, reconciled. A case can legitimately sit for two weeks awaiting a supplier with no messages sent at all, which looks like neglect in a ticket queue and like a valid state in a tracker.
Can I manage order complaints in a spreadsheet?
Yes, and most teams should start there. A spreadsheet stops working once a second person is involved: rows lose their owner, the sheet drifts from the orders, history gets overwritten, and nothing ever announces that it stopped being maintained.
Is a returns portal the same as an order issue tracker?
No. A returns portal solves intake, letting customers submit structured issues with photos without a human transcribing them. A tracker solves internal follow-through. They are complementary, and portals are generally weaker at the supplier claim and the warehouse investigation.
