u/Creative_Slip_5497

Do you keep wholesale and retail in one Shopify store or split them?

My wife and I run a small clothing store on Shopify, and we’ve started getting more interest from local boutiques. It’s not huge volume yet, but it’s becoming enough that I need to decide whether wholesale should live inside the same store or be separated before we make a mess for ourselves.

Right now the retail side is simple. People come to the site, buy one or two pieces, and everything runs through the normal product pages and checkout. Wholesale is different. A boutique might want 12 units across sizes, different pricing, different payment expectations, and sometimes a cleaner way to reorder the same items later. I can handle that manually for a few buyers, but I can already see how it could get annoying once more stores are involved.

My first instinct was to keep everything in one Shopify store because inventory would stay cleaner. I don’t really want to manage two catalogs, two sets of product photos, two stock counts, and two admin workflows. But the downside is that wholesale pricing, buyer approval, minimum quantities, and product visibility all have to be handled very carefully. One wrong rule and either a retail customer sees the wrong thing or a wholesale buyer has a confusing checkout.

The other option is a separate wholesale store. That sounds cleaner for buyers, but it also sounds like more maintenance. Updating products twice, syncing inventory, keeping collections consistent, and making sure both stores do not slowly drift apart sounds like its own headache.

For people who run both DTC and wholesale on Shopify, which route did you take?

Did you keep wholesale inside the main store, or did you eventually separate it? I’m less interested in app names and more interested in the operational problems that showed up later. Inventory, checkout confusion, buyer approval, minimum orders, duplicate product work, tax, payment terms, whatever ended up being more annoying than expected.

reddit.com
u/Creative_Slip_5497 — 3 days ago

I run a SaaS in the AI video space, and we went through the usual Intercom dilemma.

Intercom is a very good product. I don’t think anyone serious can say otherwise.

But at an earlier stage, it started feeling like we were paying for a lot more platform than we were actually using.

We were mostly using:

live chat
shared inbox
basic routing
some saved replies/workflows
basic support visibility

We were not using the heavier stuff like product tours, advanced outbound campaigns, complex customer journeys, or deep support ops reporting.

That made me step back and look at alternatives more carefully.

Not as a “top 10 tools” thing.

More like:

If we move away from Intercom, what should we not mess up?

Because switching support tools is not like changing a landing page tool. If customers are already messaging you there, the migration affects your team, response times, workflows, historical conversations, and sometimes even sales.

Here’s how I’d compare Intercom alternatives after going through this.

First filter: pricing model

This matters more than the homepage feature list.

Some tools charge per seat. Some charge by conversation volume. Some charge extra for AI resolution. Some are more flat monthly pricing.

This sounds boring until your usage grows.

A tool that looks cheap at 200 conversations/month may not feel cheap at 3,000 conversations/month.

For example, Intercom is powerful, but once you add seats, AI usage, and other add-ons, the bill can climb fast. Tidio is easier to start with, but you still need to watch conversation and automation limits. Crisp is attractive if you like predictable pricing. Chatway looked interesting to me mainly because it sits closer to the “simple inbox + live chat + AI without enterprise complexity” side of the market.

Second filter: Are you replacing Intercom or replacing only 20% of Intercom?

This was the biggest mindset shift for me.

A lot of startups say they need an Intercom alternative.

But what they actually need is:

a live chat widget
a shared team inbox
simple automation
AI for repetitive questions
customer context
easy handoff to humans

That is very different from needing a full customer engagement platform.

If you need lifecycle campaigns, complex segmentation, product tours, enterprise-grade reporting, and advanced outbound flows, Intercom still makes sense.

If you mostly need faster replies and fewer missed conversations, you can probably use something lighter.

Third filter: AI pricing and handoff

Every support tool now says “AI”.

That doesn’t mean the pricing or workflow is the same.

I’d check:

Does AI charge per resolution?
Does it charge per conversation?
Can it hand off cleanly to a human?
Can it be trained on your help docs?
Does it work only in chat, or across other channels too?
What happens when the AI fails?

That last one is underrated.

Bad AI handoff creates more support work, not less.

Fourth filter: channels

Early on, website chat was enough for us.

Later, customer conversations started coming from more places.

Website. Email. Sometimes social. Sometimes random support messages through forms.

That’s when the multichannel inbox started mattering more.

Not because it is fancy.

Because switching between tabs is where small teams quietly lose time.

So if you are comparing tools, I’d look at whether the product can centralize the channels you actually use today, not every channel under the sun.

Fifth filter: migration pain

This is where founders underestimate the switch.

Before moving, I’d ask:

Can we export old conversations?
Will we lose customer context?
How hard is it to train the team?
Will the new widget slow the site?
Can we recreate basic workflows quickly?
Can we keep response times stable during the switch?

A cheaper tool that creates two weeks of chaos is not really cheaper.

My rough read on the main options:

Intercom is still the most complete if you use the full platform. Great product, but can feel heavy and expensive if you only need basic support.

Chatway feels more suited for small teams that want live chat, shared inbox, AI support, and simpler pricing without turning support into a full enterprise setup.

Tidio is strong for e-commerce and smaller teams that want chat + chatbot quickly, but I’d watch how pricing scales with usage.

Crisp is good if predictable billing matters and you want more of an all-in-one support inbox style setup.

Freshdesk makes sense if you are moving toward ticketing and structured support processes.

Zendesk is powerful, but for many early-stage teams it may feel like too much too soon.

My main takeaway:

Don’t ask “what is the best Intercom alternative?”

Ask:

What part of Intercom are we actually using?

If the answer is mostly live chat, inbox, basic automation, and AI replies, then a lighter tool probably makes sense.

If the answer is advanced customer engagement, campaigns, support ops, reporting, and complex workflows, then Intercom may still be worth the cost.

For early-stage teams, I’d optimize for:

simple setup
predictable pricing
clean inbox
good AI handoff
enough integrations
easy migration

Not the longest feature list.

Would love to hear from other founders here.

If you moved away from Intercom, what did you switch to and what was the real reason?

Pricing, complexity, support workflow, AI, or something else?

reddit.com
u/Creative_Slip_5497 — 20 days ago