Product feed
The main feed: one row per product. Which fields MarketplaceHub requires, how images and variants are expressed, and where the marketplace's own required fields come from.
The product feed is the only one you must have. One row per product, with whatever columns your system already exports — you map them to system fields during import rather than renaming anything.
Download the sample product feed — 43 columns of a clothing catalog, showing a parent product and its variants.
What MarketplaceHub actually needs
Only one column is genuinely required:
| System field | Required | Notes |
|---|---|---|
| SKU | Yes | The join key for everything. Must be unique per product and stable between runs — a changed SKU reads as a new product. |
| Title | Practically | Every marketplace requires a title. Publishing fails without one. |
| Description | No | |
| Price | No | Can come from this feed or from a separate price and stock feed. |
| Quantity | No | As above. |
| Cost | No | Unit cost. Only used as the margin floor for automated repricing. |
| Barcode | No | UPC, EAN or ISBN. The type is inferred from the value, so there is no separate type column to map. Worth supplying — Amazon and eBay both rank and gate on identifiers. |
| Category | No | Your own category, not the marketplace's. |
| Main image + up to 24 more | No | URLs. See below. |
Everything else in your file is carried through as an attribute and offered to the AI when it fills in marketplace-required fields, so a wide export is useful rather than a problem.
Marketplace-required fields are a separate matter
The list above is what MarketplaceHub needs. What the marketplace needs depends entirely on the product type you list under, and is often far longer. Look it up in the field reference before building a feed for a specific channel.
Images
Images are URLs, not uploads. MarketplaceHub fetches and stores each one at publish time, so the URL must be publicly reachable at that moment.
There are 25 image slots: a main image and 24 gallery slots, matching the maximum the marketplaces accept. If your extra images live one-per-row in a second file, link that file and map the column once — the values spill across the gallery slots in order rather than needing 24 mapped columns. See Linking several files.
Variants
Parent/child products use three columns, as the sample shows:
parent-sku— empty on the parent row, the parent's SKU on each child.parentage—ParentorChild.relationship-type— the variation relationship.
The parent row is the listing; the child rows are the buyable options. Both need their own SKU.
Scheduling
A feed can be uploaded once or re-fetched on a schedule you choose. There is no fixed cadence — how often it runs is a property of the import you configure, and the source it re-reads is remembered, so subsequent runs are a fetch rather than an upload. See Where data comes from.