ChatGPT answers, unedited

For a dropshipping MVP where the goal is speed of prototyping + rapid iteration, I’d usually pick Shopify. It minimizes the amount of infrastructure you have to build and lets you spend your time on the things that actually validate the idea: product pages, offers, ads, checkout flow, and fulfillment. Shopify is widely used for dropshipping because of its app ecosystem and integrations. TechnologyAdvice PagePilot

My ranking for a freelancer building a client MVP:

1. Shopify — best default choice

Best for: getting a working store live in days.

Pros:

• Hosted (no servers, security, updates)
• Very fast theme customization
• Huge ecosystem of dropshipping/fulfillment apps
• Easy handoff to a non-technical client
• Easy A/B testing of products, landing pages, pricing, bundles

Cons:

• Monthly cost + app costs
• Some deeper customizations require working within Shopify’s ecosystem

Typical MVP stack:

• Shopify store
• Premium/free theme
• DSers / Zendrop / Spocket-style supplier integration
• Klaviyo for email
• Meta/TikTok pixels
• Replo/PageFly/GemPages if you need custom landing pages

2. WooCommerce — if the client needs ownership/custom code

Best for: clients who already live in WordPress or need unusual workflows.

Pros:

• Maximum control
• Easier to customize backend logic
• No platform lock-in

Cons:

• More maintenance
• Hosting, plugins, security, updates become your problem
• Iteration can slow down because every change touches more pieces

WooCommerce is powerful, but for an MVP it often turns you into the store's infrastructure engineer. NicheDropshipping

3. Wix — fastest for simple demos

Good if the goal is:

• "Show the client what the store could look like"
• Validate branding/layout
• Build a lightweight catalog

Less ideal if the MVP needs serious dropshipping automation.

4. Custom build (Next.js + headless commerce)

Only choose this if:

• The client is testing a genuinely differentiated product experience
• They need custom UX
• They already have engineering resources

For a dropshipping MVP, it is usually premature.

My freelancer recommendation

I’d structure the engagement like this:

Phase 1: 1–2 week MVP

• Shopify
• One theme
• 1–5 products
• Basic fulfillment integration
• Analytics installed
• Conversion-focused product pages

Phase 2: after validation

• Custom Shopify theme sections
• Better branding
• CRO experiments
• Subscription/bundling logic
• Custom apps only if needed

The biggest mistake I see freelancers make is building a "perfect" store before proving the product. Shopify lets you get to the learning loop fastest. ecommerce-platforms.com

If you tell me the client's MVP type (single-product store, AliExpress-style catalog, private supplier, POD, subscription, etc.), I can suggest a more specific stack.

For a freelancer building a dropshipping MVP, I’d pick Shopify in most cases—especially if the goal is prototype → get client feedback → iterate → launch quickly.

My ranking

Why Shopify wins

Shopify's developer workflow is unusually good for this exact scenario. You can create free development stores, generate test data, create unlimited test products/orders, and use Shopify CLI to preview theme changes without deploying every iteration. shopify.dev

For a freelancer, that means you can do something like:

Day 1:
Store skeleton → products → collections → cart → checkout

Day 2:
Client says "make the product page look more premium" → modify theme → instant preview

Day 3:
Client wants a custom bundle/upsell → add an app or small custom extension

Day 4:
Client changes the niche/branding → swap catalog, imagery, colors, copy

You aren't spending your MVP budget maintaining WordPress, PHP, hosting, plugin compatibility, etc.

Shopify also has theme app extensions, which are useful when the MVP needs custom functionality without turning the whole project into a custom storefront. shopify.dev

When I'd choose WooCommerce instead

I'd choose WooCommerce if the client specifically needs unusual business logic or wants you to own/control essentially everything.

It's extremely flexible and has excellent developer tooling—WP-CLI, local environments, Store API, REST API, custom themes/plugins, etc. developer.woocommerce.com

But that flexibility comes with more moving parts. For an MVP where speed and iteration are the product, I'd generally avoid introducing that complexity unless there's a reason.

One important Shopify distinction

If you're building for a client, use a Shopify Partner client-transfer store, rather than accidentally building on a development store with configurations that can't be transferred. Shopify explicitly distinguishes client-transfer stores for merchant builds from dev stores intended for testing. shopify.dev

My default stack would be:

Shopify + native theme/sections + Shopify CLI + a small number of proven apps + custom app/extension only where necessary.

For a dropshipping MVP, I'd resist building a headless Next.js storefront initially. You can always go headless once you've validated that the store actually needs it.

For a dropshipping MVP where your priority is “build → show client → change → repeat,” I’d pick Shopify.

My ranking

Why Shopify wins: as a Shopify Partner, you can create development/client-transfer stores specifically for client projects, and Shopify provides test orders, products, themes, apps, and development tooling. help.shopify.com

For an MVP, I'd avoid building the fulfillment/supplier infrastructure yourself. Shopify already supports the basic dropshipping model and has an ecosystem for sourcing/fulfillment integrations. help.shopify.com

How I'd structure the MVP

Phase 1 — fake the complexity

• Shopify dev/client-transfer store
• Dawn or another lightweight theme
• 5–20 products
• Shopify's native product/cart/checkout
• Mock or test fulfillment
• Basic analytics
• No custom app unless absolutely necessary

Phase 2 — validate

• Get the client reviewing the actual storefront
• Iterate on product pages, pricing, navigation, bundles, etc.
• Run test orders
• Validate the customer journey before spending time on backend automation

Phase 3 — automate only what proves necessary

• Supplier integration
• Inventory syncing
• Automated fulfillment
• Custom pricing rules
• Custom app/API work

The important freelancer trick is not to confuse “MVP” with “minimum technically impressive product.” For a dropshipping client, you want the smallest amount of custom code that lets them validate whether customers will actually buy.

When I'd choose WooCommerce instead

I'd use WooCommerce if the client specifically wants WordPress, maximum ownership/control, or substantial custom backend behavior. It's very flexible and has an official dropshipping extension with supplier management, automated supplier notifications, packing slips, and AliExpress-related functionality. woocommerce.com

But for a freelancer trying to iterate rapidly, that flexibility generally means more things for you to configure, maintain, and debug.

Bottom line: Shopify + a development/client-transfer store is probably the lowest-friction choice. help.shopify.com

Shopify developer documentation

If the goal is “get a believable dropshipping MVP in front of the client/users ASAP, then iterate”, I’d pick Shopify.

My ranking for an MVP

Shopify is particularly attractive because it's managed—you don't have to spend MVP time on hosting, WordPress/plugin compatibility, security, checkout infrastructure, etc. Shopify itself emphasizes quick store setup and experimentation with products, suppliers, and sales channels. www.shopify.com

Shopify

How I'd build it as a freelancer

I'd deliberately avoid building the “real” system first:

Shopify
→ lightweight theme/custom sections
→ 5–20 products
→ supplier integration/app
→ Shopify checkout
→ basic analytics
→ email/order notifications
→ client validates demand

Then iterate based on actual behavior.

For example, if the client wants a custom product-selection flow, I'd initially implement it as a Shopify theme/app layer rather than replacing the entire commerce backend. That lets you validate the UX without spending weeks rebuilding carts, checkout, orders, payments, inventory, etc.

When I'd choose WooCommerce instead

I'd go WooCommerce if the MVP is really a custom application disguised as a store—e.g. unusual product configuration, complex supplier logic, custom pricing rules, or the client already has a WordPress stack.

WooCommerce is open-source and extremely extensible; its official developer tooling supports custom extensions and local development environments. developer.woocommerce.com It also has dedicated dropshipping extensions capable of supplier assignment, inventory importing, supplier notifications, packing slips, and fulfillment workflows. woocommerce.com

But that flexibility comes with more things for you to maintain.

My freelancer rule of thumb

Client says: “We need to test whether people will buy this.”
→ Shopify

Client says: “We need to test this unusual ecommerce workflow.”
→ Shopify + custom app/theme first, unless Shopify's model genuinely gets in the way.

Client says: “The entire business logic is custom.”
→ WooCommerce or a custom stack, depending on complexity.

For a normal dropshipping MVP, I'd strongly favor Shopify and keep the first version intentionally disposable. The platform should disappear into the background while you spend your time testing the actual business hypothesis.

For a dropshipping MVP where you’re optimizing for speed of prototyping + iteration, I’d pick Shopify.

My ranking

Shopify is particularly good because you're getting a managed commerce backend, checkout, products, orders, payments, etc., without spending your MVP budget on infrastructure. Shopify's current ecosystem also has hundreds of sourcing/dropshipping apps, including options for AliExpress, US/EU suppliers, POD, and automated fulfillment. apps.shopify.com

Shopify

How I'd build the MVP

Shopify + lightweight custom theme + 1–2 apps

I'd avoid building a custom ecommerce frontend initially. Instead:

1. Shopify → products, cart, checkout, orders
2. Custom Liquid/theme work → make the storefront match the client's brand
3. Dropshipping app → sourcing/import/fulfillment
4. Shopify webhooks/API → only for genuinely custom functionality
5. Analytics → track product views → add-to-cart → checkout → purchase

That gives you a very fast feedback loop: client says "change this product page" or "let's test a bundle" and you're iterating in hours rather than modifying a custom commerce stack.

Shopify also currently offers first-party sourcing through Shopify Collective, where products can be imported and suppliers fulfill orders. www.shopify.com

When I'd choose WooCommerce instead

Use WooCommerce if the client specifically needs deep WordPress integration or unusually extensive backend customization. Its dropshipping tooling can handle supplier assignment, automated supplier notifications, packing slips, AliExpress integration, etc. woocommerce.com

But for a freelancer trying to validate a business idea quickly, WooCommerce generally gives you more infrastructure/plugin decisions than you actually want. Shopify's managed SaaS model is much better suited to an MVP. www.shopify.com

My practical recommendation: start with Shopify, keep custom code to the storefront and a small integration layer, and don't build anything that Shopify already does well.

If you tell me what the MVP actually needs (e.g. AliExpress/Spocket supplier, subscriptions, custom product configurator, marketplace, AI recommendations, etc.), I can suggest the exact stack I'd use and where I'd not spend development time.

For a dropshipping MVP where the priority is “get something working, learn, iterate, repeat,” I’d pick Shopify.

My ranking

Why Shopify for this project

1. You don't need to build commerce infrastructure.
Products, variants, carts, checkout, orders, customer accounts, payments, taxes, etc. are already there. You can concentrate on the client's actual differentiator.

2. Iteration is unusually fast.
Shopify's current tooling gives you CLI scaffolding, dev stores, app extensions, custom admin functionality, checkout extensions, and APIs. Shopify explicitly recommends its CLI for scaffolding apps and provides dev stores for testing without touching the client's live store. help.shopify.com

3. You can start “low-code” and progressively customize.

I'd structure the MVP roughly:

Shopify
├── Theme / storefront
├── Products + collections
├── Shopify Checkout
├── Dropshipping supplier/app
│
└── Custom Shopify App
    ├── supplier/product sync
    ├── custom business logic
    ├── order automation
    └── client-specific dashboard

That lets you validate the business before spending weeks building infrastructure.

4. You can go deeper when the MVP proves itself.
Shopify Functions let you inject custom backend logic into things like discounts, delivery options, payments, and checkout. shopify.dev

When I'd choose WooCommerce instead

I'd go WooCommerce if the client specifically wants:

• maximum control over the backend/database
• lots of custom WordPress functionality
• unusual content/SEO requirements
• self-hosting
• avoiding Shopify's platform constraints/fees
• a supplier workflow that doesn't fit Shopify well

WooCommerce is genuinely flexible because it's open-source, and its dropshipping extension already handles supplier assignment, inventory, supplier notifications, packing slips, and AliExpress importing. woocommerce.com

But for a freelancer being paid to prototype quickly, I'd generally rather not inherit the WordPress/plugin/theme/hosting maintenance surface area unless there's a reason.

What I'd actually do

For a client MVP, I'd use:

Shopify + a dropshipping integration + a small custom Shopify app only where necessary.

Don't build a custom ecommerce backend yet.

The key architectural principle I'd pitch to the client is:

Validate the storefront, product economics, fulfillment workflow, and customer demand first. Custom-build only the pieces that are demonstrably preventing the business from working.

If you tell me what kind of dropshipping MVP they're building (e.g. AliExpress-style catalog, curated single-product store, multiple suppliers, marketplace-like, AI product discovery, etc.), I can recommend the specific stack and architecture I'd use as a freelancer.

For a dropshipping MVP where your priority is prototype → test → iterate quickly, I’d default to Shopify.

My ranking for a freelancer

Why Shopify wins: it's managed SaaS, so you're not spending MVP time on hosting, WordPress updates, plugin conflicts, security, checkout infrastructure, etc. Current comparisons also put Shopify ahead on implementation speed and overall implementation burden. www.shopify.com

For dropshipping specifically, Shopify has a mature app ecosystem. For example, DSers supports product importing, supplier connections, order syncing, and fulfillment automation, with a free plan available. apps.shopify.com

How I'd build the MVP

I'd keep the architecture deliberately boring:

Shopify
→ lightweight/custom theme
→ 5–20 test products
→ dropshipping app/supplier integration
→ Shopify checkout
→ analytics + pixels
→ only custom-code the pieces that differentiate the client's concept

Then iterate on product selection, landing pages, pricing, bundles, offers, and conversion, rather than building commerce infrastructure.

If the client later needs a genuinely custom experience, you can move toward a headless Shopify setup rather than having built the whole commerce backend yourself.

When I'd choose WooCommerce instead

I'd pick WooCommerce if the client already has WordPress, needs unusually deep backend customization, or wants you to own essentially every layer. Its REST API gives you programmatic access to products, orders, customers, coupons, etc., and its Store API supports customer-facing cart/checkout functionality. developer.woocommerce.com

But for a freelancer trying to validate a dropshipping idea quickly, WooCommerce tends to give you more knobs than you actually want during an MVP.

Bottom line:

Shopify for the MVP. Custom code only around the edges.
Optimize for getting something testable in front of users in days, not building the perfect ecommerce stack.

If you tell me what the client is selling + how custom the storefront needs to be, I can recommend a specific stack (Shopify theme vs Hydrogen/headless vs WooCommerce vs custom) and a sensible MVP architecture.

For a freelancer building a dropshipping MVP, I’d default to Shopify.

Shopify is hard to beat for rapid prototyping because you get hosted infrastructure, checkout, payments, product/catalog management, and a huge app ecosystem without having to build the commerce plumbing yourself. Its App Store specifically has categories for dropshipping/supplier sourcing, fulfillment, storefronts, checkout, marketing, etc. apps.shopify.com

My ranking for an MVP

1. Shopify — best default

• Fastest path from idea → functioning store
• Easy to swap themes/apps as requirements change
• Excellent checkout out of the box
• Lots of dropshipping/supplier integrations
• Easy for your client to take over later
• You can still inject custom Liquid/JS or build against its APIs when the MVP needs something unusual

2. WooCommerce — if the client already lives in WordPress

• Much more control over the stack
• Great for highly customized workflows
• But you're taking on hosting, plugin compatibility, updates, security, etc.
• That extra flexibility generally works against rapid iteration. www.shopify.com

3. BigCommerce — if the MVP already has complex commerce requirements

• Stronger built-in functionality for complicated catalogs/B2B
• Less dependence on apps for some features
• But I'd consider it overkill for a typical dropshipping MVP. www.shopify.com

What I'd actually build

For a freelancer, I'd keep the first version deliberately boring:

Shopify + lightweight custom theme + supplier/dropshipping app + analytics + a few carefully chosen apps.

Don't build a custom storefront/backend unless the hypothesis you're testing actually requires it. Shopify's ecosystem lets you test product sourcing, pricing, landing pages, upsells, checkout, fulfillment, etc. without spending your MVP budget rebuilding ecommerce infrastructure. apps.shopify.comwww.shopify.com

The key freelancer consideration is iteration speed vs. client lock-in. Shopify wins that tradeoff for most MVPs: you can get something live quickly while leaving room for custom development later. Current 2026 comparisons similarly put Shopify ahead on implementation speed and ease of use, while WooCommerce trades that simplicity for greater control. www.shopify.com

If you tell me what the MVP actually needs (supplier source, number of products, custom UX, subscriptions, AI/product recommendations, custom pricing, etc.), I can tell you whether I'd use Shopify, Shopify + custom app, WooCommerce, or a totally custom stack.

For a dropshipping MVP where the priority is prototype → test → iterate quickly, I’d pick Shopify.

My ranking

Shopify is particularly strong here because you can avoid building the boring commerce infrastructure—products, cart, checkout, orders, payments, admin—and iterate on the actual hypothesis you're trying to validate. Its App Store currently has a substantial dropshipping ecosystem, including DSers, HyperSKU, Printify, Zendrop, etc. apps.shopify.com

What I'd actually build as the freelancer

Shopify + lightweight custom theme/app

• Shopify for catalog, checkout, orders, payments
• A dropshipping app for supplier/product fulfillment
• Custom Liquid/theme components for the storefront
• Shopify metafields for anything unusual about the products
• Small custom Shopify app only where the client's idea genuinely needs custom logic
• Analytics + pixels from day one
• Don't build a custom backend unless the MVP proves you need one

That gives you a nice separation:

Shopify handles:
products → cart → checkout → payment → order → fulfillment

You build:
the differentiated customer experience

This is especially useful when the client is likely to say "Can we try this instead?" every few days.

When I'd choose something else

WooCommerce if the client already has WordPress infrastructure or wants maximum control at low platform cost.

Medusa if the MVP itself is testing a non-standard commerce model—for example, a marketplace, unusual pricing engine, complex supplier routing, or a highly custom checkout. Medusa is open-source and designed specifically as customizable commerce building blocks, so it's much more developer-friendly than Shopify for that scenario. github.com

Custom Next.js + backend only if the "store" isn't really a conventional store and you're effectively building a software product around commerce.

Freelancer perspective

I'd optimize for time-to-client-demo, not technical elegance.

If you can get:

idea → functioning storefront → test order → client feedback

in 1–3 days with Shopify, that's generally more valuable for an MVP than spending two weeks building a beautifully architected commerce stack.

If you tell me what the client's dropshipping concept is (normal single-product store vs marketplace vs subscription vs custom product configurator, etc.), I can tell you whether I'd use Shopify, WooCommerce, Medusa, or a custom stack and what I'd build in the first sprint.

For a freelancer building a dropshipping MVP where speed of prototyping + iteration matters most, I’d pick Shopify.

Shopify is usually the lowest-friction option because you get hosting, checkout, payments, product/catalog management, themes, and a huge app ecosystem without having to build the underlying commerce infrastructure. Shopify is still being recommended as a top ecommerce platform in 2026, particularly for its app ecosystem. www.techradar.com

My ranking for an MVP

Why I'd use Shopify

For the MVP, I'd deliberately avoid building the dropshipping machinery yourself.

Use Shopify for:

• Storefront
• Products/variants
• Cart + checkout
• Customer accounts
• Orders
• Payments
• Basic analytics

Then bolt on a supplier app. For example, DSers has a free tier and handles product importing, pricing, bulk ordering, inventory/order synchronization and tracking. apps.shopify.com Shopify itself maintains a current list of recommended dropshipping/POD apps. help.shopify.com

That lets you spend your client's budget on validating the business, rather than recreating ecommerce infrastructure.

The freelancer-friendly architecture I'd choose

Shopify + custom theme/app + supplier integration

I'd keep the first version roughly:

Shopify storefront → Shopify checkout → Shopify orders → DSers/supplier → fulfillment

Then build custom functionality only where the client's concept actually differentiates itself.

If they need a heavily customized UX, you can still use Shopify as the commerce backend and build a custom frontend later. That gives you an escape hatch without prematurely committing to a custom commerce stack.

When I'd choose WooCommerce instead

I'd choose WooCommerce if the client already has WordPress, specifically needs deep WordPress customization, or wants maximum control over the underlying stack.

WooCommerce does support automated dropshipping workflows, including supplier notifications, packing slips, and AliExpress integration, but there is more infrastructure/plugin management involved. woocommerce.com

Bottom line: for a freelancer trying to get a dropshipping concept from idea → working store → client feedback → iteration as quickly as possible, I'd start with Shopify and keep the custom code thin.

For a freelancer building a dropshipping MVP where speed of prototyping + iteration matters most, I’d pick Shopify.

My ranking

Why Shopify: you can get a functional store up extremely quickly without building the underlying commerce infrastructure. Its app ecosystem covers sourcing, fulfillment, inventory, checkout, reviews, upsells, analytics, etc.; Shopify currently lists 16,000+ apps, including dedicated dropshipping integrations. apps.shopify.comapps.shopify.com

For an MVP, that's particularly valuable because you can change the product/catalog, theme, pricing, fulfillment workflow, and marketing stack without rebuilding your backend. Shopify itself specifically highlights that dropshipping makes it easy to change the products you offer. help.shopify.com

The stack I'd use

Shopify + lightweight theme + dropshipping app + minimal custom code.

For example:

• Store: Shopify
• Theme: Dawn or a lightweight premium theme
• Supplier: client's preferred supplier
• AliExpress/Alibaba: DSers or another appropriate sourcing app
• POD: Printify/Printful if applicable
• Custom functionality: Shopify app/extensions or small JS/Liquid additions
• Analytics: Shopify + GA4/Meta Pixel
• Payments: Shopify Payments

The Shopify App Store currently has dedicated sourcing/fulfillment options such as DSers, EPROLO, Printify, etc., so you can swap suppliers without redesigning the whole MVP. apps.shopify.comapps.shopify.com

When I'd choose WooCommerce instead

I'd go WooCommerce if the client specifically wants:

• full ownership/control of the stack
• unusual business logic
• extensive WordPress integration
• custom supplier/fulfillment workflows
• freedom to modify essentially everything at the code level

WooCommerce is open-source and extremely extensible, and its official dropshipping extension supports supplier assignment, automated supplier notifications, and packing slips. woocommerce.com

But that flexibility comes with more infrastructure and plugin decisions—which is exactly what I'd avoid when the goal is "get something in front of users this week and iterate."

Bottom line: for a freelancer MVP, I'd optimize for time-to-learning rather than technical ownership. Shopify wins that tradeoff pretty decisively.

Shopify · Shopify App Store

For a dropshipping MVP where the priority is “build → test → change → repeat,” I’d pick Shopify.

My ranking

Why Shopify: you can get the store, products, cart, checkout, payments, orders, themes, and basic integrations working without building those systems yourself. Shopify's current developer tooling also makes iteration pretty painless: Shopify CLI scaffolds apps/extensions, and its dev server gives you live previews while developing. shopify.dev

For storefront experimentation specifically, Shopify's theme app extensions let you add functionality without modifying the underlying theme code, and merchants can position/configure app blocks through the visual theme editor. That's a very good fit for an MVP where you're going to be changing UI frequently. shopify.dev

How I'd build the MVP

I'd avoid going headless initially.

Shopify + Dawn/theme + small custom app + external backend only where necessary.

For example:

• Shopify → products, variants, inventory, cart, checkout, orders
• Theme → storefront UI
• Custom app → your client's differentiating functionality
• Supabase/Postgres → only data Shopify shouldn't own
• Serverless functions → supplier/API automation
• Stripe/payment integrations → only if Shopify's native payment setup doesn't cover the requirement

That lets you spend your time validating the business workflow, rather than recreating ecommerce infrastructure.

One important caveat: don't design the MVP around heavily customizing Shopify checkout unless the client is willing to use the appropriate Shopify plan. Several checkout UI extension capabilities are restricted to Shopify Plus. shopify.dev

When I'd choose WooCommerce instead

I'd go WooCommerce if the client's MVP needs unusual backend behavior, deep WordPress integration, or you're expecting to hack/customize virtually everything.

Its APIs are quite flexible: the REST API can manage products, orders, customers, coupons, shipping zones, etc., while the Store API provides customer-facing product/cart/checkout functionality. developer.woocommerce.com

But that flexibility comes with more infrastructure and maintenance. For a freelancer trying to prove a dropshipping concept quickly, Shopify generally gives you a much better “boring infrastructure, interesting product” ratio.

My default stack: Shopify + Liquid/theme extensions + lightweight Node/TypeScript backend + Supabase. I'd only go headless once the MVP proves that the standard Shopify storefront is actually constraining the product.

For a freelancer building a dropshipping MVP, I’d default to Shopify unless the client has unusually custom requirements.

My ranking for fast MVP iteration

Why Shopify wins: you get a functioning commerce engine immediately—products, variants, cart, checkout, orders, payments, customer accounts, etc.—so you're mostly prototyping the business logic and UX, rather than rebuilding ecommerce infrastructure.

For client work specifically, Shopify's development/client-transfer store workflow is very convenient. Shopify lets Partners create development stores, test apps/themes, and then hand a client-transfer store over to the merchant. shopify.dev

The developer tooling is also geared toward rapid iteration: Shopify CLI can run your app locally against a development store and preview changes without deploying a new production version. shopify.dev

When I'd choose WooCommerce instead

Pick WooCommerce if the client specifically wants WordPress, wants maximum control over the backend, or needs unusual functionality that is easier to implement as PHP/WordPress extensions.

Its REST API gives you programmatic access to products, orders, customers, coupons, shipping, etc., and its Store API supports customer-facing product/cart/checkout functionality. developer.woocommerce.com

WooCommerce also has an official dropshipping extension that can automate supplier order notifications. woocommerce.com

For your particular MVP

I'd probably structure it:

Shopify
→ Shopify theme / lightweight custom frontend
→ dropshipping supplier integration
→ small custom Shopify app for anything proprietary
→ Shopify handles checkout/orders/payments
→ external DB only for your unique business logic

That lets you iterate on things like supplier selection, product sourcing, pricing/margins, automated fulfillment, customer UX, and order routing without committing the client to a giant custom ecommerce codebase.

One important caveat: if the "MVP" is actually intended to become a multi-vendor marketplace / dropshipping SaaS, rather than a single dropshipping store, I'd reconsider Shopify and look at Medusa or a custom commerce backend. Medusa is specifically designed as a framework for custom commerce features and business logic. docs.medusajs.com

Rule of thumb:

• Single dropshipping store → Shopify
• WordPress/client wants control → WooCommerce
• Marketplace / complex custom fulfillment logic → Medusa/custom
• Don't build the commerce engine yourself for an MVP.

If you tell me what the MVP actually does (e.g. AliExpress-style product import, supplier matching, automated fulfillment, AI product selection, multi-vendor marketplace), I can recommend a specific stack and architecture.

For a dropshipping MVP where the priority is speed of prototyping and iteration, I’d pick Shopify.

Why:

• Fastest path to a working store: products, checkout, orders, payments, shipping, themes, and admin are already there.
• Huge app ecosystem: Shopify currently has a dedicated dropshipping ecosystem with sourcing/fulfillment apps, including DSers, Zendrop, Printify, etc. apps.shopify.com
• Easy to change direction: you can swap themes, products, suppliers, pricing, and apps without rebuilding the underlying commerce system.
• Good client handoff: once the MVP works, the client can operate it without needing you to maintain a custom backend.
• Easy to fake/mock parts of the MVP: you can start with manually fulfilled orders or a lightweight supplier integration and automate only after validating demand.

What I'd use for the MVP

Shopify + custom theme/components + one dropshipping app

I'd keep your architecture deliberately thin:

Shopify
├── Storefront/theme
├── Products
├── Cart + checkout
├── Orders
├── Customer accounts
└── Dropshipping app
      └── Supplier / fulfillment

Then only build custom code for the actual differentiator—e.g. product discovery, personalization, a special bundle builder, recommendation logic, custom landing experience, etc.

I would not start with WooCommerce unless the client specifically wants WordPress. WooCommerce can absolutely handle dropshipping, but you're taking on WordPress hosting/plugins/configuration and more integration surface area; its official dropshipping extension, for example, handles supplier notifications, product/supplier assignment, packing slips, and fulfillment workflows. woocommerce.com

My rule of thumb:

If the MVP is primarily “Can people discover products → add to cart → pay → receive the product?”, use Shopify.
If the MVP's core innovation is outside standard ecommerce, still use Shopify for commerce and build the innovation around it.

If you tell me what the client’s MVP actually does (supplier source + what makes the store different), I can suggest the leanest stack and where I'd use custom code vs Shopify apps.