Mapping to Core Fields (manufacturer)
The Manage Core Fields page is where you map your relevant CSV spreadsheet fields to our Core Fields before you activate your spreadsheet on the Manage Data page. All uploaded CSVs regardless if they are going to be a Master or Append CSVs need applicable fields mapped to our Core Fields. For example, map your product name field (regardless of what you name your field) to our "Model Name" field. Select "Not Applicable" if you don't have a specific Core field in your spreadsheet. Any fields not mapped to a Core Field are created as custom fields and show up in your Data page Gallery View. Watch a video of a user mapping to Core Fields at the bottom of this help article.
How do I map my fields to Shotfarm Core Fields?
You have two tasks, tell us which rows contain information, then map your fields to our Core Fields. Read below.
What is the Row Location and Assignment section?
This feature allows you to have flexibility on where information is located on your data CSV. Simply tell us which unique rows contain Field Names, Descriptions, and Data Start. For example, your CSV could have the Field Descriptions in Row 6, the Field Names in Row 7, and the Data rows start on Row 10. In this example, we'll ignore information on all other rows above the Data Start row except for Rows 6 and 7. Any information in your CSV below your Data Start row will be treated as product data.
How do I map my fields to Shotfarm Core Fields?
This should be straightforward, especially if you use our template. If your fields (the column header row in your spreadsheet) are named the same as the Shotfarm Core Fields they will auto-match and you'll only need to review and click the checkmark in the center of the page between your field name and our field name. If they don't match up, then you search for your field in the Field Name dropdown menu and select the appropriate field. If you don't have an appropriate field then select "Not Applicable" and confirm by clicking the checkmark. All fields need to be mapped, or select "not applicable" so that you reach 100 percent mapped fields.
What Core Fields should I always map to?
You should always map to Brand, Model Name, Model Number, or Keywords (ex. logos and lifestyle images) so your colleagues and partners can search for and identify assets or products.
What fields are required?
You are required to map to the Main Product Category field or we'll default to "General" as your main product category. We strongly suggest you map to Brand, Model Name, and Model Number as they are basic fields used to search for and identify products and assets across Shotfarm. Colleagues and partners will not be able to find or ID your products without this basic information. You can also use keywords to identify non-product assets such as logos, ads, or lifestyle images. Remember to select "Not Applicable" for all fields that you do not have data to map to so that you reach 100 percent mapping.
Are product categories required?
If you are creating custom fields then you must have at least one product category as your custom fields map to the lowest level of your product categorization (aka product hierarchy). However, if you don't map and upload to the Main Product Category field then we default to "General" as your main category. You can add as many product subcategories as you need. If you label your columns product subcategory (01), product subcategory (02), they will auto-match with our Core category fields during the mapping process. Mark the last one as "Not Applicable" if you are done mapping to subcategories.
What is the difference between Main File Name and Additional File Name?
If you only have one image for a product then you must map to the Main File Name field. The main file is the one that shows up on your Assets page Gallery View as the first image. Additional File Name (01), Additional File Name (02) only show in the Product Detail View. They are considered alternate images such as side, back, or top views of the product. You can map to as many Additional File Names as you have files.
What is a Unique ID and why should I map to this field?
What field does your company use to uniquely identify your products? Often it is a UPC, but we allow you to map to the Unique ID field or mark a Core field such as UPC as your UID. If you are going to add to, or edit existing product information through Append CSVs you must have a unique ID identified when you Map Core Fields for your Master CSV. Your Master CSV sets the UID from that point on. Make sure the Append CSVs you upload always have the same column with the corresponding Unique ID if you want to add to or edit existing data. The Unique ID is the 'key' that matches the updated content to the existing product data in your Shotfarm account. If you mix up the Unique ID the content will get mixed up. Your Master CSV sets the UID for your account.
Is a Unique ID required?
No, it is only used if you want to add to, or edit, existing product data. If you only upload complete rows of data then you don't need to worry about mapping to, or selecting your Unique ID (UID).
How do I mark what field is my company's Unique ID (UID)?
There are two ways to mark what is your UID. 1) map specifically to the Unique ID Core Field, or 2) use the checkmark on the right side of the Core Fields to mark which one if your Unique ID (UID). For example, if you map your UPC to the Shotfarm GTIN-12 (UPC-A) field and want that to also be your Unique ID click the checkmark on the right side of the column. Your Master CSV sets the UID for your account.
When I map to LightBox (01), LightBox (02) shows up. Why?
LightBoxes are repeatable fields, you can add as many as you like. Mark the last one as "Not Applicable" if you are done mapping to LightBoxes.
Do I map my custom fields?
No, you only have to map to the Shotfarm Core Fields. Any field in your Master CSV not mapped to Core Fields will become a custom field and any field in your Append CSVs not mapped to a Core Field and "Included" in your field set will become a custom field.
Watch a user upload a Master CSV and map to Core Fields: