Localization preferences
Show how buyers and sellers could browse listings, notices, regional formats, pickup details, and support cues in language and region settings that match their market.
Language Preferences
- Account settings should let buyers choose marketplace language, fallback language, region, currency display, and measurement style.
- Seller tools should show which listing fields are written by the seller and which fields are presented as translated copy for buyers.
- Language choices should follow the customer across search, listing detail, checkout review, pickup scheduling, messages, and support routes.
Listing Translations
- Item title, condition notes, included accessories, flaw descriptions, pickup notes, and return terms need clear translated versions.
- Category-specific proof words should stay precise for graded cards, GPUs, sneakers, retro games, art, books, automotive parts, garden tools, and home goods.
- High-value listings should show a seller-written source note when translated wording could affect condition, fit, grading, or authenticity.
Regional Formats
- Prices, duties, taxes, dates, times, distances, weight, dimensions, and pickup windows should display in the buyer's selected region format.
- Auction close times need clear timezone labels so buyers understand when bids, top bids, and payment review close.
- International carts should keep item price, shipping, duty estimate, tax estimate, insurance, and refund exposure readable in one view.
Customer Notices
- Checkout review, support cases, pickup release, return eligibility, restricted categories, and duty responsibility need approved translated notices.
- Urgent notices should remain short and action-first: bid closed, pickup ready, seller response needed, proof needed, return window, or support decision.
- Notification preferences should define which translated notices can be sent, delayed, muted, or escalated as urgent.
Messages and Support
- Buyer and seller messages should separate translated display text from the original message so support can review the source when needed.
- Support cases should show customer language, seller language, route context, evidence language, and whether a human review is required.
- Reports involving condition, authenticity, restricted items, payment, or pickup release should preserve original wording with the case record.
Policy Review
- Buyer protection, seller standards, returns, prohibited items, fees, privacy, and terms should have approved translated versions before launch.
- Policy changes need version history, language owner, approval date, affected routes, and customer-visible change summary.
- Unsupported language or region choices should fall back to a clear customer notice instead of hiding key terms.
Accessibility
- Translated labels must preserve form names, button meaning, error text, focus order, live updates, and screen-reader clarity.
- Long words, different date formats, and multi-line notices should not break mobile cards, search filters, checkout review, or item proof sections.
- Language switching should never move a buyer away from the item, cart review, support case, pickup window, or seller task they were reviewing.
Owner Approval
- Owners should approve launch languages, fallback rules, supported regions, policy versions, support escalation, and region-specific checkout wording.
- Route checks should confirm translated pages keep current demo state, future platform state, noindex safety, and customer-facing labels intact.
- Rollback should remove unsupported language choices from new sessions while preserving existing order, message, and support history.
Account Preferences
Saved language, region, privacy, notification, handoff, and seller visibility choices.
International Shipping
Country eligibility, customs detail, duties, restricted categories, return paths, and notices.
Notification Preferences
Translated alerts, quiet hours, urgent notices, consent records, and delivery review.
Communications
Buyer alerts, seller messages, support notices, templates, and delivery review.
Message Safety
Original message retention, translated display text, reports, blocks, and privacy rules.
Language Quality
Customer copy, claim safety, route labels, policy clarity, guard coverage, and release checks.
Terms & Consent
Buyer acknowledgements, seller terms, auction rules, notices, version history, and approval.
Mobile Quality
Touch targets, focus, live updates, responsive cards, reduced motion, and translated labels.
Current demo state
Localization is represented as a guided preferences route.
The demo shows language preferences, translated listing fields, regional formats, customer notices, message boundaries, policy review, accessibility, and owner approval without storing account settings.
Future platform state
Launch needs account-linked localization services.
Launch needs verified language storage, translated policy versions, regional price formatting, message source retention, support review tools, notification delivery, and owner-approved fallback rules.