Basic Guide to Bulk Upload
This guide equips you with the knowledge to efficiently upload your product data into the NoChannel Commerce Product Information Management (PIM) system.
Upon logging in, navigate to the side menu of the NoChannel Commerce Portal, go to PIM, and click on Bulk Upload. By leveraging the bulk upload functionality, you can streamline product data entry, saving significant time and resources compared to manual data entry.
In the Bulk Upload section, Download the necessary templates, such as product and variant templates, to facilitate uploading product data using a single template file. Ensure to download the correct templates tailored to your data requirements.
In the PIM system, there are six different templates to upload and populate your product data:
- Attribute: Define and upload your product characteristics such as size, color, and material.
- Attribute Group: Organize and upload your related attributes into groups for better manageability, e.g. (Product Specifications).
- Product Template: Specifies the structure for your product information, detailing which attributes are required for each product.
- Products: Create and upload your Product information, including names, descriptions, and categories.
- Variants: Facilitates the upload of product variants, detailing variations such as product sizes or colors.
- Products & Variants: Combines product and variant information in a single upload file, streamlining and managing multiple product variations.
NOTE: Start by downloading the Attribute, Attribute Group, and Product Template templates. These templates form the foundation for your product data. Once downloaded, fill them with your product information and upload them back into the PIM system. Then, you can proceed with downloading and creating Products and Variants.
Once the templates are downloaded to your system, open the template files in Excel. Fill in all the necessary details, including, product template ID, tags, states and other relevant fields.
While filling out your bulk upload templates, you must add the following information and fields in the templates.
NOTE: Within the templates, fields marked with an asterisk (*) are Mandatory, while others are Optional.
- *id: This is a unique identifier for the attribute. It distinguishes each attribute from others.
- *name: This is the internal name of the attribute. It is used within the system to reference the attribute.
- adminDisplayName_en_US: This is the attribute's name as displayed in the admin interface for English (US) users.
- displayGroup: This specifies the group in which the attribute is displayed. It helps organize attributes into logical groups, making it easier to manage them.
- inputType: This defines the type of input for the attribute (e.g., text, dropdown, checkbox). Choose the input type based on how you want users to provide the attribute value.
- helperText_en_US: This is the help text displayed in the admin interface for English (US) users. It provides additional information or instructions about the attribute to help administrators.
- *description_en_US: This describes the attribute in English (US). It explains what the attribute is used for and any important details about it.
- *multiValued: This indicates if the attribute can have multiple values (true or false). Set it to true if you want users to be able to select various options or provide multiple entries.
- priority: This determines the order in which the attribute appears on the PIM system. Attributes with lower priority numbers appear before those with higher numbers.
- *scope: This specifies the attribute's scope, PRODUCT, VARIANT, and OVERRIDEABLE. For more information on Scope, refer to the Attribute Data Types guide.
- *isRequired: This indicates if the attribute is mandatory (true or false). Set it to true if users must provide a value for this attribute.
- *type: This defines the data type of the attribute (e.g., string, number). Choose the data type based on the kind of data you expect for this attribute. For more information on Types, refer to the Attribute Data Types guide.
- units: This specifies the units for the attribute, if applicable (e.g., kg, cm). Provide units if the attribute value represents a measurement.
- allowedValues: This lists predefined values allowed for the attribute. Use this for dropdowns or selections to restrict the choices available to users.
- defaultValue: This specifies the default value for the attribute. Set a value here if you want the attribute to have a predefined value when users first encounter it.
- minimum: This sets the minimum value allowed for the attribute. Use this for numerical attributes to enforce a lower limit.
- maximum: This sets the maximum value allowed for the attribute. Use this for numerical attributes to enforce an upper limit.
- minLength: This specifies the minimum length for the attribute value. Use this for text attributes to ensure the value is not too short.
- maxLength: This specifies the maximum length for the attribute value. Use this for text attributes to ensure the value is not too long.
- *sites: Indicates the IDs of the websites or online marketplaces where the product is listed and available for purchase. These IDs correspond to specific platforms or sales channels where the product can be found.
- *attributes: These are additional attributes related to this attribute. Use this to link other relevant attributes, if needed. (Mandatory incase of custom attributes)
- *contentBucketRef: This is a reference to the content bucket associated with the attribute. Use it to link the attribute to specific content storage.
- *productType: This specifies the product types to which the attribute applies. Use this to restrict the attribute to certain types of products. collectionType: This defines the type of collection the attribute belongs to. It helps in categorizing and managing attributes within collections.
NOTE: While inputting your product data, certain fields support Multiple Values. To accurately input these values, please use a comma "," to separate each entry. This format ensures that all relevant information is correctly processed and displayed.
PIM systems allow you to create and upload custom attributes in the Attribute template, which are customized details specific to your products. Think of them as labels you create to describe unique aspects of your items. These custom attributes can be organized in a hierarchical structure, like a family tree. A broad category, called a parent attribute, can have more specific details nested beneath it as child attributes. This helps keep your product information organized and easy to manage.
Example: Creating a Shipping Package Custom Attribute
- Parent Attribute: Shipping PackageThis is the broad category for all your shipping information.
- Child Attributes:
- Weight: This specifies the weight of the shipping package.
- Dimensions: This specifies the dimensions of the shipping package.
For custom attributes, you will define child attributes to add specific details based on your business needs. You can combine these child attributes in different ways to best represent your product information.
- groupId: This is a unique identifier for the product template. It ensures that each product template can be distinctly identified within the system.
- *groupName: This specifies the type or category of the product that the group is for. Examples might include electronics, clothing, or furniture. Use this to categorize the product templates to make them easier to manage and apply.
- *description: This provides a detailed description of the product template.
- *displayName: This is the name of the product template as it will be displayed to users. It should be clear and descriptive so users can easily understand what the template represents.
- attributes: This is a list of individual product attribute IDs to include in the attribute group. These attributes can be related to size, color, or material, and they will be associated with this product template.
- attributeGroups:: These are groups of related attributes that help you organize your product information more effectively. For example, you might have a "Product Specifications" group that includes attributes like size, weight, and color.
Note: Attribute Groups are optional if you choose to define individual Attributes.
- *sites: Provide the list of sites where the product template is applicable. Specify the sites if the template should only be used in certain locations or for specific instances.
- productTemplateId: This is a unique identifier for the product template. It ensures that each product template can be distinctly identified within the system.
- *productType: This specifies the type or category of the product that the template is for. Examples might include electronics, clothing, or furniture. Use this to categorize the product templates to make them easier to manage and apply.
- *description: This provides a detailed description of the product template.
- *displayName: This is the name of the product template as it will be displayed to users. It should be clear and descriptive so users can easily understand what the template represents.
- attributes: This is a list of attribute IDs associated with the product template. These attributes define the various properties or characteristics that products using this template will have. (attributes are optional if any attribute group below is provided)
- attributeGroups: These are groups of related attributes that help in better organization of the attributes. (attribute groups are optional if any attribute above is provided) *sites: Provide the list of sites where the product template is applicable. Specify the sites if the template should only be used in certain locations or for specific instances.
When preparing your bulk upload files for products and variants, you will need to provide the following information:
- *itemScope: Defines the scope of the item, indicating whether it is a product or a variant. Use PRODUCT for products and VARIANT for variants. This helps in categorizing the type of item being uploaded.
- *itemId: Unique identifier for the item based on the item scope. For products, this is the product ID, and for variants, this is the variant ID.
- *Product Template Id: Identifier for the product template being used for the product. This links the item to a specific product template, which defines the attributes and structure of the product or variant.
- tags: Provide a list of tags that help in organizing and searching for the product. Tags can include keywords related to the product's features, uses, or category.
- *state: Set the State of the created product. Options included:
- View Only: The product is visible but cannot be purchased.
- Hidden: The product is not visible to customers.
- Normal: The product is fully visible and available for purchase.
For more information on states. refer to the States guide.
- *displayName_en_US: Display the name of the product in English (US). This is the name that will be shown to customers. Make it descriptive and user-friendly.
- activationDate: Specify the date on which you want the product to become active.
Date Formatting
All dates must be formatted as YYYY-MM-DDThh:mm:ssTZD e.g. 2009-07-01T00:00:00Z in the PIM system. This format ensures consistency and accurate interpretation of date and time data across the system.
- associatedItems: Input the IDs of related items, such as accessories or complementary products. This helps in cross-selling and creating product bundles.
- *description: Provide a detailed description of the product's features and specifications. Example: The Truck Sleeper by Zeen of 3lb Memory Foam and 6" of Heavy Duty Furniture-Grade Foam, for a full 8" of Sleeping Comfort, even when you are on the road.
- brandName: Specify the brand to which the product belongs. This helps in building trust and brand recognition.
- deactivationDate: Specifies the date when the product becomes inactive or is no longer available for sale. After this date, the product may be removed from listings or marked as unavailable.
- media: Refers to the media assets associated with the product, such as images, videos, or audio clips. These assets are used to visually or audibly represent the product to customers.
- relatedIds: Provides IDs of related products that are typically recommended alongside the main product. This helps suggest complementary or similar items to customers.
- seo: Contains search engine optimization (SEO) information for the product, including meta description, page title, and meta keywords. These elements help improve the product's visibility and ranking in search engine results.
- shippingMethodIds: Lists the IDs of available shipping methods for the product. These IDs correspond to different delivery options offered to customers during checkout.
- *sites: Indicates the IDs of the websites or online marketplaces where the product is listed and available for purchase. These IDs correspond to specific platforms or sales channels where the product can be found.
- taxCode: Specifies the tax code associated with the product, which helps determine the applicable taxes during purchase or checkout.
After completing the templates with all the required details, return to the NoChannel Commerce Portal.
Click on the Upload File button at the top-right corner of your screen to initiate the upload process. Select the completed template file from your system and proceed with the upload.
Adherence to formatting and data requirements outlined in the template instructions is essential to avoid rejection errors by the PIM system.
Once you've uploaded your file, the system will begin processing it. The import time may vary depending on the file size and complexity of your data.
During the upload process, you'll see various states displayed on-screen, such as scanning, processing, importing, and batch commit. These represent different stages of the import process.
For a detailed explanation of these upload states, refer to the Bulk Upload States guide.
Upon a successful "batch commit" status, your product data will be uploaded and live on the PIM system. However, if the system encounters any errors during processing, proceed to Step 6.
If the upload is unsuccessful, you will need to review the errors provided by the system. Below are some common errors you might encounter:
- Duplicated SKUs provided: Ensure that all SKUs are unique. Duplicate SKUs will prevent the file from being uploaded.
- Invalid item scope provided: Check that the item scope is correctly specified as either PRODUCT or VARIANT. An incorrect item scope will result in an error.
- Product SKUs not needed, only sellable products need SKUs: SKUs should only be assigned to sellable products. Non-sellable products should not have SKUs.
- Invalid brand or brand does not exist: Verify that the brand name is spelled correctly and exists in the system. An invalid or nonexistent brand name will cause an error.
These errors will be shown at the bottom left of the screen in the PIM system. You can also visit the notifications bar to view all error reports.
The screenshot below shows how the PIM system provides a detailed description and ID for each error. Use this ID to find the corresponding issue in your Excel file and fix it.
Follow these steps to identify and fix the bulk upload errors.
- Locate Errors: The PIM system will display a notification bar listing errors with detailed descriptions and IDs.
- Find Errors in Excel: Use the error IDs from the PIM system to search your Excel sheet. These IDs will pinpoint the exact rows where the errors occurred.
- Correct Errors: Once you've identified the errors in your Excel sheet, correct them accordingly. Ensure all SKUs and IDs are unique, the item scope is correct, and each field is filled with accurate information.
- Upload Again: After correcting all errors, save your Excel sheet and upload the entire file again to the PIM system.
If you still encounter errors, you can reach out to our support team at [email protected] for further assistance.