
Most Linnworks Rules Engine setups start out clean. A few rules assign shipping services, route orders to the right location and hold anything unusual. They work, so nobody touches them.
Then the business grows. A new channel arrives, a courier changes its services, a second warehouse opens, and each change gets its own rule or a quick exception. A few years later there are dozens of rules, some of them disabled, some contradicting each other, and only one person on the team really knows how they fit together.
This post explains how to recognise when your rules have outgrown their original design, what that costs you, and what to do about it.
Signs your rules have become too complicated
1. Nobody can say for certain which rule changed an order
When an order ends up with the wrong shipping service or in the wrong location, the team has to work backwards through several rules to find out why. If that investigation takes longer than fixing the order, the rules are no longer easy to understand.
2. Rule order matters, and nobody wants to change it
Rules run in sequence, so a later rule can overwrite what an earlier one did. Once a setup depends on a precise order that isn’t written down anywhere, adding or moving a rule becomes risky.
3. The same logic exists in several places
A common pattern is one rule per channel doing almost the same thing. When a courier or service changes, someone has to update every copy, and it’s easy to miss one.
4. “Temporary” rules and disabled rules pile up
Rules added for a promotion, a peak period or a courier problem often stay long after they’re needed. Disabled rules are kept “just in case”. Over time, the list gets harder to read and the live logic gets harder to find.
5. Staff correct orders after the rules have run
If the team routinely changes services, locations or flags by hand after import, the rules aren’t doing their job. The manual correction has become part of the process without anyone deciding it should be.
6. The logic is being forced into rules
Using tags or extended properties as stepping stones between rules, or chaining several rules to imitate a calculation, are signs the requirement has gone beyond what rules handle comfortably. At that point a macro or small custom script is often simpler and easier to test.
7. Only one person understands the setup
If changes wait until a particular person is available, the rules have become a single point of failure. Holidays, sick days and staff changes then become a risk to order processing.
What it costs
Complicated rules rarely fail all at once. The cost shows up in three ways:
- Time: investigating why an order was handled a certain way, correcting orders by hand, and testing every change carefully because nobody is sure what it will affect.
- Cost: wrong shipping services mean overpaying for postage or paying for redeliveries, and staff hours go on checking and fixing rather than processing orders.
- Risk: a small change before a busy period can send orders to the wrong location or service, and the problem may not be spotted until customers complain or a channel penalises late despatch.
A practical example
Imagine a seller with three marketplaces, a web store and two warehouses. Over four years their shipping rules have grown to more than 80, including separate rules for each channel, weight band and courier, plus a set of peak-season exceptions that were never removed. This is an illustration, but the pattern is common.
When their main courier changes a service, the team updates the rules they can find. A week later, orders from one marketplace are still going out on the old service, because a duplicate rule further down the list was missed.
On review, they find that:
- most of the channel-specific rules do the same thing and can be combined into a smaller set based on weight and order value;
- the peak-season rules can be deleted, or kept disabled in a clearly named group;
- a calculation that was spread across four rules can be replaced by one macro that is easier to test; and
- a simple document listing each rule, its purpose and its position in the run order means anyone on the team can make changes safely.
The result is fewer rules, fewer manual corrections and changes that no longer depend on one person. The exact improvement depends on your setup and volumes.
How to get your rules back under control
- List what you have. Export or record every rule, what it does, which orders it applies to and where it sits in the run order.
- Remove what isn’t needed. Delete expired temporary rules and decide whether disabled rules should go.
- Combine duplicates. Where several rules do the same job for different channels, see whether one rule with broader conditions can replace them.
- Name rules clearly. A consistent naming pattern, for example “Shipping – UK – under 2kg”, makes the list readable.
- Move complex logic out of rules. Calculations, lookups and multi-step decisions are often better as a macro or custom script.
- Test changes before they go live. Check new or changed rules against real order examples, ideally outside your busiest hours.
- Keep a change log. Note what changed, why and who changed it, so problems can be traced quickly.
Our Linnworks Automation & Rules Engine services cover this kind of clean-up, and our Linnworks developer services can take on the logic that no longer fits in rules.
When to look beyond rules
The Rules Engine is very good at clear, condition-based decisions. It is less suited to logic that needs calculations, data from another system or many exceptions. If your rules are imitating code, a macro or integration is usually easier to maintain. If you’re not sure whether your other processes are worth automating, our earlier post on 10 Linnworks processes worth reviewing for automation is a good place to start.
Not sure whether your rules need attention?
We offer a free, no-obligation 30-minute Linnworks Efficiency Review. We look at how your rules and automations run today and point out where they are costing you time or creating risk, before any work is discussed.
Book your free Linnworks Efficiency Review
To see everything we do for Linnworks users, from rules and macros to integrations and reporting, visit our Linnworks services page. If you’d prefer an experienced team to keep your setup in shape over time, see our Linnworks technical support retainer.
