Prepare your Shopify product data for marketplace integration
Written by Jesse Franken · Updated September 7, 2026
Reach more buyers with a Shopify catalog that is ready for the marketplace you choose. Before publishing the full assortment, check whether product identity, variants, category attributes and seller offer data survive the journey from Shopify to the destination.
Use the worked example below to decide which facts belong in Shopify, which need metafields, and which transformations belong in the feed or connector.
Choose the destination and identify the missing data
Start with one marketplace, one target country and a representative product family. Download or inspect its current category requirements and compare them with the fields your connector actually imports.
Shopify documents metafields and attribute mapping for Marketplace Connect. The same planning principle applies to a separate feed tool, but supported metafield types and export mappings depend on the connector. A metafield displayed by the theme is not proof that the connector exports it.
Check channel coverage before selecting the integration. Shopify’s Marketplace Connect documentation lists supported destinations; this example is a data-preparation workflow, not a claim that every marketplace uses that app.
For hands-on launch support, explore our marketplace setup service.
Worked example: Shopify fields to marketplace fields
Illustrative example: a cotton T-shirt has two colors and three sizes. Treat each sellable combination as a distinct variant and keep the product-family relationship. The field names below describe a proposed catalog setup, not a universal connector template.
Use the actual manufacturer brand and identifiers. Shopify vendor may hold a distributor or your own store name; confirm its meaning before mapping it to brand. Preserve leading zeros in GTINs and never substitute a SKU for a manufacturer identifier.
| Shopify source | Metafield or extra fact | Feed / transformation | Destination output |
|---|---|---|---|
| Variant barcode and SKU | Supplier GTIN for that exact variant | Preserve GTIN as text; keep a stable variant ID | Product identifier and seller SKU |
| Vendor = distributor | custom.brand = Northline, verified | Use the manufacturer brand field | Brand = Northline |
| Options: Color = Navy; Size = M | Sizing system = EU where applicable | Map option names and accepted values | Color, size and applicable size-system fields |
| Product ID and variant IDs | None if the relationships are reliable | Keep each variant distinct; group only genuine siblings | Variant identity and destination-specific family relationship |
| Product type = T-shirt | custom.material = 100% cotton, verified | Choose the marketplace category; map required attributes | Category, material and other category-required fields |
| Inventory at fulfilment locations | Allocation or buffer rule | Export stock the chosen operation can fulfil | Seller quantity / availability |
| Variant price = EUR 29.95 | Approved destination pricing policy | Apply currency/tax/price rules once | Offer price consistent with the intended market |
Run a test export before publishing the full catalog
Select one complete variant, a second size, a second color, one item with a missing required attribute and one zero-stock item. For each, compare the imported Shopify value with the final export or API preview. A correct admin screen is only the starting point.
Check the destination category first, then its required fields. For our T-shirt, confirm the supplier’s material fact, accepted color/size values and images for the selected color. Requirements vary by marketplace and category; use the current listing requirements for your destination.
For stock, identify the authoritative location or backend and the update route. For pricing, test the final currency, tax treatment and any channel adjustment. Check whether an old connector override could apply a second adjustment.
- Identity: each sellable size/color combination maps to the intended GTIN and stable seller SKU.
- Grouping: sibling variants remain together without combining different models or packs.
- Completeness: missing required attributes are visible in a review queue, rather than filled with guesses.
- Offer: stock and price match the approved destination policy, including the zero-stock case.
- Export: inspect the final values and included item count, then retain the test output for comparison.
Validate the listing and operational flow after launch
After the platform processes the test export, compare its received values and errors with the exported record. Open the product and select the tested variant. Verify its image, size, color, seller, price, availability and delivery promise. Check whether an existing catalog match attached the offer to the wrong product.
Use an approved test-order procedure where available to verify order import, stock updates and shipment feedback. Monitor the next scheduled source update as well: a launch is fragile if the second sync overwrites the correction.
Record who owns source facts, feed rules and destination exceptions. That gives your team a repeatable launch checklist for the next product family. ChannelBoosters connects product-data preparation, marketplace setup and order and stock sync so expansion remains manageable.
