CMS Product Import - Revision history

Dan hacker: /* CMS-SKU */

2020-02-24T22:05:25Z

CMS-SKU

← Older revision		Revision as of 22:05, 24 February 2020
Line 11:		Line 11:
	This file will contain information that defines the high-level product information like product code, invoice description, etc. The data in this file would pertain to all size/color combinations of the product (if any existed).		This file will contain information that defines the high-level product information like product code, invoice description, etc. The data in this file would pertain to all size/color combinations of the product (if any existed).

	== CMS-SKU ==		== CMS-SKU.CSV ==
	This file will contain information that defines a secondary level of detail for the product, such as size/color, UPC, length, width, etc. It is important to understand that even when a product in CMS has no defined size/color combinations, it still uses a "hidden" SKU record to store this data. That is why this spreadsheet would also be used to import products without sizes and colors.		This file will contain information that defines a secondary level of detail for the product, such as size/color, UPC, length, width, etc. It is important to understand that even when a product in CMS has no defined size/color combinations, it still uses a "hidden" SKU record to store this data. That is why this spreadsheet would also be used to import products without sizes and colors.

Dan hacker at 22:04, 24 February 2020

2020-02-24T22:04:52Z

← Older revision		Revision as of 22:04, 24 February 2020
Line 50:		Line 50:
	--screenshot of loaded/processed		--screenshot of loaded/processed

	At this point, the user can look at the various settings that are about to go into CMS. It is a good chance to see if there are any special issues with the data that wouldn't be caught by the preprocessing step (such as spelling mistakes, incorrect number values, etc). If an issue is found, it is possible to edit the data directly on this screen, and it will be imported instead of what was initially brought in by the import files. Although it is possible to make edits this wa, we advice against it and suggest editing the ~~origal~~ CSV files and reprocessing them, just so you have an external paper trail of what you actually imported.		At this point, the user can look at the various settings that are about to go into CMS. It is a good chance to see if there are any special issues with the data that wouldn't be caught by the preprocessing step (such as spelling mistakes, incorrect number values, etc). If an issue is found, it is possible to edit the data directly on this screen, and it will be imported instead of what was initially brought in by the import files. Although it is possible to make edits this way, we advice against it and suggest editing the original CSV files and reprocessing them, just so you have an external paper trail of what you actually imported.
			After we are satisfied with the data, it is time to import into CMS by clicking the "Import Into CMS" button. Depending on the number of products you are importing, this could take a little time. For a simple import like our example, it will hardly take any time at all.
	After we are satisfied with the data, it is time to import into CMS. Depending on the number of products you are importing, this could take a little time. For a simple import like our example, it will hardly take any time at all.

Dan hacker at 22:02, 24 February 2020

2020-02-24T22:02:40Z

← Older revision		Revision as of 22:02, 24 February 2020
Line 36:		Line 36:

	1) "Specify or browse to the folder containing CMS import files"		1) "Specify or browse to the folder containing CMS import files"

	Instead of pointing at each file directly, CMS only needs to know the folder in which the required files can be found.		Instead of pointing at each file directly, CMS only needs to know the folder in which the required files can be found.

	2) "Preprocess Import Files"		2) "Preprocess Import Files"

	This step allows CMS to parse the data, check for any issues, and present the pending import to the user for any corrections. If any errors are found during preprocessing, CMS will notify the user with a list of the issues. In the case where errors are found, the user must go back into the CSV files and correct the errors prior to repeating Step 2 to reprocess the newly-edited CSV.		This step allows CMS to parse the data, check for any issues, and present the pending import to the user for any corrections. If any errors are found during preprocessing, CMS will notify the user with a list of the issues. In the case where errors are found, the user must go back into the CSV files and correct the errors prior to repeating Step 2 to reprocess the newly-edited CSV.

	3) "Import Into CMS"		3) "Import Into CMS"

	The final step in the process brings the data directly into the CMS product list. This step will only be available if step 2 completed without errors.		The final step in the process brings the data directly into the CMS product list. This step will only be available if step 2 completed without errors.

Dan hacker: /* CMS-SKU */

2020-02-24T21:59:28Z

CMS-SKU

← Older revision		Revision as of 21:59, 24 February 2020
Line 19:		Line 19:
	Example:		Example:

	To import a new product into CMS we need to add a new record in CMS-Products.CSV to define ~~this~~ product.		To import a new product into CMS we need to add a new record in CMS-Products.CSV to define the product.

	--show a clip of CMS-Products with MyNewProduct defined.		--show a clip of CMS-Products with MyNewProduct defined.

Dan hacker: /* CMS-SKU */

2020-02-21T17:52:56Z

CMS-SKU

← Older revision		Revision as of 17:52, 21 February 2020
Line 15:		Line 15:

	Both of the files contain different "types" of fields, including text, numbers, and true/false (boolean). We will use each of these types in the example below.		Both of the files contain different "types" of fields, including text, numbers, and true/false (boolean). We will use each of these types in the example below.


	Example:		Example:

Dan hacker: /* CMS-SKU */

2020-02-21T17:52:23Z

CMS-SKU

← Older revision		Revision as of 17:52, 21 February 2020
Line 12:		Line 12:

	== CMS-SKU ==		== CMS-SKU ==
	This file will contain information that defines a secondary level of detail for the product, such as size/color, UPC, ~~Length~~, ~~Width~~, etc. It is important to understand that even when a product in CMS has no defined size/color combinations, it still uses a "hidden" SKU record to store this data. That is why this spreadsheet would also be used to import products without sizes and colors.		This file will contain information that defines a secondary level of detail for the product, such as size/color, UPC, length, width, etc. It is important to understand that even when a product in CMS has no defined size/color combinations, it still uses a "hidden" SKU record to store this data. That is why this spreadsheet would also be used to import products without sizes and colors.

	Both of the files contain different "types" of fields, including text, numbers, and true/false (boolean). We will use each of these types in the example below.		Both of the files contain different "types" of fields, including text, numbers, and true/false (boolean). We will use each of these types in the example below.

Dan hacker at 17:51, 21 February 2020

2020-02-21T17:51:43Z

← Older revision		Revision as of 17:51, 21 February 2020
Line 1:		Line 1:
	CMS has the ability to import ~~products from predefined spreadsheets. There are six spreadsheets in total, although not all are used in every situation~~.		CMS has the ability to import product definitions using pre-defined CSV files (Comma Separated Values).

	~~The six spreadsheets~~ are:		For importing basic product information like product code, size/color, and related product details, there are two files that are required:

	CMS-Products		CMS-Products.CSV

	CMS-SKU		CMS-SKU.CSV

	~~CMS-Inventory~~

	CMS-~~PriceCategory~~		== CMS-Products.CSV ==
			This file will contain information that defines the high-level product information like product code, invoice description, etc. The data in this file would pertain to all size/color combinations of the product (if any existed).

	CMS-~~Warehouse~~		== CMS-SKU ==
			This file will contain information that defines a secondary level of detail for the product, such as size/color, UPC, Length, Width, etc. It is important to understand that even when a product in CMS has no defined size/color combinations, it still uses a "hidden" SKU record to store this data. That is why this spreadsheet would also be used to import products without sizes and colors.

			Both of the files contain different "types" of fields, including text, numbers, and true/false (boolean). We will use each of these types in the example below.

			Example:

			To import a new product into CMS we need to add a new record in CMS-Products.CSV to define this product.
			--show a clip of CMS-Products with MyNewProduct defined.

	CMS-~~Prices~~		Here we have defined a new product called "MyNewProduct" with an "InvoiceDescription" of "This is a new product". The "AllowDecimal" field, a boolean-typed field, corresponds to the product setting checkbox in CMS called "Allow Decimal Quantities". As you can see, boolean values are designated with a '0' for false and a '1' for true. This record is enough to create a non-sized, non-colored product with no other predefined settings, and could be imported completely on its own, but we will add some more details with the CMS-SKU file.

			--show a clip of CMS-SKU with some more details

	~~== CMS-Products ==~~		As you can see, both of the files contain the field "ProductCode", which is what CMS will use to join the two files for import. In our new "SKU" record, we have again specified "MyNewProduct" as the product code as required. Additionally, we have configured more details for the new product including Weight, UPC, Length, Width and Height. Now that we have our definition, we can import the product into CMS.
	~~CMS-Products is~~ the ~~base product spreadsheet containing data that~~ is ~~solely related~~ to the ~~main product code (without consideration~~ for ~~color/size/~~SKU~~). The fields roughly correspond to what you would see at the product level if you were looking at a product in the~~ "~~Product Information~~" ~~window. Besides~~ the product code ~~itself~~, the ~~spreadsheet contains fields such as "InvoiceDescription"~~, ~~"Brand"~~, ~~"AllowDecimal"~~, and ~~"DoesNotShip"~~.

	~~This spreadsheet covers all of the essential top-level settings for a product and~~ can be ~~used to import basic product information~~.		The Product Import can be found in the CMS menu under Settings \| Inventory \| Products \| Product Import.

			--show product import window

	== CMS~~-SKU ==~~		The product import consists of three steps:
	CMS~~-SKU is~~ the ~~secondary product spreadsheet containing data related to SKU level properties~~. ~~This includes fields like~~ "~~Weight~~", ~~"Length"~~, ~~"UPC"~~, and "~~VendorSKU~~". This ~~spreadsheet~~ is ~~related to~~ the "~~CMS~~-~~Products" spreadsheet via the "ProductCode" field.~~
			1) "Specify or browse to the folder containing CMS import files"
			Instead of pointing at each file directly, CMS only needs to know the folder in which the required files can be found.
			2) "Preprocess Import Files"
			This step allows CMS to parse the data, check for any issues, and present the pending import to the user for any corrections. If any errors are found during preprocessing, CMS will notify the user with a list of the issues. In the case where errors are found, the user must go back into the CSV files and correct the errors prior to repeating Step 2 to reprocess the newly-edited CSV.
			3) "Import Into CMS"
			The final step in the process brings the data directly into the CMS product list. This step will only be available if step 2 completed without errors.

			This is what the Product Import looks like after doing steps 1 and 2 against our import files for "MyNewProduct":
			--screenshot of loaded/processed

			At this point, the user can look at the various settings that are about to go into CMS. It is a good chance to see if there are any special issues with the data that wouldn't be caught by the preprocessing step (such as spelling mistakes, incorrect number values, etc). If an issue is found, it is possible to edit the data directly on this screen, and it will be imported instead of what was initially brought in by the import files. Although it is possible to make edits this wa, we advice against it and suggest editing the origal CSV files and reprocessing them, just so you have an external paper trail of what you actually imported.

	== CMS~~-Inventory ==~~		After we are satisfied with the data, it is time to import into CMS. Depending on the number of products you are importing, this could take a little time. For a simple import like our example, it will hardly take any time at all.

Dan hacker at 22:45, 19 February 2020

2020-02-19T22:45:12Z

← Older revision		Revision as of 22:45, 19 February 2020
Line 5:		Line 5:
	CMS-Products		CMS-Products

	CMS~~-Products~~-SKU		CMS-SKU

	CMS-~~Products-SKU-PriceCategory~~		CMS-Inventory

	CMS-~~Products-SKU-Warehouse~~		CMS-PriceCategory

	CMS-~~Products-Prices~~		CMS-Warehouse

	CMS-~~Products-Inventory~~		CMS-Prices


Line 22:		Line 22:


			== CMS-SKU ==
			CMS-SKU is the secondary product spreadsheet containing data related to SKU level properties. This includes fields like "Weight", "Length", "UPC", and "VendorSKU". This spreadsheet is related to the "CMS-Products" spreadsheet via the "ProductCode" field.

	== CMS-~~Products-SKU~~ ==
	CMS-Products-SKU is the secondary product spreadsheet containing data related to SKU level properties. This includes fields like "Weight", "Length", "UPC", and "VendorSKU". This spreadsheet is related to the "CMS-Products" spreadsheet via the "ProductCode" field.		== CMS-Inventory ==

Dan hacker at 22:43, 18 February 2020

2020-02-18T22:43:32Z

← Older revision		Revision as of 22:43, 18 February 2020
Line 4:		Line 4:

	CMS-Products		CMS-Products

	CMS-Products-SKU		CMS-Products-SKU

	CMS-Products-SKU-PriceCategory		CMS-Products-SKU-PriceCategory

	CMS-Products-SKU-Warehouse		CMS-Products-SKU-Warehouse

	CMS-Products-Prices		CMS-Products-Prices

	CMS-Products-Inventory		CMS-Products-Inventory

Dan hacker: Created page with 'CMS has the ability to import products from predefined spreadsheets. There are six spreadsheets in total, although not all are used in every situation. The six spreadsheets are…'

2020-02-18T22:20:04Z

Created page with 'CMS has the ability to import products from predefined spreadsheets. There are six spreadsheets in total, although not all are used in every situation. The six spreadsheets are…'

New page

CMS has the ability to import products from predefined spreadsheets. There are six spreadsheets in total, although not all are used in every situation.

The six spreadsheets are:

CMS-Products
CMS-Products-SKU
CMS-Products-SKU-PriceCategory
CMS-Products-SKU-Warehouse
CMS-Products-Prices
CMS-Products-Inventory

== CMS-Products ==
CMS-Products is the base product spreadsheet containing data that is solely related to the main product code (without consideration for color/size/SKU). The fields roughly correspond to what you would see at the product level if you were looking at a product in the "Product Information" window. Besides the product code itself, the spreadsheet contains fields such as "InvoiceDescription", "Brand", "AllowDecimal", and "DoesNotShip".

This spreadsheet covers all of the essential top-level settings for a product and can be used to import basic product information.

== CMS-Products-SKU ==
CMS-Products-SKU is the secondary product spreadsheet containing data related to SKU level properties. This includes fields like "Weight", "Length", "UPC", and "VendorSKU". This spreadsheet is related to the "CMS-Products" spreadsheet via the "ProductCode" field.