MarketplaceHub Docs Docs

Column mapping

Mapping your columns to system fields, which fields exist, and what happens to the columns you don't map.

Your columns rarely share names with the fields MarketplaceHub uses, so an import includes a mapping step. Matches are proposed for you to confirm or change — nothing is renamed in your file.

Mapping points each of your columns at a system field: only SKU and title must be mapped, unmapped columns are kept on the row rather than discarded, and changing a mapping later applies from the next run onwards Your columns item_sku product_name supplier_ref warehouse_bin System fields Sku — required Title — required Price, Quantity, Brand… Everything but SKU and Title is optional. Unmapped columns are kept, not discarded. They stay on the row and stay available — the AI can still read them when filling a marketplace attribute. Nothing you send is thrown away. Changing a mapping later applies from the next run It does not retrospectively rewrite rows already imported. If you need the existing rows to pick up the new mapping, re-run the import — rows are matched on SKU, so a re-run updates them rather than duplicating them.
Map two fields, keep the rest — nothing you send is thrown away.

The system fields

FieldRequiredNotes
SKUYesThe join key for the entire system.
TitleNo*Not enforced at import, but no marketplace will accept a listing without one.
DescriptionNo
PriceNo
QuantityNo
CostNoUnit cost. Used only as the margin floor when automated repricing is on.
BarcodeNoUPC, EAN or ISBN. Type is inferred from the value.
CategoryNoYour own category, not the marketplace's.
Main imageNoPrimary gallery image, as a URL.
Image 1–24NoAdditional gallery slots, as URLs.

What happens to your other columns

They are not discarded. Unmapped columns are carried through with the product and offered to the AI when it fills in whatever the destination marketplace's product type requires — so a wide export helps rather than hinders.

This is why the mapping step is short even for a 90-column feed: you are mapping the handful of fields MarketplaceHub itself needs, not every field the marketplace will eventually want. Those are filled by classification and review.

Changing a mapping later

Mapping belongs to the import, not to one upload, so it applies on every subsequent run. Changing a step invalidates the steps after it, which are then re-run — the alternative would be a configuration whose later stages silently describe data that no longer exists.