Fix broken postal codes before the courier rejects them

Buyers mistype postal codes, marketplaces pass them through unchanged, and your courier refuses the label. easySales can detect and correct the postal code on the incoming order automatically, as part of a wider address clean-up that runs before anything is printed.

  • Postal codes detected and corrected on arrival
  • Phone numbers normalised in the same pass
  • Fewer failed labels and fewer undelivered parcels
Try free for 14 days See how it works
No card required
Automation flow diagram showing an incoming order having its postal code detected and corrected Trigger New order created Condition Postal code missing or invalid Action Auto-detect postal code

HOW IT WORKS

Clean the address on the way in

Normalisation is a flow action, so it runs before the label exists.

1

Trigger on arrival

Attach the action to the order-created trigger so it runs the moment the order lands, well before anyone tries to generate a shipping label.

2

Detect and correct

The action works out the correct postal code from the rest of the delivery address and writes it onto the order.

3

Clean the rest too

Chain phone normalisation, client-detail tidy-up and company auto-fill in the same flow, so the whole address is courier-ready in one pass.

Bad addresses caught late vs caught early

Doing it by hand

  • Label generation fails at the packing bench
  • Someone googles the postal code by hand
  • Parcels go out with a wrong code and get returned
  • Phone numbers in five different formats
  • The same city gets corrected again next week

With easySales

  • The address is corrected before packing starts
  • No manual lookups at the bench
  • Fewer undeliverable parcels coming back
  • Phone numbers stored in one consistent shape
  • Every order gets the same treatment automatically

ADDRESS QUALITY

Data cleaning as part of the pipeline

01

Postal codes worked out from the address

When the code is missing or does not match the rest of the address, the action derives the right one and writes it to the order. The correction happens once, on arrival, rather than being rediscovered by whoever tries to ship the parcel.

Auto-detect Writes to the order Runs on arrival
Clean-up log showing corrected postal codes and normalised phone numbers per order Address clean-up Applied ORDER FIELD RESULT #300429 Postal code Corrected #300430 Phone Normalised #300431 Postal code Corrected #300433 Postal code Already valid
02

Part of a whole normalisation set

Postal code detection sits in a group of data-normalisation actions: phone-number normalisation, VAT-number normalisation, company auto-fill, client-detail updates, tax-rate alignment. Chain the ones you need and every order arrives in a consistent shape.

Phone normalisation VAT normalisation Company auto-fill Tax alignment

See VIES validation →

Diagram showing several normalisation actions chained after an order-created trigger Trigger New order created Action Auto-detect postal code Action Normalize phone number Action Auto-fill company details
03

Only writes when something actually changes

A correction that is not needed is not made. Orders whose address is already valid pass through untouched, so your order history is not filled with meaningless edits and your team can trust that a change means something.

No noise Idempotent Clean history
Diagram showing a valid postal code passing through without modification Trigger Normalisation runs Condition Value already correct Action Leave the order untouched
04

Route the exceptions instead of blocking them

Some addresses cannot be salvaged automatically. Combine the correction with a custom status so the handful that genuinely need a human are collected in one queue rather than discovered one at a time at the packing bench.

Exception queue Custom status Human review

See custom status routing →

Diagram showing an uncorrectable address being routed to a review status Trigger Correction attempted Condition Address still invalid Action Set status: address review

Clean addresses on orders from every marketplace and online store you connect

Shopify
Amazon
WooCommerce
Allegro
IdoSell
eMAG
Shoper
Trendyol
PrestaShop
eBay
OpenCart
Decathlon
Magento 2
Skroutz
MerchantPRO
Vivre
GoMag
See all integrations
5 stars

"Labels stopped failing"

5 stars

"Fewer returns to sender"

5 stars

"Addresses arrive clean"

The rest of the clean-up set

VIES Company Validation

EU VAT numbers checked and normalised
Automatic Shipping Labels

AWBs created by rule, per courier
Custom Status Routing

Move orders through your own workflow
Return to Sender

Scan refused parcels back into stock
Automation Flows

Event-driven rules with a visual builder
Order Management

Every order from every channel in one dashboard
SMS Notifications

Tell customers when their parcel moves
Flow Templates

Start from a proven automation
No card required
14-day free trial
Cancel anytime

Ready to stop fixing addresses at the packing bench?

Add one normalisation flow and let every order arrive courier-ready.

Start free trial

Frequently Asked Questions

Have a question? Contact us and we'll be happy to help.

Whenever you trigger it — usually on order creation, so the address is clean long before anyone generates a label. It is a flow action, so the timing is yours to choose.

No. The action only writes when the value actually changes, so valid orders pass through untouched and your order history stays meaningful.

Phone numbers, VAT numbers, company details, client details and order tax rates all have their own normalisation actions in the same group, so you can chain the ones your channels need.

Add a condition that routes them to a custom status, so the handful needing human judgement collect in one queue instead of surfacing individually at the bench.

Because couriers and SMS providers both reject inconsistent formats. Normalising the phone number in the same flow is what makes automated delivery notifications reliable.

No. It is a visual flow action — pick the trigger, add the action, save. No scripting involved.