Shopware Dropshipping 2026: What the Store Promises and What the Core Actually Does

Shopware dropshipping is usually explained as if it were a question of picking the right extension: install a plugin, add your suppliers, done. That framing is not wrong — it is simply silent at the decisive point. It tells you which plugins exist, but not whether they run on your Shopware version, and certainly not what the Shopware core does on its own when goods ship from more than one source.

So for this article we did not summarise other guides. We measured two things. First: all 18 extensions the official Shopware Store returns for the search term “dropshipping” — every product page fetched, compatibility, price and reviews parsed. Second: a running Shopware 6.7.2.2, in which we filled a cart with products from two different manufacturers via the Store API and watched what the system made of it.

Both measurements produce a result that does not appear in the usual round-up articles — and that reverses the order in which the decisions should be made.

The short version

Methodology: all 18 Store entries retrieved from store.shopware.com on 5 Sep 2026 (search term “dropshipping”; the Store itself reports “18 products” — there is no second page), compatibility and purchase state parsed from each product page. Core measurements on a running Shopware 6.7.2.2 (dockware/dev, PHP 8.3.25, MariaDB), cart filled via the Store API. Pickware prices and help articles retrieved the same day from pickware.com and help.pickware.com.

What Shopware brings for dropshipping out of the box

The honest answer first: nothing that carries the name. The instance we measured has 237 database tables. Not one is called supplier, warehouse, dropshipping or similar. There is no supplier entity, no sourcing, no forwarding of orders to third parties.

What does exist is half the job, in a different place. The product table already has fields that could have been built for drop-shipped goods:

Read via DESCRIBE product on Shopware 6.7.2.2 on 5 Sep 2026.

That last field is the interesting part. Shopware has no concept of a supplier — but it does have a concept of a manufacturer, and that can be repurposed. Create one “manufacturer” per supplier and suddenly you have an assignment the rule engine can hook into.

And there is plenty of rule engine: the core ships 95 rule classes. The relevant ones for dropshipping are LineItemOfManufacturerRule (internal name cartLineItemOfManufacturer) plus rules on weight, volume, dimensions, purchase price, stock level and destination country. That is enough to build a shipping method that only applies when goods from a particular supplier are in the cart — without writing a line of code.

This is where most guides stop and say “so it works”. We kept measuring, and that is exactly where the problem sits.

The finding that overrides everything else: one order, one delivery

With multiple suppliers, the central question is not whether you can calculate shipping per supplier. It is: what happens when a customer puts goods from two suppliers into one cart? In reality that becomes two parcels, two lead times, two tracking numbers.

Shopware sees it differently. From the core’s DeliveryBuilder:

public function buildByUsingShippingMethod(
    Cart $cart,
    ShippingMethodEntity $shippingMethod,
    SalesChannelContext $context
): DeliveryCollection {
    $delivery = $this->buildSingleDelivery($shippingMethod, $cart->getLineItems(), $context);

    if (!$delivery) {
        return new DeliveryCollection();
    }

    return new DeliveryCollection([$delivery]);
}

Source: vendor/shopware/core/Checkout/Cart/Delivery/DeliveryBuilder.php, Shopware 6.7.2.2, read 5 Sep 2026.

The method is called buildSingleDelivery and returns a collection with exactly one element. That is not a setting and not a configuration option in the admin — it is the architecture.

Reading code, however, is not the same as measuring. So we tried it: cart filled via the Store API with two products from two different manufacturers.

lineItems: 2
  item: Main product
  item: Main product with advanced prices
DELIVERIES: 1
   positions: 2 | method: Standard | cost: 0

Two suppliers, two positions — one delivery. Cross-check with an item carrying its own free-shipping flag combined with a normal item: again one delivery, both positions showing an identical delivery date.

What the core does with differing lead times is remarkably consistent: it takes the latest one. In getDeliveryDateByPositions it walks all positions and keeps the later date each time. For the customer that means an item which would arrive tomorrow is pulled out to the date of the slowest item in the cart — at least in the display.

The practical consequence, and it is unpleasant: a cart with three suppliers shows the customer one shipping method, one delivery time and one tracking number. In reality it becomes three parcels. No plugin closes that gap through configuration — it requires an intervention in the order process, or an ERP behind it that turns one Shopware order into several supplier orders.

That is why the right question is not “which plugin?” but: how many suppliers may end up in a single cart? Anyone who can answer “one” — because they integrate a single wholesaler, say — has a far smaller problem than someone with five sources.

The Store census: 18 extensions, and what is left of them

The official Shopware Store is the obvious first stop. We did not skim it, we counted it in full: search term “dropshipping”, 18 results, no second page. Every product page fetched individually.

The result sorts itself uncomfortably:

Survey 5 Sep 2026: all 18 product pages retrieved from store.shopware.com, compatibility statement and purchase state read from each page’s HTML.

A third of the offering is built for a Shopware generation nobody installs fresh any more. And it includes precisely the names that come up most often in recommendation lists: the BigBuy Connector, “Dropshipping Advanced”, and Dropshipping powered by Pickware — the latter compatible from 5.2.7 to 5.7.20.

The picture sharpens further when you separate the results by whether they actually do dropshipping. Of the 18, 11 are dropshipping-specific (supplier integration, order forwarding, marketplace connectors). The other 7 are general-purpose helpers that surface because their description contains the word: tax rules at checkout, a CSV export for orders, an alternate shipping email, a sender address for neutral shipping.

Apply both filters at once — dropshipping-specific AND running on 6.7 AND purchasable — and you are left with:

Three. Out of an offering that looks like 18 options at first glance.

One more detail you only see when counting: a single vendor (Melomate UG) supplies 5 of the 18 results — all of them small shipping and tax helpers. So the perceived choice in the Store is not just old, it is also more concentrated than the result count suggests.

Reviews: little substance, but honestly little

Across all 18 extensions there are 31 reviews in total, averaging 4.74. That sounds good until you break it down: 9 of the 18 have no review at all. The four best-rated entries carry most of the votes.

An average of 4.74 from 31 votes spread over 18 products is not market validation — it is the statistical signature of a thinly populated niche. Anyone choosing here is choosing, in almost half of the cases, without any third-party experience to draw on.

The Pickware finding: a recommendation that quietly went stale

Pickware is the most-named ERP in the German-speaking Shopware world, and “just use Pickware” is a standard answer to dropshipping questions. We checked that at the source — in the Pickware help centre.

Searching for “dropshipping” there returns 7 articles. The most relevant is titled “Is dropshipping supported in Pickware?” and answers:

“Pickware is primarily designed as an ERP for trading with your own warehouse. For drop shipments, our Dropshipping plugin is suitable.” — help.pickware.com, retrieved 5 Sep 2026 (translated from German)

All seven articles are tagged “Shopware 5”. Not one refers to Shopware 6. That matches the Store finding exactly, where Dropshipping powered by Pickware ends at 5.7.20 — two independent sources, the same statement.

This does not mean Pickware is useless for Shopware 6 shops. The ERP products for Shopware 6 exist and are mature; they are simply built around your own warehouse. The prices, also checked at the source:

Retrieved from pickware.com/de/preise on 5 Sep 2026. Pickware WMS costs an additional €199/month per device licence, hardware separate. Annual payment gives a 10 % discount.

The lesson generalises beyond Pickware: a plugin recommendation throws no error when the plugin was built for the previous major version. It simply keeps sitting in forums, blogs and agency lists, and keeps sounding right. It only becomes visible when somebody tries to act on it.

Inventory: the problem you only notice in production

In dropshipping the stock belongs to somebody else. Your shop displays a number that came from a foreign system and may already be out of date by the time it arrives.

Shopware gives you a usable foundation here — it distinguishes stock (physical) from available_stock (available, i.e. minus reservations) and knows restock_time. What it does not have is any way to fetch those numbers from a supplier automatically. For that there are exactly three routes:

1. Feed import (CSV/XML, scheduled). The classic. The supplier provides a file, a cron job reads it. Low effort, poor freshness: between two runs your display is a claim. With hourly imports and fast-moving items, overselling is not an edge case — it is built in.

2. API integration (live lookup). The supplier offers an interface, your shop queries it on page load or at checkout. Good freshness, high coupling: if the other end is slow, your shop is slow. Anyone building this needs a timeout and a defined failure behaviour — otherwise your product page depends on a foreign server being up.

3. An ERP in between. The ERP synchronises with the supplier and with Shopware. Cleanest option, and the most expensive — see the Pickware prices above.

The point guides rarely make: choosing between these three is not a technical preference, it is a decision about who pays for the oversell. With a feed import you pay in cancellation rate and customer contact. With an API you pay in load time and outage risk. With an ERP you pay in euros per month. There is no free option.

One pragmatic middle path the core already supports: set stock deliberately conservatively (a safety buffer) and maintain restock_time realistically, instead of promising availability nobody can guarantee. That costs revenue at the peak and saves trouble across the board.

Shipping costs per supplier: what the Rule Builder really does

Here is the good news, and it is genuine: the Rule Builder is more capable than its reputation suggests. 95 rule classes ship in the core, and the blueprint for supplier-based shipping costs works without a plugin:

1. Create each supplier as a “manufacturer”. Shopware has no supplier entity, but product_manufacturer is a free field with its own ID.
2. One rule per supplier, using the condition “line item of manufacturer” (cartLineItemOfManufacturer).
3. One shipping method per supplier, bound to that rule, with its own price matrix (weight, quantity or cart value).
4. Optionally: delivery time per item via delivery_time_id, so the display does not lie in a blanket fashion.

And here is the limit you need to know before building it. The approach works cleanly as long as a cart contains goods from one supplier. As soon as two suppliers are in play, two rules match — and the customer is offered two shipping methods to choose from, not two deliveries with combined costs. They pick one, pay one, and you ship two parcels.

That is exactly the restriction from the section above, now in its practical form. Anyone wanting to bill this correctly has three options:

• Build surcharge rules that detect the multi-supplier case and raise the shipping price. It works, but grows combinatorially with each additional supplier.
• Buy a specialised extension — precisely the niche Shipping Cost – Drop Shipping & Warehouse Grouping (€29/month) occupies.
• Flat-rate the shipping and price the difference in as a calculation item. Inelegant, but for many assortments the most economical answer.

The third option is rarely recommended and frequently correct. A surcharge of a few euros across all orders costs less than bespoke logic that has to be maintained forever.

What this means legally — the part technology does not solve

In dropshipping, the shipping moves outward but the responsibility does not. That is not a Shopware topic, but it co-determines whether the model holds.

Two points that weigh especially heavily in 2026 for shops with suppliers outside the EU — both of which we documented against the original texts in our article on Shopify dropshipping:

Customs. Since 1 July 2026 the €150 duty-free threshold in the EU has been abolished. In its place came a flat duty of €3 — and, crucially, per category of goods, not per shipment. For a model built on individual parcels from third countries this is a structural deterioration that grows with every additional item in the cart.

Product liability. Under the GPSR, offering goods to consumers in the Union means making them available on the market — and without an economic operator established in the EU they may not be placed on the market at all. If your supplier sits outside the EU, you move into that role. The shipping is outsourced; the liability is not.

For Shopware practice this has a concrete consequence: the import of supplier data must carry mandatory information, not just price and stock. Manufacturer details, safety information, the responsible person in the EU — all of it belongs in the feed or in the integration. An import that only transfers title, image and price produces product pages that are legally incomplete, and does so at scale.

When Shopware is the wrong choice for dropshipping

We write a lot of good things about Shopware — it is a strong system, and we run instances of it ourselves. Even so, honestly:

Shopware is the wrong choice if dropshipping is your entire business model and you are starting from zero. The reason is not the technology but the ecosystem. Three usable extensions out of 18 results, a third of the offering stuck on the previous major version, half of them without any review — that is a market which gives you very little. Shopify has an incomparably denser app landscape for exactly this use case; we counted 38 apps there in the dropshipping category alone.

Shopware is the right choice if dropshipping is part of your assortment. An established shop with its own warehouse that has bulky goods or slow movers shipped directly from the wholesaler is precisely the case the built-in tools cover: one supplier per product group, clean separation via manufacturers and rules, no multi-supplier carts. In that case you often need no dropshipping plugin at all, just well-built shipping logic.

Shopware is likewise the right choice if you already run an ERP. Then the whole topic moves out of the shop: the ERP splits orders, maintains stock and creates supplier orders. Shopware is then only the storefront — and at that it is very good.

If you need that comparison in full breadth, it is in our Shopify vs Shopware comparison with its own TCO calculation. What a Shopware project costs overall is covered in Shopware 6 pricing and costs and Shopware store costs. If you are considering the hosted variant: Shopware Cloud.

The decision order that actually works

Everything above yields an order of operations that is the exact reverse of the usual one. Not “which plugin”, but:

1. How many suppliers may end up in one cart? If the answer is “one”, almost everything is solvable with built-in tools. If it is “several”, you need an answer to the one-delivery problem before you install anything.
2. Where does stock come from, and how stale may it be? Feed, API or ERP — the decision about who pays for the oversell.
3. Does the candidate run on your Shopware version? By our count that is not the case for a third of the offering. This check takes thirty seconds and saves weeks.
4. Does the vendor actually support the plugin? With 9 of 18 extensions carrying no reviews, that is an open question, not a rhetorical one.
5. Only now: plugin, custom build or ERP.

Conclusion: the core does more than expected, the Store less

After two measurements a picture emerges that differs from the usual account in both directions.

The Shopware core does more than you would think. 95 rule classes, a manufacturer assignment that can be repurposed as a supplier concept, stock fields with reservation logic and replenishment time — for simple drop shipments that is enough without a line of code.

The Shopware Store does less than it looks. Eighteen results sound like choice. After removing the Shopware 5 plugins, the unpurchasable ones and the merely adjacent ones, three dropshipping-specific extensions remain for Shopware 6.7. And the most-cited recommendation in the German-speaking market — Pickware — concerns Shopware 5 exclusively in this matter.

Between those two sits the finding that touches the architecture: Shopware builds exactly one delivery per order. Not as a default, but by design. Anyone working with several suppliers is therefore not “adding dropshipping to Shopware” — they are bridging an assumption that sits deep in the core. That is doable. But it is a different task from installing a plugin, and it belongs at the start of the planning, not at the end.

The most honest closing recommendation: if you want to find out whether Shopware suits your dropshipping plans, do not start a plugin shortlist. Build a test cart with items from two suppliers and watch what happens at checkout. It takes ten minutes and answers the question that governs all the others.

Frequently asked questions about Shopware dropshipping

Can Shopware 6 do dropshipping without a plugin?

Partly. The core has no supplier entity and no order forwarding, but it ships 95 rule classes including “line item of manufacturer”. That lets you build supplier-dependent shipping methods without code. For order forwarding, stock synchronisation and multi-supplier carts you need an extension, an ERP or custom development.

How many dropshipping plugins actually exist for Shopware?

The Shopware Store lists 18 extensions for the search term “dropshipping”. Of those, 11 are genuinely dropshipping-specific; the other 7 are general shipping and tax helpers. Combining compatibility with Shopware 6.7 and actual purchasability leaves three dropshipping-specific extensions (as of 5 Sep 2026).

Does Pickware support dropshipping in Shopware 6?

No. All seven articles on dropshipping in the Pickware help centre are tagged Shopware 5, and the corresponding Store plugin is compatible only up to version 5.7.20. Pickware itself writes that it is “primarily designed as an ERP for trading with your own warehouse”. The ERP products for Shopware 6 exist but target your own warehouse.

Why does Shopware show only one delivery when several suppliers are in the cart?

Because the core is built that way. The buildByUsingShippingMethod method in DeliveryBuilder calls buildSingleDelivery and returns a collection with exactly one element. We measured this on a running Shopware 6.7.2.2: a cart with two products from two manufacturers produced two positions but a single delivery.

How do I calculate shipping costs per supplier in Shopware?

Create each supplier as a manufacturer, add one rule per supplier using the condition “line item of manufacturer”, and bind a shipping method with its own price matrix to each rule. This works cleanly as long as only one supplier appears per cart. With several suppliers the customer is offered several shipping methods to choose from, not several combined deliveries.

What does a dropshipping extension for Shopware cost?

Of the 18 Store entries, 16 are paid, with a median of €26.99 per month and a range from €6.99 to €50.00. Two extensions are free. An ERP such as Pickware starts at €99 per month on the Starter plan with 1,000 orders included.

How do I keep my suppliers’ stock levels current?

There are three routes: a scheduled feed import (cheap, but stale between runs), a live API lookup (current, but makes you dependent on the supplier’s server being up), and an ERP in between (clean, but expensive). Each route mainly decides whether you pay for overselling in cancellation rate, in load time or in euros.

Is Shopware or Shopify better for dropshipping?

For pure dropshipping as your only business model, Shopify is clearly better positioned: we counted 38 apps there in the dropshipping category alone, against three usable extensions in Shopware. For dropshipping as one part of an established shop with its own warehouse or an existing ERP, much speaks for Shopware.

What changed legally in 2026 for dropshipping from third countries?

Since 1 July 2026 the €150 duty-free threshold in the EU has been abolished; a flat duty of €3 applies instead, per category of goods rather than per shipment. In addition, under the GPSR you move into the role of the responsible economic operator if your supplier sits outside the EU. The shipping is outsourced; the liability is not.

Do I need an ERP for dropshipping in Shopware?

Not necessarily. With a single supplier and a manageable assortment, built-in tools plus possibly one extension are enough. An ERP pays off as soon as several suppliers can appear in one cart, because then somebody has to turn one Shopware order into several supplier orders — and that is precisely what the shop itself cannot do.

How do I tell whether a Shopware plugin is outdated?

Every product page in the Shopware Store shows the supported version range under “Compatible with”. If it ends at 5.7.20, the plugin was built for Shopware 5 and will not run on any Shopware 6 installation. By our count that applies to 6 of the 18 dropshipping extensions — a third of the offering.