b2c-localization

Localize B2C Commerce storefronts by managing templates and resource bundles.

51|16|Updated Oct 31, 2025
One-click install
npx skills add https://github.com/SalesforceCommerceCloud/b2c-developer-tooling --skill b2c-localization
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: b2c-localization
Source: https://github.com/SalesforceCommerceCloud/b2c-developer-tooling/tree/main/skills/b2c/skills/b2c-localization
Command: npx skills add https://github.com/SalesforceCommerceCloud/b2c-developer-tooling --skill b2c-localization

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill enables localization of B2C Commerce storefronts by managing templates, resource bundles, and locale-aware formatting for multiple languages and regions.

Core Features & Use Cases

  • Localizes templates and resource bundles to support multilingual storefronts.
  • Manages locale-specific content such as dates, currencies, and forms.
  • Real-world use: add French translations to account/checkout bundles and configure locale fallbacks.

Quick Start

Use the skill to add translations for target locales (e.g., en_US, fr_FR, de_DE) and verify the locale fallback chain fr_CA -> fr -> default.

Frequently Asked Questions about b2c-localization

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I localize B2C Commerce storefronts for multiple languages and regions?

Localize B2C Commerce storefronts by managing templates, resource bundles, and locale-aware formatting to support multiple languages. You configure locale folders for target regions like en_US, fr_FR, and de_DE, applying translations without requiring external dependencies.

How does locale fallback work with Resource.msg and properties files?

Locale fallback chains work by cascading resource lookups from specific to general locales, such as fr_CA resolving to fr before hitting the default bundle. Resource.msg queries standard properties files within locale folders to retrieve the first available translation.

Can I use this approach to add French translations to checkout and account bundles?

Yes, you can add French translations to account and checkout bundles by placing locale-specific properties files in the appropriate locale folders. The system applies these translations using Resource.msg to deliver multilingual storefront content.

Do I need external dependencies to format dates and currencies for different locales?

No external dependencies are needed for locale-aware date and currency formatting. The skill relies on standard B2C Commerce tooling and properties files to apply locale-specific formatting directly within your storefront templates.

What is the best way to manage multilingual content across B2C storefront templates?

The best way to manage multilingual content is using standard resource bundles and properties files mapped to specific locales. This approach separates template logic from translated strings, allowing efficient localization across all supported languages.

Why are my B2C Commerce translations not displaying correctly for the fr_CA locale?

Translations for fr_CA may not display correctly if the locale fallback chain to fr and the default bundle is misconfigured. Verify that your properties files exist in the correct locale folders and that Resource.msg is querying the proper resource bundles.