Suggestion to "Shipping by Weight" Computation Method

Hi guys,

The last two sites we've put together using nopCommerce the client has needed to set different shipping costs for different states and/or post code areas.

For example:

- In the United Kingdom it is £5.00 to send a parcel between 0lbs and 10lbs anywhere
- However, in the Scottish Highlands it is actually £12 for the same weight parcel. The Scottish Highlands is not a state so we used the first 2 characters of the post code.
- There is also an anomaly where London is slightly higher for the same weight parcel (£5.50)

We actually created our own computation method called "Shipping by Band", but in hindsight there is no reason why the "Shipping by Weight" couldn't be extended quite easily. When configuing the method the user should be able to set the shipping price for either :

- A country
- A state
- A post code (or part of a post code)

There should probably be validation in place that ensures that a rate for the entire country has been entered before a state/postcode is entered - this will ensure that if the administrator has missed a State, end-users will still be able to get a price for shipping.

I think this would be a really useful extension. It's certainly very relevant to the UK, and whilst I haven't been involved with shipping in the US I would imagine there are extreme differences in shipping costs depending on which State you are sending to....it's slightly larger (just slightly!!) than the UK so I would think the costs are even more variable.

What do you think?

Regards,
Al

higgsy wrote:
I agree with you. I have seen similar requirements in this forum. In Mexico for instance we have special shipping cost for some large metropolitan areas such as Mexico  City Metropolitan Area which crosses several states boundaries.
This extension would be very useful and enhaces my suggestion in https://www.nopcommerce.com/boards/t/13311/nopcommerce-v230-released.aspx?p=3

I would change your proposal to:
- A country
- One or more post codes (or parts of  post codes; i.e.: 123, 34, 124, ...)
since all post codes are build hyerarchically in which the first characters/digits refer to a state/province, thencounty/municipality and so on. Thus the post code covers state boundaries.

Merging both proposals you could have, following your example: UK £5.00 for 0 to 10lbs + £0.5 for additional lbs. + 2% of products value for insurance and London UK £5.50 for 0 to 10lbs + £0.55 for additional lbs. + 2%.

I am including your proposal in my suggestion and its work item. You can vote  here. I have proposed this for v2.6 roadmap

Hi Eduardo,

Ok sounds great. Just to clarify, would your suggestion allow you to enter multiple postcode parts for one cost entry. For example, in the UK I live in Essex, where there are at least 10 different prefixes for postcodes i.e.

CM
CB
RM
SS
CO
IG
EN
E

So, in your proposal you are suggesting using postcodes instead of states. In the example above I would want to enter "CM, CB, RM, SS, CO, IG, EN, E" as one single entry rather than having to set a price for each. Is that what you are suggesting?

Regards,
Al

higgsy wrote:
Hi Al:
Yes thats exactly the idea. In the case of Mexico City Metropolitan Area the entry would be something like "0, 11, 12, 13, 14, 15, 16, 53, 55, 547, 57, 525, 528, 527" meaning ALL beggining with "0" OR "11" OR "12" OR "14" ...

The search should begin with the longest string and end with the shortest and if not found then, as you stated, the corresponding for the (rest of) the country. As example imagine my previous plus another for "62, 665"; the search would begin with 547, 525, 528, 527, 665, then 11, 12, 13, 14, 15, 16, 62, then 0 and if not found then assign the settings stated for Mexico.

Hi Eduardo,

Sounds great - I've voted for it although much of the work item seems unrelated to that which I have suggested.

What do you think the chances are of getting it into version 2.6? It looks like the work item has already been open for sometime now..

Thanks
Al