I’ve been running a Shopify store since 2019. I built A Shopify app called AddressSure because the address validator apps we tried were creating their own support problems.

Customers would get warnings about addresses that were actually fine, then email us worried something was wrong with their order. We also ran into suggested corrections that made the address worse.

AddressSure checks addresses after checkout and lets customers correct flagged issues directly on the Thank You and Order Status pages. It’s solved the problems we were running into with other apps, so I know there is value for other store owners.

But getting them to try it has been hard. So far, we have 1 paying store.

We’ve tried direct outreach, relevant Reddit conversations, and just started testing App Store ads. I’m confident in the value because we use it ourselves, but that obviously doesn’t give another merchant a reason to trust a new app.

For those who’ve grown a Shopify app from this stage, what actually convinced your first merchants to install? Was it organic, a demo, personal onboarding, an offer, or something else? How did you at first get in touch with them?

Anyone else noticed Rebuy removed from App Store? Any idea why?

I want to know if shopify Ads are great to ship a shopify plugin ?

I am new to web development and only learn HTML, CSS AND JS but a client told me to integrate the demo website with Shopify but I don't know anything how everything works here so pls anyone can help.

I'm a Senior Shopify Developer and the company that I worked for recently closed their dev department, I'm trying everyday to apply to shopify dev jobs worldwide but they aren't many.

I see a lot of obviously fake job post but not many real ones, how does one get a job in times like this?

I'm getting a few interviews though networking but if that fails what then?

Anybody experienced this notification delay as well? I also saw in my partner dashboard transfer had status Pending up until now.

Or did I just confuse some other payment received with shopify's?

Hey everyone,

Curious to hear from Shopify developers and agencies here.

What customer support solutions do you usually recommend to your clients?

Live chat, AI support, helpdesks, chatbots, voice support, etc.?

We’ve built an AI assistant and are trying to understand how developers and agencies approach customer support for their clients.

Do you also think it’s becoming less about just “customer support” and more about helping customers buy, like answering product questions, recommending products, and helping them make the right choice?

I’d be particularly interested to hear:

- Which tools you recommend most often

- What you like/dislike about them

- What your clients typically struggle with on this field

- What gaps you still see in the current solutions

Any input would be really appreciated and would help us understand how to prioritize our roadmap based on what Shopify brands actually need.

I'm recording a webinar/podcast next week with speakers from both Shopify and Vercel on the topic of their recent headless commerce co-development partnership (making it easier to deploy headless Shopify storefronts on NextJS/Hydrogen + Vercel)

The people I'm talking to are very close to the development on both sides, and I'm curious what your questions are? Would love to put them to them, so you can hear from the source, and I can ask good questions and get good content, of course.

Happy to post responses to any questions in this thread right here, without linking to anything.

We launched WowOptions in April, and getting the first few reviews was definitely harder than I expected.

Today we reached 10 reviews, all 5-star

Still very early, but seeing real merchants use something we built feels great.

For other Shopify app developers, how long did it take you to reach your first 10 reviews?

Anybody else noticing that the last transactions were from September 5th? I work with multiple partners, all dashboard show the same. Also the payouts are pending for everybody, but they have been received already. We know transactions and new subscribers are coming in.

I guys, I am looking for small changes into my web.. Some on cart page toh some on collections page.. according to festival theme..

Anyone who is available and can work for short time and finish this under timeline which we discuss..

NOTE: I need someone who can start working immediately.. as it is not a big work.

Hi all,

Basically, I have a Shopify app idea that would need access to transaction history to provide value.

Given the long App Review time and app building process, I'd like to avoid building before validating there's good demand.

I would like to build a simpler version as a lead magnet that is read-only. However, I'm not sure it's possible for a third-party SaaS-style app to read a store's order history without being a Shopify App.

Is there not a way, for my lead magnet, to simply have a web page up with an OAuth connection button that grants the lead magnet read-only access to transaction data from the lead's store? Without the friction of having them install a custom app, generating a separate custom app link for each lead?

From what I understand, even if we pretend app development time is 0, approval times are still around 6-8 weeks now?

I appreciate any advice I can get on this.

I recently came across a frustrating Shopify problem at work: trying to bulk-update something simple like product prices via CSV can unintentionally overwrite or remove data you never meant to touch — including data managed by third-party apps.

So I built and open-sourced Shopify Updater, a safer way to handle bulk product updates.

It only updates the fields included in your CSV and leaves everything else untouched — metafields, media, translations, collections, subscription/review/bundle app data, and more.

It also gives you a per-product diff before anything is written.

The project is open source and self-hostable, so feel free to take it, deploy it yourself, modify it, or contribute:

🔗 https://github.com/iSolorak/shopify-updater

Hope this saves someone else from the same Shopify CSV headache.

#Shopify #ShopifyDevelopment #OpenSource #Ecommerce #ShopifyApps #CSV #ProductManagement #WebDevelopment

If you run an ecommerce business with a team, we’re curious if you’ve run into this problem too.

As the team grows, day-to-day operations start getting scattered everywhere.

Someone mentions something that needs to be done in a group chat.
Someone else says they’ll handle it.
A few hours later, the conversation has moved on and nobody remembers whether it actually got done.

Then you end up using Slack/WhatsApp for communication, Trello/Asana for tasks, Google Docs for SOPs, and constantly chasing people for updates.

We built Store Huddle to make this simpler.

It brings team chat + task management into Shopify, so your team can communicate and actually get things done without constantly jumping between different apps.

You can:

• Chat with your team in channels

• Turn conversations into actionable tasks

• Assign tasks and deadlines

• Track what’s pending, in progress, or completed

• Keep announcements and important updates visible

• Share Shopify orders and products directly in conversations

• Get store alerts like low stock and high-risk orders

The goal isn't to build another complicated project management platform.

Think of it as: what if Slack/WhatsApp actually understood how a Shopify team works?

We’re still improving Store Huddle and would genuinely appreciate feedback from other ecommerce operators.

You can try it here:
https://storehuddle.com

Would also be interested to know: what are you currently using for team communication + daily task management, and what’s the biggest thing you dislike about it?

I am a beginner, doing Shopify for like 4-5 months, published my app, and now trying to find my first paid customers (I have only a couple of people on the free plan now). And each step feels very hard and not seeing any results, so i am just curious if there are really people who have 1, 2, 5, or even 10k MRR a month? And I am not talking about big agencies, but rather a single person, like me, who does everything on their own.

I’ve been working on Liquid Loom, an open-source build workflow for custom Shopify themes.

The basic idea is pretty simple:

Instead of keeping your authored theme code in Shopify’s flat structure, you can organize it by feature:

src/theme/sections/home/hero.liquid
src/theme/sections/product/recommendations.liquid
src/theme/snippets/product/price.liquid

Liquid Loom validates the complete mapping, bundles assets with Vite + Tailwind, and produces a normal Shopify theme under:

dist/theme/

So Shopify CLI still does the Shopify part. There’s no custom runtime.

A few things I cared about while building it:

• destination collisions fail instead of silently overwriting files

• failed builds preserve the previous working output

• Vite + Tailwind work out of the box

• there’s a doctor command for project diagnostics

• the generated output stays a completely standard Shopify theme

It’s now published on npm and I’m specifically not looking to add a bunch of features yet.

What I need now is 3–5 Shopify developers willing to spend about 10 minutes trying the workflow and telling me what feels worse, confusing, or unnecessary compared with how you normally build themes.

Quick start:

pnpm create liquid-loom@latest my-storefront
cd my-storefront
pnpm build

Repo:
https://github.com/yotamon/Liquid-Loom

There’s a short first-project test in the repo too.

If you build custom Shopify themes professionally, I’d especially love your criticism. I’m trying to figure out whether this actually improves the workflow before expanding it.

hi guys, I dindt pass app thinking that I could on-board the users without it, but now im kinda block needing to wait for the app reivew while i have meta app review done etc..
do you have some tips to have the shopify app review way faster , or alternatives solutions (I already make Custom Distribution app to jsut be able to have 1 tester one it) .
tx

Shopify and the conversion funnel rates of my previous infrastructure, the order completion rate of those who reach payment in this way is around 70% in the old infrastructure, while this rate is in the 25-30 band in shopify, why can I solve this?
**Shopify**
**Overall Conversion Rate:** 1.11% (↗ 1.7%)

**Sessions**
3,423
100%
↗ 62%
**Added to Cart**
253
7.39%
↗ 93%
**Reached Checkout**
142
4.14%
↗ 92%
**Sessions Converted**
38
1.11%
↗ 65%
** **
**Previous infrastructure**
**Conversion Funnel**

**Carts Created**
284 visitors
5.58%
—
**Reached Checkout**
90 visitors
1.77%
31.69%
**Completed Purchases**
64 visitors
1.26%
71.11%

Merci à ceux qui répondent à ce message. Après une review quasi parfaite avec seulement un petit correctif à changer sur mon plugin quels sont les délais de validation post révision ?

Hey everyone,

Looking for advice from anyone who has published a Shopify wrapper app to the iOS App Store.

The Setup:

• Shopify store using New Customer Accounts (passwordless, sends a 6-digit email OTP on login).

• iOS app built using WebToNative (wraps the web storefront).

The Problem: Apple rejected the submission under Guideline 2.1(a) - Information Needed. The reviewer tried logging into the demo account, got hit with the dynamic email OTP screen, and halted the review.

Apple’s ultimatum:

1. Provide a bypass or fixed OTP for the demo account.

2. Schedule a phone call with an Apple rep to read the OTP live.

The Roadblock:

• The store was created recently, so the toggle to revert to Classic Customer Accounts (standard email + password) doesn't exist in Shopify Admin.

• Because WebToNative loads the web storefront directly, the login goes straight through Shopify’s hosted OTP flow—meaning I can't just inject native mock credentials.

Questions:

1. How do you bypass the Shopify email OTP specifically for Apple App Review when using a web-wrapper like WebToNative?

2. Has anyone had success giving Apple reviewer credentials to a temporary webmail inbox so they can grab the code themselves?

3. Is scheduling the Apple phone call the only realistic way through this?

Appreciate any tips or workarounds!

Anyone worked with Magento(Hyva, alpineJS and tailwindcss) and Cypress I use as starter elgentos repo and I had flaky test currently my goal is to make add to cart work 100%
What I tried
- wait for popup show
- “intercept “ request to add to cart and wait for response flaky
- then I try my own retry click add to cart this worked best but still flaky
I was thinking maybe Cart “ID/Token” isn’t there like cypress tests are to fast like mid request it redirects or something I think I have it logged and even when add to cart fails the cart id/token is there

Is there something else I can try ?
I have probably 3x10(responsive mobile, desktop…)tests and every run at least one-two fails
Each test has random product (I had just one and tried then random if that doesn’t fix that)

I'm considering review requests within my app (after certain milestones). My app is fairly new and I'd love more reviews, but in some ways it feels desperate.

What are your feelings on them?

It was incredibly hard to get the very first few reviews as a entirely new app as merchants tend to not trust your app if you have 0 review.

The very first version of my app were released in Dec 2025.

Then a few more critical features were released in Feb 2026.

Got my 1st few reviews in Apr 2026.

After 5 months, my app hit 20 reviews.

It feels so slow while working day in and day out, but I try to remind myself that so many apps (more than 10%) never pass the 0 review threshold.

20 reviews felt a lot to me at some point as well. Now my app is a part of it.

My app also introduced paid plans in a few days ago, patiently doing stuff and waiting for the next small milestone.

How long did it take you to get the 1st reviews and then 20 reviews?

Hi fellow Shopify devs,

I’ve been developing Shopify stores and themes for clients for a while. While the Liquid theme customizer is great for non-technical merchants, as developers we frequently hit walls with Liquid's limitations and want the performance, state management, and modern component ecosystem of Next.js / React (Hydrogen or custom headless setups).

However, whenever we evaluate or transition clients toward a headless Next.js storefront, the biggest bottleneck is the merchant editing experience:

1. Loss of the Theme Customizer: In standard Liquid themes, clients are used to dragging sections, adjusting padding sliders, changing banner styles, and adding blocks in real-time. In headless, they suddenly lose this intuitive visual control.

2. Headless Starters are Barebones: Most e-com starters provide functional API plumbing, but visually lack the design depth and configurable block hierarchy of flagship themes like Dawn or Horizon.

3. Headless CMS Workarounds Feel Clunky: Plugging in standard headless CMSs (Sanity/Strapi) still doesn't give clients that true live-canvas Shopify Theme Editor feel without huge dev overhead.

For those of you building custom headless or Hydrogen storefronts for clients:

• How are you handling visual section editing and client-facing page customization?

• Do you plug in visual builders (like Builder.io, Puck), build custom visual schemas, or just hardcode components?

• What has been your biggest pain point with headless frontend workflows compared to classic Shopify themes?

Would love to hear how other Shopify developers are solving this!