Multiple Markets in the Same Marpipe Account

If you sell across multiple countries and languages from a single Shopify store, Multi Markets lets you manage all of it in one Marpipe account. You can import region- and language-specific product data, build designs that automatically use the right variations, and output a dedicated feed for each region and language combination.

Region and language are handled as two independent dimensions. You choose them separately when designing and when creating an output feed — so you can mix and match, like United States / English and United States / Spanish, or Germany / German and Germany / English.

This article covers the three parts of the workflow: importing your market data, designing with it, and outputting region- and language-specific feeds.

You'll need:

Note: Product data that varies by region or language in Shopify (like localized pricing or translated titles) is what Marpipe imports as variations. Fields that don't vary by market in Shopify — such as images — are shared across all regions and languages.

Marpipe will pull in the region- and language-specific variations for each field that has them in Shopify.

After resyncing, any field that has region or language variations shows an icon next to it on the Manage Fields page and the Data Sources page.

Click to expand a field and see all of its individual variations — for example, price might expand to show price, price_fr, price_de, and so on.

Each region and language variation is edited separately. Field modifications do not cascade across variations.

Important: If you edit the default price field, that change applies only to the default — it won't carry over to price_fr or any other variation. Update each variation directly if you want the same change applied everywhere.

The ad builder has two separate selectors: one for region and one for language.

When you select a region and language in a design, any dynamic fields used in that design automatically switch to the matching region and language variations.

For example, if you select France, a price field in your design automatically pulls from price_fr.

If a field doesn't have a variation for the selected region or language, it falls back to that field's default value. So if a product has a French price but no French title, the design will show the French price alongside the default title.

This means you can build a design once and preview how it renders across different regions and languages using the two selectors.

When you create a new output feed, you can select a region and a language for the feed. All product data in that feed uses the selected region and language.

Any designs you add to the feed automatically switch to the feed's region and language selection — you don't need to set it on each design individually.

On the Manage Fields page for the output feed, you'll see that the correct field variations are mapped to the relevant output field names. For example, a France / French feed maps price_fr into the standard price output field, so the feed exports clean, standard field names with the right localized values.

These feeds are built to be uploaded as the primary feed for a standalone catalog that represents a specific region and language. Each catalog gets its own dedicated feed.

Note: These are not override feeds. If you want to run all your regions and languages from a single catalog using override feeds, that's a separate workflow — we'll cover it in its own article once it's released.