Aah a common software designer's dilemma, do the right thing or the pragmatic thing? It kind of depends on the context of the website, but usually there is a demand that websites are geographically neutral, which makes sense in terms of the internet as global phenomenon philosphically. So sometimes the pragmatic approach gets pooh-poohed by regulatory guidelines or idealists, software owners keeping in mind some hypothetical and misplaced future globalised sales, or all of the above. You _can_ do some interpretation off the request object, ip lookups and so forth to go to a country on your list, but they're clumsy and unreliable and involve calling some sort of function which could annoy someoen on a slow connection even if ajaxy. There's a halfway house approach that sort of has a popular list, say US UK Germany France etc ----------- everybody else but this tends to alienate everyone who isn't where they perceive themselves to be, so alphabetical just ends up being the safe option. If the site is quite clearly uk centric, then I say just have a damn text box to stipulate country if you aren't uk and don't cause the bother in the first place.