Skip to main content

Custom eCommerce: Configuring Multiple Regions

This article provides an overview of options to configure Creator Storefronts across multiple regions for custom eCommerce sites.

L
Written by Lauren McClurg
Updated over 6 months ago

Overview:

For international eCommerce brands that have multiple eCommerce regions, LoudCrowd offers several configurations to enable international sales. To determine the proper configuration for a brand, this guide outlines how LoudCrowd defines regions and provides guidance on how to build the best creator and consumer experience.

Step 1) Determine the number of eCommerce and Creator Regions

eCommerce Regions: Determine how many regions exist for your eCommerce store. LoudCrowd defines a region as a unique store that has its own products and prices. For example, if the US and Canada have unique products and prices, the US and Canada would both be regions.

Creator Regions: Determine how many regions for creators. All creators must be assigned to a program. And each program will be assigned to one region. For example, if all creators are US based, then one program that is assigned to the US is required.

If creators are based out of the US and Canada, and those exist as separate regions on your eCommerce store, two unique programs would be required to support those creators. One US Program for US creators and US products, and another Canadian program for Canadian creators and Canadian products.

Step 2) Choose the consumer experience

Many creators have audiences that span multiple regions. For instance, if you are creator from the US, you may have followers in Canada or elsewhere in the world. US Creators will build their storefronts on the US site with US products, so we need to decide on how we manage their traffic from other regions (like Canada).

Option A: If a US creator shares their storefront link, and a Canadian clicks on that link, most websites will automatically redirect the user to the Canadian site (typically the home page). For eCommerce sites with this functionality enabled, this will automatically happen for the creator storefront.

Option B: For brands that wish to allow users to browse the storefront before being redirected, it is possible to configure the storefront page to ignore system redirects and allow consumers outside of a region to browse the page.

How to implement:

This can be configured using a simple URL parameter on the storefront page and updating redirect logic on the backend:

Similarly, server configurations or redirect scripts can be modified to allow the storefront page URL to ignore system redirects.

When de-activating the redirect before to the storefront, most eCommerce configurations will then automatically redirect the consumer after they click on a product page.

For sites that automatically redirect “out of region” consumers to the homepage, the consumer will then be redirected to the home page of their local region.

For brands that have more advanced site routing (PDP to PDP), this is the preferred configuration. Then, when a consumer clicks on a PDP link from the storefront, they will be redirected by the site to the product page on their local region (if it exists).

Note: while it is possible to have creators build storefronts in multiple regions, we do not recommend adding that level of complexity to the creator’s workflow.

Language Tracking

For brands that want to translate a storefront from a creator’s language to the consumer’s local language, there are options to configure translation on the page.

This configuration is rarely used, since it does not actually redirect users from a region, it just translates the content on that region. The most common implementations of this are for French-Canadian implementations with legal French legal requirements, and Spanish consumers living in the US.

If required, LoudCrowd’s storefronts can independently handle translations of the product title, the product options, as well as link to a language specific PDP url based on the location of the buyer’s browser.

To enable this, the brand must send additional language variants in the product file, as documented here: Product File documentation

Did this answer your question?