I spent 2 years fixing the same Shopify support tickets, so I packaged the fixes into 10 workflows
For 2 years I worked support at PrestaShop, helping merchants run their stores. Same tickets, every week: "where's my order", abandoned carts nobody followed up on, stock running out with no warning, refund requests sitting in the inbox for days.
None of it needed a developer. It needed automation that most store owners never get around to setting up because it eats a weekend they don't have.
So I built 10 of these as ready-to-import workflows, in both Make.com and n8n versions:
Order status auto-responder (pulls real tracking from Shopify, handles 40-60% of "where's my order" emails on its own)
Abandoned cart recovery, 3-touch sequence
Low stock alert with a pre-written reorder email to your supplier
Return/refund auto-acknowledgment
Daily sales and ops report at 8am
Negative review monitor and alert
Plus 4 more covering new order notifications, review requests, customer welcome sequences, and support triage.
Each one comes with a setup guide, takes about 30 minutes to get running, no code.
Put it on Gumroad: https://emmanuelbarencourt.gumroad.com/l/jmtye?utm_source=indiehackers&utm_medium=post&utm_campaign=launch
Happy to answer questions if anyone's dealing with the same support ticket grind.
Hi, the framing here is stronger than most automation product launches — "2 years of the same ticket" is a much more convincing origin story than "I thought merchants might need this."
The 40–60% deflection rate on order status emails is the number I'd lead with everywhere. That's the one that makes a store owner stop scrolling.
I've wired up similar flows in n8n for e-commerce clients and the abandoned cart sequence is always the one with the fastest visible ROI — merchants can see the recovered revenue directly in their Shopify dashboard within the first week.
Good launch. If anyone wants to extend these or connect them into a broader stack, happy to talk through it: https://teams.live.com/l/invite/FBAk3iOSJkDyS11JQ?v=g1
This is a smart angle. Most Shopify merchants I've talked to treat support as a cost center they just have to eat, not something that can be systemized.
One thing worth considering early: the support tickets that are easy to automate (order status, return labels, tracking) are usually the ones where merchants least feel the pain. The real value tends to be in the messy ones; partial refunds, exchange bundles, inventory holds. Those are harder to template but that's where the time savings actually show up.
Are you planning to expand the set to cover those trickier cases, or are you keeping it focused on the high-volume structured stuff?
Keeping v1 on the high-volume structured stuff on purpose, that's where the logic is simple enough to ship as a no-code blueprint and the time saved is immediate. The messy cases you mention (partial refunds, exchange bundles, inventory holds) usually need branching rules specific to each store's policies, so they don't fit a generic import, they'd need a setup call per store. If enough people ask for it I'll build a v2 covering those, but didn't want to launch with workflows that need heavy customization to actually work.
Smart call keeping v1 focused. Most founders over-invest in flexibility before they have enough users to know what flexibility actually matters.
One thing worth watching: even across different store policies, the messy cases tend to share branching patterns. Customer scenarios like 'ordered A and B, returned A, wants exchange on B' follow similar logic trees even if the specific decisions differ. Those patterns might be easier to template than they look on paper.