Imports: ECommerce Data

Imports: ECommerce Data

Imports: ECommerce Data

The Ecommerce Data Import provides a convenient way for Fulfillers to import and set Ecommerce Data against Products in the Platform. 

The required import format is CSV. 

What is the Ecommerce Data Import used for?
The import is used to create Ecommerce Data or to edit existing data. 

All products found within Platform can have Ecommerce set against them which can be imported into the system. eCommerce data is important as it allows for data such as Names, SKUs, Descriptions, Lead Times, Weights, Shipping Carriers and Machine Type.

Including eCommerce data on products makes them more professional and an increase in product engagements, the data is a huge benefit for all retailers and fulfillers using the system. A document has been added to the further reading section of this article to breakdown all of the headers and which ones we feel are most beneficial for retailers listing lines. 
eCommerce data is essential if products are going to be added to Feeds, which allows other retailers to list products

Create: Add new Ecommerce Data to Products in bulk.

To create new Ecommerce Data, the relevant Products should first be 'selected' or filtered in Product Manager prior to generating an Ecommerce Data Export.

The generated CSV file serves as a template, allowing the Product data to be added in a format that is then suitable for use with the Ecommerce Data Import to update the Products. 
It is recommended that Imports are tested on a sample range prior to rollout across a high volume of Products.

For more information on using the Ecommerce Export / Import click here

Edit: Update existing Ecommerce Data across a range of Products. 

To edit Ecommerce Data, the relevant Products should be 'selected' or filtered in Product Manager prior to generating an Ecommerce Data Export.

The generated CSV file serves as a template, allowing the Product data to be edited in a format that is then suitable for use with the Ecommerce Data Import to update the Products.
It is recommended that Imports are tested on a sample range prior to rollout across a high volume of Products.

For more information on using the Export / Import to edit Ecommerce Data click here

What fields can be updated with the eCommerce Data import?
All of the following fields are the most commonly updated fields from the eCommerce import. 
  1. Basic Details - Name, Fulfiller SKUs, Retail SKUs, Product Type, Product Classification, Product Categories, Product Images
  2. Defualt Fulfiller - Fulfiller Company, Owner Company, Stock Base Product ID, Wholesales Blank Product ID, Output Type, Machine Type
  3. App Defaults - Default App, App Config, App Locale
  4. Sales Data - Sales Description, Long Sales Description, Notes, Meta Data, Lead Time, Manufactors Code, Weight, Tax Code, Tax Rate, Barcode, HS Code, Nominal Code, Default Shipping Carrier, Number Of Parcels, Production Instructions
  5. Licence Information - Licence, Licence Company, Licence Percetange, Brand Code, Brand Name, Branding Attribute Set, Design Name, Design Code

Are there other ways to update eCommerce Data?
eCommerce Data can be set manually on each individual product, however this solution means with one import a wide selection of products can be updated, increasing efficency. If the data needs to be updated manaully, simply head to the eCommerce & Data section found against every product in the Platform. 

Its perfectly viable if small changes are needed to set these manually but Kornit X recommends the use of the export and import as this is a quicker process and allows for multiple products to be updated at once. 
Within Feeds, this allows for retailers to access the products and view data. In therory, the more detailed the eCommerce Data is the more likelty retailers will want to establish a dropship relationship. 

CSV Import Format Requirements
If using Excel, the file must be saved as a .CSV.

If using OpenOffice or equivalent, save as .CSV and be sure to:
  1. Enable 'Edit the Filter Settings'
  2. Keep Current Format
  3. Change the character set to UNICODE (UTF-8)
  4. The saving delimeter needs to be ","
  5. Enable 'Quote all text cells'
The file can then be imported.

Further Reading
Virtual Products | Enhanced Print On Demand import
Breakdown Of All Headers Of The eCommerce Import

Still Need Help?
You can access our extensive knowledge base or raise a ticket with our technical support teams using the buttons below

View all help articles

Raise a support ticket

    • Related Articles

    • Exports: ECommerce Data

      Exports: ECommerce Data The Ecommerce Data Export provides a convenient way to extract ECommerce information in bulk.  The export produces a CSV document for any 'selected' or filtered Products in Product Manager; this allows you to target a specific ...

    • Imports: No Preview

      Imports: No Preview        The No Preview Import provides a convenient way to create No Preview Products via CSV. No Preview refers to products that offer customisation functionality without an interactive live preview.  What is the No Preview Import ...

    • Imports: Attributes

      Imports: Attributes The Attributes Import provides a convenient way for Fulfillers to import and create Attributes against Products in the Platform.  The required import format is CSV.  What is the Attribute Import used for? The import is used ...

    • Imports: Excel

      Imports: Excel The Excel Import provides a convenient way for Fufillers to upload Blank Product setup information to the Catalog.  The required import format is .xlsx   What is the Excel Import used for? The import is used by Fulfillers to create new ...

    • Imports: Variants

      Imports: Variants The Variants Import provides a convenient way for Fulfillers to upload and apply Variant information to Products within the Catalog.  The required import format is CSV.  What is the Variant Import used for? The import is used by ...