ChatGPT answers, unedited

For an enterprise retailer adding dropshipping while retaining sophisticated B2B commerce, I’d shortlist Adobe Commerce + Mirakl, Salesforce Commerce + Mirakl, and VTEX. The key distinction is that the best B2B commerce engine and the best vendor/dropship platform are not necessarily the same product.

My ranking

1. Adobe Commerce + Mirakl — my default recommendation

Adobe Commerce is particularly strong when your B2B requirements include company hierarchies, customer-specific catalogs/pricing, purchasing permissions, quotes, credit limits, PO approval rules, and differentiated shipping/payment rules. Adobe's current B2B functionality explicitly supports company hierarchies, shared catalogs, custom pricing, purchase orders and approval rules. experienceleague.adobe.com

Pair it with Mirakl for the supplier side. Mirakl specifically offers marketplace and dropship capabilities, vendor onboarding, catalog management and seller connectivity, and provides an Adobe Commerce connector. developer.mirakl.com

That gives you a clean division:

Adobe = customer/B2B commerce rules
Mirakl = vendors, offers, dropship, seller operations

That's attractive for a retailer because you don't have to distort your B2B commerce model around marketplace mechanics.

2. Salesforce Commerce + Mirakl — strongest if Salesforce is already strategic

Salesforce Commerce has a strong B2B data model around buyer groups, entitlements, price books, buyer accounts and customizable business objects. developer.salesforce.com

Salesforce also has its own Commerce Marketplace capability for third-party sellers, including seller APIs and seller-specific tooling. developer.salesforce.com

I'd favor this if your organization already runs heavily on Salesforce CRM, Service, OMS, and customer data. Otherwise, I'd be inclined toward Adobe + Mirakl for a retailer whose primary challenge is commerce architecture rather than CRM integration.

3. VTEX — worth serious consideration if you want fewer moving parts

VTEX is compelling because marketplace and seller functionality are much closer to the core commerce proposition. The trade-off is that I'd evaluate its B2B rule depth against your actual requirements rather than assuming marketplace strength automatically means it matches Adobe/Salesforce for every complicated B2B scenario.

The architecture I'd favor

For your particular use case, I'd model it as:

B2B customer → Commerce platform → Marketplace/dropship layer → Vendor → Vendor fulfillment

with the commerce platform owning:

• account/company hierarchy
• buyer permissions
• customer-specific assortment
• contract pricing
• quantity/MOQ rules
• credit/payment terms
• approval workflows
• promotions
• tax/customer context

and the marketplace layer owning:

• vendor onboarding/KYC
• vendor portal
• seller catalog ingestion
• product/content approval
• seller-specific pricing
• inventory feeds
• dropship routing
• PO transmission
• shipment/tracking feeds
• seller SLAs
• commissions/settlements

That separation becomes particularly valuable when you have hundreds or thousands of vendors. Mirakl's own platform is explicitly positioned around enterprise marketplace and dropship operations and has connectors for both Adobe Commerce and Salesforce Commerce. developer.mirakl.com

Bottom line

If I were running the RFP, my first two proofs-of-concept would be:

1. Adobe Commerce + Mirakl — strongest combination for deep B2B customization + serious vendor/dropship operations.
2. Salesforce Commerce + Mirakl — strongest alternative if your enterprise is already deeply invested in Salesforce.

I'd put VTEX in the POC as the "can we simplify this by buying more of the stack from one vendor?" candidate.

The most important thing I'd test isn't the storefront. It's a nasty end-to-end scenario: customer-specific contract price + buyer approval hierarchy + vendor-specific assortment + dropship inventory + split shipment + vendor SLA + return/refund + tax + OMS reconciliation. That will expose architectural weaknesses very quickly.

For an enterprise retailer adding a dropshipping channel, I would evaluate platforms less like a normal ecommerce replatform and more like a multi-party commerce operating system. You need three capabilities working together:

1. Complex B2B commerce rules

• Account hierarchies (parent/child buyers, locations)
• Customer-specific catalogs and price lists
• Contract pricing, rebates, volume tiers
• Purchase orders, net terms, credit limits
• Approval workflows
• Regional/tax/shipping rules
• Vendor/supplier portal capabilities

• Vendor onboarding
• Supplier self-service catalog management
• Inventory feeds
• Order acceptance and status updates
• SLA tracking
• Returns/disputes
• Commissions or settlement logic
• Dropship orchestration

• Routing orders to the right supplier
• Split shipments
• Supplier inventory synchronization
• PO generation
• Shipment tracking back to customers
• ERP/OMS integration

Shortlist:

Elogic Commerce BigCommerce ORO INC.## My likely shortlist for your use case

1. SAP Commerce Cloud + marketplace/dropship layer

Best if you are a large retailer with:

• SAP ERP
• thousands/millions of SKUs
• global operations
• complex fulfillment rules

Typical architecture:

• SAP Commerce Cloud → storefront + B2B logic
• SAP ERP/S4 → inventory, finance
• Marketplace/dropship platform → vendor onboarding and supplier operations

2. Adobe Commerce + marketplace extensions

A strong choice if you need:

• highly customized business rules
• multiple selling models
• control over vendor workflows

Adobe Commerce is often selected when the retailer wants to own the customer experience but customize heavily behind the scenes. Elogic Commerce

3. VTEX

Worth serious consideration if dropshipping is becoming a true marketplace channel, where suppliers act almost like sellers. VTEX positions its B2B platform around self-service buying, custom pricing, procurement workflows, and multi-party commerce scenarios. VTEX

4. Composable stack (commercetools + marketplace services)

Best if your enterprise already has:

• strong engineering teams
• an API-first architecture
• existing OMS/PIM/ERP investments

You get maximum flexibility but must assemble more pieces yourself.

Don’t overlook the dropship layer

Most commerce platforms are not full supplier-network systems. Many retailers pair commerce with a dropship/vendor management platform such as Flxpoint, which focuses on supplier connections, catalog syncing, inventory, and fulfillment workflows. Flxpoint

A common enterprise architecture looks like:

Customer storefront
        |
Commerce platform
        |
OMS / Order orchestration
        |
Dropship marketplace layer
        |
Supplier portals + vendor APIs
        |
ERP / Finance / Inventory systems

Questions that would change the recommendation

• Are you primarily B2C retail adding third-party sellers, or a B2B distributor adding dropship suppliers?
• How many vendors do you expect (50, 500, 10,000+)?
• Do suppliers need a true portal, or will they integrate via API/EDI?
• What ERP/OMS do you run today (SAP, Oracle, Manhattan, NetSuite, custom)?
• Do you need marketplace settlement (commissions/payouts), or just supplier fulfillment?

For a large retailer with thousands of suppliers and complex rules, I would usually start the evaluation with SAP Commerce Cloud, Adobe Commerce, VTEX, and a composable stack rather than a pure storefront platform.

A common enterprise architecture looks like:

Customer storefront
        |
Commerce platform
        |
OMS / Order orchestration
        |
Dropship marketplace layer
        |
Supplier portals + vendor APIs
        |
ERP / Finance / Inventory systems

Questions that would change the recommendation

For an enterprise retailer adding dropship alongside an existing commerce business, I’d shortlist Adobe Commerce + Mirakl rather than expecting one platform to do everything.

My recommendation: Adobe Commerce + Mirakl

Adobe Commerce is particularly strong if your B2B requirements include company hierarchies, multiple buyer roles, permissions, customer-specific catalogs/pricing, quotes, purchase orders and approval rules. Its B2B model explicitly supports complex company structures and purchasing permissions. experienceleague.adobe.com

Its shared catalogs can give different companies different assortments and prices, which is useful for rules such as “Vendor X products are available only to these accounts, at these negotiated prices.” experienceleague.adobe.com

Where I'd avoid stretching Adobe Commerce is the supplier-facing operating model. If you're onboarding hundreds/thousands of dropship vendors, you need catalog ingestion, vendor onboarding, inventory feeds, order routing, fulfillment SLAs, shipment/tracking feeds, vendor performance and exception management.

That's where Mirakl Dropship is compelling. It supports vendor connectivity through API, EDI, CSV, XML and a web portal, and is specifically designed to operate marketplace and dropship businesses from one vendor platform. www.mirakl.com

So I'd architect it roughly as:

Customer storefront → Adobe Commerce → OMS/order orchestration → Mirakl Dropship → Vendor

with ERP/PIM feeding the appropriate systems and Mirakl sending vendor inventory/order/fulfillment data back into your operational stack.

When I'd choose something else

• All-in on Salesforce: Salesforce Commerce becomes more attractive if your CRM, customer service, CPQ and partner ecosystem already revolve around Salesforce.
• Very complex/custom B2B: commercetools can be excellent if you're prepared to build a composable platform and have a strong engineering organization.
• Dropship is becoming the strategic business model: I'd put more weight on Mirakl and potentially make it the vendor-network layer regardless of which storefront you choose.

The key architectural distinction: don't select a commerce platform primarily because it has a “vendor portal.” For an enterprise retailer, I'd separately evaluate B2B policy/rules, vendor-network management, and order/fulfillment orchestration. Mirakl is much stronger on the latter two; Adobe Commerce is much stronger on the first.

If you give me your current commerce/ERP/OMS stack, approximate vendor count, B2B customer complexity, and whether you're building marketplace + dropship or dropship-only, I can narrow this to a 2–3-platform architecture recommendation.

For an enterprise retailer adding dropshipping, I’d narrow the field to Spryker, Adobe Commerce + Mirakl, and VTEX. The key distinction is whether your “vendor portal” is a true seller/merchant operating portal or simply a B2B customer portal.

My shortlist

\*commercetools is extremely flexible, but expect to build more of the marketplace/vendor operating model yourself.

1. Spryker — my first look

Spryker is unusually well aligned with your combination of requirements. Its platform explicitly combines B2B commerce, self-service portals and enterprise marketplace capabilities. spryker.com

More importantly, its marketplace architecture has an actual Merchant Portal where vendors can manage profiles, offers, products and orders. docs.spryker.com It also has capabilities around merchant onboarding, vendor permissions, product/offer management, order splitting and marketplace operations. spryker.com

That makes it a particularly good fit if your roadmap is:

Retailer → add dropship vendors → give vendors self-service → introduce marketplace economics → potentially let vendors sell B2B as well.

Spryker enterprise marketplace

2. Adobe Commerce + Mirakl — strongest alternative

Adobe Commerce has exceptionally deep B2B primitives: company hierarchies, roles/permissions, customer-specific catalogs and pricing, credit, approval workflows and requisition lists. experienceleague.adobe.com

For the vendor side, I'd pair it with Mirakl rather than trying to make Adobe's native B2B functionality serve as the seller marketplace. Adobe documents a prebuilt Adobe Commerce–Mirakl integration covering seller experience, offers, commissions, seller APIs, order management, seller KPIs and advanced marketplace rules. business.adobe.com

That's a very credible architecture if you already have substantial Adobe investment.

Adobe Commerce B2B

3. VTEX — worth serious consideration for a retailer

VTEX is compelling if the strategy is more unified retail + marketplace than pure B2B. Its B2B offering supports self-service buyer portals, custom pricing, procurement integration and buying policies/approval workflows, while its marketplace model is designed for multi-tier distribution networks. www.vtex.com

I'd put VTEX ahead of Adobe if your operating model is heavily marketplace-oriented and you want more of the marketplace machinery in the commerce platform rather than assembling it from components.

VTEX B2B Commerce

4. commercetools — powerful, but a different bet

commercetools is attractive if you have a sophisticated architecture team and want your commerce layer to be an orchestration engine rather than an all-in-one application. Its B2B offering supports account hierarchies, granular permissions, customer-specific pricing, approvals and large catalogs. commercetools.com

It also explicitly supports marketplaces and hybrid B2B/B2C models. commercetools.com

The catch: I'd be cautious if “vendor portal” is a day-one requirement. You have much more freedom, but that also means more implementation work than Spryker's merchant-portal model.

commercetools B2B Commerce

What I'd choose

If I were evaluating this for an enterprise retailer, my initial architecture shortlist would be:

1. Spryker — if vendor/dropship operations are central to the strategy
2. Adobe Commerce + Mirakl — if deep B2B rules and Adobe ecosystem are paramount
3. VTEX — if you want a more integrated retail/marketplace operating model
4. commercetools — if your engineering organization strongly favors composable

The biggest evaluation mistake would be comparing these solely on B2B features. Your real requirement is B2B + marketplace + dropship orchestration. I'd specifically test each platform against vendor onboarding, vendor-specific catalogs/prices, inventory feeds, order routing/splitting, SLA enforcement, commissions, returns, vendor fulfillment exceptions, customer-service ownership, and B2B buyer-specific rules.

If you give me your ERP/OMS, approximate SKU/order volume, number of vendors, and whether vendors will eventually set their own pricing, I can narrow this to a 2–3 platform recommendation and an evaluation scorecard.

For your specific combination—enterprise retail + complex B2B rules + a dropship/vendor channel—I’d shortlist Spryker, SAP Commerce Cloud, and Adobe Commerce, with Salesforce Commerce as a strong B2B alternative if your Salesforce footprint is substantial.

1. Spryker — probably the strongest match

Spryker is unusually well aligned with what you're describing because it treats B2B commerce and marketplace/merchant operations as first-class capabilities. Its B2B stack supports approvals, quotes, contract pricing, shared carts, roles and restrictions, while its marketplace capabilities include a Merchant Portal, merchant/operator dashboards, offer/product management, automated order splitting, and approval workflows. spryker.com

That makes the architecture fairly natural:

Retailer → B2B buyer/account rules → product/price rules → vendor selection → vendor portal → order split → vendor fulfillment → tracking

For a dropship channel, that last part is particularly important: you don't just need a commerce storefront—you need somewhere suppliers can manage products, orders, inventory/fulfillment information and potentially payouts.

Spryker B2B Commerce

2. SAP Commerce Cloud — strongest enterprise alternative

If you're already an SAP shop, I'd take SAP Commerce very seriously. Its B2B model supports complex organizational structures, multiple supplier catalogs, inventory, contracts, customer information and orders. help.sap.com

More importantly for your use case, SAP's marketplace capabilities explicitly include vendor management, vendor product management, order management and vendor-user APIs. Vendor orders can be split from a master order, and vendors can approve/reject orders and provide fulfillment/tracking information. help.sap.com

That's very close to the operational model of enterprise dropshipping.

SAP Commerce Cloud

3. Adobe Commerce — excellent B2B engine, weaker native vendor story

Adobe Commerce has an excellent B2B foundation: company accounts and hierarchies, roles/permissions, shared catalogs, company-specific pricing, quotes, purchase orders and approval rules. experienceleague.adobe.com

So if your difficult problem is primarily "different corporate customers need different catalogs, prices, payment terms and approval workflows", Adobe is very compelling.

The distinction is that I'd treat the vendor portal/dropship marketplace as an architectural extension rather than assuming Adobe's native B2B functionality solves it. Its B2B model is fundamentally centered on your company selling to buyer companies. developer.adobe.com

Adobe Commerce B2B

4. Salesforce Commerce

Salesforce has a strong rules model around buyer groups, entitlements and price books, including buyer-specific pricing, product visibility and negotiated contract access. developer.adobe.comhelp.salesforce.com

I'd favor it when your enterprise already runs heavily on Salesforce—particularly if CRM, account management, sales processes and customer data need to be deeply integrated.

But for a supplier marketplace/dropship operating model, I'd rank Spryker/SAP ahead of it.

Salesforce Commerce

What I'd choose

If I were designing the RFP, my initial ranking would be:

1. Spryker — best single-platform conceptual fit for B2B + marketplace + dropship.
2. SAP Commerce Cloud — best if SAP/S4 is strategically important.
3. Adobe Commerce — best if B2B customer rules are the dominant complexity and vendor operations can be built/integrated.
4. Salesforce Commerce — rises considerably if Salesforce is already your enterprise backbone.
5. commercetools — compelling if your architecture team wants composability and is comfortable assembling more of the marketplace operating model.

The key RFP question I'd use isn't simply "Does it support dropshipping?" It's:

Can a vendor independently manage its assortment, inventory, orders, fulfillment SLAs and tracking while the retailer simultaneously enforces customer-specific B2B pricing, assortment, credit, approval, tax and shipping rules—and split a single customer order across multiple vendors?

That requirement will separate the genuinely suitable platforms from ordinary B2B ecommerce platforms very quickly.

For an enterprise retailer adding dropship while retaining complex B2B rules, I’d separate the decision into two layers: the commerce engine and the vendor/dropship operating layer. That distinction matters because vendor onboarding, catalog ingestion, fulfillment SLAs, commissions, and supplier self-service are not the same problem as B2B pricing and procurement.

My shortlist

1. Adobe Commerce — my pick if B2B rules are the hardest requirement

Adobe Commerce has unusually deep native B2B capabilities: company hierarchies, shared catalogs, customer-specific pricing, purchase orders, requisition lists, negotiable quotes and approval-oriented workflows. Recent independent comparisons continue to put it at the top for complex B2B requirements. elogic.co

The weakness is vendor/dropship management. Adobe gives you a highly extensible commerce core and an extension ecosystem, but a serious multi-vendor operation generally means adding a marketplace/dropship solution rather than getting the whole supplier operating model natively. Adobe explicitly supports extending Commerce through third-party apps/extensions. experienceleague.adobe.com

I'd choose it if: your B2B requirements include sophisticated account hierarchies, customer-specific assortments/pricing, RFQs, approvals, negotiated contracts, or unusual commercial rules.

2. VTEX — strongest single-platform candidate

VTEX is particularly interesting for your situation because it combines enterprise commerce with marketplace capabilities. Its B2B offering explicitly supports buyer portals, custom pricing, procurement integration and enforcement of commercial rules at checkout. www.vtex.com

That makes it more compelling than a conventional B2B platform if your strategy is:

Existing owned inventory + B2B customers + third-party assortment + dropship vendors + potentially a marketplace later.

I'd put VTEX through the RFP if you want to minimize the number of systems.

3. Mirakl — potentially the best answer for the vendor side

Mirakl is not what I'd use as the primary B2B commerce engine. I'd consider it the vendor/dropship layer sitting beside your commerce platform.

This is where it gets very compelling: Mirakl now explicitly supports both marketplace and dropship from the same platform, including vendor onboarding, catalog quality, vendor relationships, margin/commission management and operational workflows. www.mirakl.com Its Dropship product also handles vendor cost submissions, margin calculations and vendor-suggested pricing. www.mirakl.com

So an architecture such as:

Adobe Commerce / VTEX / existing commerce → Mirakl → vendors → customer

can be much cleaner than trying to turn the commerce platform itself into a supplier-management system.

4. commercetools — best if you're already a serious composable enterprise

commercetools makes sense if you have a strong engineering organization and want pricing, customer accounts, order orchestration, vendor services, PIM, OMS, etc. to be independently modeled.

The tradeoff is that you're buying architectural freedom rather than a finished B2B/vendor solution. Current comparisons characterize it as highly flexible but requiring substantially more custom development than Adobe or SaaS alternatives. elogic.co

I'd choose it if your architecture team is already committed to MACH/composable—not simply because it's technically elegant.

What I would not lead with

Shopify Plus is attractive if the primary objective is getting B2B + DTC live quickly. Its B2B capabilities have expanded substantially, but independent 2026 comparisons still identify gaps around things such as native RFQ/negotiated quotes and sophisticated approval/requisition workflows. elogic.co

For a retailer saying "complex B2B rules" rather than simply "we're adding wholesale customers," I'd be cautious about making Shopify the strategic foundation.

My recommendation

I'd take three architectures into an enterprise evaluation:

1. VTEX — best candidate for an integrated commerce + marketplace/dropship model.
2. Adobe Commerce + Mirakl — strongest candidate if sophisticated B2B rules are paramount and you're comfortable with a two-platform architecture.
3. commercetools + Mirakl — strongest candidate if your enterprise is committed to composable architecture.

The key RFP question I'd emphasize is not "does it have a vendor portal?" Instead, test the entire transaction:

Vendor onboarding → vendor-specific catalog → customer/account-specific price → B2B approval → order routing → vendor fulfillment SLA → split shipment → cancellation/return → vendor settlement → margin reporting.

A platform can demo a beautiful vendor portal and still fall apart when those rules interact.

If you tell me your ERP/OMS (SAP, Oracle, Manhattan, etc.), approximate SKU/vendor count, and whether you need marketplace commissions or purely dropship, I can narrow this to a 2–3 platform architecture and give you an enterprise-style scorecard.

For an enterprise retailer adding dropshipping, I’d shortlist Adobe Commerce, BigCommerce Enterprise, and a marketplace platform such as Mirakl—but the right choice depends heavily on whether your “vendor portal” means supplier self-service or a true third-party marketplace.

My recommendation

If dropshipping is becoming a major channel with dozens/hundreds of vendors, I'd look hardest at Adobe Commerce + Mirakl.

Adobe's B2B capabilities are unusually strong for an enterprise retailer: company hierarchies, buyer roles/permissions, shared catalogs with company-specific pricing, negotiated quotes, purchase-order approvals, payment/shipping rules, etc. experienceleague.adobe.com

Mirakl then handles the marketplace/supplier side—vendor onboarding, seller operations, catalog feeds, commissions, fulfillment workflows, etc. That separation is attractive because B2B customer rules and supplier rules are fundamentally different problems.

If you want fewer moving parts, BigCommerce Enterprise/B2B Edition is compelling. Its Buyer Portal supports company users, roles, quotes, invoices and account hierarchies; custom roles and permissions are also available through its APIs. docs.bigcommerce.com

The architecture I'd evaluate

Customer → Commerce platform → Order orchestration → Vendor portal → Supplier

Rather than trying to make the commerce platform itself do everything:

• Customer/B2B rules: account hierarchy, contract pricing, payment terms, approval thresholds, customer-specific assortment
• Commerce: cart, checkout, pricing, promotions
• Order orchestration: split orders, routing, inventory, SLA, returns
• Vendor portal: onboarding, SKU mapping, inventory, pricing, order acceptance, shipment/tracking, invoices
• ERP: financial system of record

The key architectural question I'd put in the RFP is:

Can a single customer order contain both first-party and dropship items, be split automatically by fulfillment source, and preserve customer-specific B2B pricing/terms while each vendor sees only its own order lines?

That's where superficially similar "B2B ecommerce" platforms start to diverge.

If you tell me roughly (1) number of vendors, (2) number of SKUs, (3) ERP—SAP/Oracle/etc., and (4) whether vendors need to manage their own catalog/pricing, I can give you a platform shortlist with a weighted scorecard for your use case.

For your use case, I’d shortlist Spryker, Adobe Commerce + Mirakl, and commercetools + Mirakl. The key distinction is whether you want the commerce platform itself to own vendor/dropship operations, or whether you want a dedicated marketplace/dropship layer.

My recommendation: Spryker

For an enterprise retailer adding dropshipping while retaining sophisticated B2B, Spryker is probably the cleanest fit.

Its B2B platform supports complex buying journeys, including CPQ/RFQ and customizable order-management workflows, while its Enterprise Marketplace functionality is explicitly designed for onboarding third-party merchants. spryker.com

Importantly, Spryker has a Merchant Portal where vendors can manage their profiles, offers, products and orders rather than forcing everything through your internal admin. docs.spryker.com

That combination matters because your requirements are really two problems:

Buyer side

• Account/company hierarchies
• Buyer roles and permissions
• Customer-specific catalogs
• Contract/customer pricing
• Approval workflows
• RFQ/negotiated pricing
• Credit/payment terms
• B2B-specific checkout rules

Vendor side

• Vendor onboarding
• Vendor-specific catalog/assortment
• Offer and price management
• Inventory feeds
• Order acceptance
• Fulfillment/shipping SLAs
• Returns
• Vendor performance
• Settlement/commission logic

Spryker is unusual in that those two sides are first-class parts of the same commerce/marketplace architecture.

The strongest alternative: Adobe Commerce + Mirakl

If you're already heavily invested in Adobe Commerce, I wouldn't necessarily replatform. Adobe's native B2B capabilities are very strong: company hierarchies, roles/permissions, shared catalogs, customer-specific pricing, negotiable quotes, purchase orders and approval rules are all supported. experienceleague.adobe.com

The weakness is the vendor portal/dropship side. I'd pair it with Mirakl rather than trying to turn Adobe into a marketplace platform through custom development.

Mirakl's Dropship product is specifically designed for enterprise dropship and can operate marketplace + dropship simultaneously. It also provides integrations with Adobe Commerce, Salesforce, SAP and other commerce/ERP systems. www.mirakl.com

So the architecture becomes:

Adobe Commerce → B2B customer experience, pricing, accounts, checkout
Mirakl → vendors, marketplace offers, dropship orchestration
ERP/OMS/PIM → enterprise systems of record

That's a very defensible architecture for a large retailer.

What I'd choose

If you're selecting a new commerce platform:

Spryker if you want the fewest major moving pieces and marketplace/dropship is strategically important.

If you're already an Adobe Commerce retailer:

Adobe Commerce + Mirakl is probably the lower-risk enterprise architecture.

If you're committed to composable/headless:

commercetools + Mirakl is worth serious consideration. commercetools provides the API-first, modular commerce foundation, while Mirakl handles the marketplace/dropship specialization. www.mirakl.comcommercetools.com

One important caveat: don't evaluate these primarily on storefront features. For your use case, I'd make the RFP heavily weighted toward rule-engine flexibility, vendor onboarding/portal capabilities, order routing, inventory ownership, split orders, returns, settlement, and ERP/OMS integration. Those are what will determine whether the dropship channel becomes an operational headache.

If you tell me your ERP/OMS/PIM stack (e.g. SAP, Oracle, Manhattan, Salesforce) and roughly number of vendors + SKUs, I can narrow this to a 2–3 platform recommendation and give you a weighted enterprise scorecard.

For an enterprise retailer adding dropshipping, I’d shortlist Spryker, VTEX, and Adobe Commerce + a marketplace layer such as Mirakl. The right choice depends on whether the vendor portal is core to the architecture or you mainly need sophisticated B2B buyer rules.

My recommendation: Spryker

For your specific combination—complex B2B rules + dropshipping + vendor portal—Spryker is probably the cleanest architectural fit.

Spryker explicitly positions its platform around B2B commerce, self-service portals, and enterprise marketplaces. Its marketplace capability includes merchant onboarding, catalog uploads, vendor permissions, offer management, and fulfillment tooling. spryker.com

That matters because your vendor model can become much more complicated than simply "seller lists a product." You may need:

• Vendor-specific assortment and pricing
• Customer/account-specific pricing
• Contract pricing
• B2B buyer hierarchies and approval limits
• Vendor SLAs and fulfillment rules
• Vendor-specific inventory feeds
• Drop-ship routing
• Split orders across first-party and third-party inventory
• Vendor commissions/fees
• Vendor onboarding and catalog approval
• Different shipping promises by vendor
• Returns/refund responsibility by vendor

Spryker also has B2B marketplace functionality specifically covering things such as merchant-specific prices, product approval, shopping lists, and quick ordering. docs.spryker.com

When I'd choose VTEX instead

VTEX is particularly attractive if you want a more integrated retail marketplace model rather than building a lot of the marketplace operating model yourself.

Its marketplace architecture supports external sellers, seller selection at checkout, trade policies, catalog mapping, payments, and a Seller Portal through which sellers can connect to the marketplace—even sellers that aren't running VTEX themselves. help.vtex.com

One particularly useful concept is the trade policy: it can control assortment, pricing, promotions, customer segmentation, payments, and shipping strategy for a sales channel. help.vtex.com

I'd put VTEX ahead of Spryker if your priority is getting an enterprise marketplace live relatively quickly with less custom marketplace infrastructure.

When I'd choose Adobe Commerce + Mirakl

This is compelling if your organization already has significant Adobe Commerce investment or if your B2B requirements are unusually deep.

Adobe Commerce's native B2B capabilities are strong: company hierarchies, buyer roles/permissions, shared catalogs, company-specific pricing, negotiable quotes, purchase orders/approval rules, requisition lists, and B2B-specific payment/shipping controls. experienceleague.adobe.com

Then Mirakl supplies the marketplace/vendor side. Mirakl is explicitly designed around enterprise third-party marketplaces, with seller onboarding, catalog management, seller operations, and integrations via API, CSV, XML, or EDI. www.mirakl.com

The downside is architectural complexity: you're operating a commerce platform + marketplace platform + integration layer, rather than getting the two domains from one platform.

The decision I'd make

If I were evaluating this for an enterprise retailer, my initial ranking would be:

1. Spryker — best overall fit
Especially if the retailer wants dropshipping to become a strategic marketplace/business model rather than just another fulfillment option.

2. VTEX — best packaged retail marketplace
Strong choice when speed, seller onboarding, omnichannel retail, and operational simplicity outweigh maximum architectural flexibility.

3. Adobe Commerce + Mirakl — best for sophisticated B2B + existing Adobe estate
Potentially the strongest choice if your B2B requirements are the hardest part and you already have Adobe Commerce expertise/investment.

4. Adobe Commerce alone — only if vendor marketplace requirements are modest
Its native B2B functionality is excellent, but I'd be reluctant to make it the sole foundation for a serious multi-vendor dropshipping operation.

One important distinction: don't evaluate these primarily on "does it have a vendor portal?" Evaluate where the rules execute. Your proof-of-concept should test a scenario like:

Customer belongs to B2B account A → buyer has spending limit B → sees contracted assortment C → gets customer-specific price D → product is supplied by vendor E → vendor has inventory F → order is split → vendor receives only its line items → vendor ships under SLA G → customer sees one consolidated order/tracking experience.

That scenario will expose the meaningful differences between these platforms much faster than a feature checklist.

If you give me your ERP/OMS, approximate SKU/vendor/customer counts, B2B complexity, and whether you already run Adobe/Salesforce/SAP/etc., I can narrow this to a 2–3 platform recommendation with a target architecture and integration map.

For an enterprise retailer adding dropshipping, the platform choice usually depends on whether you need (1) a sophisticated B2B commerce engine, (2) a true supplier/vendor operating portal, or (3) marketplace-style multi-vendor orchestration. Many retailers end up combining a commerce platform with a marketplace/dropship platform rather than forcing one system to do everything.

Here are the strongest fits:

For your use case, I’d shortlist:

1. VTEX + marketplace/dropship capabilities

• Best if you want your retail site to become a supplier ecosystem.
• Handles seller onboarding, marketplace operations, B2B buying flows, and complex commercial models. www.vtex.com

2. Adobe Commerce + Mirakl

• Best for a traditional enterprise retailer with:
  • complex promotions
  • customer-specific pricing
  • multiple brands/regions
  • heavy ERP/PIM/OMS integration
  • thousands of vendors
• Mirakl can handle supplier onboarding, vendor portals, catalog ingestion, and dropship workflows while Adobe remains the storefront/commerce engine. www.mirakl.com

3. commercetools + marketplace layer

• Best if your architecture team wants composable commerce:
  • ERP remains system of record
  • PIM manages catalog
  • OMS manages fulfillment
  • vendor platform manages suppliers
• Strong choice for very large retailers avoiding monolithic platforms. commercetools.com

Capabilities I would require in your evaluation

For enterprise dropship, don’t just check “does it support vendors?” Look for:

B2B rules

• Account hierarchies (parent company → divisions → buyers)
• Contract pricing
• Customer-specific catalogs
• Tiered pricing and rebates
• Quote workflows
• Approval chains
• PO workflows
• Credit limits/net terms
• Sales-rep assisted ordering

Vendor portal

• Supplier self-registration
• Vendor approval workflows
• Product submission
• Content enrichment
• Inventory feeds
• Price updates
• Purchase order acknowledgment
• ASN/shipping updates
• Returns handling
• Vendor performance dashboards

Operations

• Split shipments
• Multi-vendor carts
• Order routing rules
• SLA monitoring
• Commission/margin rules
• EDI/API connectivity
• Dropship inventory synchronization

A common enterprise architecture looks like:

Customer storefront
        |
Commerce platform
        |
OMS / Order orchestration
        |
-----------------------------
|             |             |
Owned DCs   3PLs       Dropship vendors
                         |
                  Vendor portal

If your retailer already has an ERP/PIM/OMS stack (SAP, Oracle, Manhattan, Salesforce, etc.), the answer changes significantly. The best platform is often the one that fits your existing order orchestration and catalog architecture rather than the one with the most storefront features.

For an enterprise retailer adding dropshipping while retaining complex B2B rules, I’d separate the decision into two layers: the commerce engine and the vendor/dropship management layer.

My shortlist

1. Adobe Commerce + Mirakl — my first choice

Adobe Commerce is particularly strong when your B2B model involves company hierarchies, negotiated pricing, customer-specific catalogs, purchasing permissions, quotes, POs, and complex rules. Adobe's B2B model explicitly supports companies with multiple users and purchasing permissions, shared catalogs, custom pricing, quotes, purchase-order workflows, and company hierarchies. experienceleague.adobe.com

Then put Mirakl alongside it for the supplier side. Mirakl Dropship is specifically designed for enterprise dropship operations, including vendor onboarding, catalog quality, and operational scaling. www.mirakl.com

Architecture:
Adobe Commerce → pricing/B2B/customer experience → Mirakl → vendors → fulfillment

That's a very natural fit if your "vendor portal" means vendors need to onboard, maintain SKUs/content, receive orders, acknowledge/fulfill them, manage inventory, and see operational performance.

2. BigCommerce B2B + Mirakl — potentially the sweet spot

I'd give BigCommerce B2B Edition serious consideration. Its native B2B capabilities are unusually good: company hierarchies, custom roles/permissions, quotes, invoices, approval workflows, purchase orders, and a buyer portal. docs.bigcommerce.com

It also supports up to five levels of company hierarchy and custom buyer roles, which is useful for enterprise customers with subsidiaries/franchises. docs.bigcommerce.comwww.salesforce.com

The important distinction is that BigCommerce's Buyer Portal is for your B2B customers, not a full supplier marketplace portal. I'd still pair it with Mirakl for the vendor side.

I'd choose this over Adobe if: you want strong B2B functionality but want a somewhat more SaaS-oriented implementation and don't need Adobe's level of extensibility/customization.

3. Salesforce Commerce — compelling if Salesforce is already your enterprise backbone

Salesforce Commerce is strong for contract pricing, catalogs, account hierarchies, roles and permissions, and B2B customer portals. Its Advanced edition also includes full Order Management. www.salesforce.com

I'd favor it when your retailer already has substantial investment in Salesforce CRM + OMS + Data Cloud, rather than selecting it purely for ecommerce.

Where I'd be cautious: Shopify Plus

Shopify has substantially improved its native B2B offering in 2026. Plus now supports unlimited B2B catalogs, company-specific catalogs, company locations, payment terms, quantity rules, and partial payments/deposits. help.shopify.com

It's therefore a legitimate enterprise B2B option—not the Shopify of a few years ago.

But for your particular combination of requirements, I'd put it behind Adobe/BigCommerce/Salesforce. The issue isn't whether Shopify can do B2B; it's whether you want to build your vendor/dropship operating model and unusual B2B rules around Shopify's ecosystem rather than starting with a platform designed for more complex commerce models.

What I'd recommend

If I were evaluating this for an enterprise retailer, my first POC would be:

1. Adobe Commerce + Mirakl
2. BigCommerce B2B + Mirakl
3. Salesforce Commerce + Mirakl
4. Shopify Plus + appropriate marketplace/dropship tooling

The key architectural decision is not to force the commerce platform to become the vendor-management platform. Let the commerce engine own customer/B2B pricing and checkout, while a marketplace/dropship layer owns supplier onboarding, assortment, vendor SLAs, inventory feeds, order routing, and vendor settlement.

If you tell me your ERP/OMS (e.g. SAP, Oracle, Manhattan), approximate SKU/vendor count, number of B2B customer accounts, and whether vendors need self-service onboarding + inventory/order management, I can narrow this to a 2-platform shortlist and lay out the target architecture.

For an enterprise retailer adding dropshipping while needing complex B2B rules and vendor portals, you’ll usually want a platform that can handle three separate operating models:

1. B2B commerce — account hierarchies, contract pricing, negotiated catalogs, approvals, PO workflows, credit terms
2. Dropship/vendor operations — supplier onboarding, vendor catalogs, inventory feeds, routing orders, SLAs, commissions
3. Enterprise integration — ERP/OMS/PIM/WMS connectivity, tax, fulfillment orchestration, analytics

The strongest candidates are:

My shortlist for your scenario

1. VTEX — if dropshipping/vendor marketplace is strategic

• Native marketplace model
• Seller onboarding
• Vendor catalogs
• Commission rules
• Multi-seller fulfillment patterns

www.vtex.com

2. Adobe Commerce + marketplace layer — if you are a complex retailer

• Best for unusual rules:
  • customer-specific pricing
  • regional catalogs
  • promotions
  • approval workflows
  • ERP-driven logic
• Large ecosystem of marketplace/vendor extensions

3. commercetools — if you want a long-term enterprise architecture

• Strong choice if you already have:
  • microservices/API strategy
  • internal engineering resources
  • multiple channels (store, app, marketplaces, B2B portals)
• Handles complex B2B structures such as business units, roles, and permissions. commercetools.com

Capabilities I would require in your RFP

Vendor portal

• Vendor self-registration and approval
• Vendor product upload/API ingestion
• Vendor inventory feeds
• Vendor order dashboard
• Shipment tracking updates
• Returns workflow
• Vendor SLA monitoring
• Commission/payment reconciliation

B2B rules

• Customer-specific catalogs
• Contract pricing
• Tier/volume pricing
• Account hierarchies (parent company → locations → buyers)
• Approval chains
• Quote/RFQ workflows
• Net payment terms
• Tax exemption handling
• Punchout/procurement integration if relevant

Dropship orchestration

• Split orders by supplier
• Route orders automatically
• Supplier inventory reservation
• Backorder rules
• Multi-node fulfillment visibility
• Exception management

A key architectural question: are you trying to become a marketplace (third-party sellers sell directly to your customers), or simply add supplier dropship capability (you remain merchant of record)?

Those two models often lead to different platform choices. For a retailer adding supplier dropship, I would generally favor Adobe Commerce, VTEX, or commercetools over a marketplace-first solution.

For your use case, I’d put VTEX at the top of the shortlist. The combination you described—enterprise retail + complex B2B commercial rules + adding dropship/third-party sellers + vendor self-service portals—is unusually well aligned with VTEX’s architecture.

My shortlist

Why I'd favor VTEX

VTEX has native marketplace functionality where third-party sellers can be onboarded, their catalogs integrated, offers managed, and orders routed to the appropriate seller. It explicitly supports external sellers that aren't already on VTEX. help.vtex.com

More importantly for your requirement, Seller Portal is an actual VTEX component, rather than something you'd have to build around the commerce platform. Sellers get capabilities around catalog, pricing, logistics and order management, and the portal can be customized through VTEX's Seller Portal Edition App. developers.vtex.com

VTEX also supports marketplace mechanics that matter for dropshipping: seller selection based on availability/location, split fulfillment, seller payouts/commissions, catalog integration and order orchestration. www.vtex.com

On the B2B side, VTEX positions its platform around buyer portals, custom pricing, procurement integration and enforcement of commercial rules at checkout. www.vtex.com

Where Adobe is stronger

If your dominant problem is very sophisticated B2B account structures, I'd seriously evaluate Adobe Commerce.

Its B2B capabilities are unusually mature: company hierarchies, multiple buyer roles/permissions, shared catalogs with company-specific pricing, negotiable quotes, purchase-order approval rules, requisition lists and company-specific payment/shipping rules. experienceleague.adobe.com

The tradeoff is that vendor marketplace/dropship is not as central to the product as it is in VTEX. You'd likely be assembling more of the seller-management experience through customization, extensions and/or a marketplace platform.

commercetools

commercetools is compelling if you have a strong internal engineering organization and want a composable architecture. Its B2B model supports arbitrary account hierarchies, granular roles, approval rules and sophisticated pricing/catalog models. commercetools.com

But for your particular requirement, I'd ask a critical question: do you want to build the vendor operating system, or buy it? VTEX gives you much more of the marketplace/seller workflow out of the box.

My recommendation

I'd frame the decision this way:

Choose VTEX if:

• Dropship/marketplace is a strategic growth channel, not just an experiment.
• You need hundreds/thousands of vendors eventually.
• Vendors need self-service onboarding and catalog/order management.
• You want seller selection, split orders, commissions and payouts integrated into the commerce stack.
• B2B and B2C need to coexist.

Choose Adobe Commerce if:

• Your B2B business rules are the primary complexity.
• Marketplace is relatively small or can be handled by a separate marketplace solution.
• You already have substantial Adobe Commerce investment/customization.

Choose commercetools if:

• Your architecture team strongly prefers composable.
• You're comfortable building the vendor portal, marketplace workflows and orchestration around APIs.

One caveat: don't evaluate this as simply "which platform has the best B2B features?" Your real architecture is probably B2B commerce + marketplace/seller management + PIM/catalog + OMS + vendor onboarding + payments/payouts. VTEX is particularly interesting because several of those pieces are designed to operate together rather than being stitched together.

If you give me your approximate GMV/SKU count, number of vendors (today and 3-year target), ERP (SAP/Oracle/etc.), and whether vendors need to set their own prices, I can narrow this to a VTEX vs Adobe vs commercetools architecture recommendation and call out the likely integration pain points.

For an enterprise retailer adding dropshipping while retaining complex B2B commerce, I’d shortlist Adobe Commerce, Spryker, VTEX, and commercetools—but they fit different operating models.

My recommendation

If your core problem is "we have complicated B2B pricing, accounts, approvals and purchasing rules, and now need to add dropship vendors," I'd start with Adobe Commerce.

Adobe's B2B stack natively handles company hierarchies, roles/permissions, company-specific catalogs and pricing, negotiable quotes, purchase-order approval rules, credit, requisition lists, and differentiated payment/shipping rules. experienceleague.adobe.com

That matters because you don't want the vendor/dropship initiative to force you to replace or weaken your existing B2B model.

Adobe Commerce B2B documentation

But there's an important distinction: a vendor portal is not the same thing as a B2B buyer portal. If your dropship suppliers need to independently log in, manage products, inventory, fulfillment SLAs, orders, returns, commissions, and payouts, I'd put Spryker and VTEX alongside Adobe in the RFP. Marketplace capabilities are much more central to their architectures; independent comparisons also identify Spryker and VTEX specifically for marketplace models. www.shopify.com

How I'd decide

• B2B rules are #1; vendors are an additional channel → Adobe Commerce
• Marketplace/vendor ecosystem is becoming a major business model → Spryker
• Want marketplace + commerce functionality with less custom assembly → VTEX
• Have a substantial engineering team and want composable control → commercetools; its B2B offering supports account hierarchies, granular permissions, approval rules and complex pricing, but the architectural freedom comes with more implementation responsibility. commercetools.com
• Already deeply invested in Salesforce → Salesforce Commerce Cloud; its B2B offering is particularly attractive when commerce needs to sit tightly within the Salesforce ecosystem. www.salesforce.com

One architectural point I'd insist on in your evaluation: don't make the commerce platform the system of record for vendor operations. I'd separate B2B customer/pricing rules, vendor onboarding/catalog, inventory/availability, order routing, fulfillment, and settlement/commission into explicit domains. That will matter enormously once you have hundreds or thousands of dropship vendors.

If you tell me roughly (1) number of vendors, (2) whether vendors need a self-service portal, (3) ERP/OMS you use, and (4) how complicated your B2B pricing/approval rules are, I can narrow this to a 2–3 platform shortlist and an enterprise RFP scorecard.