Summary
Your Product Catalog file is one row per SKU, and each row is one of four types: an item, an alias, a kit, or an assembly. This article covers the format for each, so you can build a file that matches how you actually sell.
How your catalog file is structured
Your catalog is one row per SKU. Only the sku column is required, everything else is optional, and column names aren't case sensitive. Leave out the type column and every row is treated as an item.
The four row types
Items
A standalone product you sell. This is the default type - if you don't include a type column, every row is treated as an item. Only sku is required.
type | sku | name |
item | BB-CHK-340 | Chicken Bone Broth Concentrate 340g |
Aliases
An alternate SKU pointing at a master item - useful when the same product ships under a different code per sales channel. Set refers_to to the canonical SKU, and the alias will automatically inherit its cost from the master item.
type | sku | name | refers_to |
alias | BB340C-AMZ | Chicken Broth (Amazon SKU) | BB-CHK-340 |
Kits
Multiple member SKUs sold together as one SKU. Leave cost blank - it's calculated automatically from the cost of the member items. List members in refers_to as SKU*qty; SKU*qty.
type | sku | name | refers_to |
kit | BB-GIFT-PACK | Wellness Gift Pack | BB-CHK-340*1; BB-OIL-500-VAN*1 |
Assemblies
Like a kit - multiple member SKUs sold as one - but you set the cost yourself rather than it rolling up from the members.
type | sku | name | refers_to | cost |
assembly | BB-SAMPLER-4PK | Bone Broth Sampler 4-pack | BB-CHK-340*2; BB-BEEF-340*2 | 32.00 |
Matching SKUs exactly
Your SKU or alias must exactly match the SKU as it appears in your Amazon, Shopify, Walmart, or eBay settlements. Small formatting differences - an extra space, a different case, a missing dash - will stop a cost from matching.
đĄ A note on special characters: if a SKU containing a backslash isn't matching correctly, set it up as an alias pointing to a cleaned-up version of the SKU as a workaround.
Troubleshooting
A cost isn't applying to one product: the SKU in your file doesn't exactly match the SKU in your settlement. Compare the two, correct your file, re-upload, and refresh your settlements.
A SKU containing a backslash isn't matching: set it up as an alias pointing to a cleaned-up version of the SKU. The alias inherits the cost from the master item, so the cost still applies.
A kit is showing no cost: one or more of its member SKUs is missing a cost. A kit's cost is calculated from its members, so every member needs one.
A row was skipped on upload: check that refers_to points at a SKU that exists in the same file, and that quantities use the SKU*quantity format.
If a SKU still won't match after that, our support team is happy to take a look with you.