Errors while setting up Match rules
Navigating the intricacies of postcode range rules in your Postcode Shipping app is crucial for accurate and seamless operations. In this step-by-step tutorial, we'll guide you through common errors and provide clear solutions to ensure your postcode ranges are error-free. Let’s dive into it:
For pseudo numerical and alphanumerical postcodes this could mean that you’re not respecting the same order of number-letters for the postcode on both sides of the range. This means, even if they are both acceptable formats for postcodes in the country, if they’re not exactly the same on both ends, you will have this error.
Take the example of UK postcodes, where AA9A* and A9* are both valid. However, placing them in the same range can lead to errors if the formats aren't exactly the same:
Solution: Separate Lines for Different Formats
If you're dealing with multiple formats, consider creating separate lines for each. This ensures clarity and avoids mixing formats within a single range.
This error could also mean that the number of characters on either end is different:
To solve this, you’d have two options:
Solution 1: Specify Lines for Each Character Count
Place several lines for each number of character, like this:
Solution 2: Leading Zeros
You can place a 0 before the starting character on the lower number to have the same characters on both sides (this logic also works for pseudo-numeric postcodes):
This will show the rate even if the customer doesn’t place a 0 when entering their postcode at checkout, so if the customer places, for example, 800 instead of 0800 they will still get the proper rate you set up for that region:
For alphanumeric postcodes with wildcard range rules, the process differs slightly. Unlike numerical and pseudo numerical postcodes, the 0 workaround doesn't apply to alphanumeric postcodes due to the need for precise character matching; for alphanumeric postcodes, follow solution 1:
The ‘from’ side is the left side of the range (before the hyphen) and the ‘to’ side is the right side (after the hyphen). If either of the sides contain a format invalid for the country in question, you will have this error. Either if it is number of characters or character order:
Solution: Learn how to identify and resolve errors when either side of the range contains an invalid format, whether it's the number of characters or character order.
It’s the same error as the latter but in this case both ends of the range are in an invalid format for the country, this is also solved by double-checking and making sure the format is the correct one for the country.
Solution: Ensure both ends of the range align with the correct format for the country, eliminating this error by double-checking and correcting any discrepancies. For Alphanumeric postcodes, ensure you add the asterisk for non fully entered postcodes.
By following these solutions, you'll enhance the accuracy of your postcode range rules, ensuring a seamless experience for your Postcode Shipping app.
Error: Both sides of the range should be the same format
Due to Mixed Formats within a Range
For pseudo numerical and alphanumerical postcodes this could mean that you’re not respecting the same order of number-letters for the postcode on both sides of the range. This means, even if they are both acceptable formats for postcodes in the country, if they’re not exactly the same on both ends, you will have this error.
Take the example of UK postcodes, where AA9A* and A9* are both valid. However, placing them in the same range can lead to errors if the formats aren't exactly the same:
Solution: Separate Lines for Different Formats
If you're dealing with multiple formats, consider creating separate lines for each. This ensures clarity and avoids mixing formats within a single range.
Due to inconsistent Character Counts
-Addressing Numeric and Pseudo-numeric Postcodes
This error could also mean that the number of characters on either end is different:
To solve this, you’d have two options:
Solution 1: Specify Lines for Each Character Count
Place several lines for each number of character, like this:
Solution 2: Leading Zeros
You can place a 0 before the starting character on the lower number to have the same characters on both sides (this logic also works for pseudo-numeric postcodes):
This will show the rate even if the customer doesn’t place a 0 when entering their postcode at checkout, so if the customer places, for example, 800 instead of 0800 they will still get the proper rate you set up for that region:
-Addressing Alphanumeric Postcodes
For alphanumeric postcodes with wildcard range rules, the process differs slightly. Unlike numerical and pseudo numerical postcodes, the 0 workaround doesn't apply to alphanumeric postcodes due to the need for precise character matching; for alphanumeric postcodes, follow solution 1:
Error: The 'from' or ‘to’ side of the range does not match any known format for this country.
The ‘from’ side is the left side of the range (before the hyphen) and the ‘to’ side is the right side (after the hyphen). If either of the sides contain a format invalid for the country in question, you will have this error. Either if it is number of characters or character order:
Solution: Learn how to identify and resolve errors when either side of the range contains an invalid format, whether it's the number of characters or character order.
Error: This postcode rule does not match any known format for this country.
It’s the same error as the latter but in this case both ends of the range are in an invalid format for the country, this is also solved by double-checking and making sure the format is the correct one for the country.
Solution: Ensure both ends of the range align with the correct format for the country, eliminating this error by double-checking and correcting any discrepancies. For Alphanumeric postcodes, ensure you add the asterisk for non fully entered postcodes.
By following these solutions, you'll enhance the accuracy of your postcode range rules, ensuring a seamless experience for your Postcode Shipping app.
Updated on: 17/11/2023
Thank you!