Product Restrictions - Limit on Geo, Age, other criteria

Some products are legal in X location but not in Y location

So, would be great if you could put limiters in for this or that product so that such a restricted item would show "not eligible" in the checkout once the shipping location (or whatever the limiters are) are determined. Could be country, state, whatever.

Also, some products are limited by purchaser's age, like you can't buy a bb gun or something if you're not at least X years old, so limiter on age would be good too if needed.

Product shipping restrictions too but I think there is an extension around for that, such that item X needs ground shipping only, etc.

While I do believe the suggestions above may bring some interesting approach regarding registered customers, how would these restrictions be applied towards guests ?

thanks straightlight

1. items with such restrictions would display a list of their restrictions on their product page (thus all visitors would see the restrictions)

2. if a guest shopper still tries to purchase a product that has, say, restricted shipping to their area, then the restrictions would kick in once the guest submitted their shipping information, and also those items with such restrictions would then be greyed out in the shopping cart, the shopping cart contents adjusted, and the restrictions for each item would be repeated under each respective item, thus reminding the guest that these are restricted items

3. if the restriction relates to method of shipping, then the shipping methods would need to be limited as such, or perhaps there could be some sort of split shipping where the regular items can use any of the regular shipping methods, but the restricted item could display its own limited shipping options (like UPS Ground ONLY) with separate shipping charge, unless the customer chooses to ship the entire order all using the restricted-item's shipping method, then the shipping charge would all be bundled together, versus separate shipping and split and adjusted charges

4. if the customer has a mix of restricted and non-restricted items in their cart that involve different shipping methods, and the customer chooses to ship the non-restricted items separately, then the cart should calculate the split shipping, one sub-total-shipping for the non-restricted and one sub-total-shipping for the restricted so that the merchant can accurately charge shipping because the restricted item might be rather expensive to ship

thus, if it's a mixed cart and the customer chooses to ship separately, then the cart would essentially do two shipping look-ups

5. if the customer is logged in, then (1) geo-restricted items would not be displayed and (2) if they already have restricted items in their cart, then those items would be grayed out and display the reason why and the cart totals would be adjusted appropriately

sorry if this seems complicated, it's just that the merchant can get killed on shipping a split order if the shipping is not calculated correctly up front.

if you've read this far, you get a pat on the back

thanks

Actually, you do make interesting points above. Although, this part:

4. if the customer has a mix of restricted and non-restricted items in their cart that involve different shipping methods, and the customer chooses to ship the non-restricted items separately, then the cart should calculate the split shipping, one sub-total-shipping for the non-restricted and one sub-total-shipping for the restricted so that the merchant can accurately charge shipping because the restricted item might be rather expensive to ship

would be the complicated subject since Businesses and contributors may have different approach based on their publicized subjects which could corrupt this validation from the core which is why modules exists in OpenCart so to avoid corrupting on one and another (so it says).

As for number 2, there are actually known methods through API Web Service that can already track down shipping locations from merchant views which is more efficient than local modules development since these modules can be easily tricked by simply modifying the guest form before completing the order. As for registered customers, simply editing their account would also be easy for them to manipulate an order while an API Web Service facilitates the validation process on knowing if these changes are still amongst their terms in order for you to deliver your products without loosing the investment.

As for number 3, providing an example like UPS Ground would simply mean minor customization to individual shipping modules and not centralized restrictions from the cart or the checkout process which can already be done.

I am having this problem with paypal for restricted items - is there a module that we can use to make items restricted and force a customer to use a different method of payment other than paypal

CSS wrote:I am having this problem with paypal for restricted items - is there a module that we can use to make items restricted and force a customer to use a different method of payment other than paypal

What happens when the customer's only option is to pay via PayPal because he may not have any other solutions to provide the transaction and his limitations are not related to the topic subject?