I recently published my Shopify app, JsWorkflows: Store Automations.
I built it for merchants who need more flexible automations than simple fixed rules (where Shopify Flow is not enough). You can start from templates or create custom workflows for tasks such as inventory updates, bulk product imports, bulk price changes, scheduled jobs, integrations, and other advanced store operations.
I would appreciate honest feedback on a few things:
Is it clear from the listing what the app does?
Does the difference between JsWorkflows and simpler automation tools come across quickly?
Which workflow templates would be most useful for your store?
Does the onboarding look approachable for non-developers?
Hey @YOD_Solutions I manage 3 Shopify apps so here’s my honest take.
The listing is too feature-focused. Merchants don’t think “I need workflow automation.” They think “I need to auto-tag orders over $100” or “sync inventory to Google Sheets nightly.” Lead with specific problems you solve, not capabilities.
The MCP integration with Claude/ChatGPT is your best hook. “Build workflows by describing what you want in plain English” is way more compelling than listing technical triggers. I’d move that front and center.
Credit-based pricing is confusing. Add a real-world example like “500,000 credits = approximately X workflow runs per month” so merchants can estimate what they’ll actually pay.
Your priority right now: get your first 5 reviews. Offer hands-on setup help to every install and make sure they succeed. Those first reviews make or break an app’s growth.
Hello, @YOD_Solutions Looks interesting, this is the kind of tool a lot of stores eventually need once Shopify Flow feels limiting.
From the listing perspective, it’s mostly clear, but I think the core value could land faster if it was more direct like: “advanced Shopify automations beyond Flow using custom workflows.” Right now it takes a second to understand the difference.
Also, the biggest question users will have is “why not just use Shopify Flow?” if that comparison is made clearer in the first section, it would help conversion a lot.
On onboarding, non-developers will likely need very guided templates at the start. I’d prioritize a few high-impact ones like:
auto inventory syncing rules
price change scheduling
bulk product updates based on conditions
simple integrations
Quick question: what’s the most common use case you’re seeing from early users so far?
Congrats on the launch! Mateo’s feedback is spot on — lead with merchant pain points, not features.
One thing I’d add: your onboarding will make or break early retention. Get a few ready-to-use templates for the most common use cases (inventory sync, scheduled price changes, bulk product updates) so merchants see value within the first 5 minutes without writing a single line of code.
The Claude/ChatGPT MCP angle is genuinely unique — that needs to be your headline, not buried in the listing.
Thanks, this is helpful. It is still too early for me to claim one dominant use case from users, but the workflows I have prioritized so far are inventory sync, bulk product imports, scheduled price updates, bulk catalog operations, and integrations with external services.
Your point about leading with concrete merchant problems rather than workflow capabilities makes sense. I also agree that the AI-assisted workflow creation should be easier to notice without relying on technical terminology.
I already offer free workflow setup and will keep improving the ready-to-use templates so merchants can get value without writing code. The credit explanation also needs a more practical example.
I just checked out your app, credits are confusing. How much credit is used per automation? does it depend on how complex it is? or is it a set amount?
Congrats on the launch! I took a close look at your app concept and listing details. Here is my honest feedback:
Firstly, the core idea is clear. You handle heavy lifting like bulk imports and scheduled jobs. However, the name “JsWorkflows” might scare normal merchants. “Js” screams “JavaScript” and coding.
Secondly, which templates are most useful?** Automated bulk price changes and scheduled inventory syncs are absolute gold. Merchants hate doing those manually. Put those front and center.
Thirdly, is onboarding friendly for non-developers? This is your biggest hurdle. If a non-dev sees “Js,” they assume they need to write code. Your onboarding needs to show visual blocks immediately. Do not show code snippets on day one, or they will uninstall.
It looks like a very powerful tool. You just need to make it feel less scary for everyday store owners! Keep pushing, you are on the right track.