Skip to main content

Portal postcode lookup showing 'not delivered to' after zone setup

Explains why portal postcode lookups may show delivery errors immediately after setting up delivery zones, and how sync timing works.

Written by Phil Whitehead

If a customer is seeing a 'postcode not currently delivered to' error on the portal immediately after you have set up a delivery zone in Weighsoft, this is usually caused by a sync delay between Weighsoft and the portal.

Why this happens

Delivery zone changes made in Weighsoft are not reflected in the portal instantly. The portal syncs zone data on a schedule, which means there is a delay between saving a new zone in Weighsoft and it becoming available for postcode lookups on the portal.

This is expected behaviour and does not indicate a configuration error.

What to do

  1. Confirm the delivery zone and postcode have been saved correctly in Weighsoft.

  2. Wait until the next sync cycle has completed — this is typically processed overnight or within 24 hours of the change.

  3. Ask the customer to try the postcode lookup again after that period.

  4. If the error persists after 24 hours, contact support with the postcode and zone details so we can investigate the sync.

Checking zone configuration

Before waiting for a sync, verify that the zone is set up correctly in Weighsoft and that the postcode falls within the defined zone boundaries. An incorrectly configured zone will not resolve after a sync.

Note: If you have just completed an initial portal go-live setup, all zone and product data will sync as part of the go-live process. Contact support if data has not appeared within 24 hours of go-live.

Did this answer your question?