-
Notifications
You must be signed in to change notification settings - Fork 72
Description
Describe the bug
When two shipping zones are configured—one with specific wildcard postcode restrictions and another covering the same region without postcode restrictions—the system fails to match the more specific zone. Instead, it applies the more general zone, even when the address clearly matches the restricted wildcard pattern.
If an order is placed with the wrong shipping method, Google Pay orders will always select the pickup address, even when selecting to ship it.
To Reproduce
You need to switch to the legacy local Up method before testing this.
- You need to set up two UK shipping zones. The first one with restricted wildcard zipcodes and the second want to cover rest of the UK.
- First, set up shipping for UK but with the below wild card zipcodes:
BN1 1*
BN1 2*
BN1 3*
BN1 4*
BN1 5*
BN1 6*
BN1 7*
BN1 8*
BN2 0*
BN2 1*
BN2 2*
BN2 3*
BN2 4*
BN2 5*
BN2 9*
BN3 1*
BN3 2*
BN3 3*
BN3 4*
BN3 5*
BN3 6*
BN3 7*
BN3 8*
- Next, set up shipping for the UK but no restriction this time:
-
Now, use the following zipcode to place an order using Gpay: BN1 2PA, and check the shipping output
-
As per our restriction, the zip code should satisfy the first shipping zone (The one with the wildcard restriction). Therefore, the expected output should be:
Local Pickup = Free
Local Delivery = 4.5
Instead the, the system is giving output form the second shipping zone:
Local Pickup 2 = Free
UK Delivery = 7.5
Actual behavior
If there’s just the wildcard zipcode shipping zone available, Google Pay orders will always select the pickup address even selecting to ship it.
Screenshots
Expected behavior
In an ideal scenario, the shipping output should align with the shipping configuration regardless of the payment method.
Additional context
Slack discussion: p1741703377030399-slack-C7U3Y3VMY