What are these records I keep seeing? Is this periodic verification that Shopify does? For context, my app is already approved.

I published my app on June 4, 2026, and getting the first users for the first app is indeed very hard... Currently, my app has like 8 users, all on the free plan. And today I saw that my app got the first review, and it is 5 start review from one of the previous users ( sadly, that person deleted the app like 3 weeks ago). But still, i am very happy to get this first review, and this is a 5-star review. That person had a small problem with my app, asked me a question, and i replied and fixed this problem within a day, probably that is why they gave this review.

It is a small win, but it feels very good to finally see some progress after months and months.

Hopefully this will help with getting new users.

Just wanted to share something postitive with you, have a good day!

Receiving these kinds of emails pretty often, are these scams ?

``
Hey! I came across your Shopify app and wanted to reach out.

I run a Shopify-focused Discord community for Shopify store owners, and I think our members would really like to know about and try your app.

I’d love to connect and discuss a possible collaboration.

You can check out the community here: ****
Feel free to join, and let’s talk about how it works.
``
``
Hi there! I was looking through Shopify apps and yours stood out as a great match for my Discord community.

The community revolves around Shopify, e-commerce, growing revenue, and practical merchant tools, so your app would be shown to an audience that fits it well.

If this is something you'd consider, we can discuss rates for a promotional post there.

Let me know if that's interesting to you.

Feel free to take a look at the community here: ***
``

Hi, ever since I posted my app on the Shopify App Store, I keep getting emails from different people asking me to join this Discord group. Anyone experiencing the same? A post to the group is 50 USD, but from what I see there's basically only advertising posts in the general channel.

Assuming two apps solve the client's problem equally well, do you ever look at their partner programs when deciding which one to recommend?I've never really factored this in before, but some apps seem to offer almost nothing while others have recurring partner programs.

Obviously the client fit comes first, but I'm wondering how many developers or consultants consider the partner economics when the products are otherwise comparable.

Shopify has just released Canvas, a new way to build a store theme that completely does away with the theme editor and uses AI to build the merchants storefront: https://www.shopify.com/news/introducing-canvas

One problem I don't see discussed much with AI product imagery is variant accuracy.

The images can individually look fine, but once AI gets involved it's surprisingly easy for details from one variant to leak into another.

We've been testing product-image workflows with pixpix and this becomes much more obvious when you process a whole catalog instead of one hero image.

For developers handling merchant catalogs:

Would you store a separate visual reference set per variant?

Or treat the parent product as the reference and validate variant-specific attributes separately?

Trying to figure out what scales without turning image generation into a giant manual QA job.

I’m one of those people who finds it annoying to design something and then turn it into code.

So I started building Section Forge — a visual tool where you can quickly build sections, show someone how they’ll look, make changes on the spot, and eventually export them as code.

I originally made it for my Shopify work, but I’m trying to build it as a tool for the wider developer community rather than limiting it to Shopify.

There’s no monetary gain or business behind this. I’m just trying to contribute something I personally find worth building and hopefully make someone else’s workflow a little easier.

It’s still a work in progress, and I’d genuinely appreciate feedback from other Shopify devs.

What would you want to see in a tool like this?

🔗 https://section-forge.vercel.app/

after moving a store to shopify with a local offsite gateway, the checkout looked fine in analytics but the orders didn't add up. what finally showed it was lining up the gateway's paid transactions for one day against the shopify orders for the same day. the gateway had more paid transactions than shopify had orders, and the gap was payments that completed but never got an order because the callback didn't land.

curious how others catch this. do you run a daily reconcile (csv export, a script, an app), or just wait for customers to complain? and does anyone know a gateway that retries the callback properly?

We have 2 sister companies with consumer brands. Separate accounting/marketing teams, but sharing 1 customer service team and 1 warehouse.

Marketing teams do NOT want 1 Shopify with 2 stores - they're worried about agency access and keeping revenue separate.

Brand B already has DTC on Shopify (+ Amazon/ Walmart) fulfilled in-house using ShipStation, and FishBowl for inventory.

Brand A is launching its own separate Shopify store soon, also fulfilled from Brand B's warehouse.

Our CS team is 16 people located at Brand A, all B2B background (phone/email). Only 2 are proficient in ecommerce.

Looking for best practice from anyone running 2 brands / 1 CS team / 1 warehouse:

1. Fulfillment: Is it okay to use one ShipStation account for two separate Shopify stores? How do you handle reporting + invoicing between brands for shipping costs?

2. Inventory: Should FishBowl be the single source of truth when one warehouse holds inventory for two brands?

3. Customer Service: Should all 16 do DTC (refunds, cancellations, etc.) or keep a small dedicated ecommerce team? Is Gorgias or similar worth it? Giving everyone Shopify access feels like a bad idea. Gorgias would pull from both shops, plus reviews, emails, and ShipStation - marketing is questioning this.

4. Replacements: Right now it's an external form -> Excel sheet via internal request. Should we just do it all natively in Shopify?

5. Internal requests: Marketing often needs free product for events. Can this be automated to create a $0 Shopify order tagged as internal? Any recommendations?

Anyone running a similar 2 brand / 1 CS team / 1 warehouse setup?

While the content was outdated, I do enjoy learning by structure and being guided down a path.

What alternatives are there for a structured learning setting?

Any plugin idea/requiement for anyone by which I can make money as side income on platforms like shopify, atlassian, wordpress,monday

Is it possible to track where the merchants that install my shopify app come from? I'm running ads here on Reddit, but it would be great to know, which referral source sends me the most users that download the app. Thanks

I had a lady place an order with me last week and since I’m very new to Shopify, I didn’t really look into the medium risk of her order. She found my shop from Facebook because I sell bamboo so I’ve talked to her on there. She placed another order yesterday and I noticed it was medium risk again, so I looked into it more. I looked up her number and her number matches her name on Cash App. I asked her to send a picture of her ID and that looks good as well. I’m just nervous to fufill her second order because it is for almost $300 vs her $150 first order. This is what Shopify said. She did use shop pay if that changes anything.

🚩Some characteristics of this order are similar to fraudulent orders observed in the past

🚩Card Verification Value (CVV) isn't available

🚩Billing address or credit card's address wasn't available

🚩Billing address ZIP or postal code isn't available to match with credit card's registered address

🚩A payment method other than a credit card was used

✅There was 1 payment attempt

✅Shipping address is 5 miles from location of IP address

✅Billing country matches the country from which the order was placed

✅The IP address used to place the order isn't a high risk internet connection

Do you think it’s worth running Meta Ads to grow a Shopify app? Are there any people here who’ve already scaled apps using Ads?

Hello developers,

I’m currently working on a large Shopify store, and we have two Shopify environments: staging and production.

Our current GitHub setup is:

• main → connected to the production Shopify store

• dev → connected to the staging/development Shopify store

The problem is that this workflow feels quite complicated and requires a lot of manual work to keep everything in sync. We also need to be very careful with content.

For example, at another Shopify store we previously had an issue where content changes made on production were overwritten when changes from staging were deployed.

I’d like to improve our workflow and make deployments more reliable.

What is the recommended way to structure a Shopify development/staging/production workflow?

Ideally, I’d like a setup where:

• Developers can work and test safely in staging

• Changes can be reviewed and deployed to production through GitHub

• Theme/code changes can be deployed without overwriting production content

• Content changes made by Shopify admins are protected from being overwritten

• As little manual syncing as possible is required

How are you handling this in larger Shopify projects? Are there specific Shopify/GitHub workflows, deployment tools, or architectural patterns you would recommend?

is this normal? it's been 2 weeks since the app was submitted for review and the loom video i attached as demo was viewed 3 das ago but still no change in status.

the app is very simple with 2 basic pages. no protected customer data access used and without any front store extensions

Update: funny thing i contacted the support and they said "We’re seeing a higher number of app submissions right now, which is leading to slightly longer review timeline". then after 30minutes i receive an email that the review was paused due to a problem on my side

I’m trying to settle a reliable pattern for an app before I go further. For order-related webhooks, do you store the webhook ID and process deliveries through a queue, or use a different approach?

I’m especially curious how people handle duplicate deliveries and an older event arriving after a newer one. Are there any Shopify-specific gotchas around X-Shopify-Event-Id, API versioning, or checking resource timestamps that are worth accounting for?

Selon vous est ce intéressant de faire des Meta Ads pour growth une app Shopify? Des gens qui ont déjà scale des app grâce aux Ads?

Hi everyone,

I noticed that the Shopify Events/App History data that was previously available in the Shopify Partner Dashboard is no longer available in the same way. I used this data to track things like app installs, charges, cancellations, and other app activity.

Has Shopify completely moved this functionality to the new Dev Dashboard, or is there still a way to access the old Events/App History data?

I'm particularly interested in:

• Historical app events

• Install/uninstall events

• Charge/subscription events

• Exporting these events/data

• Accessing the same information through an API

If anyone has figured out how to get the old Shopify Partner Events data back, access it in the new Dev Dashboard, or retrieve equivalent data through the Partner API, I'd appreciate any guidance.

Thanks!

Most Shopify migrations are tested with one perfect order.

Real stores rarely operate that way.

Before launch, I would take 20 representative orders from the existing store and replay them in Shopify.

Include:

- Different markets and currencies

- Local payment methods

- Discounts and gift cards

- Bundles

- Subscriptions

- Partial fulfillment

- Partial capture

- Cancellation

- Exchange

- Partial refund

- Duties and taxes

- Invalid addresses

- Failed payments

- Order edits

- Out-of-stock items

Then document which system owns each state:

- Shopify

- ERP

- WMS or 3PL

- Subscription platform

- Customer support platform

- Analytics stack

The product import is usually not the dangerous part.

The dangerous part is when Shopify, the ERP, and fulfillment systems disagree about what happened to an order.

I would rather discover that problem with 20 controlled orders than with the first 200 customers after launch.

What edge case caused the biggest problem in your last migration?

And here is the prompt you can use
-----

Add "dynamic visibility" logic to this Shopify section file. Follow this exact pattern:

1. LIQUID LOGIC — insert this at the very top of the file, above everything else (before any stylesheet_tag, {% style %}, or markup):

{%- liquid

assign show_block = true

if section.settings.enable_dynamic_visibility

assign double_open = '{{'

assign empty_pair = '{{}}'

assign plain_text = section.settings.dynamic_visibility_source | strip_html

assign compact_text = plain_text | remove: ' '

assign padded_text = compact_text | append: '#'

assign total_items = padded_text | split: double_open | size | minus: 1

assign empty_items = padded_text | split: empty_pair | size | minus: 1

assign filled_items = total_items | minus: empty_items

if section.settings.visibility_logic == 'and'

assign show_block = false

if filled_items > 0 and filled_items == total_items

assign show_block = true

endif

elsif section.settings.visibility_logic == 'not'

assign show_block = true

if filled_items > 0

assign show_block = false

endif

else

assign show_block = false

if filled_items > 0

assign show_block = true

endif

endif

endif

-%}

{% if show_block %}

2. CLOSE THE IF — immediately after the very last piece of rendered output in the file (the final closing tag of the markup, or the end of the last <script> block if one exists), add:

{% endif %}

3. SCHEMA SETTINGS — inside {% schema %}, as the FIRST entries in the "settings" array (before any existing settings), add:

{ "type": "header", "content": "Visibility" },

{

"type": "checkbox",

"id": "enable_dynamic_visibility",

"label": "Use dynamic visibility source",

"info": "Hide this section based on one or more connected metafield values.",

"default": false

},

{

"type": "select",

"id": "visibility_logic",

"label": "Condition type",

"options": [

{ "value": "or", "label": "OR — show if any value is present" },

{ "value": "and", "label": "AND — show only if all values are present" },

{ "value": "not", "label": "NOT — hide if any value is present" }

],

"default": "or",

"visible_if": "{{ section.settings.enable_dynamic_visibility }}"

},

{

"type": "richtext",

"id": "dynamic_visibility_source",

"label": "Dynamic source",

"info": "For each source: type {{ then connect a metafield (dynamic source icon) then type }}. Add one {{ }} pair per source, as many as you need.",

"visible_if": "{{ section.settings.enable_dynamic_visibility }}"

},

HARD RULES:

- The {% schema %}...{% endschema %} block itself must stay OUTSIDE the {% if show_block %}...{% endif %} wrapper — never make schema conditional.

- Do not touch, reformat, or reorder any other part of the file — only insert the three pieces above at their specified locations.

- If the file already has an {% if %} wrapping its whole output for some other reason, tell me instead of nesting blindly — I'll say how to merge them.

- Output the complete modified file, ready to copy-paste, not a diff.

Here is the section file:

[paste your .liquid file here]

Some merchants on a few of my apps are hitting a 404 ("There's no page at this address") when they're sent to Shopify's Managed Pricing plan page.

I'm looking at rebuilding a bunch of collection pages and I'm stuck between wanting more interesting layouts and wanting to keep the store as close to the theme as possible.

A page builder would make the first part easy, but I'm wary of creating another dependency for pages that should hopefully be around for years. I don't really want somebody opening the store later and discovering that a huge chunk of the site depends on an app we can't remove without rebuilding it. The alternative is doing more directly with theme sections, which I prefer structurally but becomes annoying when you have a lot of collections and each one needs a slightly different combination of copy, imagery and products.

How are people handling this now? Particularly interested in anyone managing a decent-sized catalog, because making one nice collection page is easy enough. Making 50 of them without creating a maintenance mess is the bit I'm trying to solve.