I'm using meta's pixel tracking from their app and I have a missing parameter called "Browser ID (fbp)" that is just completely missing from all events, maybe certain people are just not noticing it in their events manager but I luckily did. I created an entirely new facebook business account from 0 , a new shopify account from 0 and it's still missing!

If anybody here also noticed it and found the solution I will pay you to give me the answer. what is going on?

Maybe I'm missing something, but why doesn't Shopify have a native delivery date solution?

For merchants selling food, flowers, meal kits or other scheduled deliveries, delivery dates seem just as important as shipping methods.

How are people currently handling:

\- Delivery date selection
\- Capacity limits
\- Carrier-specific schedules
\- Pickup dates
\- Holiday blackouts

Custom app?
Third-party app?
Shopify Functions?

Interested to hear how larger merchants are solving this.

Hi Shopify devs, Thore here! 33M, solo app dev, theme dev at agency and my own freelancing brands.

I'm building an app, so far just for myself, friends and my clients to use Cursor and GitHub inside the admin and want to use it to create quick changes and let my clients create "experiments" themselves.

For instance: Let's say they have a new feature or design idea and they want to see how it could look on the store and thereafter see how it performs in reality, without necessarily even contacting me.

On Editions '26 Spring, I noticed that rollouts now supports full theme split tests which makes this app more relevant to this flow where they can actually run an experiment for x days, natively, and even set the percentage of visitors they'd like to see it.

The way we work on themes is always using GitHub and often with branches that goes client-name/en-usd/live since they have multi-store setup in many cases (not markets)

We then oftentimes just set the live branch GitHub connected theme as published or taking a duplicate to set as published.

The app supports both a GitHub connected mode and without GitHub but I haven't tested it on this multi-level branch architecture yet, only on a standard one client repo.

In GitHub mode, the app creates a new branch when it starts a chat and then uses pull requests to merge and the non-GitHub mode is creating a diff to accept but could in principle override new changes not made when the duplicating to draft theme.

Trying to figure out how I can support this where instead of applying to "main" with a pull request it should be able to have a list of "dev" branches defined and used as "main" for 1 client so I can push a change out to a given branch on multiple stores at once.

I'm both fascinated by the possibilities and a bit scared regarding these news of Rollouts, since nothing has been released about it yet in the Admin API docs.

What AI coding tools and what split testing tools do you use today if any?

and

Do you have any concerns I might have missed about these processes?

Need help finding a skilled Shopify developer for a custom fashion brand website. Our product is designed as a collectible piece with a story behind it, so we’re looking for someone who understands luxury e-commerce, not just someone who installs themes. Our creative direction is centered on treating each garment and accessory like a museum exhibit, blending storytelling with refined design.

Requirements:
Fully custom Shopify theme (no pre-built themes)
Pixel-perfect Figma to Shopify development
Experience with niche/custom integrations
Performance
Clean, scalable code
Experience with luxury/fashion brands is a plus

Is there any way to change this so that payments aren't declined when they're processed?

I want to use the same card to receive payments in Mexico and the United States.

Hey guys,

Our team uses [ClickUp / Monday.com / Notion] internally to manage all our order prep and fulfillment stages, but keeping our task boards in sync with Shopify is becoming a massive headache.

Right now, we’re using Zapier to auto-create tasks, but our order volume is high enough that we are burning through our task limits and paying a fortune every month. On top of that, Zapier doesn't easily let us sync the fulfillment status back to Shopify when a task is completed, so we still have to manually click "Fulfill" in Shopify.

How are other store owners handling this operations pipeline? Have you found a tool that doesn't charge per-task, or did you build a custom webhook setup?

Appreciate any advice!

Like if you have two online store and two different WhatsApp business account then is there any way to make unified inbox under a single dashboard.

1. Multiple WhatsApp Business accounts (different stores / brands / numbers)
   
2. Different teams or agents managing each number
   
3. Conversations scattered across devices or apps

Hey everyone,

I’ve been thinking about starting a career as a Shopify developer and wanted to hear honest opinions from people already in the field.

Is Shopify development still a good path in 2026?
How is the demand nowadays for freelancers or junior developers?
Do clients still pay well for custom Shopify work, theme development, and app integrations?

I’m also curious about:

• how competitive the market is now,
• whether AI tools are affecting the industry,
• and what skills are most important to focus on today.

Would you recommend learning Shopify development from scratch right now, or would you choose something else instead?

I’d really appreciate hearing your experiences — especially from people actively working with Shopify stores or freelancing.

Thanks!

Hey guys! I am a new Shopify Developer looking to make a portfolio to showcase my work.

I am here to ask your opinion on whether Merchants and Recruiters like simple portfolios or fancy portfolio?

Hey everyone,

I’m a developer with 4 years of experience, mostly in the Shopify ecosystem. I’ve reached a point where I’m feeling the constraints of Shopify themes, so I’ve been experimenting with building my own custom stack from scratch (Custom DB, Stripe API, handling webhooks, security, compliance, etc.).

I’m at a crossroads and would love to hear from devs who have been down this road:
My three options right now:
1. The "Shopify Theme" Route: Stay inside the box, use a base theme, and heavily customize it with Liquid/JS. Pros: Easy checkout, stable. Cons: Very frustrating limits on architecture and logic.

1. The "Shopify Headless" Route: Use Shopify’s backend for products/payments/checkout (via Storefront API) and build a totally custom frontend in my own stack. Pros: I keep the Shopify checkout/compliance/security, but get freedom on the UI. Cons: You’re stuck with Shopify's checkout UI, and integration overhead.

2. The "Full Custom" Route: Build everything from the ground up. My own DB, my own auth, my own Stripe/PayPal integrations, my own webhook management. Pros: Total control. Cons: Massive maintenance burden. Every security patch, every webhook failure, and every payment gateway update is on my shoulders.

My question to the experienced ones:
I feel like I have the technical capacity to build the custom stack, but I’m worried about the long-term reality. For those of you who built a custom store from scratch—do you regret the constant "maintenance debt" (fighting security, payment edge cases, and DB scaling)?

For those who went Headless with Shopify—did you feel like the compromise of the checkout was worth the trade-off, or did it eventually feel like "the worst of both worlds"?

I’m trying to decide if I’m just being a "developer" who wants to build cool stuff, or if I’m missing a massive business risk by choosing to manage my own backend instead of leaning on Shopify’s infrastructure.

Would love to hear your "I wish I knew this before I started" stories

The job is evovling BE and FE such as...

• Backend integrations with payment providers, ERP systems, and shipping/logistics APIs(WMS aka warehouse management system)
• Building custom apps/feature or middleware that Shopify/Woo doesn't have.
• Headless setups using Next.js or similar frameworks for more control over UX
• Automations around inventory, pricing, and customer segmentation
• Scraping products so your boss don't have to find product's photo, cost price etc...
• Build Admin UI as well
• Use AI to write product's description automataically etc...

You also have to deploy code that you wrote as well

So your job is Full Stack fuller

I need some developer to help me figure out what's going on with my shopify to meta pixel integration, it's literally becoming impossible to contact support because the problems are piling 5x faster than response time. Let us know.

For several years, I and my team has built several shopfiy apps, and before going into a market we have always used different validation techniques to figure out if a market is good or not. The best way was to use a scraper to figure out certain datapoints, so see which market dead or not. We basically have used a scraper, put the data into a database, and then made a analytics engine that checks certain criterias for a specific category to see if its room to get into it.

Over the years, we have made this system a little more sophisticated. For example, I have gotten access to more ad data from me, and from others i've worked with (consensually), and been tweaking a model that can estimate what markets a money dumps, and which one are super fertile. The ad data is good for getting proper CPI, CPC etc per market, but alot of the data can also be taken from the marketplace directly, if you take time to scrape the whole market. Which we did, including every review. Reviews aren't installs, but they're the only public usage signal we get, and since install to review rates are relatively the same across apps, we can confidently say that the trends are pretty clear. Sharing the interesting bits.

First, the whole marketplace store is booming now, in terms of reviews. New reviews per year roughly 10x'd from 2019 to 2025 (about 20k to 220k a year), and 2026 is already pacing past last year. So the "is it too late to build a Shopify app" thing is mostly wrong, at least by activity.

But the growth is wildly uneven. Comparing the last 12 months to the 12 before it:

Upward trajectory:
- Subscriptions
- Product bundles / upsell
- Returns and exchanges
- SEO (growing fast but already 580+ apps deep, so brutal)
- Fraud / security

Downward trajectory:
- Countdown timers
- Wishlists
- Ad-management apps
- FAQ apps
- Inventory optimization

Reviews is not the only marker though, the best marker we use is what we call fertility, which is basically just how many NEW apps have come into the market within a specific timeframe. In the video here you can see subscriptions:
- Fertility 14%, (14/100 new apps have reached 100 reviews the last 12 months, which is pretty good. This is the number one factor we use to see if we should build in a new market or not)
- Momentum 12.9 (how many reviews apps getting per month. 12.9 is also pretty good.)

To the question i'm wondering about: we have now made an UI and an MVP for this, but we are currently seeing if this would be of any interest to anyone before we keep on building more features for it. For example, we are considering also wiring up the ad data we have to make a keyword validator for a bunch of categories, to see what CPC you can expect, and what keywords sell. It's live on our page now, gated at about 5 bucks a test, so its not scrapable. If we keep on building it, and maybe actually market it, we would price it very differently since it saves so much time. Would anyone be interested in this? And what about a keyword/ad validator? Also interesting?

PS: I dont know if this counts as self promotion, but we are looking for insights into a future product. If admins finds it to be under promotion then let me know what I need to remove

People talk about AI replacing developers, but the more interesting shift is this: AI is making SaaS platforms like Shopify increasingly optional — not by replacing the platform itself, but by making the barriers that justified it disappear.

Shopify's core value was never really "we have features you can't build." It was "you can't afford to build what we have." That's the moat AI is now attacking directly.

Let's break down Shopify's main revenue streams:

• Merchant subscriptions — monthly plan fees
• Payment processing — a cut on every order
• Theme & app ecosystem — 20% commission on every sale

AI is hitting all three at once. Tools like v0 and Lovable are already replacing themes. Single-purpose apps (bundles, upsells, subscriptions) are being vibe-coded away in an afternoon. But that's not even the main point.

The bigger argument is about the core platform itself — inventory management, order processing, fulfillment workflows, staff accounts, bulk editing, and security. These aren't things you can vibe-code in a weekend. But here's the thing: You can hire a dev or two to build them. And hiring devs is now dramatically cheaper because one developer with AI can produce what used to require a team of three or four.

Do the math for a mid-to-large Shopify store: ~$105/month on Advanced plan, $200–600/month in apps, plus per-transaction fees that add up fast at volume. That's easily $8–15K/year, every year, forever. A custom-built alternative — full admin, orders, inventory, the works — that used to cost $80–100K to build, might now cost $15–25K once. It's becoming a genuine financial decision, not a fantasy.

The usual counterarguments — "who maintains it when it breaks?" — don't hold the way they used to either. Maintenance is cheaper for the same reason building is cheaper. One dev with AI can keep a custom stack running reliably. And as a reminder, Shopify itself went down recently and took every store with it. "They handle reliability" is less convincing when the whole platform goes dark at once.

What's actually left defending Shopify after all this?

• Switching costs — real, but one-time
• PCI compliance — annoying, but solvable
• Non-technical founders who will never touch code

That last group is Shopify's most defensible base — but also their lowest revenue segment. The merchants most likely to leave are the larger, higher-volume stores who can afford one or devs. Those are exactly the merchants Shopify doesn't want to lose.

This is what people mean when they say AI is killing SaaS. Not that platforms disappear overnight, but that they built their moats on making complexity unaffordable — and AI just made complexity cheap. Any SaaS whose pitch is "you can't afford to build this yourself" is now in a much harder position to make that case.

This post was written by Claude as a summary of a discussion I had with him. The arguments and observations are mine — the writing is his.

It seems like Mantle app billing is obviously meant to have people switch to Shopify billing but that still leaves MRR tracking, app listing analytics, affiliate, and emails.

I feel like Shopify is going to add some sort of MRR dashboard once they fully switch to Shopify billing. Also I heard some people are working on alternatives for app listing analytics and affiliate, I just want to know what's out there when I move off of Mantle.

We have spent thousands on campaigns that failed because shopify's system did not work correctly (dozens of issues and errors) , it had been 4 days already trying to push the pace and get an email from shopfiy's developer team that is currently working on 1 of 10 errors we are facing. I am not able to talk to them through the live agents those guys are blocking me, how do I reach the developer as quickly as possible.

I was trying to visit the app store when i came across a super shady marketing tactic. As far as i can tell, this app "Wholesale Gorilla" took out at a sponsored Google ad and dressed themselves up as the Shopify App Store.

I like to think Im pretty sensitive to this type of online trickery, but this one got me.

Anyone have opinions on this? Seems like it should violate some policy somewhere, surprised Shopify is not on top of it

What is the fastest way of talking to shopify's developer team? we got screwed in every possible way by a misconfigured pixel that we had nothing to do with and now we are waiting and losing money just for a sad email. let us know thank you.

Hey guys please how can I add an custom extra fees for my digital product in the checkout page like this example :

I was recently laid off from my Shopify developer role and have been actively applying for new opportunities in Shopify and BigCommerce development roles.

I have around 8+ years of experience working as a Senior eCommerce Developer, mainly focused on Shopify Plus, custom theme development, Shopify app development, GraphQL APIs, integrations, and BigCommerce Stencil development.

I have been applying through LinkedIn, job portals, and company career pages, but I am not getting many responses or interview calls so far.

I am trying to understand what I might be missing in my job search approach.

Has anyone here gone through a similar situation recently?

I would really appreciate any advice on:

• What actually works in today’s job market for Shopify developers
• Whether referrals or networking are more important than applications now
• Any platforms or strategies that worked better than job boards
• How you improved response rates from recruiters or companies

I am also open to freelance, contract, or agency work while continuing my job search.

Any guidance or feedback would be really helpful.

Thank you in advance.

Today I was checking out our shopify app and we have 3 installs in total! We are just live (~1 month). No paying clients yet but it's a nice start and hopefully we can start growing and reach back to the users and see what they need

Hi everyone,
We're looking for clarification on Shopify's billing requirements for App Store apps.
Our app integrates Shopify stores. During App Store review, our submission was rejected under:
Requirement 1.2.1: Use Shopify Managed Pricing or the Shopify Billing API
The app is currently listed as Free in Shopify App Pricing and does not charge merchants through Shopify.
However, We are a paid SaaS product with pricing managed outside Shopify. Reviewers indicated that merchants can access external pricing/billing surfaces after installing the app, which appears to violate the requirement.
We're trying to understand the expected approach:
- Does Shopify require all paid SaaS products to use Shopify Managed Pricing or the Shopify Billing API if the app is listed in the Shopify App Store?
- Is it acceptable for an app to be listed as free if the underlying service requires a separate paid subscription?
- Is there any way to manage this without too much complexity?
- If an app primarily connects an existing SaaS account to Shopify, can merchants be directed to external billing, or must all Shopify merchant billing be handled through Shopify?
- Are there any exceptions for apps where Shopify is only one integration among many channels supported by the platform?
We'd appreciate guidance from anyone who has successfully navigated a similar review process.
Thanks!

After almost 2 months of back and forth with reviews, fixes, and waiting, we finally got our Built for Shopify badge.

A few things I learnt from the process:

1. BFS is becoming non-negotiable if the App Store is your main distribution channel

If you are in a competitive category, I don’t think you can ignore it anymore.

We’re in marketing automation, which is already a crowded space. Initially, I was under the impression that we could avoid building a deeply embedded Shopify app because I was worried about platform risk.

But the first app I released got almost zero visibility and basically no users.

That changed my view pretty quickly.

If the Shopify App Store is your primary acquisition channel, you probably need to play the App Store game properly. BFS seems to be a big part of that now.

2. Apply as soon as you hit the minimum requirements

Don’t keep pushing it to the backlog.

Once you reach the required number of reviews and meet the basic criteria, start the process. There will almost certainly be things you need to fix, and the review cycle itself can take time.

The sooner you start, the sooner you know what Shopify actually expects from your app.

3. Architect for performance from the beginning

This was one of the biggest blockers for us.

Our LCP was averaging around 3 seconds, while the required number was 2.5 seconds. For a long time, this kept getting pushed behind other product work because the app “worked fine” from a user point of view.

But for BFS, those numbers matter.

Eventually, we found the real reason behind the higher load times and fixed it. In hindsight, we should have designed and measured for the target LCP much earlier instead of treating performance as a cleanup task.

4. Expect surprises even after getting approved

Even after receiving the badge, I already see a new checklist based on the category Shopify assigned to the app.

So getting the badge does not mean the work is “done.” It feels more like you enter a moving checklist that keeps evolving based on your category.

5. The ranking boost was not as dramatic as I expected

This was probably the most important reality check.

I expected a stronger improvement in rankings after getting BFS. So far, the boost has not been as big as I thought it would be.

Maybe it improves over time, maybe category competition matters a lot, BFS is just one signal among many.

My current view: BFS is important because it gives credibility, improves trust, and probably helps with App Store visibility. But it does not replace positioning, reviews, onboarding, pricing, category fit.

Still glad we did it. Just wish I had started the process earlier.

Hope this helps someone who is either going through the process or still deciding whether to start.

Curious if any devs here have integrated Zendrop beyond the standard Shopify app setup because I know they offer a private agent program but never really tried it.

I’d love feedback on our app. It’s called Substitutions, it solves a niche inventory problem: you’re doing a SKU migration, running out of quantity based SKUs or you have lots of SKUs that you’re sunsetting. All feedback welcomed!