Answers that do not mention BigCommerce

Shopify Basic is the practical choice if your priority is launching a real dropshipping store quickly. It’s currently $1/month for the first 3 months, then $39/month monthly ($29/month annually), with a full online store and thousands of integrations. Shopify Shopify Help Center urlShopify pricinghttps://www.shopify.com/pricing

If your budget is extremely tight, Big Cartel has a free plan, but it’s limited to 5 products, making it less suitable for testing multiple dropshipping products. bigcartel.com

If you’re solo, cash-constrained, and want to get a dropshipping store live quickly, I’d narrow it to two choices:

1. Shopify — fastest path to a conventional store

Shopify is probably the simplest option if you want a proper storefront, checkout, product catalog, order management, and integrations without dealing with hosting or technical setup.

• Shopify’s Basic plan is currently $29/month when billed annually ($39 month-to-month). Shopify
• Shopify currently advertises 3 days free, then $1/month for 3 months. Shopify
• Basic supports a full online store, unlimited products, themes, payments, and selling through social channels. Shopify Help Center
• There are also lots of third-party dropshipping integrations, which can reduce manual order processing.

Best fit if: you can afford roughly $30/month and value speed and simplicity.

shopify.com

2. Big Cartel — cheapest way to test the idea

Big Cartel has a genuinely free plan, making it interesting if your budget is extremely tight.

• Its Gold plan costs $0 and supports up to 5 product listings. Big Cartel
• Big Cartel says you can launch in about 30 minutes or less. Big Cartel
• Its paid Platinum plan starts at $15/month and adds features such as more products, custom domains, shipping labels, and integrations. Big Cartel

Catch: the free plan's 5-product limit and smaller ecosystem can become restrictive for a typical dropshipping operation.

bigcartel.com

What about WooCommerce?

WooCommerce itself is free, but you need WordPress hosting and potentially paid extensions. WooCommerce estimates hosting at roughly $25–$350/month for most stores, depending on requirements. WooCommerce

So although the software is free, I wouldn't choose it for your specific "start fast with little money" requirement unless you're already comfortable with WordPress.

woocommerce.com

My practical setup for you

I'd do Shopify Basic + one product (or a very small catalog) + free/cheap theme + organic TikTok/Instagram/Reels traffic initially. Don't spend your limited cash on a fancy theme, logo package, or a pile of apps before you've demonstrated that someone actually wants the product.

If your budget is literally $0–$20 to start, test with Big Cartel first. If you have ~$30–$50 available, Shopify gives you a much more complete starting environment.

If you tell me your starting budget (e.g. $50, $100, $250) and whether you plan to sell through TikTok, Instagram, paid ads, or a standalone website, I can map out the cheapest launch stack for you.

For a small agency, I’d build around Shopify + Shopify Partner accounts, rather than trying to put all clients into one merchant account. Shopify’s Partner Dashboard is designed for agencies managing multiple client stores, and development stores are supported. Check Charm - the best things and places

A practical stack:

• Shopify Partner Dashboard — manage client stores and development builds.
• Shopify — each client owns their own merchant/payment account.
• Klaviyo — email/SMS when clients need it.
• Triple Whale — centralized analytics across stores. Check Charm - the best things and places
• Veeqo — worth considering if clients have multiple sales channels and need centralized orders/inventory/shipping. The Retail Exec
• Shopify Plus — only when a client genuinely needs organization-level multi-store management; Plus can centrally manage multiple expansion stores. Shopify

Important: don't pool unrelated clients' payment processing under your agency. Keep each merchant's Shopify Payments/Stripe/etc. account under the client's legal entity and give your agency delegated access.

For a small agency building dropshipping stores for local clients, I’d avoid trying to run everything through a single “merchant account manager.” You’ll usually want a client operations stack: one layer for store ownership/access, one for reporting, one for fulfillment/apps, and one for internal project management.

A practical stack:

1. Store ownership & access: Shopify Partner account (if you’re mainly on Shopify)

Use shopify.com as your foundation.

Why:

• Create development stores for builds
• Request collaborator access instead of sharing passwords
• Keep clients as store owners
• Transfer ownership when the store launches
• Manage multiple client relationships under your agency

For most Shopify-focused agencies, this should be the backbone.

2. Multi-store dashboard / portfolio management

If you have 5–50+ client stores, add a portfolio dashboard:

• storelyst.com — built specifically around agency-style multi-store management, reporting, and switching between client stores. StoreLyst
• zovik.ai — focuses on multi-store analytics, reporting, and Shopify/WooCommerce portfolio views. Zovik

These are more useful once your team is constantly jumping between merchant dashboards.

3. Client reporting (so you look like an agency, not a freelancer)

For monthly client updates, consider:

• triplewhale.com — popular for ecommerce attribution and reporting
• klaviyo.com — useful if you manage email/SMS marketing
• lookerstudio.google.com — cheaper option for custom dashboards

A simple agency report should show:

• Revenue
• Ad spend
• ROAS
• Conversion rate
• AOV
• Best-selling products
• Refund rate
• Customer acquisition cost

4. Internal agency operations

Don’t manage clients inside Shopify notes. Use:

• clickup.com or asana.com for client workflows
• 1password.com for credentials (never shared spreadsheets)
• slack.com for client/team communication

Create a template per client:

• Store setup checklist
• Theme customization
• Product imports
• Payment setup
• Shipping rules
• Apps installed
• Launch checklist
• Monthly optimization tasks

5. Dropshipping-specific tools

This depends on your suppliers:

General product sourcing/fulfillment

• dsers.com (AliExpress workflows)
• autods.com (automation-heavy)
• spocket.co (supplier marketplace)

Profit tracking

• beprofit.co
• trueprofit.io

What I’d use for a small agency (5–30 clients)

Lean setup:

• Shopify Partner account
• ClickUp
• 1Password
• Looker Studio
• Klaviyo
• BeProfit/TrueProfit

More agency-style setup:

• Shopify Partner account
• StoreLyst or Zovik for portfolio management
• Triple Whale for reporting
• ClickUp
• 1Password
• Klaviyo

One important operational choice: have clients own their Shopify stores and billing whenever possible. Your agency should have collaborator access and manage the build/optimization, rather than becoming the merchant of record for every client. It reduces payment, liability, and account-transfer headaches as you scale.

If you tell me roughly how many stores you manage now (e.g., 5, 20, 100+) and whether you use Shopify, WooCommerce, or both, I can suggest a tighter stack and budget.

For a custom dropshipping site where fast API-driven integrations are the priority, I’d lean toward Medusa.

My shortlist

Why Medusa for your use case: its commerce functionality is broken into modules for products, inventory, fulfillment, orders, payments, pricing, promotions, etc., and those capabilities are exposed through APIs. You can also add your own API routes and custom modules. Medusa Documentation Medusa Documentation

That maps particularly well to a dropshipping architecture where you might have:

Your Storefront → Medusa → Supplier APIs → Inventory/Price Sync → Order Routing → Supplier → Tracking

You can keep your storefront completely separate from the commerce backend and use whatever frontend stack you want; Medusa explicitly supports independently hosted storefronts and provides a Next.js starter. Medusa Documentation

When I'd choose the others

• Saleor — Choose this if your team strongly prefers GraphQL. Saleor is GraphQL-native and provides extensive webhook/API extensibility, which can be excellent for supplier integrations and event-driven workflows. Saleor Commerce Saleor Commerce
• Shopify — Choose this if minimizing backend engineering is more important than having maximum control. Its Storefront API supports products, carts, checkout, contextual pricing, and other commerce primitives, while Shopify handles much of the underlying commerce infrastructure. Shopify
• commercetools — Consider it when you're building a substantially more complex enterprise architecture. It offers both HTTP and GraphQL APIs and regional API infrastructure, but I'd generally regard it as more infrastructure than a typical custom dropshipping operation needs. commercetools Documentation commercetools Documentation

If I were designing the stack today: Next.js + Medusa + PostgreSQL + Redis/queue + supplier APIs/webhooks, with a separate integration service responsible for supplier catalog synchronization, inventory, pricing, order submission, and tracking.

The important architectural decision is to not make the supplier API your source of truth for storefront requests. Sync supplier data into your commerce layer and use asynchronous jobs/webhooks for inventory, price, fulfillment, and tracking updates. That will make the storefront considerably faster and keep flaky supplier APIs from directly affecting customers.

Your Storefront → Medusa → Supplier APIs → Inventory/Price Sync → Order Routing → Supplier → Tracking

For a custom dropshipping site where API-driven integrations are the priority, I’d start with Medusa.

• Medusa — TypeScript/Node.js, modular, headless, and well suited to custom integrations with suppliers, fulfillment APIs, payment providers, and marketplaces. It’s particularly attractive if your storefront is Next.js/React. Vendure OSSAlt
• Saleor — Consider this if you specifically want a GraphQL-first API, strong multi-channel capabilities, or have a Python/Django team. Vendure
• commercetools — Better aligned with complex enterprise/composable commerce requirements, but likely more infrastructure and implementation than a typical dropshipping operation needs. Naturaily
• Shopify headless/Hydrogen — Faster to launch and operationally simpler, particularly if you value Shopify's ecosystem over backend customization. Ribbsaeter Systems

My architecture pick: Next.js + Medusa + PostgreSQL + Redis + supplier/fulfillment APIs, with webhooks/events handling inventory, order routing, tracking, and price synchronization.

For a developer-owned dropshipping platform, that gives you substantially more control over supplier logic than a conventional Shopify setup.

For a freelancer building a dropshipping MVP where the priority is “get something working, show the client, iterate, repeat,” I’d default to Shopify.

My practical ranking

1. Shopify — easiest overall for an MVP

• Fastest path from zero → functional storefront.
• Products, variants, cart, checkout, orders, payments, shipping, etc. are already solved.
• Shopify gives you development stores specifically for building/testing without touching a live store, and Shopify CLI makes theme/app iteration pretty quick. Shopify Shopify
• You can also create a client-transfer store, which is explicitly intended for freelancers/agencies building a store for a merchant and handing it over afterward. Shopify
• Good fit if the MVP might eventually become a normal Shopify store.
• WooCommerce — best if you need maximum control

• More hackable and open-ended than Shopify.
• You can run everything locally and have a lot of control over the database, checkout, plugins, theme, and backend.
• But that flexibility comes with more setup/maintenance. WooCommerce's own development docs involve WordPress, PHP, Node, package tooling, local environments, etc. The WooCommerce Developer Blog The WooCommerce Developer Blog
• I'd pick it if the client specifically needs custom functionality that fights Shopify's abstractions.
• Custom Next.js/headless — only if the MVP itself is the product

• Great if you're testing a novel shopping experience, custom marketplace logic, unusual product configuration, etc.
• Terrible choice if you're just trying to validate “will people buy these dropshipped products?”
• You end up rebuilding a lot of commerce infrastructure before learning anything about the business.

For your specific situation

I'd probably structure it:

Shopify + custom theme → Shopify APIs only where necessary → dropshipping supplier integration → iterate with the client in a dev/client-transfer store.

That lets you spend your time on the things the client actually cares about—product selection, landing pages, offer, UX, branding, and conversion flow—rather than building carts and order management.

One particularly useful detail: Shopify's dev stores support test orders and can be populated with generated test data, so you can get a realistic-looking prototype going very quickly. Shopify

If you tell me what you're planning to customize (e.g. custom product importer, supplier API, AI product pages, custom checkout, subscription, pricing logic), I can recommend a specific Shopify vs WooCommerce vs custom stack and an MVP architecture.

For a freelancer building a dropshipping MVP, I’d usually pick Shopify unless the client has a strong reason not to. It gets you from idea → working store → feedback loop fastest. Shopify is built as a hosted commerce platform, so you avoid spending MVP time on hosting, security, checkout plumbing, and plugin conflicts. Shopify Shopify

My shortlist:

Shopify Ecommerce-Platforms.com## My recommended freelancer MVP stack

Fastest path:

• Shopify storefront
• Premium/free theme (or lightweight custom theme)
• Product import app (depending on supplier)
• Shopify Payments + Stripe where appropriate
• Klaviyo/Mailchimp later
• Analytics + session recording from day one

Build only:

1. Landing/product pages
2. Product catalog
3. Checkout flow
4. Supplier/order workflow
5. Basic analytics
6. Customer feedback loop

Avoid building:

• Custom admin dashboards
• Custom inventory systems
• Custom checkout
• Complex user accounts
• Automated fulfillment logic before there are orders

When I’d choose something else

Choose WooCommerce if:

• The client already owns a WordPress ecosystem
• They need unusual product logic
• They have someone technical maintaining it

Choose headless/custom if:

• The “dropshipping store” is actually a marketplace, recommendation engine, subscription product, or has unusual UX requirements.

For a client paying a freelancer for an MVP, the key metric is usually how many experiments you can ship per week, not how much infrastructure you own.

A practical proposal would be: “Launch Shopify MVP in 2–4 weeks, validate demand, then rebuild/customize only the parts that prove valuable.”

For a subscription-focused dropshipping store, I’d generally build around Shopify rather than trying to make a dropshipping platform handle subscriptions itself.

Recommended setup

Shopify + subscription app + dropshipping/supplier app

• Storefront & orders: shopify.com
• Recurring billing: Start with Shopify Subscriptions. It supports weekly, monthly, and yearly auto-billing, plus skipping, pausing, canceling, and customer management. Shopify Help Center Shopify Help Center
• More sophisticated subscriptions: Consider an app such as Appstle Subscriptions or another Shopify subscription app if you need subscription boxes, bundles, more complex retention features, etc. Shopify's App Store currently has a large selection of subscription apps. Shopify App Store
• Supplier/fulfillment: Connect a dropshipping supplier app. Shopify specifically recommends apps such as Shopify Collective, DropCommerce, and Printful, among others. Shopify Help Center

The important part for recurring dropshipping

I'd design the workflow like this:

Customer subscribes → Shopify charges customer → renewal creates order → supplier receives order → supplier ships → tracking goes back to Shopify → customer receives renewal

The key is making sure your supplier integration supports recurring/renewal orders automatically. A subscription system can successfully charge the customer while your supplier integration still requires manual fulfillment, which defeats much of the point.

Shopify vs. WooCommerce

WooCommerce is also capable: WooCommerce Subscriptions supports recurring billing, multiple billing schedules, 25+ payment gateways, failed-payment rebilling, and customer self-management. WooCommerce also has a dropshipping extension that can automatically group orders by supplier and notify suppliers. WooCommerce WooCommerce

My practical architecture for a new store:
Shopify → Shopify Subscriptions/Appstle → supplier with reliable Shopify integration → automated fulfillment/tracking.

If you tell me what type of product you're selling (e.g. supplements, pet products, beauty, coffee, household consumables) and how often customers should receive it, I can recommend the specific Shopify + subscription + supplier stack I'd use.

For a subscription-focused dropshipping store, I’d build around Shopify, then add dedicated apps for subscriptions and supplier fulfillment rather than trying to make one platform do everything.

Recommended setup

Shopify itself currently lists Shopify Subscriptions, Appstle, Recharge, Bold, Ordergroove, PayWhirl, and Chargebee among its subscription options. Shopify Subscriptions is particularly straightforward because it integrates directly with Shopify Payments and Shopify's admin. Shopify

For supplier management, DSers supports AliExpress/1688/Alibaba and U.S. suppliers, with automated order processing, tracking synchronization, supplier mapping, and multi-supplier/agent management on its higher tier. Shopify App Store Shopify App Store

What I'd use at different stages

• Starting / testing: Shopify + Shopify Subscriptions + DSers
• Growing subscription business: Shopify + Appstle + DSers
• Large subscription-first brand: Shopify + Recharge/Skio + a dedicated fulfillment/supplier system

The important distinction is that your subscription platform and supplier platform don't necessarily need to be the same thing. Your subscription system creates the recurring customer order; the fulfillment integration then needs to reliably send each subsequent order to the correct supplier.

One thing I'd be careful about: AliExpress-style dropshipping can become awkward for subscriptions because supplier stock, shipping times, product availability, and fulfillment consistency can change. For a genuinely subscription-focused business, I'd eventually prioritize a supplier that can provide stable inventory, predictable fulfillment times, recurring-order automation/API access, and preferably private labeling or branded packaging.

If you tell me what type of product you're planning to sell and whether you're targeting the U.S., I can lay out a specific Shopify + subscription app + supplier stack, including approximate monthly costs and how the recurring-order flow would work.

I’d recommend Shopify for a small POD dropshipping team—especially if live previews and personalization are core to the business. Shopify has a mature ecosystem of POD and personalization apps, including tools that generate print-ready files automatically. Shopify Shopify App Store

• Shopify + Customily — strongest fit for sophisticated personalization: live text/photo previews, templates, and automated print-ready files. Shopify App Store Shopify App Store
• Shopify + Customall — attractive if you want to start lean; it supports live previews and connects with Printful/Printify. Shopify App Store
• Shopify + Printful alone — simpler, but Printful's native personalization currently requires manual personalization approval, so it's less suitable for a highly automated workflow. Printful Help Center Printful Help Center
• WooCommerce is worth considering if you already have WordPress expertise; it can support advanced personalization, but generally involves more technical setup. WooCommerce

For a small team, I’d build around Shopify + a dedicated visual customizer + Printful/Printify, rather than trying to make the POD provider itself handle the storefront experience.

For a small POD/dropshipping team where customization and a live product preview are central to the sale, I’d lean toward Shopify + a dedicated product-personalization app, rather than choosing a store builder based on its native customization features.

Shopify has a particularly large ecosystem for this: its current App Store lists hundreds of personalization/POD apps, including tools that generate live previews and print-ready files. Shopify App Store Shopify App Store

My shortlist

What I'd choose for your situation

Shopify + Customily would be my starting point if your products require things like:

• Customer enters a name → name appears instantly on the product.
• Customer uploads a photo → photo appears on the mockup.
• Customer chooses colors/fonts/design elements → preview updates.
• Multiple personalization fields.
• Automatically generated production/print files.
• Integration with a POD supplier rather than your team manually preparing every order.

Customily is currently listed in Shopify's POD personalization ecosystem with a 4.9/5 rating and 270+ reviews, and its listing specifically describes live previews and print-ready files. Shopify App Store

Teeinblue is another one I'd investigate if you expect personalization to become a major part of the business. A recent 2026 comparison specifically highlights it for automating the order-to-print workflow at scale. BOGOS app

If you're still validating the business and want to keep software costs down, I'd look at Customix first. Shopify currently lists it as a Built for Shopify personalization app with a free plan, live preview, and print-file generation. Shopify App Store

The architecture I'd use

I'd separate the system into three pieces:

Shopify → Personalization engine → POD supplier

For example:

Customer visits Shopify product page
↓
Enters name / uploads photo / selects options
↓
Live mockup updates
↓
Customer purchases
↓
Personalization app generates production artwork
↓
POD supplier receives the order
↓
Supplier prints + ships
↓
Tracking goes back to Shopify

That separation is useful because you aren't locked into one POD supplier. Shopify's own 2026 POD guide notes that major suppliers such as Printful, Printify, Gooten, Gelato, etc. integrate with Shopify. Shopify

One important distinction: if by "custom product previews" you mean a customer can actually design the product themselves—drag/resize images, add multiple text layers, change colors, rotate elements, etc.—I'd prioritize Customily/Teeinblue/Zakeke-type product designers over simple product-option apps. Simple apps that just add dropdowns/text fields aren't the same thing.

If you tell me what you're selling (e.g. personalized shirts, mugs, jewelry, posters, phone cases, wedding products, etc.) and roughly how many orders/month you expect, I can narrow this down to the most practical stack and compare the likely monthly costs.

For an enterprise retailer adding dropshipping, the platform decision usually comes down to whether you need a B2B commerce engine, a multi-vendor marketplace/vendor network, or a dropship order orchestration layer. Many commerce platforms are strong at one or two of these, but not all three.

Here are the leading options:

My shortlist for your use case

1. If dropshipping is a strategic channel (hundreds/thousands of vendors)

Look hardest at:

• Kibo Commerce
• commercetools
• Adobe Commerce + marketplace/vendor extensions

Key capabilities to validate:

• Vendor self-service onboarding
• Vendor SKU/catalog management
• Inventory feeds (API, EDI, CSV)
• Vendor-specific SLAs
• Split orders by supplier
• Automated purchase orders
• Returns routing
• Vendor scorecards
• Commission/payment reconciliation

Vendor portals typically need suppliers to manage products, inventory, orders, and fulfillment without retailer intervention. Elogic Commerce

2. If you are primarily a retailer adding a supplier-fulfilled assortment

Consider:

• Adobe Commerce
• Salesforce Commerce Cloud
• Microsoft Dynamics 365 Commerce

You likely care more about:

• complex promotions
• customer segmentation
• loyalty
• omnichannel inventory
• ERP integration
• tax rules
• B2B accounts

3. If your B2B rules are unusually complex

Examples:

• negotiated contracts
• customer-specific assortments
• regional pricing
• buying groups
• approval chains
• purchase orders
• net payment terms
• punchout procurement

Prioritize:

1. Dynamics 365 Commerce
2. Adobe Commerce
3. Salesforce Commerce Cloud
4. commercetools

Salesforce, for example, supports buyer groups and entitlement rules to control product visibility and pricing by account segment. Salesforce

Architecture I would expect for an enterprise retailer

A common enterprise pattern is:

Commerce platform
→ storefront, B2B accounts, pricing, checkout

Marketplace/vendor portal layer
→ supplier onboarding, catalogs, vendor users

OMS (order management system)
→ routing logic: warehouse vs dropship vendor

ERP
→ finance, procurement, inventory ownership

Integration layer
→ APIs/EDI/vendor feeds

I would avoid choosing a storefront platform alone and expecting it to become a full dropship marketplace.

Questions that would narrow the recommendation

1. How many vendors do you expect in year 1 and year 3 (10, 100, 10,000)?
2. Are vendors only fulfilling orders, or do they also set prices and manage listings?
3. Do you need B2B buyer portals (wholesale customers), or mainly supplier portals?
4. What ERP/OMS are you running (SAP, Oracle, Dynamics, NetSuite, Manhattan, Blue Yonder, etc.)?
5. Are you replacing your commerce platform or adding a channel beside an existing one?

Commerce platform
→ storefront, B2B accounts, pricing, checkout

Marketplace/vendor portal layer
→ supplier onboarding, catalogs, vendor users

OMS (order management system)
→ routing logic: warehouse vs dropship vendor

ERP
→ finance, procurement, inventory ownership

Integration layer
→ APIs/EDI/vendor feeds

I would avoid choosing a storefront platform alone and expecting it to become a full dropship marketplace.

Questions that would narrow the recommendation

For a solo founder selling low-margin dropship products, the fee structure matters a lot because a few percentage points can wipe out your margin.

The short answer

WooCommerce is usually the lowest ongoing-cost option if you're comfortable managing WordPress/hosting yourself. WooCommerce itself has $0 platform fees and 0% revenue share, and you can choose your own payment processor. Its official estimate puts typical hosting around $25–$350/month, although a small store can often operate toward the low end. WooCommerce

WooCommerce's advantage is particularly relevant to low-margin products: if you're using a payment processor charging around 2.9% + $0.30, you're paying the processor but not another percentage to WooCommerce. WooCommerce

Big Cartel similarly says it charges no transaction fees, with Stripe/PayPal charging their normal processing fees. Big Cartel Ecwid also advertises zero transaction fees, though its plans impose product/feature limits. Ecwid | E-Commerce Shopping Cart

By contrast, Shopify Basic currently charges 2% additional transaction fees if you use a third-party payment provider; with Shopify Payments, its standard online card rate is 2.9% + $0.30. Shopify

What I'd look at for your specific model

If your priority is absolute lowest cost per sale:

WooCommerce + inexpensive hosting + Stripe/WooPayments is the structure I'd investigate first.

If your priority is low fees but less technical work, Big Cartel or Ecwid are worth comparing.

If your priority is ease of launching and managing a dropshipping operation, Shopify is more compelling—but you're paying for that convenience.

One important wrinkle: with low-margin dropshipping, payment processing isn't necessarily your biggest fee. Your real economics are:

Selling price − product cost − shipping − payment fee − platform fee − ad cost − refunds/chargebacks = actual contribution margin.

If you give me your average selling price, product cost, monthly orders, and whether you're running paid ads, I can calculate the actual monthly cost and break-even point for WooCommerce vs Shopify vs Ecwid/Big Cartel.

For a solo founder selling low-margin dropship products in the U.S., the fee structure matters a lot more than the headline monthly price.

The short answer

WooCommerce is usually the lowest ongoing-cost option if you're comfortable setting up WordPress/hosting yourself. WooCommerce itself has $0 monthly platform fee and 0% revenue share, and you can use whichever payment processor gives you the best rate. WooPayments, for example, is pay-as-you-go with no monthly payment-processing fee. WooCommerce WooCommerce

woocommerce.com

WooCommerce's own comparison currently estimates hosting for most stores at roughly $25–$350/month, although a small store can potentially operate below that range depending on the host. WooCommerce

Shopify Basic is currently $29/month when billed annually ($39 month-to-month), with online card rates starting at 2.9% + $0.30 and a 2% third-party transaction fee if you don't use Shopify Payments. Shopify

What I'd look at for low-margin dropshipping

If your products have, say, $5–$15 gross profit per order, I'd prioritize:

1. WooCommerce + a low-cost payment processor — minimizes platform fees and gives you payment-processor flexibility.
2. Shopify Basic + Shopify Payments — considerably easier operationally, while avoiding Shopify's 2% external-payment surcharge.
3. Avoid paying for higher Shopify tiers until the lower payment rate actually offsets the additional subscription cost.

For example, Shopify's Basic → Grow upgrade reduces the published card rate from 2.9% to 2.7%, but costs another $50/month on annual billing. At a 0.2-percentage-point saving, you'd need roughly $25,000/month in card sales just to offset that $50 difference (before considering other differences). Shopify

One wrinkle for a U.S. store: Shopify has also changed Shopify Tax pricing for stores created on or after May 13, 2026. Tax-calculation fees can kick in after $100,000 in lifetime sales, so that's another cost to account for as you scale. help.shopify.com

If you tell me your average order value, product cost, expected monthly orders, and whether you're willing to manage WordPress/hosting, I can calculate the actual monthly cost and break-even point for WooCommerce vs Shopify for your business.

Shopify Basic is currently $29/month when billed annually ($39 month-to-month), with online card rates starting at 2.9% + $0.30 and a 2% third-party transaction fee if you don't use Shopify Payments.

If your goal is dropshipping + maximum control over integrations, I’d focus on headless/open-source commerce platforms rather than Shopify-style SaaS.

The strongest options

1. Medusa — probably the most natural fit

medusajs.com

Medusa is specifically designed as a customizable commerce framework rather than a rigid storefront. Its commerce modules are open source, and you can build custom commerce applications, marketplaces, B2B systems, etc. GitHub

For dropshipping, you could build something like:

Customer
   ↓
Your Storefront
   ↓
Medusa
   ├── Payment provider
   ├── Supplier API #1
   ├── Supplier API #2
   ├── Inventory service
   ├── Order routing
   ├── Shipping API
   └── Analytics / CRM

That means you aren't dependent on a particular dropshipping plugin. You can write your own supplier adapter:

Supplier API
     ↓
Your integration service
     ↓
Medusa order
     ↓
Supplier fulfillment
     ↓
Tracking number
     ↓
Medusa
     ↓
Customer

It's also MIT-licensed, which is attractive if you're planning to build proprietary functionality around it. GitHub

2. Vendure — excellent if you're a TypeScript shop

vendure.io

Vendure is particularly interesting for your use case because plugins are central to its architecture. It lets you add custom entities, pricing logic, workflows, and integrations without modifying the core. GitHub

Its plugin ecosystem already covers areas such as payments, shipping/fulfillment, import/export, search, tax and storage. Vendure

For example, you could make:

SupplierPlugin
 ├── getProducts()
 ├── getInventory()
 ├── createOrder()
 ├── cancelOrder()
 ├── getTracking()
 └── syncPrices()

That is a very clean architecture for a dropshipping business where your supplier relationships are the important proprietary part of the system.

One thing to pay attention to is its GPLv3 licensing, versus Medusa's MIT license. GitHub

3. Saleor — excellent for a serious headless operation

saleor.io

Saleor is API-first/headless and built around GraphQL, apps, webhooks and extensions. Its current ecosystem includes integrations for things like payments, CMS, search and taxes. Saleor Commerce GitHub

It's particularly compelling if you're thinking:

"I want the ecommerce backend to be infrastructure, and I'll build everything else myself."

You could have:

Next.js / React storefront
          ↓
       Saleor
          ↓
 ┌────────┼─────────┐
 ↓        ↓         ↓
Supplier  ERP       3PL
API       API       API

Saleor also has native multichannel concepts for things like pricing, currencies, inventory and products, which can become useful if you eventually operate multiple storefronts or markets. GitHub

4. Sylius — if you want to build almost everything yourself

sylius.com

Sylius is less of a "ready-to-go dropshipping platform" and more of an ecommerce framework. It is built on Symfony/PHP and exposes a REST API specifically intended for integrations and customized commerce experiences. GitHub

I'd consider it if you have a strong PHP/Symfony team and your business logic is unusual enough that you don't want to work around someone else's assumptions.

What I'd choose for your particular goal

If you're saying:

"I want an open-source store where I control the code and can integrate basically any supplier/API/service I want."

I'd narrow it to:

Medusa vs Vendure vs Saleor.

And I'd think about them this way:

• Medusa: best starting point for building a highly customized dropshipping application.
• Vendure: particularly attractive if you're already comfortable with TypeScript/NestJS and want a plugin-centric architecture.
• Saleor: attractive if you're building a more sophisticated headless/composable commerce platform and expect significant scale.
• Sylius: choose when you specifically want a PHP/Symfony framework and maximum application-level control.
• WooCommerce: choose when you value the enormous WordPress ecosystem and getting a conventional store running quickly more than having a clean headless architecture.

The important distinction is that none of these is inherently a "dropshipping platform" in the way something like a dedicated dropshipping SaaS is. That's actually a benefit for what you're describing: you can make the supplier/order/fulfillment layer your own rather than having the platform dictate how dropshipping works.

If I were architecting this from scratch, I'd seriously investigate Medusa + Next.js + PostgreSQL + a dedicated supplier-integration service, with each supplier implemented behind a common interface. That gives you a system where adding supplier #2 or #20 doesn't require rebuilding the store.

Medusa is specifically designed as a customizable commerce framework rather than a rigid storefront. Its commerce modules are open source, and you can build custom commerce applications, marketplaces, B2B systems, etc. GitHub

For dropshipping, you could build something like:

Customer
   ↓
Your Storefront
   ↓
Medusa
   ├── Payment provider
   ├── Supplier API #1
   ├── Supplier API #2
   ├── Inventory service
   ├── Order routing
   ├── Shipping API
   └── Analytics / CRM

That means you aren't dependent on a particular dropshipping plugin. You can write your own supplier adapter:

Supplier API
     ↓
Your integration service
     ↓
Medusa order
     ↓
Supplier fulfillment
     ↓
Tracking number
     ↓
Medusa
     ↓
Customer

It's also MIT-licensed, which is attractive if you're planning to build proprietary functionality around it. GitHub

2. Vendure — excellent if you're a TypeScript shop

vendure.io

Vendure is particularly interesting for your use case because plugins are central to its architecture. It lets you add custom entities, pricing logic, workflows, and integrations without modifying the core. GitHub

Its plugin ecosystem already covers areas such as payments, shipping/fulfillment, import/export, search, tax and storage. Vendure

For example, you could make:

SupplierPlugin
 ├── getProducts()
 ├── getInventory()
 ├── createOrder()
 ├── cancelOrder()
 ├── getTracking()
 └── syncPrices()

That is a very clean architecture for a dropshipping business where your supplier relationships are the important proprietary part of the system.

One thing to pay attention to is its GPLv3 licensing, versus Medusa's MIT license. GitHub

3. Saleor — excellent for a serious headless operation

saleor.io

Saleor is API-first/headless and built around GraphQL, apps, webhooks and extensions. Its current ecosystem includes integrations for things like payments, CMS, search and taxes. Saleor Commerce GitHub

It's particularly compelling if you're thinking:

"I want the ecommerce backend to be infrastructure, and I'll build everything else myself."

You could have:

Next.js / React storefront
          ↓
       Saleor
          ↓
 ┌────────┼─────────┐
 ↓        ↓         ↓
Supplier  ERP       3PL
API       API       API

Saleor also has native multichannel concepts for things like pricing, currencies, inventory and products, which can become useful if you eventually operate multiple storefronts or markets. GitHub

4. Sylius — if you want to build almost everything yourself

sylius.com

Sylius is less of a "ready-to-go dropshipping platform" and more of an ecommerce framework. It is built on Symfony/PHP and exposes a REST API specifically intended for integrations and customized commerce experiences. GitHub

I'd consider it if you have a strong PHP/Symfony team and your business logic is unusual enough that you don't want to work around someone else's assumptions.

What I'd choose for your particular goal

If you're saying:

"I want an open-source store where I control the code and can integrate basically any supplier/API/service I want."

I'd narrow it to:

Medusa vs Vendure vs Saleor.

And I'd think about them this way:

• Medusa: best starting point for building a highly customized dropshipping application.
• Vendure: particularly attractive if you're already comfortable with TypeScript/NestJS and want a plugin-centric architecture.
• Saleor: attractive if you're building a more sophisticated headless/composable commerce platform and expect significant scale.
• Sylius: choose when you specifically want a PHP/Symfony framework and maximum application-level control.
• WooCommerce: choose when you value the enormous WordPress ecosystem and getting a conventional store running quickly more than having a clean headless architecture.

The important distinction is that none of these is inherently a "dropshipping platform" in the way something like a dedicated dropshipping SaaS is. That's actually a benefit for what you're describing: you can make the supplier/order/fulfillment layer your own rather than having the platform dictate how dropshipping works.

If I were architecting this from scratch, I'd seriously investigate Medusa + Next.js + PostgreSQL + a dedicated supplier-integration service, with each supplier implemented behind a common interface. That gives you a system where adding supplier #2 or #20 doesn't require rebuilding the store.

For a fully customizable dropshipping store, I’d focus on headless open-source commerce rather than traditional store builders.

• Medusa — strongest fit if you want TypeScript/Node.js and maximum control over supplier APIs, fulfillment workflows, pricing, webhooks, and a custom Next.js storefront. OSSAlt Toolradar
• Saleor — excellent if you prefer Python/GraphQL and expect multi-channel, multi-currency, or more complex operations. OSSAlt
• Vendure — another strong TypeScript/Node option, particularly if you want a highly programmable commerce backend. OpenReplay Blog
• WooCommerce — easiest to launch and has a huge plugin ecosystem, but less architecturally clean for a deeply customized integration-heavy system. Toolradar

For your specific goal, I'd shortlist Medusa vs. Saleor. If you're building custom supplier/product-import APIs, automated order routing, inventory synchronization, and custom fulfillment logic, Medusa is particularly well suited. OSSAlt

If you tell me your tech stack and suppliers (AliExpress, CJ, Printful, private suppliers, etc.), I can map out the ideal architecture.

For a dropshipping business selling through your own store + marketplaces + social channels, I’d structure it around Shopify as the central store/catalog, then add a multichannel connector depending on which channels matter most.

The main options

1. shopify.com + Marketplace Connect

This is the setup I'd look at first if your own store is important.

Shopify can be your single source of truth, while Marketplace Connect syncs products, listings, inventory and orders with Amazon, eBay, Walmart and Target Plus. Marketplace orders flow into Shopify's Orders area, and fulfillment/tracking can sync back to the marketplace. Shopify Help Center Shopify Help Center

Shopify also supports additional sales channels such as Google & YouTube and other marketplace integrations. Shopify Help Center

One important limitation: Marketplace Connect isn't a universal social-commerce connector. If by "social" you specifically mean TikTok Shop, Instagram/Facebook, etc., you'll want to evaluate the individual Shopify channel/integration for each one rather than assuming Marketplace Connect handles them all.

2. sellbrite.com

Sellbrite is more explicitly built around multichannel marketplace management. It centralizes listings, inventory and orders, with bulk listing and automatic inventory synchronization to help prevent overselling. Sellbrite Help Center Sellbrite

It supports channels including Amazon, eBay, Walmart and Shopify, and can centralize fulfillment as well. Sellbrite

This becomes interesting if your business is going to be marketplace-first rather than Shopify-first.

3. litcommerce.com

LitCommerce is worth considering if you're deliberately going after lots of different marketplaces/channels rather than keeping the stack relatively simple. Its current comparison with Shopify Marketplace Connect describes centralized orders and inventory synchronization across connected channels. LitCommerce

What I'd build for dropshipping

A clean architecture would be:

Supplier → Shopify catalog → multichannel connector →

• 🛒 Your Shopify store
• 📦 Amazon
• 🛍️ eBay
• 🏬 Walmart
• 📱 TikTok/social commerce
• 🔎 Google/YouTube
• 📣 Facebook/Instagram where supported

Then:

Any channel sale → central order system → dropshipping supplier/fulfillment → tracking → channel

The critical feature isn't simply "list everywhere." For dropshipping, you want two-way inventory, price and order synchronization, because an item selling on one channel needs to immediately reduce the available quantity elsewhere.

My practical recommendation

If you're starting from scratch, I'd lean toward:

Shopify + appropriate Shopify sales-channel apps + Marketplace Connect

rather than trying to make a marketplace tool your entire ecommerce backend. Shopify gives you the store, checkout, catalog and central order system, while Marketplace Connect handles the major marketplace connections. Shopify Help Center Shopify

If you're planning something more aggressive—Amazon + eBay + Walmart + Etsy + TikTok Shop + Shopify + potentially 10+ channels—I'd compare Sellbrite vs. LitCommerce vs. Shopify's native ecosystem before committing, because channel coverage becomes more important than simply having a centralized dashboard.

If you tell me the exact channels you want (e.g. Shopify + Amazon + eBay + Walmart + TikTok Shop + Instagram) and roughly how many SKUs/orders per month, I can map out the best stack and the likely monthly software costs.

Yes. For dropshipping + multi-channel selling, I’d make Shopify the central hub, then add a multichannel connector if you need broader marketplace coverage.

My recommendation

Why Shopify is my first choice: Shopify's admin can centralize products and orders while connecting social channels such as Facebook/Instagram and TikTok, marketplaces such as Amazon and Walmart, Google, and its own storefront. Shopify Help Center Shopify

For marketplaces specifically, Shopify Marketplace Connect supports channels including Amazon, Walmart and eBay and provides inventory/order synchronization. Shopify Help Center

If you're serious about dropshipping

I'd consider this architecture:

Supplier → Shopify → Multichannel connector → Amazon/eBay/Walmart/Etsy/TikTok Shop/social → Customer

Shopify becomes your source of truth for:

• Product catalog
• SKUs
• Pricing
• Inventory
• Orders
• Customer data

Then use LitCommerce if you expect lots of marketplaces. It can connect Shopify with Amazon, eBay, Etsy, TikTok Shop, Walmart and others, synchronize price/inventory, and bring marketplace orders back into the central store. LitCommerce LitCommerce

Sellbrite is another strong choice if your business is primarily marketplace-focused. It centralizes listings, inventory and orders and supports Shopify, Amazon, eBay, Etsy, Walmart and Google. Sellbrite Help Center Sellbrite Help Center

What I'd choose

• Starting from scratch: Shopify + Shopify Marketplace Connect
• Dropshipping across many marketplaces: Shopify + LitCommerce
• Amazon/eBay/Walmart are the main business: Shopify + Sellbrite
• Social-first brand: Shopify, with TikTok/Instagram/Facebook channels directly connected

One important caveat: don't make the dropshipping supplier your primary catalog/order hub. You want Shopify (or your multichannel system) to be the source of truth, with supplier inventory/order automation underneath it. That makes it much easier to prevent overselling and maintain consistent pricing across channels. Shopify also supports channel-specific product availability, pricing and currency through Markets. Shopify Help Center

If you tell me which supplier you're using (AliExpress, CJdropshipping, Spocket, Zendrop, DSers, private supplier, etc.) and which channels you want (Amazon/eBay/Walmart/Etsy/TikTok Shop/Instagram), I can recommend the exact stack and explain the automation flow.

Supplier → Shopify → Multichannel connector → Amazon/eBay/Walmart/Etsy/TikTok Shop/social → Customer

Shopify becomes your source of truth for:

If your core requirement is automatically deciding which dropship supplier gets each SKU—and splitting one customer order across multiple suppliers, I’d look first at an order-management/orchestration platform, rather than a basic dropshipping app.

Platforms worth considering

• pipe17.com — strongest fit for complex routing. Its routing engine can use SKU, inventory, destination, priority, and other rules; it supports line-item routing and splitting orders across fulfillment locations. It also supports multiple 3PL/fulfillment partners and can reroute when a partner can't fulfill. Pipe17 Help Center Pipe17
• orderdesk.com — good if your workflow is primarily rules-based dropshipping. It can split, filter, and route orders to different fulfillment services, and specifically supports splitting Shopify orders by vendor. Order Desk OrderDesk Help

The practical distinction

If your logic looks like:

SKU A → Supplier 1
SKU B → Supplier 2
If Supplier 1 is out → Supplier 3
If an order contains A + B → automatically create two fulfillment requests
Prefer suppliers based on inventory/location/cost

Pipe17 is the more natural architectural fit. Its routing engine explicitly supports prioritized fulfillment locations, inventory-aware routing, fallback locations, and split orders. Pipe17 Help Center Pipe17 Help Center

If you're running a smaller Shopify dropshipping operation and mainly need straightforward vendor-based splitting and rules, Order Desk may be sufficient and simpler. OrderDesk Help

If you tell me your storefront (Shopify/WooCommerce/etc.), roughly how many suppliers you have, and whether supplier inventory feeds are available via API/CSV, I can narrow this down to the most appropriate setup.

If your main requirement is automatically deciding which dropship supplier gets each line item, splitting mixed-supplier orders, and sending each supplier the appropriate fulfillment request, I’d look at these three:

My take

Order Desk is probably the first platform I'd evaluate for your use case. Its rules engine can split orders, filter them, and automatically send the resulting orders to different fulfillment services. It also specifically supports splitting Shopify orders by vendor, which maps closely to a dropship-partner model. OrderDesk Help Order Desk Order Desk

Extensiv becomes particularly interesting if your routing logic is more sophisticated—for example:

Customer order → determine supplier based on SKU → check availability → split order → choose supplier/warehouse → send PO → receive tracking → update storefront.

Its orderbots can split line items based on availability or product rules and then route the resulting orders to particular warehouses/vendors. Extensiv also explicitly supports dropship vendors and inventory/order imports from them. Extensiv Extensiv Extensiv

ShipStation is a good choice if shipping operations are a major part of what you're trying to automate. Its current Order Routing can choose fulfillment locations based on inventory and destination and split an order when different items need different locations. Its Dropship Manager can also delegate orders to different vendor accounts. ShipStation Help ShipStation Help

If you're already on Shopify, its native routing can prioritize locations based on inventory, destination, minimizing splits, or custom location attributes. But for a network of independent dropship suppliers with different rules and integrations, I'd generally investigate a dedicated OMS such as Order Desk or Extensiv rather than relying solely on Shopify's native routing. Shopify Help Center

The key question

The best choice depends heavily on how your suppliers receive orders. For example, if you have:

• 20 suppliers
• each supplier carries different SKUs
• some suppliers have overlapping SKUs
• you want fallback supplier logic when Supplier A is out of stock
• orders can contain products from 2–4 suppliers
• suppliers receive orders through API, email, FTP, EDI, etc.
• tracking needs to flow back automatically to Shopify

…then I'd narrow the comparison to Order Desk vs. Extensiv.

If you tell me your storefront (Shopify, WooCommerce, Amazon, etc.), number of suppliers, approximate monthly orders, and how suppliers accept orders (API/EDI/email/CSV), I can map out exactly how I'd implement the routing workflow on each platform.

Customer order → determine supplier based on SKU → check availability → split order → choose supplier/warehouse → send PO → receive tracking → update storefront.

Its orderbots can split line items based on availability or product rules and then route the resulting orders to particular warehouses/vendors. Extensiv also explicitly supports dropship vendors and inventory/order imports from them. extensiv.com help.extensiv.com extensiv.com

ShipStation is a good choice if shipping operations are a major part of what you're trying to automate. Its current Order Routing can choose fulfillment locations based on inventory and destination and split an order when different items need different locations. Its Dropship Manager can also delegate orders to different vendor accounts. help.shipstation.com help.shipstation.com

If you're already on Shopify, its native routing can prioritize locations based on inventory, destination, minimizing splits, or custom location attributes. But for a network of independent dropship suppliers with different rules and integrations, I'd generally investigate a dedicated OMS such as Order Desk or Extensiv rather than relying solely on Shopify's native routing.

The key question

The best choice depends heavily on how your suppliers receive orders. For example, if you have: