Launching a Multilingual, Multi-Currency Classifieds Platform: What We Learned Building Livben

livben — Tue, 06 Jan 2026 00:44:58 +0000

We recently launched Livben, a classifieds and promotion platform where individuals and businesses can publish product/service listings and connect directly with potential buyers.

Because our audience is international, two requirements shaped almost every product and engineering decision:

1) Multilingual discovery (people should browse comfortably in their language)

2) Multi-currency clarity (people should understand prices without confusion)

This post is a practical “here’s what worked / what surprised us” overview—especially useful if you’re building a marketplace, directory, or listings-style product.

1) Language: UI language vs. listing language

One of the earliest product questions was: what exactly are we translating?

UI language (menus, buttons, filters, account screens)
Listing content (title, description, specs, location fields)

Treat these as separate layers. Users may prefer an English UI but want listings in Japanese (or vice versa). We found that separating the two prevents a lot of edge-case confusion.

Tip: store a listing’s “original language” as metadata. It helps with:

showing “original vs. translated” content
debugging mismatched translations
improving SEO decisions later

2) Translation workflow: don’t assume “auto-translate” is enough

Automatic translation is great for coverage, but it is not the same as “ready for conversion.”

What helped us:

keeping manual edits possible (so sellers can correct key terms)
labeling content clearly (e.g., “auto-translated” vs “edited”)
ensuring the original text is always available

If your platform includes regulated or safety-critical categories, this becomes even more important.

3) Currency: store a source of truth and be transparent in display

Currency logic becomes surprisingly tricky once you go global.

A pattern that kept us sane:

store the listing price as a single source of truth (amount + currency)
if you display conversions, treat them as display-only
be consistent with rounding rules (and document them internally)

Avoid: silently converting and overwriting the original price. Users need confidence that what they entered is what’s shown.

4) “Discovery” is a product problem, not just a search bar

Classifieds succeed when users can quickly answer:

“Is this relevant to me?”
“Can I trust it?”
“Can I contact someone fast?”

We focused on:

clear category structure
listing detail pages that surface essential info first
predictable filtering and sorting behavior
a frictionless path to contact (without hiding everything behind walls)

5) Trust & safety: set expectations early

If you’re not a payment/shipping intermediary, say it clearly and consistently.

It’s important to communicate:

how buyer–seller communication happens
what the platform does and does not do
basic safety guidance (e.g., verification, meeting safely, avoiding scams)

This reduces support load and improves user trust.

6) Launch content: write for humans first

For a launch post, resist the temptation to cram keywords everywhere. Editors and readers can spot keyword stuffing instantly.

What worked better:

a simple explanation of the problem we solve
a short “how it works”
a few specific examples of who benefits (SMEs, exporters, service providers)

Questions for you

If you’ve built a global product before:

How do you handle currency rounding and “price perception” across markets?
Do you keep original + translated content in the same record, or separate it?
Any i18n/SEO gotchas you wish you’d known earlier?

Happy to answer questions in the comments.

Forem: livben