MarketplaceHub Docs Docs

Category feed

Optional file describing your own category tree, so rules and defaults can hang off folders.

Optional. Supply this only if you want your own category tree mirrored into MarketplaceHub — it is not what a marketplace files your listing under. See Categories and mapping for why the two are different.

Two optional files describe your own folders: a category feed listing each folder and its parent, and a product-category feed pairing SKUs with folder ids for catalogs that keep that relationship in a separate table CATEGORY FEED — THE FOLDERS THEMSELVES IDNAMEPARENT ID 10Wall art— 11Posters10 12Prints10 Becomes your tree Wall art Posters Prints Why bother Rules and defaults hang off a folder, and everything inside inherits them. Optional — imports can build it. PRODUCT-CATEGORY FEED — WHICH PRODUCT SITS WHERE SKUCATEGORY ID MUG-0111 MUG-0212 For catalogs that keep the relationship separately If your product feed already carries a category column you do not need this file. It exists for systems that hold products and their filing in two different tables.
The category feed builds the tree; the product-category feed files products into it.

Download the sample.

Format

ColumnRequiredNotes
category-idYesYour identifier for the category. Referenced by the product-category feed.
parent-idNoThe parent's category-id. Empty for a top-level category.
nameYesDisplay name.

Example

category-id,parent-id,name
1,,All clothes
2,1,Sweaters
3,1,Dresses

Nesting is expressed purely through parent-id, so depth is unlimited and order in the file does not matter.

Why bother

Category folders are where rules and defaults hang. A rule set on a folder applies to everything filed under it, which is the cheapest way to avoid repeating the same marketplace settings across thousands of products.