Mail Queue Priority

by scope01

Send Shopware emails through a dedicated priority queue so important messages are processed promptly, even during large imports and indexing operations.

Expected release: October 2026

Compatible with:

Self-hosted

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

Dedicated priority queue for Shopware emails
Prompt email delivery during large imports and indexing operations
Existing Messenger worker commands remain unchanged
Automatically uses the shop's existing broker
Safely returns pending emails when the plugin is deactivated

About the Extension

Mail Queue Priority for Shopware 6

Order confirmations, password emails and other important messages should not have to wait behind thousands of import, indexing or webhook jobs. This plugin routes Shopware emails to a dedicated Messenger queue and places that queue ahead of regular asynchronous messages during processing.

Your benefits

Faster email delivery: Emails are processed before less time-sensitive queue messages.
Reliable under heavy load: Large imports and indexing operations no longer delay email delivery unnecessarily.
No new worker commands: Existing messenger:consume calls that process the async transport remain unchanged.
Automatic broker integration: The additional queue is derived from the existing Messenger connection.
Safe deactivation: Pending emails are transferred back to the regular async queue.

How it works

The plugin creates the scop_mail_priority transport on the same broker as the existing async queue. Shopware and Symfony mail messages are routed to it automatically. For CLI workers consuming the async transport, the mail queue is moved internally to the first position.

Symfony Messenger starts checking the transport list from the beginning after every processed message. As a result, pending emails are drained before the worker continues with the remaining transports.

Existing workers, retry settings and command arguments remain unchanged. Common Shopware transports using Doctrine, RabbitMQ/AMQP, Redis, Beanstalkd and SQS are supported. A separate DSN can be supplied through an environment variable for unusual or external broker configurations.

Important requirement

A CLI worker running messenger:consume and consuming the async transport is required. The Shopware Administration worker does not consume the priority mail queue and is not sufficient on its own.