Order routing to suppliers and branches Pro

A route says: when an order looks like this, tell these people. Build one under StoreMaster → Order routing.

Conditions use the same language as every other StoreMaster rule — product, category, tag, order status, country, order value, customer role — so what you learn for pricing works here too.

What a route does not do

It never changes whether WooCommerce sends an email. WooCommerce decides that, exactly as before. A route adds recipients to a message that is already going out, or sends its own.

Only the lines that concern them

A route can be set to minimise. When it is, the recipient does not get a copy of the customer’s email — they get their own message listing only the lines they are responsible for.

That is not a formatting preference. Everyone on one message sees the same message, so a supplier added as a CC would see every other supplier’s products and the customer’s total. Minimising routes therefore get their own message, one per address, so no recipient learns who else was copied either.

The message is deliberately plain: item, SKU, quantity, and the delivery address if you enabled it. No totals, no payment method, no other supplier’s lines. It is a picking instruction, not a receipt.

Only on the emails you choose

A route can name which order emails it applies to. Leave it empty and the route applies to every order email WooCommerce sends for a matching order; choose one or more — new order, completed, refunded — and it applies only to those.

This matters more than it sounds. WooCommerce’s order emails include the ones that go to your customer, not only the ones that go to you. A supplier on a route with nothing chosen is copied on the customer’s completed-order email as well as your own new-order notification. If a route should only reach a supplier when an order first comes in, say so here.

Sending once

A route sends once per order per email type. WooCommerce sometimes fires an email more than once, and background jobs retry; neither produces a second copy.

If you genuinely want to resend, do it deliberately from the order screen.

Addresses

An address that does not validate is dropped and logged. An address containing a line break is refused outright — that is an attempt to inject a mail header, and quietly repairing it would hide the attempt.

A health check tells you if a published route has no usable address at all, because a route that silently sends to nobody looks exactly like one that works.

If you built routes before StoreMaster 0.4.1, open them and check both fields. Addresses and email types shared a single box in earlier builds, and a route saved that way did not send at all. Those routes work now — which means addresses that have never received anything will start to, and if the route names no email types it applies to every order email, your customers’ included. Worth five minutes before it surprises a supplier.