Shipping & fulfillment — Rules2Tag presets
Where it goes, how it ships, and what that costs you.
Each of these is a ready-made rule you can adopt in one click inside Rules2Tag, then change however you like. Nothing runs until you say so, and every rule can be previewed against your own store first.
15 presets in this category
Local customers by postcode
I want to tag customers near my store
Tags a customer whose postcode is one of the ones you list.
Why: Local delivery, click-and-collect and in-store events all need a way to reach the people close enough to use them, and a postcode list is how most merchants actually think about it.
Orders that shipped free
I want to track how much free shipping I am giving away
Tags an order whose shipping was free.
Why: Free shipping is usually a threshold promise nobody measures afterwards. Tagging it makes the cost visible in the order list, without an analytics integration.
Orders shipping to a country
I want to tag orders going to particular countries
Tags an order shipping to any of the countries you list.
Why: Customs paperwork, courier choice and delivery promises all change by destination, and the people packing orders need to see it before they pack.
Heavy orders
I want to flag orders that need special shipping
Tags an order weighing more than the number of grams you choose.
Why: Weight decides courier, cost and whether one person can lift it — and it is knowable at the moment the order arrives rather than at the packing bench.
Orders with a customer note
I want to make sure nobody misses a customer note
Tags an order that has a note on it.
Why: Notes carry delivery instructions and gift messages, and they are easy to miss in a busy order list — which is exactly when missing one costs the most.
Unfulfilled orders
I want to keep an eye on orders that have not shipped
Tags an order that is not yet fulfilled.
Why: The tag lifts itself the moment the order ships, so this is a live worklist rather than a snapshot someone has to remember to clear.
Orders containing a particular supplier’s products
I want orders routed by which supplier has to fulfill them
Tags an order containing at least one product from the vendors you list.
Why: Dropshipped and consignment lines have to reach a different party from the rest of the order, and whoever splits them is otherwise opening each order to check. This is the flag a 3PL, a purchase-order export, or a Flow that emails the supplier can read directly.
Orders placed in a particular language
I want packing slips and emails to go out in the right language
Tags an order placed in one of the locales you list.
Why: The language the customer actually shopped in decides which packing slip, which insert, and which follow-up email is correct — and it is on the order already. Most fulfillment tools can branch on a tag long before they can be taught to read a Shopify locale.
Orders fulfilled from a particular location
I want to see what each warehouse is actually shipping
Tags an order fulfilled from one of the locations you list.
Why: Per-location volume is the number behind staffing, stock transfers and carrier contracts, and Shopify reports it only where you happen to be looking. A tag puts it in every export and every saved view you already use.
Orders using a particular shipping method
I want express orders picked first
Tags an order whose shipping method is one of those you list.
Why: An express order that sits in the queue in order of arrival has already failed, and the shipping line is not something a picker sees on a list. This is the flag that lets a saved view, a printer queue or a 3PL sort by urgency instead of by time received.
Orders shipping from one location
I want the straightforward orders separated from the split ones
Tags an order fulfilled entirely from a single location.
Why: The counterpart to the split-shipment rule. These are the orders that can go down the simple lane — one pick, one box, one label — and separating them is what lets the complicated ones get the attention they actually need.
Orders sitting unfulfilled too long
I want to catch orders nobody has shipped yet, before the customer emails me
Tags an order that is still unfulfilled N or more days after it was placed.
Why: The single most common ops automation there is, and the one Shopify itself cannot express. Its order filters know "unfulfilled" and they know an absolute date — but not "older than two days" as a standing rule you never have to edit. The tag is what a saved view, a Slack alert, or a daily picking list can then hang off.
Part-shipped orders
I want to see which orders went out incomplete
Tags an order that has been only partially fulfilled.
Why: A part-shipped order is the one most likely to generate a "where is the rest of it" ticket, and it hides in plain sight. It is neither unfulfilled nor fulfilled, so it falls out of both views most merchants check.
Orders shipping from more than one location
I want to know which orders have to be split across warehouses
Tags an order fulfilled from more than one location.
Why: A split shipment costs more, arrives in pieces, and confuses the customer — and you generally find out after it has happened. Tagging it makes the pattern visible: if the same pairs of products keep splitting, that is a stocking decision, not a fulfillment accident.
Single-item orders
I want to route one-item orders down a faster packing lane
Tags an order containing exactly one item.
Why: A one-item order can be picked, packed and labeled in a fraction of the time a mixed one takes, and many 3PLs price it differently. Separating them is one of the cheapest throughput wins in a warehouse, and it needs nothing more than a reliable flag on the order.