New Address

How to flag loyal customers shipping to a new address in WooCommerce

Flag established customers shipping to a new postcode

Badges orders from loyal customers who are shipping to a postcode they have never used before, prompting your team to confirm the address before dispatch.

Shipping warning
The problem

When an established customer suddenly ships to a completely new location, it may indicate a legitimate address change, a gift, or a compromised account. Without a flag, these orders are dispatched without a second look, risking delivery to the wrong address or an intercepted shipment.

The solution

OrderBadger can automatically flag orders from established customers that are shipping to a postcode they have never used before.

Who this is for

Any store with repeat customers - especially those shipping high-value goods where address verification reduces fraud and delivery failures.

At a glance
Requires 5 or more previous paid orders First-ever delivery to this postcode Compares by postcode, not full address Routes to inbox for address confirmation Badge: New Address (yellow)
People also search for
alert when established customer uses new shipping address WooCommerce flag regular buyer new delivery postcode verify address change for repeat customers detect unusual shipping destination from loyal buyers new address warning for established WooCommerce customers

How it works

Checks two conditions: the customer must have 5 or more previous paid orders, and the current shipping postcode must have zero previous deliveries. When both conditions are true, the order is badged and routed to your inbox for address confirmation.

Verify the shipping address with the customer before dispatch. A quick email or SMS confirming the new delivery location can prevent costly misdeliveries and protect against account takeover fraud.

Rule template

Plain English rule Customer has 5 or more previous paid orders and previous orders to same postcode count is 0

Write this (or something similar) in the OrderBadger rule builder. The AI compiler turns it into executable logic automatically.

Make it yours

Adjust thresholds
  • Lower '5 or more previous paid orders' to '3 or more' if you want to flag new-address orders sooner in the customer relationship.
  • Raise '5 or more previous paid orders' to '10 or more' if you only want to flag address changes for your most established accounts, reducing noise.
Add or remove conditions
  • Add 'and order total is over £200' to only flag high-value shipments to new addresses, where the cost of a misdelivery is significant. … paid orders and previous orders to same postcode count is 0 and order total is over £200
  • Add 'and shipping is international' to focus on address changes that cross borders, which carry higher risk and cost if wrong. … paid orders and previous orders to same postcode count is 0 and shipping is international

Badge preview

Default: New Address

When this rule matches

Loyal Customer New Postcode
Previous paid orders: 12  |  Guest: no
Customer has 12 previous paid orders and has never shipped to this postcode before - both conditions are met.
Boundary 5 Orders New Postcode
Previous paid orders: 5  |  Guest: no
Customer has exactly 5 previous paid orders and zero prior shipments to this postcode - boundary values met.

When this rule does not match

Loyal Customer Familiar Postcode
Previous paid orders: 10  |  Guest: no
Customer has 10 previous orders, but has shipped to this postcode 3 times before - not a new address.
New Customer New Postcode
Previous paid orders: 2  |  Guest: no
Previous orders to this postcode is 0, but customer only has 2 previous paid orders - below the 5-order threshold.
First Time Buyer Any Postcode
Previous paid orders: 0  |  Guest: no
Customer has 0 previous orders, so the 5-order minimum is not met. First-time buyers always have a 'new' postcode but are not flagged.

Workflow

This rule includes workflow features that help your team act on flagged orders.

Inbox
Yes

Good to know

  • Address comparison uses postcodes only. A customer shipping to a different street within the same postcode will not trigger this rule.
  • Guest checkouts are excluded because order history tracking requires a registered customer account.
  • The 5-order threshold filters out new customers, who always have a 'new' postcode. Adjust if you want to flag newer customers too.

Frequently asked questions

  • Does this compare exact addresses or just postcodes?
    It compares postcodes only. The previous_orders_to_same_postcode_count field tracks how many prior orders shipped to the same postcode. Different addresses within the same postcode area will not trigger the flag.
  • Why require 5 previous orders instead of flagging all customers with a new postcode?
    New and low-frequency customers always have few or zero orders to any postcode, which would cause excessive false positives. The 5-order minimum ensures only established customers with a clear address pattern trigger the rule.
  • Will the badge appear if the customer previously ordered to this postcode but it was years ago?
    No. If the customer has any prior order to the same postcode - regardless of how long ago - the count will be 1 or more and the rule will not fire.
  • Can I combine this with a value threshold to only flag high-value orders to new addresses?
    Yes. Edit the natural language rule text to add an order total condition, then recompile. This narrows the scope to high-value shipments to unfamiliar addresses.

Related rules

Try this rule in your store

OrderBadger is free on WordPress.org. Install it and create this rule in minutes - no code required.

Install OrderBadger Free