You can now send a different product title, description and image set to each sales channel from inside Shopify admin, without cloning the product. Open the channel in your admin, find its product data settings, and map each field either to the default product field or to an override you control — a metafield, usually. That's the whole answer to how to map product data per sales channel in Shopify. The storefront keeps your brand copy. Noon, Amazon.ae and your Meta catalogue get the keyword-heavy bilingual version they actually rank on. One product record, several faces.
Shopify shipped the per-channel mapping page at the end of October 2025. For GCC brands this matters more than it does almost anywhere else, because the gap between what converts on a Dubai D2C storefront and what gets found on Noon search is wider here than in most markets. Arabic, English, transliterated Arabic, brand names spelled four ways — the marketplace shopper types all of it. Your homepage copy does not.
The duplicate catalogue everyone built, and why it was quietly expensive
Before this, if you wanted "Nourishing Argan Hair Oil" on your own site and "زيت الأرجان للشعر Argan Oil Hair Treatment 100ml Moroccan Organic" on the marketplace feed, you had two options. Either you let the marketplace title leak onto your storefront and lived with a product page that reads like a parts catalogue, or you created a second product record, hid it from the Online Store channel, and published only that one to the feed.
Almost everyone picked the second. And then paid for it in three places.
Inventory is the first. Two product records means two sets of variants, which means either you split stock between them or you wire up an inventory sync and pray. We have cleaned up more than one White Friday oversell that traced back to exactly this: 60 units of a bestseller, 30 allocated to the "feed" duplicate, the marketplace sold 30 in an afternoon, and the storefront carried on taking orders against stock that had already shipped out of the Dubai warehouse.
The second is reporting. Every sales report, every ABC analysis, every "what should we reorder" query now has the same product sitting in two rows under two names. Someone has to remember to add them together. Someone eventually forgets.
The third is maintenance drag. Ramadan pricing, Eid bundles, DSF discounts — each one is a double edit. Bulk editor makes it survivable, but the error rate is not zero, and the errors show up on the channel you look at least.
How to map product data per sales channel, step by step
- Decide which fields genuinely need to differ. For most GCC catalogues it's three: title, description, and the image order. Everything else can inherit.
- Create the override fields first. A product metafield per channel-variant of the field — for example custom.marketplace_title and custom.marketplace_description_ar. Use metafield definitions so they appear cleanly in the product editor and in bulk edit.
- Populate them. Matrixify or the bulk editor for a back catalogue; make it part of the product-creation checklist going forward.
- Go to the sales channel in admin, open its product data settings, and point each field at the metafield rather than the default.
- Preview before you publish. More on that below, because this is the step people skip.
Two honest caveats. Not every channel exposes every field for mapping, and the set differs between a first-party channel like Facebook & Instagram and a third-party app channel. Check what your specific channel offers before you write a hundred metafield values you can't use. And the feature has been rolling out, so if you don't see it yet, it is coming rather than missing.
Marketplace titles and brand titles are written to different rules
A storefront title is read by a person who already clicked. It can be short, it can be confident, it can assume context from the collection page and the brand. "Argan Hair Oil" is fine when the logo is at the top of the page and the collection is called Hair Care.
A marketplace title is read by a search engine first and a person second, inside a grid of forty competing tiles. It needs the brand, the product type, the key attribute, the size, and — this is the part GCC brands underuse — the Arabic term shoppers actually type. Noon and Amazon.ae shoppers in the UAE and Saudi search in a mix of English, Arabic script, and Arabic words typed in Latin letters. All three happen. A feed title that only carries one of them is invisible to the other two.
A workable pattern for the override field: Brand + English product type + key attribute + size | Arabic product type + Arabic attribute. Keep the brand at the front, because truncation eats the end of the string and you want the brand to survive it.
Resist the urge to stuff until the field screams. There is a point where additional keywords stop helping rank and start hurting click-through, and on a crowded grid the tile that reads like a human wrote it wins the tap. We usually land around 90 to 130 characters for the marketplace override and leave the storefront title under 50.
Arabic product titles and bilingual data for GCC channels
Your storefront probably handles Arabic through Shopify's translation layer, with an RTL-aware theme and locale-specific URLs. That's a separate system from channel mapping, and it should stay separate. Translations serve the Online Store. Mapping serves the feed.
Where they intersect is the source text. If you already have professionally written Arabic product copy for the storefront, don't re-translate for the feed — but don't copy it across verbatim either. Storefront Arabic is marketing prose. Feed Arabic is search terms. The Arabic word a copywriter chooses for "moisturiser" and the Arabic word a Riyadh shopper types into Noon are often not the same word, and the dialect register matters. Have whoever writes your Arabic look at the actual search suggestions on Noon and Amazon.ae before they fill the metafield. It takes an afternoon and it is the single highest-return hour in this whole exercise.
One practical trap: Arabic text pasted into a CSV from a Windows machine picks up direction marks and non-breaking characters that marketplace validators reject. If an import silently drops twenty rows, that's usually why. Export, open in a plain text editor, look for the invisible stuff.
Overriding product images by channel
Marketplaces want a pure white background on the first image, the product filling most of the frame, no text, no badges, no lifestyle context. Meta wants the opposite: the first image is a thumbnail in a feed, competing with photos of people's friends, and a flat packshot on white loses to a hand holding the bottle in daylight.
Before mapping, you picked one and compromised on the other, or you uploaded a second set to the duplicate product. Now you can keep the brand image order on the storefront, map a white-background shot to position one for the marketplace feed, and map a lifestyle crop for the Meta catalogue. Store the alternates as a list-of-file-references metafield and point the channel at it.
Square crops matter more than people expect. If your product photography is shot 4:5 for the storefront, the marketplace square crop will chop the top and bottom of a tall bottle. Crop deliberately rather than letting the platform do it.
Meta catalog title mapping is a different job again
Meta is not a marketplace, so the keyword logic does not transfer. In an Advantage+ catalogue ad the title sits under the image in a small, truncated line. Long bilingual strings get cut mid-word and read as spam. What we map to the Facebook & Instagram channel is usually closer to the storefront title than to the Noon title — brand plus product, short, plus the price point doing the work in the price field where it belongs.
Where Meta mapping earns its keep is the description and the image. Catalogue descriptions feed dynamic creative, and a description written for a product page (three paragraphs on sourcing) performs worse than one line written as ad copy. Map it separately. Write it like an ad.
Use the preview, because the mapping is not the hard part
The mapping page has a preview that shows you the resolved values a channel will receive for a given product. Use it on five products before you touch the rest of the catalogue: your bestseller, your newest SKU, one with a long variant list, one with Arabic in the title, and one you suspect has incomplete data.
What the preview catches is empty overrides. If a product has no value in custom.marketplace_title, you will either get a blank or a fallback depending on how the channel handles it, and a blank title on a feed is a rejected listing. We get this wrong on roughly a third of first passes, usually on SKUs added during a campaign when nobody remembered the new field existed. Make the metafield required in your product checklist, and run a quick filtered view of products where the override is empty before every major push.
What mapping will not fix: price, VAT and the Riyadh problem
Do not try to solve pricing here. Channel mapping handles presentation; price belongs to Shopify Markets, and the UAE-to-Saudi gap is a tax question, not a copy question.
Work it through. A product listed at AED 199 inclusive of 5% UAE VAT is AED 189.52 net (199 ÷ 1.05). Sell the same item into Saudi Arabia at 15% VAT and the gross equivalent is 189.52 × 1.15 = AED 217.95. Both currencies are pegged to the dollar — AED at 3.6725, SAR at 3.75 — so the conversion is stable at 3.75 ÷ 3.6725 = 1.0211. That gives SAR 222.55, which you would round to SAR 225 for a clean shelf price. Not SAR 203, which is what you get if you convert AED 199 directly and forget the tax rate changed. That ten percent is your margin.
Same logic applies to fulfilment. Dubai and Riyadh are separate logistics problems with separate carriers, separate customs paperwork and separate COD economics, and a single delivery promise written into your product description will be wrong in one of them. Keep delivery claims out of mapped descriptions entirely and let the channel's own shipping settings carry it. If you are structuring a cross-GCC setup properly, our notes on running Shopify from Dubai and selling into Saudi Arabia go deeper on the market split.
Getting a Noon feed out of Shopify
Noon does not have a first-party Shopify sales channel the way Meta does. Most brands push to it through a feed or marketplace-integration app, or by exporting and uploading through Noon's seller tools. That means the per-channel mapping UI may not cover it directly, depending on how the app you use is built.
The metafield approach still works, and this is the real reason to build it that way rather than typing overrides into a channel-specific box. Your marketplace title and marketplace image live on the product as structured data. Any feed app that can read metafields can map them. Any export can include them. When Noon changes its title requirements — and it will — you edit one metafield definition and re-export, instead of re-running a translation project.
If your feed app can't read metafields, that's a reason to change the app, not a reason to change your data model. For catalogues where no off-the-shelf connector handles the attribute structure Noon expects, a small purpose-built private app that transforms your product data into the exact feed shape is usually a week of work and ends the problem permanently.
A sensible sequence if you're starting Monday
Define the metafields. Fill them for your top 50 SKUs by revenue, not the whole catalogue — that's where the marketplace traffic is anyway. Map one channel, preview, publish, watch for a week. Then unwind the duplicate products, which is the satisfying part: merge the stock back into one record, fix the reporting, and stop paying for the same SKU twice.
If you want a second pair of eyes on the feed structure before White Friday volumes hit, we'll look at your catalogue and channel setup in a free audit and tell you which fields are actually costing you listings.