Aperçu illustratifA build-to-order Magento 2 / Adobe Commerce extension that gives each marketplace vendor its own warehouse,
carrier accounts and dropship routing, with automatic split shipments and per-vendor shipping labels. Built, installed and supported by
ECOSIRE on your store.
Qu'est-ce que Multi-Vendor Marketplace Shipping & Dropship for Magento 2 ?
A build-to-order Magento 2 / Adobe Commerce extension that gives each marketplace vendor its own warehouse, carrier accounts and dropship routing, with automatic split shipments and per-vendor shipping labels. Built, installed and supported by ECOSIRE on your store. Built to order by ECOSIRE for Magento 2 / Adobe Commerce (build-to-order) — indicative price from $999.00 USD; request a quote for a scoped proposal.
Fonctionnalités clés
Fait sur commande, clé en main
Aucune configuration à faire vous-même — une app fonctionnelle conçue, installée et prise en charge par ECOSIRE.
- 1
Vous commandez
Commencez par un prix de développement unique. Nous cadrons le projet avec vous au lancement.
- 2
Nous développons et installons
ECOSIRE la développe, la configure et l'installe sur votre Magento 2.
- 3
Mise en ligne + assistance
Vous êtes en ligne en une semaine ouvrée environ, avec deux semaines d’assistance après la mise en production. Les défauts du code que nous livrons sont corrigés gratuitement.
À propos de ce produit
Most Magento multi-vendor marketplaces ship everything from a single origin, so a cart spanning three vendors is forced through one carrier account, one set of rates, and one fulfillment queue. This extension gives every vendor its own warehouse, its own carrier credentials, and a direct vendor-to-customer dropship path — without you forking the marketplace module or hand-rolling shipping logic per vendor.
It is delivered as a proper Magento 2 module under app/code/Ecosire/MarketplaceVendorShipping, wired through di.invoke and di.xml rather than core hacks. A plugin (interceptor) on the rate-request flow and an observer on sales_order_save_after resolve each quote item to its vendor, split it into per-vendor shipments, and request live rates from that vendor's own Aramex, ShipStation or SMSA account. Service contracts (PHP interfaces in Api/) expose vendor-warehouse and rate operations so both the storefront checkout and your admin tooling consume the same code path.
Vendors manage their warehouse origin, carrier keys and packaging defaults from a dedicated admin grid gated by its own ACL resource (Ecosire_MarketplaceVendorShipping::vendor_shipping). Labels are generated per shipment and stored against the order; a cron job reconciles tracking. The module ships REST and GraphQL resolvers so headless storefronts and vendor mobile apps read shipment state directly.
Honest about delivery: this is not an instant Adobe Commerce Marketplace download. ECOSIRE scopes it against your exact marketplace module (Webkul, Marketplacer, or custom), builds it, installs it on your staging then production Magento, and supports it. It works on Magento Open Source and Adobe Commerce 2.4.x, and is tuned to your carrier contracts and vendor onboarding flow rather than shipped as a one-size-fits-all package.
Ce que vous obtenez
- Custom-built Magento 2 module installed under app/code/Ecosire/MarketplaceVendorShipping on your staging and production environments
- Integration layer matched to your existing multi-vendor marketplace module (Webkul, Marketplacer or your custom vendor schema)
- Configured carrier connections for the carriers you use (Aramex, ShipStation, SMSA) with each vendor's credentials onboarded
- Database schema (db_schema.xml) plus data/schema patches for vendor warehouse, carrier and shipment-mapping tables
- Admin configuration UI, ACL roles and vendor grid, plus REST/GraphQL endpoints documented for your team
- Installation, deployment notes and a short technical handover covering di.xml wiring, plugins, observers and the cron schedule
- Post-launch support window covering bug fixes and Magento 2.4.x patch-level compatibility checks
Pour qui c'est
Marketplace operations lead
Runs a Magento multi-vendor marketplace and needs each vendor to ship from their own location with their own carrier, instead of routing every order through one central warehouse and one Aramex account.
Magento technical lead / solution architect
Wants distributed fulfillment added the right way — service contracts, plugins, observers and DI — without core patches or a brittle module fork that breaks on the next 2.4.x upgrade.
Dropship-model marketplace founder
Operates a near-zero-inventory marketplace where vendors fulfill directly to customers, and needs automatic split shipments, per-vendor labels and tracking surfaced back to buyers.
Comment Multi-Vendor Marketplace Shipping & Dropship for Magento 2 se compare
| Critère | ÉCOSIRE | Construction personnalisée | Concurrent | Natif Magento 2 |
|---|---|---|---|---|
| Per-vendor warehouse origin and per-vendor carrier accounts | Inclus | Prise en charge partielle | Prise en charge partielle | Non inclus |
| Automatic split shipments and labels per vendor in a multi-vendor cart | Inclus | Prise en charge partielle | Inclus | Non inclus |
| Direct vendor-to-customer dropship routing | Inclus | Prise en charge partielle | Prise en charge partielle | Non inclus |
| Aramex / ShipStation / SMSA integration tuned to your contracts | Inclus | Prise en charge partielle | Prise en charge partielle | Non inclus |
| Built, installed and supported on your store (no self-integration) | Inclus | Non inclus | Non inclus | Non inclus |
| Instant self-service download, no scoping or wait | Non inclus | Non inclus | Inclus | Inclus |
| Matched to your exact multi-vendor module and vendor schema | Inclus | Inclus | Non inclus | Non inclus |
| Service contracts, REST and GraphQL for headless / vendor apps | Inclus | Prise en charge partielle | Prise en charge partielle | Prise en charge partielle |
Foire aux questions sur Multi-Vendor Marketplace Shipping & Dropship
How long does delivery take, since this is build-to-order?
After a scoping call to confirm your marketplace module, carriers and vendor schema, typical delivery is about one working week: a draft build on staging mid-way for your review, then production install. The timeline depends on how many carriers need integrating and whether your vendor data model is standard (Webkul/Marketplacer) or custom. You get a firm date in the written scope before any payment beyond the deposit.
Is this an instant download from the Adobe Commerce Marketplace?
No. This is a custom build that ECOSIRE writes, installs and supports on your own Magento install. There is no Marketplace download link. We build the module against your exact multi-vendor setup and carrier contracts, deploy it to your staging and production environments, and hand over the source code and technical docs so your team owns it.
What ongoing support and updates are included?
The price includes a post-launch support window for bug fixes and Magento 2.4.x patch-level compatibility checks. Because you receive full source, your developers can extend it freely. Beyond the included window we offer optional retainer support for new carriers, new vendor flows, or major-version upgrades — quoted separately so you only pay for what you need.
Will it work with my existing multi-vendor extension?
Yes — that is exactly why it is build-to-order. We integrate against your current vendor module (Webkul Marketplace, Marketplacer, or a custom vendor schema) by resolving each quote and order item to its vendor through your existing data, using plugins and observers rather than modifying your marketplace module's code. We confirm the integration points during scoping.
Does it run on Magento Open Source or only Adobe Commerce?
Both. The module targets Magento 2.4.x and uses only standard framework features — service contracts, di.xml, plugins, observers, ACL, cron, REST and GraphQL — so it runs on Magento Open Source and Adobe Commerce alike. If you use Adobe Commerce B2B or MSI features, we align vendor warehouses to your existing MSI source codes during the build.
How are carrier credentials and labels handled securely?
Each vendor's Aramex, ShipStation or SMSA API keys are stored using Magento's encrypted config storage, never in plain code, and access to the vendor shipping grid is gated by a dedicated ACL resource. Labels are generated per shipment through the carrier API and stored against the Magento shipment record, downloadable only by authorized admin and vendor roles.
Modules associés
Mobile WMS Scanner App for Magento 2
A native mobile/tablet warehouse app that lets floor staff scan to receive, putaway, pick, pack, transfer and stock-take against Magento 2 MSI inventory in real time — built, installed and supported by ECOSIRE.
Multi-Carrier Shipping Suite for Magento 2
A custom-built Magento 2 / Adobe Commerce extension that unifies live rate quotes, bulk label printing, pickup scheduling and tracking write-back across 50+ carriers from one admin. Built, installed and supported by ECOSIRE on your store.
MyDeal Integration for Magento 2
A build-to-order Magento 2 module that connects your store to Australia's MyDeal marketplace — bulk listing with category mapping, two-way inventory and price sync, automated order import, and Australian shipping handling, all managed from the Magento admin.
MyFatoorah Payment Gateway for Magento 2
A custom-built MyFatoorah payment integration for Magento 2 and Adobe Commerce: unified GCC checkout (KNET, mada, cards, Apple Pay), payment links, invoicing and admin-side refunds — built, installed and supported by ECOSIRE on an honest delivery timeline.
Multi-Vendor Marketplace Shipping & Dropship
A build-to-order Magento 2 / Adobe Commerce extension that gives each marketplace vendor its own warehouse, carrier accounts and dropship routing, with automatic split shipments and per-vendor shipping labels. Built, installed and supported by ECOSIRE on your store.
- Per-vendor warehouse and inventory origin, mapped to MSI source codes so rates and stock deduct from the correct vendor location
- Vendor-level carrier integration with Aramex, ShipStation and SMSA, each vendor using their own API credentials stored encrypted in config
- Direct vendor-to-customer dropship routing that bypasses a central warehouse for vendors flagged as self-fulfilling
- Automatic split shipments per vendor: a multi-vendor cart yields one shipment, label and tracking number per vendor