Configuring Postcodes
Configuring Postcodes
- The system will only match on area code and does not match on street level, therefore only the first (outer) section of the postcode is compared, i.e. the NG31 part of NG31 7FZ.
- The postcode field can use [A-Z] to represent an alpha character.
- The Postcode field can use [0-9] to represent a numeric digit..
- You can use a % symbol as a wildcard, e.g. NG3% will match NG31, NG3C and NG3.
- When being matched, Postcodes are case-sensitive and [a-z] will not match 'A'. It is recommended that [A-Z] i.e. upper-case is used
Limited ranges can be used, for example:
- [B-G] will match B and F but not A or Q.
- [3-6] will match 3 and 5 but not 7.
- You can add ranges after each other, e.g. [B-G][D-G][1-3] will match DF1 but NOT DF14 (and similar).
- Using the range [1-9] does not include 0, which can be valid in postcodes. [0-9] should be used instead, where appropriate.
Postcode Search Gotchas
Put the most detailed codes first and the least detailed last
When matching a postcode, the system will use the first match it finds. So, for example, if your London deliveries are made by motorcycle courier and all other towns are sent by post, then don't put "N" (North London) ahead of "NG" (Nottingham), otherwise deliveries to "NG31 7XY" will get sent by motorcycle courier!
Entering Postcode Ranges
A format of "NG[0-4]" can be used on the Courier Banding and Delivery Rates screens of System Data. When used in this way the value "NG[0-4]" will be interpreted to mean all Postcodes starting with "NG0", "NG1", "NG2", "NG3" and "NG4".
Make use of the priority field
We suggest starting with a value of "100" and using increments of 10 (e.g. 100, 110, 120, etc.) as this allows you to add in further options at some future date, without having to renumber the entire table. Where a numeric priority is entered, the system will attempt to match each entry in ascending numeric order.