divine:
I have just discovered at some cost that Fastway freight is not necessarily calculated on postcode - there might be multiple towns with the same postcode and the freight varies significantly between them.
This is true.
divine:
Does this module check town or postcode or both?
Both, but using the following 'rules'.
If postcode and suburb are both provided, a name lookup is performed on the postcode to ensure the name has a valid match. If so, then both values provided are used.
If the lookup fails, for example, if a person enters 3000 for the postcode, and Adelaide for the suburb, the test will fail, and the quote will be based on the first name that does match the postcode. In this example, Melbourne.
If no suburb name is provided, again, the first suburb name in the lookup list will be used.
In either case, the suburb name that is actually used is sent back to the client and displayed in the shipping estimator.
There are many reasons why a legitimate postcode/name may fail, misspelling being very common.
One problem that has been identified is when it comes to the 2000 postcode, which we all know to be 'Sydney', is that if this is misspelt (yes, it happens), or not supplied, the lookup again returns the first name in the list, which is " BARANGAROO", and for some reason or other, FastWay consider this as an invalid destination suburb, and no quotes are returned.
To mitigate against these problems, the latest versions of the ozpost module uses a little bit of JavaScript to provide a list of suburb names for the customer to select from (where needed).
Cheers
Rod