Using IP Geolocation for Ecommerce Personalisation

# Using IP Geolocation for Ecommerce Personalisation

Geolocation is a great way to set a default and a terrible way to make a final decision. Ecommerce is where that distinction earns money.

Safe to automate

• Currency display. Show local currency by default, always with a visible switcher.
• Language. Combine country with the Accept-Language header; the header wins when they disagree.
• Shipping estimates. "Delivers to Germany in 2-4 days" on the product page lifts add-to-cart rates.
• Store and warehouse suggestions. Nearest location, pre-selected but editable.

Never automate

• Tax calculation. VAT and sales tax follow the billing or delivery address, not the IP. Getting this wrong is a compliance problem, not a UX one.
• Hard redirects to a country site. A user in a hotel abroad should not be trapped on the wrong storefront. Offer a banner, not a redirect.
• Price discrimination by IP. It is detectable, it generates press, and users route around it in seconds.

The switcher matters more than the guess

Every automated default needs an obvious, persistent override. Store the choice in a cookie and honour it above the IP forever after. Most complaints about geolocation are really complaints about not being able to change the guess.

Where classification helps checkout

An order shipping to one country, billed in another, from a hosting or VPN exit is the classic reshipping-fraud pattern. Individually each fact is innocent. Together they justify a step-up check. Score the combination rather than blocking on any single field.

Measure it

Run the personalisation as an experiment. Compare conversion for auto-detected currency versus a neutral default in each major market. In our experience the lift is real but uneven, and in a few markets showing USD outperforms the local currency because it signals international availability.

Default, do not decide. That single rule prevents most geolocation-related revenue loss.