Refusing sales to a certain postal code

[dpatt111]

Is it possible to refuse sales or service to a certain postal code or group of postal codes? Trying to keep our local competition from buying our graphics and templates.

[TheOracle]

Zen-Cart does not currently filter / restrict any profile readings from customers (except username / emails if they already exists in the database). However, this does sound interesting. If you're using the overrides, for create_account.php file, would it be possible to know which type of postal codes you'd like to restrict ?

- Zipcodes
- Postal codes
- both

?

Please advise.

[dpatt111]

Sorry Oracle, I haven't even got a clue how to begin.

This situation is just upsetting because our competition is winning bids with our graphics! Would like to keep them and others (Locally) from gaining access to our store.

[TheOracle]

Just realized. Unfortunitely, it won't change anything if people were blocked by entering specific zip codes or postal codes, since they could simply enter any valid values and would still be able to checkout the orders. Meaning, nothing would actually prevent these users to pass through.

If you wish to restrict specific access, you should do so by .htaccess with IP address prefixes (or by domain name is also possible).

[Kim]

Instead of blocking sales- you need to protect your intellectual property. Your Terms of service should restrict the usage to the buyer and not be resold- You need a good lawyer not a programming change.

[dpatt111]

Does anybody really read the Terms of Service? I think people just click the agree to speed thru the checkout process.

A lawyer....I believe it would be cheaper to rewrite the program. Have you used one lately?

[TheOracle]

I think people just click the agree to speed thru the checkout process.

Even if it's true, it's still considered a risk, for each buyers, for not readings the terms and agreement. However, by considering the .htaccess way - above, here's a little tip:

- If your local competitors are using the net under constant IPs, (like: 123.321.xxx.xxx), you could easily push them away by adding their constant IPs through your .htaccess file. This way, at least, it would be the cheapest and good way protection, for you, in order NOT to have locals around your neck.

Althought, if your local spot does not really use constant IPs, (which I doubt), then there isn't much you could do rather than forcing your users to scroll down the license agreement window - before they could agree on it (doable by JS codings).

This way, this would push customers to read your license agreement text before officially proceed with the checkout process as they would be more conscent before considering to buy your products.

[dpatt111]

Hey thanks for your help and comments
I have stopped one competitor by banning his Static IP Address, but their's is the only one I can stop this way. All the others are using Dynamic IPs.

It may be tacky, but I was considering put a message to locals on the front page.

Thanks

[Kim]

You can force your customers to agree to your TOS during the checkout. You might want to add a notice there too that Copyright infringement and licenses are strictly enforced etc.

You know that if you let them get away with the infringement that you lose your rights and the work becomes public domain. If you know their customers that have benefitted from the "stolen" artwork you can serve them with cease and desists.

[TheOracle]

It may be tacky, but I was considering put a message to locals on the front page.

With .htaccess, everything is possible. You can even forward banned users to your own personalized 404 error page showing your local message.

Of course, like I said above, if your users are using dynamic IPs, but that the two first IPs remains constant - it's a great plan. Otherwise, if the two first shows different each times, it's useless. If so, I'd deeply considered the JS method. As per Kim mentions above, that is not a bad suggestion but would only show up as a more severe text note (which users could still leave aside and just press on the agreement button to proceed).

At least, with the JS codings, users must scroll down + click at the end of the next before proceeding. This should, and will, bring them more attention before they proceed - as also an obligated step before proceeding to the next step.