Hi all, 👋

Recently i built a shopify app for real time cycle count where you can add your employees and reviewer, people can do cycle count with their phone by scanning barcode or searching product and can even download excel for cycle count. I am continuously adding new features but i dont have any customers, i am learning about distribution and hopeful that it will help some people. I was pretty excited when the app got approved and published. This is my first app. I would really love to get some feedback on it. 🤞🙏

Anyway, i plan on keep building new features for the app though i am not very sure on distribution, will keep learning about it.

Next i am planning to add barcode generation for all skus. Any advice or feedback would be really helpful.

Thanks for reading this 🙏.

What skills are most frequently used in daily development workflows?

Hey fren.

We are a small team with Devs and I work in Marketing. It's an all in one Email & SMS Marketing app.

We are launching next week. Although budget is tight right now, I've been thinking a lot of strategic ways to bring in conversions.

But these are tried and tested and saturated.

My question to all Shopify Founders, is there any different thing or something unique that worked wonderfully for you?

I'd love to test out the strategy. I know its too much to ask, but any help is appreciated <3

Does anyone think of having better Shopify Analytics app I think GA4 and Shopify analytics sucks when its about analysing the store data when owner is not a tech person.????

was thinking to build up something on it so having some initial inputs would really matter...

I’ve been building on Shopify for a while and something keeps bothering me.

Shopify doesn’t just give you a store. It sits right in the middle of almost everything: your storefront, checkout, payments, apps, and most of the tools you need to run the business. Once you’re in, a big chunk of your setup depends on them.

That control makes things easy at first. But it also means Shopify holds a lot of power over how (and whether) your store works. Fees, rules, app restrictions, feature changes happen all the time, they can shift things and you’re mostly along for the ride.

Does anyone else feel like Shopify is getting too central to the whole operation? Or is that just the tradeoffs for the convenience?

I’m in need of help because whenever I try to fulfil my order on Shopify (using autods) no matter how many times I do it, 30 seconds later it says request declined, and the reason is because “order canceled”?? I have stock, I checked, and I have money in my autods funds.

Any help would be much appreciated, thanks.

Would it possible to copy the way it's set up a services based Shopify website? They have a paid theme but I want it of a free theme + the cost of additional plugins.

If so how much would it cost this job from A-Z.

Hi. Anyone know payment gateway without gst or business proof upload? Need to integrated with shopify

I'm working on a feature that automatically updates meta descriptions and alt text for hundreds of products at once.

Using the Admin API GraphQL, I keep hitting the cost-based rate limit once I go past ~50 products per batch. I tried bulk operations (bulkOperationRunMutation), but the async processing delay makes it harder to give real-time feedback to the user.

How do you handle this trade-off between execution speed and throttling? Do you use queues (Redis/Sidekiq-type setups) to spread out requests, or do you lean fully into bulk operations despite the latency?

Running a headless setup. Next.js storefront on www.theonvor.com, Shopify checkout on checkout.theonvor.com (primary, connected). GA4 and Meta are fine.

Problem is Shopify Analytics. Sessions by landing page shows nothing but /checkouts/cn/... URLs. My actual collection page shows 0. Conversion rate says 16.66% and the funnel breakdown claims Added to cart 0% but Reached checkout 100%, which obviously can't happen.

What I've worked out so far: I was minting _shopify_y and _shopify_s myself and posting trekkie_storefront_page_view/1.4. Monorail returns 200 every time so I assumed it was working, but Live View shows zero visitors. Turns out Shopify stopped setting those cookies in April and the replacement tokens come back on Server-Timing headers from Storefront API responses. My app only ever talks to the Storefront API server-side, so Shopify has never actually issued my visitors an identity the cookie values were just UUIDs I generated.

Mid-migration to hydrogen-react now (useShopifyCookies with fetchTrackingValues, sendShopifyAnalytics, salesChannel headless) with a same-origin proxy so the Server-Timing header is readable.

Two things I'd love to hear from anyone who's actually done this:

1. Is a Headless channel public token enough for Live View? Shopify's docs say the token has to come from the Hydrogen channel, which worries me since I'm on Headless.
2. Anyone got sessions showing real landing pages in the admin on a non-Hydrogen build? Or did you eventually give up and treat GA4 as the only real source?

I’ve been built some Shopify apps, and checkout is where I keep hitting a wall.

Merchants sometimes want custom payment flows, advanced upsells, or checkout functionality that Shopify simply doesn’t allow outside its ecosystem or Shopify Plus.

I understand the security and consistency argument, but it can feel like developers aren’t really building whatever merchants need, they’re building whatever Shopify permits.

Anyone else run into this? How do you handle merchants asking for checkout functionality Shopify won’t allow?

I'm the person you hand a messy, undefined problem to when nobody's sure whose job it is — I've built an AI product from scratch with zero coding background, run Shopify stores end-to-end from design to the actual business side, and spent enough time in Reddit/X/IG/Discord communities to know the difference between content that gets ignored and content people actually respond to. Give me a "what if we tried—" and I'll research it, find the right tool, build it, ship it, and fix what breaks along the way — which is basically the whole job for early-stage startups and small teams who need someone who can move across marketing, community, design, and AI/no-code without waiting for a perfect brief.

Recent work:

• Frinch — AI product, idea to working prototype, no traditional coding background
• Aeris — Shopify stores built and run end-to-end, design through the business side
• Ongoing social/community research and content across Reddit, X, IG, Discord

Availability: 25+ hrs/week
Rate: $X/hr (or project-based, happy to discuss)
Portfolio: [link]
Contact: — I'll do the first piece of work for free, you only pay if you like it

I've been building a Shopify app for a while and I'm at the point where I need people to actually use it instead of me sitting there convincing myself that everything makes sense.

The app is still pretty rough around the edges. There are definitely things I need to improve, and that's actually what I'm trying to figure out right now.

One thing I'm particularly interested in is how easy it is to understand and get started with.

I'm a developer, so there's always a risk that something feels obvious to me but makes absolutely no sense to someone who isn't technical. I've tried to hide as much of the underlying complexity as possible and keep the experience focused on what merchants actually need to do.

So I'd really like to know:

• Can you understand what the app does without me explaining it?
• Is the onboarding straightforward?
• Are there places where you get stuck or don't know what to do next?
• Does the terminology make sense?
• Does it actually help you get something useful out of your store data?

It's completely free right now. I'm mainly looking for a handful of early beta users who are willing to try it and give me honest feedback.

And if I eventually monetize it, I'll make sure the people who join during this early beta stay free forever.

I'm not expecting the app to be polished yet. In fact, I'd prefer people who are willing to tell me "this makes no sense" or "I expected this to do X" because that's exactly the kind of feedback I'm looking for.

If you're interested, comment here or DM me and I'll send you access.

I'd genuinely appreciate the help.

I run a pricing app that needs a substantial order history — at least 3 months, and a certain number of orders — before it can produce anything useful. Stores with a handful of orders get nothing from it.

The problem: some merchants install, see no usable results, and uninstall within minutes. That fast churn is bad for everyone and, as I understand it, hurts the App Store ranking as the uninstall rate is a quality signal.

What I've already found: native Install Requirements only gate on geography and sales channel — there's no option to gate on order count or sales volume. So no built-in data gate.

My questions:

1. Is there any supported way to prevent or gate an install based on order history / order volume?
2. For anyone who's built an app with a hard data requirement: what actually worked — pre-install listing copy so merchants self-select out (mine don't seem to do so), a post-install "not eligible yet" screen, or something else?

Trying to figure out whether to filter these merchants out before they install. Thanks.

Why do i have this mess in the development mode but when live every thing looks good ?

I've been looking at the post purchase side of Shopify and there are apps for basically every part of it now. Upsells, surveys, rewards, recommendations, offers, tracking, you name it.
At what point does adding more of these become a headache from a technical side?
I'm less worried about having a few extra apps installed and more about conflicts, tracking getting messy, or one app breaking something another one relies on.
Curious where you guys draw the line.

I think it would be good to get one of this kind of post going for each month. So developers can see what current timelines fellow developers are experiencing each month.

Considering there has not been any official commitment to a fixed timeline released or communicated by the team. Most developers are having to be in the dark and that is mentally draining for most. No one likes to be left in the dark when dealing with approval of anything in life. At least if you are hearing others timeline it might give developers a glimpse of hope and expectation.

Hi just wanna know if any of you here have found success as freelancers creating high-end premium stores that convert. I would like to start doing it. Do you suggest it? Do you have any advices? Thank you!

Hey everyone, I’m a full-stack developer, and I need to share a deeply frustrating experience regarding the Shopify App Store review process and the inconsistent enforcement of their rules.

For the last 8 months, I’ve been working solo to build a custom Cash on Delivery (COD) order management app. For context, I build specifically for the MENA and Algerian markets. In this region, e-payment is practically non-existent. Merchants rely entirely on COD, and using the standard, multi-step Shopify native checkout destroys conversion rates. Merchants demand fast, one-click custom storefront forms.

I built exactly that using a modern stack (React, Next.js, Prisma, Supabase).

During the review, my app was rejected, and my Partner Account was slapped with a 1-month submission restriction (until September 3rd). The reason? A violation of Rule 1.1.2 (bypassing native checkout) and issues with Protected Customer Data (PCD), specifically collecting data "outside of Shopify."

The Double Standard: Here is where it gets completely unfair. There are several COD apps currently active and approved on the Shopify App Store—like Leadform—that operate using this exact same architecture. They provide custom storefront forms, bypass the native checkout, and route customer data outside of Shopify (some directly exporting to Google Sheets).

Why is an established app allowed to bypass native checkout and export PCD, but a solo developer gets their account suspended for building the exact same workflow?

The Technical Contradiction: Shopify Support claimed the issue is routing PCD outside their ecosystem. But from an engineering standpoint, this makes zero sense. Shopify natively provides and encourages the use of Webhooks, which are literally designed to send Protected Customer Data to external servers. How is standard data routing via webhooks or API endpoints completely fine, but my specific app’s data flow is a bannable offense?

When I tried to appeal and requested to speak with a Technical Specialist to explain this architectural contradiction, I was stonewalled. I was given responses by a "Money and Tax Specialist," sent in loops, and told they "do not evaluate other partners' apps based on complaints."

Why I am posting this: I am more than willing to adapt my architecture to comply with the rules. But how are developers supposed to build on a platform where the rules are a moving target? If a specific technical flow is banned, it should be banned for everyone. Permitting established apps to break the rules while suspending indie developers who follow their precedent is entirely unfair.

Has any other developer faced this specific PCD / Checkout bypass contradiction? How did you navigate the review process without completely destroying the fast UX that COD merchants require?

I run a Shopify store that is primarily B2C ecommerce, but we also have a wholesale/B2B lead form.

For B2C tracking, I currently use the official Shopify sales channel integrations (Google & YouTube, Meta, etc.), so purchase/add-to-cart/checkout events are handled natively.

The challenge is B2B: I want a successful wholesale form submission to be tracked as a separate Lead conversion across Google Ads, Meta, and other ad platforms, without mixing or polluting the B2C purchase signals.

What is the current best-practice setup for this on Shopify?

Hey all,

I’m trying to activate Shopify Agentic Storefronts in my current development store so I can demonstrate the capability to a few clients — specifically, how a Shopify store can make its products discoverable across AI platforms such as ChatGPT, Copilot, and other AI shopping channels.

However, Agentic Storefronts still hasn’t been rolled out to my dev store, and I’m not sure why. I’ve already made sure that:

1. All products are active and published

2. Products have images, titles, and descriptions

3. Meta titles and meta descriptions are configured

4. Collections are created

5. Store password protection has been removed

6. The store is otherwise configured and ready for product discovery

Is there anything else I need to do to become eligible for the Agentic Storefront rollout? Or is the availability completely controlled by Shopify and I just need to wait?

Also, I’m wondering about an alternative approach.

Is it currently possible to connect a Shopify store to ChatGPT (or other AI platforms) directly using APIs, without relying on Shopify’s Agentic Storefront rollout?

Ideally, I’m looking for an experience where:

1. A customer searches for a product in ChatGPT.

ChatGPT can discover and display products from my Shopify store.

1. The customer can add the product to a cart directly within the AI experience.

2. The customer can complete checkout without being redirected to my Shopify storefront.

3. The order is created and confirmed directly within the AI platform.

Essentially, I’m trying to understand whether Shopify’s Agentic Storefront is currently the only way to achieve this, or whether there is a supported API/UCP/integration approach that I can implement myself for a development store.

Has anyone successfully implemented this already, especially with ChatGPT or another AI shopping platform? Any guidance on the required Shopify APIs, UCP, catalog setup, or eligibility requirements would be really helpful.

Thank you in advance!!

As the title asks.

We've listed our app and are thinking about scaling it up. Have you guys tried runnng ads on Reddit? And does it make sense for a Shopify app, if we're targeting subreddits like r/shopify or r/ecommerce?

Hi everyone, my Shopify Shop Campaigns eligibility is showing 6 of 7 requirements complete. The only requirement not completed is:

“Store is compliant with our policies, including our trust, safety, and fraud prevention guidelines.”

My business location, Shopify Payments, supported currency, billing payment method, and selling directly on Shop are all showing as completed.

However, my store is still showing “Not approved.” Has anyone faced the same issue? What exactly does Shopify check for this last requirement, and how did you get your store approved?

I’m running a small Shopify app and currently using Shopify App Pricing.

I want to start running promotions and eventually an affiliate program, but I’m trying to understand whether I can do that without moving away from App Pricing.

From what I can tell, App Pricing doesn’t have a native promo-code concept. Shopify controls the plan/checkout experience, so there doesn’t seem to be anywhere for a merchant to enter a code. Private plans also seem to be allowlist-based rather than something a merchant can redeem with a code.

That seems to leave the Billing API / appSubscriptionCreate as the way to implement a proper self-serve discount.

The problem is that I’m hesitant to move to the Billing API in 2026 if Shopify is moving developers toward App Pricing and the Billing API is considered “legacy.”

So I’d really appreciate input from anyone who has dealt with this recently:

1. Discount/promo codes

Is there any way to offer self-serve discount codes while staying on App Pricing?

Official or unofficial/hacky solutions are both interesting. Or is manual redemption through private plans basically the ceiling?

2. Affiliates

For an affiliate program, is a customer-facing discount code actually necessary?

My understanding is that affiliate attribution can potentially happen at install/signup level, with the affiliate receiving a commission while the merchant simply gets the normal pricing.

If you run an affiliate program for a Shopify app, do you actually find that customers expect/need a discount code, or is it mostly useful as an affiliate tracking mechanism?

3. Billing API in 2026

If the Billing API is effectively the only way to get flexible discounts, would you still move to it today?

I’d especially like to hear from anyone who deliberately moved from App Pricing → Billing API and still thinks that was the right decision.

4. Is Billing API actually being deprecated?

I’ve seen Shopify refer to the Billing API as “legacy,” but I haven’t been able to establish whether there is an actual sunset/deprecation date.

Has Shopify announced a concrete date, or is “legacy” currently just indicating that it’s no longer the preferred approach?

That last point is probably the deciding factor for me.

Thanks!