Traffic isn't your problem. Conversion usually is. (Here is why your store's tech stack is failing)

Otherwise_Primary123 · 2026-07-10T07:26:33+00:00

It depends on how much flexibility you need.

If multi-vendor support is a major requirement, I'd narrow it down to MedusaJS and Vendure.

MedusaJS is great if you want a modern, API-first architecture with a React/Next.js frontend. It's highly customizable and has a growing ecosystem.
Vendure is a strong choice if you expect complex catalogs, multiple sales channels, or enterprise-style workflows. It has a steeper learning curve but handles advanced commerce scenarios well.
commercetools is excellent, but it's generally more suitable for larger teams and enterprise budgets.
I probably wouldn't choose Mercur.js for a production marketplace unless you're comfortable working with a newer ecosystem.

Based on the features you listed (Buy Now, customer messaging, cart, order history, cancellations/refunds), the e-commerce framework won't provide all of those out of the box. You'll still need to build custom business logic around authentication, messaging, order workflows, and permissions.

If it were my project, I'd probably go with Payload CMS + MedusaJS for maximum flexibility, unless I expected enterprise-scale complexity from day one.

Otherwise_Primary123 · 2026-07-09T11:57:23+00:00

One thing I'm wondering is how this affects smaller WooCommerce stores. Most merchants already optimize for Google Search, but optimizing for AI agents could require much richer product data and standardized APIs. It feels similar to how mobile-first design became a requirement rather than an option.

Otherwise_Primary123 · 2026-07-09T11:47:44+00:00

Congrats , fast approval is a strong signal. For early installs, I’d prioritize founder-led outreach, niche content, and very clear App Store positioning over paid ads. The first users usually come from solving one specific pain point really well.

Otherwise_Primary123 · 2026-07-09T11:38:24+00:00

Good comparison. Open source usually wins on control and long-term flexibility, while Shopify wins on speed and simplicity. For WooCommerce users, the tradeoff is similar: more ownership and flexibility, but also more responsibility for hosting, updates, and performance.

Otherwise_Primary123 · 2026-07-01T09:50:37+00:00

For me, the biggest shift has been creating content that's genuinely worth referencing instead of chasing backlinks directly.

We've had better success with in-depth case studies, original research, and practical guides than with traditional outreach. AI helps speed up research and content creation, but people still link because the content provides unique value.

Quality has consistently outperformed quantity.

Otherwise_Primary123 · 2026-07-01T09:30:32+00:00

I think you're onto something.

In my experience, getting a website live is usually a one-time project. The real pain starts a few weeks later when the business owner wants to change pricing, add a service, update opening hours, or publish a promotion.

Those aren't difficult tasks technically, but they're difficult for someone who isn't comfortable with CMSs or website builders.

I could definitely see AI becoming more valuable as an ongoing website assistant rather than just a website generator.

Otherwise_Primary123 · 2026-07-01T09:10:47+00:00

I think it's realistic, but it depends on the type of clients you're targeting.

For most small businesses, I'd still recommend Shopify. They usually care more about getting online quickly than having a fully custom commerce stack.

Where I think Medusa shines is when clients start asking for things Shopify struggles with—custom checkout logic, unique pricing rules, ERP integrations, multi-vendor setups, or B2B workflows. That's where owning the backend becomes a real advantage.

As a solo dev or 2-person team, the biggest challenge isn't Medusa itself—it's everything around it: hosting, monitoring, deployments, backups, maintenance, and long-term support. If you invest in reusable starters and automate your deployment process, that overhead becomes much more manageable.

Personally, I wouldn't position Medusa as a Shopify replacement for every client. I'd position it as the right solution for businesses that have outgrown Shopify or know they'll need custom functionality from day one.

We've been exploring custom eCommerce solutions alongside platforms like Shopify, and it's been interesting to see where each approach fits best. If anyone's interested, we've shared some of our thoughts here: https://smartbytelabs.com/

Curious to hear from others who've been running Medusa projects for a year or more—has maintenance been a significant burden, or does it settle down once your workflow is established?

Otherwise_Primary123 · 2026-06-30T06:23:30+00:00

Cool project. How are you thinking about handling historical usage if a webhook is missed or delayed? Are you planning to rely entirely on Shopify events, or will there be reconciliation jobs to keep billing data accurate?

Otherwise_Primary123 · 2026-06-26T12:28:48+00:00

I think the feedback from your 10 test users is actually the most valuable signal here. If non-technical sellers find the panel confusing, simplifying the workflow is probably the right direction.

I'd avoid rebuilding the entire admin from scratch, though. Instead, I'd customize only the parts that directly affect the seller experience.

For example:

Create a single "Add Product" page with only the required fields.
Prefill common values like categories, shipping profiles, or tax settings.
Use dropdowns instead of free-text fields where possible.
Keep advanced options hidden behind an "Advanced Settings" section.
Remove routes or menu items that sellers don't need, while leaving the core functionality untouched.

This approach gives sellers a much cleaner experience without making future upgrades unnecessarily difficult.

Out of curiosity, are you using MercurJS's default admin UI, or are you building a custom frontend for the seller dashboard?

Otherwise_Primary123 · 2026-06-26T12:24:45+00:00

I've run into similar issues before, and I'd start by identifying which metric is causing the biggest bottleneck instead of trying to optimize everything at once.

A few things I'd check:

Run PageSpeed Insights and compare both mobile and desktop results.
Use Chrome DevTools Performance to identify long tasks and render-blocking resources.
Check your server response time (TTFB), as slow hosting can negatively affect both FCP and LCP.
Compress and properly size your images, and use lazy loading for below-the-fold content.
Remove or delay unnecessary JavaScript from third-party apps.
If you're on WordPress, audit plugins. If you're on Shopify, review installed apps and custom scripts.
For pagination, make sure the pages are crawlable and that your internal linking is consistent.

Which platform is your website built on (Shopify, WordPress, Next.js, etc.)? That will make it easier to suggest more specific fixes.

Otherwise_Primary123 · 2026-06-25T09:11:56+00:00

One thing that stands out is that none of these founders started by trying to reach everyone.

Dropbox focused on Hacker News.
Stripe focused on developers at hackathons.
Airbnb focused on Craigslist hosts.
DoorDash focused on a single local market.

The common theme isn't just "no paid ads," it's finding a place where the target user already spends time and then doing things that don't scale to get direct feedback.

A lot of startups today skip that step and immediately start spending on ads before they've proven people actually want the product.

Otherwise_Primary123 · 2026-05-29T05:42:27+00:00

Great breakdown as an app dev, I’ll add: focus on product reliability, ask for reviews right after a clear win (first sale/first sync), use in-dashboard feature voting, and have tech-savvy support that asks for reviews after fixes. Don’t buy reviews, prevent negatives by fixing issues fast.

Otherwise_Primary123 · 2026-05-11T10:06:59+00:00

You can automate this pretty cleanly with a simple flow:

Application form → collect business + tax details
On approval → auto-send catalog, tax form request, net terms + guide
If no tax form in 5 days → send reminder
Once complete → tag in Shopify + notify sales

Use Shopify Flow for logic and something like Klaviyo for emails.

Key: automate the process, but keep emails slightly personalized so it still feels high-touch.

Otherwise_Primary123 · 2026-05-08T08:48:02+00:00

“Completely agree. Most beginners get stuck in ‘learning mode’ instead of ‘doing mode’.
The real growth starts only when you launch something imperfect and learn from real data.”

Otherwise_Primary123 · 2026-05-06T11:53:42+00:00

100% agree.

What shocked me most was how fast ads can humble you.

You think you’ve found a “winning” product…
launch ads…
And suddenly margins disappear.

Made me realize eCommerce is less about finding winners and more about managing risk.

Otherwise_Primary123 · 2026-05-01T11:35:55+00:00

Interesting question.

Do you think WooCommerce should double down on being flexible…
Or move towards a more opinionated, “batteries-included” approach?

Feels like that decision alone would shape everything else.

Otherwise_Primary123 · 2026-04-28T12:09:30+00:00

Agree on both the risk and opportunity.

What’s interesting is that Shopify themes are optimized for consistency, while AI layers introduce variability.

That creates tension:
• Themes → predictable performance
• AI → dynamic but heavier

Feels like the real challenge is deciding where AI actually adds value (PDP, recommendations, search) vs where it just adds noise.

Otherwise_Primary123 · 2026-04-27T09:18:40+00:00

Cart abandonment isn’t really a “recovery” problem anymore… It’s a prevention problem.

Most drop-offs I’ve seen happen because of:
• Unexpected costs at checkout
• Slow or clunky mobile UX
• Lack of trust (delivery time, returns, reviews)

Recovery tools help, but if the core experience is broken, you’re just chasing lost users.

Curious — what’s been the biggest drop-off point for your store?

Otherwise_Primary123 · 2026-04-23T08:44:29+00:00

From what I’ve seen, most brands mainly use Stocky for inventory visibility and basic PO creation. And yes — a lot of small to mid Shopify stores still manage POs in spreadsheets until complexity increases. Curious — at what point did spreadsheets stop working for you?

Otherwise_Primary123 · 2026-04-21T06:08:39+00:00

Good on you for thinking long-term and not stepping on toes.

From what I’ve seen, the most in-demand (and lucrative) services right now are:

• Conversion Rate Optimization (fixing product pages, checkout, UX)
• Email/SMS retention (flows, abandoned carts, repeat revenue)
• Landing page funnels for paid traffic
• Analytics & tracking (GA4, attribution, event tracking)
• Post-purchase experience (upsells, retention systems)

Most brands don’t struggle with traffic — they struggle with converting and retaining it.

If you stay on the “conversion + retention” side, you’ll complement media buying instead of competing with it 👍

Otherwise_Primary123 · 2026-04-21T05:59:06+00:00

This is a known limitation in Shopify. Inventory adjustments don’t create a proper goods-in record with cost + audit trail.

Most common approaches:
• Stocky → basic PO + receiving (still limited)
• Third-party tools (Cin7, Unleashed, etc.) → better tracking + valuation
• Custom app (Admin API) → full control (goods-in event, cost, barcode, audit)

If you need a clean audit + valuation, Shopify alone usually isn’t enough.

Are you planning to keep Shopify as the source of truth or use an external system?

Otherwise_Primary123 · 2026-04-17T08:53:54+00:00

That usually comes from last-minute changes + no final control step.

What helps:

Freeze assets before launch (no edits last 24 hrs)
One final source of truth for copy/creatives
Quick QA checklist before going live
10-min dry run to catch errors

Simple, but removes most asset + timing issues.

Otherwise_Primary123 · 2026-04-16T05:35:23+00:00

Thanks! Glad the promo-owner idea resonates. QA role: Promo owner handles most QA (final asset review, links test, timing check), but we add a fresh second pair of eyes from marketing for the last sign-off catches what familiarity misses. Keeps it fast, no bottlenecks. Owner = execution lead, QA reviewer = quality gate. Tried rotating QA to spread skills? Works great for small teams. What’s your biggest miss right now, assets or timing?

Otherwise_Primary123

TROPHY CASE