Change Shipping Method by Flow

by IWV Digitalagentur

Rating: no rating ( write a review )

Downloads: <10

Flow Builder action that assigns another shipping method to an order automatically, immediately or via the message queue, for the primary delivery or all deliveries.

Annually €16.67* /month €239.88 * €199.99* /year 16.63% discount In comparison to the regular monthly price

Monthly €19.99* /month Cancelable monthly

Compatible with:

6.7.0.0 - 6.7.15.1

Includes:

Free trial month

The subscription starts with a free trial month during which it can be canceled at any time.

All updates

During the subscription all released updates are included for free

Support from the Extension Partner

In case you have any questions or problems with your extension you can always ask the Extension Partner for help during the subscription.

Description

Highlights

New Flow Builder action "Assign shipping method"
Primary delivery or all deliveries of the order
Immediately or in the background via the message queue
Safe: transaction, idempotent, active method required
Console command and event log included

Features

Assign any active shipping method of the order's sales channel from every order-related flow trigger
Use the action after a delay action, like the core actions
Change the primary delivery only or every delivery of the order
Run the change immediately or in the background, per action or as plugin default per sales channel
See the selected shipping method, deliveries and execution directly in the flow

Skip orders that already have the selected shipping method
Protect against concurrent changes with row locks inside a database transaction
Leave the order unchanged and log the reason when the method is inactive, deleted or not in the sales channel, or the order has no delivery
Continue the remaining actions of the flow after such an error
Retry temporary errors in background mode automatically
Log changes and errors in Settings > System > Event logs, or errors only, or nothing
Change single orders on the command line by order number or ID and shipping method technical name, name or ID
Preview changes with a dry run and use exit codes in scripts
React to or prevent changes with events for developers
Remove the action from all flows when uninstalling without keeping data

Show more Show less

About the Extension

Let your flows choose the shipping method

Shopware's Flow Builder can tag orders, change their status and send emails, but it cannot change how an order is shipped. This plugin adds the action Assign shipping method: whenever a flow runs for an order, the order gets the shipping method you selected. Switch paid orders to express shipping, send orders with bulky goods to your freight forwarder, or move orders of business customers to a different carrier, all without editing orders by hand.

Configured like every other flow action

The action sits in the "Order" group of the Flow Builder and works with every trigger that carries an order, including delayed actions. Choose the shipping method from the list of active methods, whether the primary delivery or all deliveries of the order change, and whether the change happens immediately or in the background. The flow shows the chosen settings at a glance.

Reliable in everyday operation

The change is written in a database transaction and is idempotent: an order that already has the method is left alone, and concurrent flows or retries never overwrite each other. If the selected method has been deactivated or deleted, is not assigned to the order's sales channel, or an order has no delivery, the order stays unchanged, the reason is written to the event log and the rest of the flow continues. In background mode the message queue retries temporary errors automatically.

For support and integrations

A console command changes the shipping method of a single order with the same logic, by order number and technical name, with a dry run and clear exit codes for scripts. Developers can react to every change, or prevent it, with two events.

Please note: only the shipping method changes. Shipping costs and order totals stay as they are, exactly like Shopware's own order recalculation; adjust them in the order if the new method costs differently.

This extension is highlighted as part of the Premium Partner Program and can therefore be displayed with priority in the store.

Details

Available: English, German
Latest update: 29 October 2026
Publication date: 30 October 2026
Version: 1.7.0
Category: Shipping provider

Resources

Reviews (0)

Write a review

If you downloaded this extension you can write a review in the Shopware Account.

Write a review

No reviews found.

About the Extension Partner

IWV Digitalagentur

See all extensions

Partner Status

Shopware
Premium Extension Partner

Details

Ø-Rating: 5

Average rating of 5 out of 5 stars
Partner since: 2019
Extensions: 68

Support

Based in: Germany
Speaks: German, English
Response time: Quickly

Are the shipping costs recalculated?

No. Only the shipping method of the delivery changes; shipping costs, taxes and order totals stay as they are. Shopware's own order recalculation keeps shipping costs as well. If the new method costs differently, adjust the shipping costs in the order.

Which flow triggers can use the action?

Every trigger that carries an order, for example order placed, order and payment status changes or shipping status changes. It can also follow a delay action.

What is the primary delivery?

Most orders have exactly one delivery. Orders with shipping discounts have additional deliveries; the primary delivery is the one the order detail page shows. Choose "All deliveries" to change every delivery.

What happens if the selected shipping method is deactivated later?

The action changes nothing, writes an error to the event log and the rest of the flow continues. Select another method in the flow.

When should I use background execution?

Immediate execution lets later actions of the same flow, such as an email, already see the new shipping method. Background execution keeps checkout fast for flows on "order placed" and retries automatically if the database is briefly unavailable; it requires a running message queue worker, as recommended for every production shop.