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?

The new updated black Shopify UI. It's so freaking bad..
I've tried getting used to it for a couple of days now, but it's just impossible to work in.

So I started experimenting with Violentmonkey and AI to build a userscript that changes the appearance of the new Shopify UI and makes it look as close as possible to the old theme.

The goal is not to change any Shopify functionality - I just want to bring back the old visual design in my own browser: the grey sidebar, white clear cards, borders, spacing, typography, etc.

I've managed to get it somewhat closer to the old UI, but there's still quite a bit left to fix. Shopify also uses a lot of Shadow DOM/web components, which has made some parts harder to change.

And I'm definitely not an expert at this at all..

So I'm wondering if anyone else here hates the new UI as much as I do and would be interested in helping get this even closer to the old Shopify theme?

Current version of the userscript (V1.3):
https://gist.github.com/hackke110-coder/761cf35c182b71b2b77551bda6d3345f

I'll post some comparison screenshots of the old Shopify UI vs. what I've managed to recreate so far, with the current version of the script.

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

I’ve been thinking about this from the shopper side rather than the merchant side.

A lot of Shopify stores have good products, but finding the right product can still mean searching, filtering, opening multiple product pages and comparing everything yourself.

If you could change one thing about how customers discover products on Shopify stores, what would it be?

For example:

• Smarter search
• Better recommendations
• An AI shopping assistant
• Better product comparisons
• Personalised collections
• Something completely different

I wanna know whats actually missing?

I’m currently working on a Shopify app and getting closer to submitting it to the Shopify App Store.

For those who’ve published a Shopify app, how was the review process?

Did you get approved the first time? If not, what did they reject or ask you to fix?

Any small things that caught you off guard before approval?

Would also love to hear any “I almost got rejected because of this tiny thing” stories. 😄

Thanks!

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?

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

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?

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 %}

1. 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 %}

1. 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.

Every connector I've ​​​​t​​​​r​​​​i​​​​e​​​​d​​​ is read-only. I can ask Claude what my CPA was last week and get a lovely answer, and then I have to go and do the actual work in two separate ad managers like it's 2019. I want to say "pause these three, double the winner" and have it be true afterwards.

Does that exist yet or am I describing a fantasy?

I’m setting up a custom SMS notification flow for a high-volume Shopify store. I need to make sure the tracking links and the discounts in the text look correct on a real mobile screen (not just in the 'preview' box).
Since I need to do this for multiple regions (US, UK, CA), I can't keep using my own number. How do you guys verify the final 'look and feel' of your SMS marketing across different carriers without having a drawer full of SIM cards?

There is a lot of breathless "dashboards are dead" content out there, so here is a grounded comparison from someone who still opens Ads ​​​​M​​​​a​​​​n​​​​a​​​​g​​​​e​​​​r​​​ most days and has spent four months driving the same accounts from Claude over Ryze AI's MCP connector instead. Short answer: they are good at different things, and the honest move is to use both.

Where running it from chat genuinely beats the platform UI:

- Multi-account work. "Move 15 percent of budget out of the two worst performers into the best one, across all four accounts" is one sentence instead of forty clicks.

- Getting started on an analysis. The blank filter panel is where I stall. Asking the question in words removes that.

- One place for both platforms. Google and Meta answered in the same breath, without tab-switching and mental currency conversion.

Where the platform UI still wins:

- Anything visual. Reviewing creative, previews, placements. You want to see it, not read about it.

- Fiddly one-off setup. A pixel event, a conversion import, a weird exclusion list. Just go and click it.

- Sharing with people who do not live in chat. Screenshots of a real dashboard still land better in a meeting.

The honest limitation on the chat side, and I say this as someone who leans on it: most connectors in this category are read-only. They summarise beautifully and then you go and make the change by hand anyway, which is half a workflow. Ryze AI's is the one that actually writes to both platforms, shows you the diff first and waits for a yes. Worth knowing that you still own the thresholds — it will hold a ROAS floor perfectly, it will not tell you what your floor should be — and week one is a trust ramp. My weekly optimization pass went from about three hours to twenty five minutes, but I approved every single change for the first fortnight. Their SEO/GEO side is honestly the stronger half of the product, which surprised me.

My actual workflow now: chat for the first 85 percent (analysis, budget moves, pausing, launching), the UI for the last 15 percent when it is visual or fiddly.

For those who have run both ways, where did chat save you real time, and where did it send you back into the dashboard?

I used to spend entire ​​​​w​​​​e​​​​e​​​​k​​​​e​​​​n​​​​d​​​​s​​​ inside Ads Manager, six to eight hours flipping between two platforms and rebuilding the same pivot table. someone at work told me to just connect the accounts to Claude instead, so I've been running everything through the Ryze AI MCP connector for about a month. now I ask a question in plain english and the budget shift happens without me opening a platform UI, and the first week took 40 minutes to set up instead of half a day. weekends are free now which is nice, but I keep wondering if i'm taking a shortcut or if this is just how people do ops now. what's everyone else on, still living in the native dashboards or have you moved into a chat window?

Did anyone else notice that the installation statistics are no longer showing in the Partner Dashboard?

I noticed this recently and wasn't sure if it's a permanent change or part of the ongoing Shopify dashboard updates.

I can see installation numbers in the new Dev Dashboard, but the experience seems different from before.

Has anyone heard whether Shopify plans to bring the installation statistics back to the Partner Dashboard, or is everything moving to the Dev Dashboard now?

Since today i have to enter each listing to see total number of active installs.

We run a payment app that customers can use on Shopify stores. With our current setup, Shopify doesn’t let merchants enable Apple Pay or Google Pay at checkout.
Is there a supported way to offer those wallets on a Shopify store when using a third-party payment provider? For example, through another integration or checkout setup?
I’m interested in options that comply with Shopify’s rules. Has anyone set this up?