If you sell across multiple countries and languages but don't connect through Shopify, you can still manage every market in one Marpipe account. A location feed is an additional source that carries region- and language-specific values for products you've already uploaded.
A location feed does not add products to your account. Like any additional source, it matches against products that already exist in your primary source and adds new values to them. Rows that don't match an existing product are dropped. Use it to layer region and language data onto your catalog — not to bring in new SKUs.
Before You Start
You'll need:
A primary source feed already uploaded to Marpipe
Your regions and languages activated in account settings (covered below — do this first)
A file or feed URL containing your region- and/or language-specific values
A key column in that file that also exists in your primary source —
idis strongly recommended
Region and Language Are Two Separate Dimensions
Every column you import is tagged with a region, a language, or both.
Region covers values that change by country: price, sale price, currency, product links, availability
Language covers translated content: title, description
Both covers values specific to one language in one country — a French-language product URL for Canada, for example
Keeping them separate means you can mix and match later. One set of imported data supports Canada / English, Canada / French, and France / French without importing anything three times.
Step 1: Activate Your Regions and Languages
Before you can tag any imported column with a region or language, you have to turn those markets on for your account. Only activated markets appear as options during the import.
Go to your account settings
Scroll down to the Account Markets section
Open Regions and activate every country you sell in
Open Languages and activate every language you publish in
You'll also see these same controls in your source feed settings modal when you first upload a feed. It's the same setting in both places — activate your markets wherever you happen to be, and account settings is where you go to change them later.
Marpipe supports the full list of regions and languages, so you're picking a handful out of a long list. Activate only what you actually need — a shorter list keeps the mapping step easy to work through.
Set Your Primary Region and Language
Underneath the two lists are Primary Region and Primary Language dropdowns. These are important, and easy to skip.
Your primary source feed already contains one region's and one language's worth of data — whatever locale you built it in. These dropdowns tell Marpipe which one that is. Setting them correctly means your default field values are understood as belonging to that specific market, so the default version maps to the right feed data everywhere downstream.
Set your primary region and language before importing a location feed. If your source feed is in British English and your primary region is left on something else, your default values get treated as belonging to the wrong market, and your output feeds will map the wrong data into standard field names.
Step 2: Preparing Your Location Feed
Your file needs a key column plus one column per localized value. Name columns so the locale is obvious — Marpipe uses the column name to suggest mappings.
id | price_fr | title_fr | price_de | title_de |
1234 | 24.99 EUR | Tapis Rayé | 24.99 EUR | Gestreifter Teppich |
5678 | 14.99 EUR | Couverture Douce | 14.99 EUR | Flauschige Decke |
Both layouts work:
One file covering all locales — a column per field per locale, as above
One file per locale — import each as its own location feed
Column headers follow the same formatting rules as any data field: all lowercase, no spaces, and only dashes, dots, or underscores.
Migrating from separate accounts? The fastest route is to copy the output feed URL from each of your locale accounts and paste it into the additional source uploader in your main account. No file export needed.
Step 3: Importing Your Location Feed
Go to Data Sources in the left nav and click New Data Source
Name the source and either paste your feed URL or upload a CSV
Turn on the This is a location feed toggle
Both one-time uploads and scheduled fetches are supported, the same as any additional source.
Set Your Key
Choose the column in your file to use as the key, then choose the field in your primary source to match it against. Any field from your primary source can be used as a key, but id is the recommendation — it's unique per product, so every row lands on exactly one item. Broader keys like item_group_id apply the same value to every variant in the group, which is rarely what you want for pricing.
Rows with no matching key are dropped.
Map Your Columns
With the location feed toggle on, the mapping step adds two columns: Region and Language.
For each column in your file, set:
The internal field it maps to —
price_frmaps onto your existingpricefieldThe region and/or language it applies to
Marpipe auto-suggests all three from the column name and the field type, so a column named price_fr is proposed as a region variant of price for France. Review every suggestion and override anything that's wrong. Columns with no match show an empty dropdown and need a selection before you can import.
Mapping to a field that doesn't exist yet creates a new parent field automatically, and it inherits the variant's values.
An availability column is optional. If you don't map one, products are treated as available in that locale.
Resolve Conflicts
If a field already has a variant for the same region and language you're importing — a second France variant of price, for example — that row is flagged as a conflict. The footer shows how many conflicts are unresolved, and the import is blocked until they're cleared.
Resolve a conflict by removing the existing variant or changing the region/language on the new row.
After Importing
Viewing Your Variants
Imported variants show up exactly like Shopify market variants. Any field with variations displays an icon on the Manage Fields and Data Sources pages. Expand the field to see each one, labeled with its dimension and value.
Editing Values
Each variation is edited separately, and field modifications do not cascade. Editing your default price field won't change price_fr. Update each variation directly if you want the same change applied everywhere.
Designing and Output Feeds
From here, everything works identically to the Shopify path — the variants are stored the same way regardless of where they came from. See Multiple Markets in the Same Marpipe Account for the full walkthrough.
The short version:
The ad builder has separate region and language selectors, and dynamic fields switch to the matching variation automatically
Output feeds let you set a region and language at creation, and the correct variants are auto-mapped into standard output field names — so a France / French feed exports
price_fraspriceDesigns added to an output feed inherit that feed's region and language
Tips
Missing variations fall back to defaults. If a product has a French price but no French title, the French feed exports the French price with the default title. Your feeds stay complete even when localization is partial.
Region doesn't filter your products. Every product in your primary source appears in every regional feed, whether or not you imported values for it. If you need a regional feed limited to a subset of products, use feed filters.
Watch for partial coverage. Because of the fallback behavior, a product with a French title but no French price will export with your default currency. Spot-check your localized feeds after the first import.
Missing a region or language in the mapping dropdown? It isn't activated yet. Go back to Account Markets in your settings, turn it on, and return to the import.
Use
idas your key unless you have a specific reason not to.Name your columns for the locale. Good column names mean Marpipe auto-suggests nearly every mapping and you just confirm.