Designing Digital Platforms for Multiple Markets
Separate language, market routing, currency display and operational policy when planning a platform for more than one region.
Model language and market separately
A visitor reading English may be in several countries, while a South African business may need more than one language. Start by listing the markets you serve and the languages available in each. Those are separate choices: a browser language setting is not proof of the visitor’s country.
For example, a visitor may want to read in English while checking the contact details for another market. Changing the language should not silently change the market they selected. When they switch markets, keep them on an equivalent page only if one exists. If it does not, explain where the link leads and offer a useful landing page instead of implying that the same service or content is available there.
Keep commercial rules on the server
Currency display does not determine tax residence, contracting entity or fulfilment policy. Keep those commercial rules on the server. Preserve the currency of account—the currency in which the amount is recorded—and use timestamped, approved exchange rates only for display.
In a quote workflow, collect the customer’s declared country and review tax treatment separately. An English language choice or a displayed currency should not fill in that answer for them. If a display rate is missing, show the original amount and its currency with a clear explanation that conversion is unavailable. Do not substitute an invented converted price.
Plan the operating differences
For each market, check the contact route, support hours, delivery constraints and who maintains each translation. We would work through these alongside the page content: a translated form is of little use if nobody can handle the enquiry it produces. Identify who receives it and how changes to the original wording reach the person maintaining the translation.
Before release, follow a visitor’s route through a representative page, its language alternatives and its contact form. Test links, canonical URLs and reciprocal language alternatives, including what happens when an equivalent page is missing. Keep market-specific claims grounded in reviewed source material and the team’s actual ability to deliver.
Apply this to your brief
Bring your current workflow and one representative example, such as a service page and the enquiry it produces. Include the markets and languages you need, the currency in which you quote, and the decision you are trying to make. That gives us something concrete to work through together. Explore Willan’s consulting approach, review development services or discuss your project.
Planning guidance from Webvelopment Editorial. Confirm platform requirements and project assumptions before committing budget.
Keep the right things connected.
Technology and Digital Strategy Consulting
Work through technology decisions with Willan Theunissen: discovery, architecture reviews, marketing technology and digital capability planning.
Bespoke Development
Plan business software around the work people need to do: choose an application, eCommerce change, PHP update or integration, with a clear first release.
Digital Project Discovery & Technical Scoping Estimator
Offer paid discovery when requirements are too uncertain for fixed build pricing.
Start a conversation
Tell us what you are working towards. We’ll help you find a practical next step.