Import / Export Data Files Help

This page allows you to import and export departments, categories, sub-categories, and products through tab-delimited text files. There are several sections contained in this help topic so please use the quick links below to jump to the area you need help with.

EXPORTING HELP

IMPORTING HELP
General Importing Tips and Notes
Selecting and Uploading Import Files - When BROWSE BUTTON is displayed
Selecting and Processing Import Files - When BROWSE BUTTON is *NOT* displayed
 Importing Department Data
Importing Category Data
Importing Sub-Category Data
Importing Product Data
Importing Product Option Data

EXPORTING DATA FILES
Exporting data files should be the first step in creating an interface between your online store and a database on your computer. Exporting allows you to view the current information in the store's database system, and see how the files and fields are formatted and used.

When you press the EXPORT button, the store will gather up all of the department, category, sub-category, product, and product option data. Next, it will store this information in special tab-delimited text files and present a page for you to download them to your computer.

NOTE: This is a very important step that should be done before you attempt to import data into your store!

Each download file will contain a series of "records" which contain information about each item in the database (departments, categories, products...). Each record consists of a series of "fields" separated by tabs. Most database and spreadsheet programs can read and write tab-delimited text files which makes it easy for you to download and manipulate the store's database.

The first record in each tab-delimited text file contains "field header" information. This record identifies the name, order, and use of each field that follows in each data record. This "field header" record MUST also exist when importing data back into your store - so please DO NOT DELETE it or change it in any way. The "field header" record must always be the first record in the file.

For information about each field in a downloaded tab-delimited text file, please see the appropriate section below.

IMPORTING DATA FILES
Importing tab-delimited text files allows you to perform data manipulation on your computer and then upload/import this information into your store's database system.

IMPORTANT: we strongly recommend using the EXPORT features above to download and inspect how the store's database files are constructed and see how the fields/data relate to each other. This is a very important step that should be done before you attempt to import data into your store.

CAUTION - make sure you have a complete store backup BEFORE performing any import function. The very nature of this feature provides for very little in the form of error checking. Be extremely careful when importing data into your store. Failure to carefully construct data within an import file may result in your store malfunctioning or not working at all. Use the import features at your own risk!

Importing Tips and Notes
Each import file must one or more "records" which contain information about each item (department, category, product...) in the store. Each record must consist of a series of "fields" separated by tabs. Most database and spreadsheet programs can read/write tab-delimited text files which will make it easy for you to manipulate the store's database system.

The first record in each tab-delimited text file contains "field header" information. This record identifies the name, order, and use of each field that follows in each data record. This "field header" record MUST exist when importing data back into your store - so please DO NOT DELETE it or change it in any way.

The "field header" record MUST always be the first record in the file and MUST contain the same field names in the same order as created by the export function above. DO NOT change it in any way.

The actual data contained in each field is equally as important. Some fields are required and must exist for the import feature to be successful. Some data fields are case sensitive while other fields require certain predefined codes to be present. You will find detailed field information for each type of import file in the section below.

IMPORTANT: The import file does NOT replace and recreate the store's database in mass - instead the store takes the import file and adds, updates, or deletes records in the store's database for the one or more records it finds in the import file.

When importing records, the store will check each import record's primary key (prod_number for example in the product import file) against the data already contained in the database. If a new record is detected (by primary key), the import function will add the import record to the store's database. If an existing record is detected (by primary key), the store will update the record in the database with the information from the import record. If an existing record is detected (by primary key) and its "delete flag" field contains "DELETE", the record will be removed from the database.

NOTE: The DELETE FLAG is one of the fields in the import file's record format. To delete a database record using the import file, the record must exist in both the store's database and in the import file (so the store knows to process it). In addition, the import record's field called "delete_flag" must contain the exact phrase "DELETE".

TIP: An import file can consist of only one record if needed (say to delete, change, or add just one record). The import file is processed record-by-record and only the records in the import file are processed (worked on) in the store's database. The import function does not delete and recreate the entire store database from the import file. Instead, it simply adds, changes, or deletes one or more database records based on the records in the import file.

CAUTION - make sure you have a complete store backup BEFORE performing any import function. The very nature of this feature provides for very little in the form of error checking. Be extremely careful when importing data into your store. Failure to carefully construct data within an import file may result in your store malfunctioning or not working at all. Use the import features at your own risk!

Selecting and Uploading Import Files - When BROWSE BUTTON is Displayed
To upload and process an import file, use the BROWSE button to find the import file on your computer's hard drive. Once you have selected the proper import file and data type to upload, click the IMPORT DATA button.

Depending on the size of the import file, this process may take a few minutes. Therefore, please be patient and allow this process to finish. Only press the IMPORT DATA button one time! This is a one step process in which the store will receive the import file from your computer and process its informaiton.

NOTE: the store must process the import file by its exact file name and therefore, it must be called: "departments.txt", "categories.txt", "subcategories.txt", "products.txt", or "productoptions.txt" (without the quotes). All files names must be in all lowercase leters, end with the ".txt" extension, and must not contain any spaces or other punctuation.

Selecting and Processing Import Files - When BROWSE BUTTON is *NOT* Displayed
To process an import file when the BROWSE button is NOT displayed, you will need to upload the import file(s) to your store manually using FTP. These files must be uploaded in ASCII text mode using FTP to the Qstore/Qtemp directory of the store.

Once the import file(s) has been uploaded to the store, enter the name of the import file you want to process in this field. Press the IMPORT DATA button to begin the import process. The store will open, read, and process the import file specified from the Qstore/Qtemp directory of the store. A message will display informing you when the store has completed the process.

NOTE: the store must process the import file by its exact file name and therefore, it must be called: "departments.txt", "categories.txt", "subcategories.txt", "products.txt", or "productoptions.txt" (without the quotes). All files names must be in all lowercase leters, end with the ".txt" extension, and not contain any spaces or other punctuation.


DEPARTMENTS

Importing Department Data
This file contains one record for each department. The following table provides field-by-field specifications that must be followed exactly as required.

NOTE: we recommend that you refer to the department data entry screen (and its fields) when reviewing this information.

Field
Num
Field
Name		Field
Type
Max Length
Required?
Case
Sensitive?
Options
Allowed
HTML
OK?
Description
1
dept_numberPrimary
Key
30
Yes
 
 
 
This must be a unique numeric string for each record. DO NOT include spaces or any other non-numeric characters other than 0-9 or a dash. The store uses this field to uniquely identify each record in the database.
2
display_posNumber
5
Yes
 
 
 
This must be a five position numeric string which is padded by leading zeros. This determines the display order for this item when it is shown to the customer during shopping. Examples: 00010, 00020, 00030, 00040, 00050
3
dept_nameString
100
Yes
 
 
 
A unique name displayed by the store during customer shopping.
4
thumbnail_imageString
80
 
Yes
 
 
Optional image name which MUST be preceded by the phrase "uploads/". This image file must be a GIF or JPG image that exists in (has been uploaded to) the store's "uploads" directory. The web server is case sensitive when locating files so be careful to match this field contents to the actual image file's name on the server. Example: uploads/Bauer_hh4000_LARGE.gif
5
link_typeString
10
Yes
Yes - ALL UPPER CASE
CATEGORIES
PRODUCTS
SINGLE
NONE
STATIC
CUSTOM
 
This tells the store what type of link to use when displaying this item. CATEGORIES links this item to a list of categories. PRODUCTS links this item to a list of products. SINGLE links this item to a single product. NONE means this item is displayed as a section header (no link). STATIC means this item links to a static web page address defined in the "static_page_URL" field below. CUSTOM means this department links to a custom web page (that uses the current skin) which displays the "custom_text" field below.
Field
Num
Field
Name		Field
Type
Max Length
Required?
Case
Sensitive?
Options
Allowed
HTML
OK?
Description
6
sub_links_assignedFlag
1
Yes
Yes - ALL UPPER CASE
Y
N
 
This tells the store whether any sub-links have been defined for this item. This is used in combination with the link_type field above to determine whether a section of the store still needs to be finished or not. Example: if this item links to PRODUCTS and this flag is N, then the store knows that a list of products has not yet been defined for this item and still needs to be done. Use Y for Yes and N for No.
7
static_page_URLString
90
  Yes when link_type field = "STATIC"
Yes
 
 
This field is ONLY used when this item's link_type field is set to STATIC. This field contains the web page address to link this item to when the store displays it to the customer.
8
spacer_typeString
6
Yes
Yes - ALL UPPER CASE
NONE
EMPTY
DASHED
DOTTED
 
This tells the store what to insert in front of this item when it is displaying it to the customer during shopping. NONE means do NOT insert anything before this item. EMPTY mean insert an empty line. DASHED means insert a dashed line. DOTTED means insert a dotted line.
9
dept_text String
15,000
 
 
 
Yes
This field is used to display text or notes to the customer when this item is viewed by the customer. This field can contain properly formatted HTML tags.
10
custom_text String
15,000
  Yes when link_type field = "CUSTOM"
 
 
Yes
This field is used when a department is linked to a "custom web page". A custom web page uses the current skin to display a web page that shows the contents of this field. This field can contain properly formatted HTML tags.
11
override_skinString
1
 
Yes - ALL UPPER CASE
Y or N
 
This flag tells the store that this department has a custom skin number to use. See the next field for the skin number.
12
skin_numberString
2
Yes when the override_skin flag = "Y"
 
01 thru 99
 
When the override_skin field contains a "Y" value, this field is used by the store to override the skin assigned globally to the store. The override skin_number is used when the customer is shopping within this department.
13
display_controlString
1
Yes
 
Y or N - note: a blank value is the same as Y
 
This flag tells the store whether you want this department (and its contents) to be displayed or not. Y (or blank) is the default value. N causes this department and its contents to be suppressed from display in the store.
14
meta_tagsString
15,000
   
If entered, it must be a set of properly formatted Meta Tag Commands!
 YES
If you want this store to insert "hidden" search engine Meta Tags into this department's web page, then enter them into the field above. These Meta Tags will only apply to this department, and they will override any "Global" Search Engine Meta Tags defined for the store.
15
delete_flagString
6
  Yes
DELETE or blanks
  
If you want this department to be REMOVED from the database, then enter "DELETE" (without the quotes) into this field. Otherwise, leave this field blank to add/update the record. NOTE: deleting a department record will also remove all of its assocaited categories, sub-categories, and products.
 DEPARTMENTS

 
CATEGORIES

Importing Category Data
This file contains one record for each category. The following table provides field-by-field specifications that must be followed exactly as required.

NOTE: we recommend that you refer to the category data entry screen (and its fields) when reviewing this information.

Field
Num
Field
Name		Field
Type
Max Length
Required?
Case
Sensitive?
Options
Allowed
HTML
OK?
Description
1
category_numberPrimary
Key
30
Yes
 
 
 
This must be a unique numeric string for each record. DO NOT include spaces or any other non-numeric characters other than 0-9 or a dash. The store uses this field to uniquely identify each record in the database.
2
dept_num_assignedRelational Key
30
Yes
 
 
 
Every category in the store's database is assigned to a specific department. This field contains the "key" value of the department it is assigned to. This must EXACTLY match one of the existing department keys in the store's database. DO NOT include spaces or any other non-numeric characters other than 0-9 or a dash.
3
display_posNumber
5
Yes
 
 
 
This must be a five position numeric string which is padded by leading zeros. This determines the display order for this item when it is shown to the customer during shopping. Examples: 00010, 00020, 00030, 00040, 00050
4
category_nameString
100
Yes
 
 
 
A unique name displayed by the store during customer shopping.
5
thumbnail_imageString
80
 
Yes
 
 
Optional image name which MUST be preceded by the phrase "uploads/". This image file must be a GIF or JPG image that exists in (has been uploaded to) the store's "uploads" directory. The web server is case sensitive when locating files so be careful to match this field contents to the actual image file's name on the server. Example: uploads/Bauer_hh4000_LARGE.gif
Field
Num
Field
Name		Field
Type
Max Length
Required?
Case
Sensitive?
Options
Allowed
HTML
OK?
Description
6
link_typeString
10
Yes
Yes - ALL UPPER CASE
SUBCATEGORIES
PRODUCTS
SINGLE
NONE
STATIC
CUSTOM
 
This tells the store what type of link to use when displaying this item. SUBCATEGORIES links this item to a list of sub-categories. PRODUCTS links this item to a list of products. SINGLE links this item to a single product. NONE means this item is displayed as a section header (no link). STATIC means this item links to a static web page address defined in the "static_page_URL" field below. CUSTOM means this category links to a custom web page (that uses the current skin) which displays the "custom_text" field below.
7
sub_links_assignedFlag
1
Yes
Yes - ALL UPPER CASE
Y
N
 
This tells the store whether any sub-links have been defined for this item. This is used in combination with the link_type field above to determine whether a section of the store still needs to be finished or not. Example: if this item links to PRODUCTS and this flag is N, then the store knows that a list of products has not yet been defined for this item and still needs to be done. Use Y for Yes and N for No.
8
static_page_URLString
90
  Yes when link_type field = "STATIC"
Yes
 
 
This field is ONLY used when this item's link_type field is set to STATIC. This field contains the web page address to link this item to when the store displays it to the customer.
9
spacer_typeString
6
Yes
Yes - ALL UPPER CASE
NONE
EMPTY
DASHED
DOTTED
 
This tells the store what to insert in front of this item when it is displaying it to the customer during shopping. NONE means do NOT insert anything before this item. EMPTY mean insert an empty line. DASHED means insert a dashed line. DOTTED means insert a dotted line.
10
category_text String
15,000
 
 
 
Yes
This field is used to display text or notes to the customer when this item is viewed by the customer. This field can contain properly formatted HTML tags.
11
custom_text String
15,000
  Yes when link_type field = "CUSTOM"
 
 
Yes
This field is used when a category is linked to a "custom web page". A custom web page uses the current skin to display a web page that shows the contents of this field. This field can contain properly formatted HTML tags.
12
meta_tagsString
15,000
   
If entered, it must be a set of properly formatted Meta Tag Commands!
 YES
If you want this store to insert "hidden" search engine Meta Tags into this category's web page, then enter them into the field above. These Meta Tags will only apply to this category, and they will override any "Global" Search Engine Meta Tags defined for the store.
13
delete_flagString
6
  Yes
DELETE or blanks
  
If you want this category to be REMOVED from the database, then enter "DELETE" (without the quotes) into this field. Otherwise, leave this field blank to add/update the record. NOTE: deleting a category record will also remove all of its assocaited sub-categories and products.
 CATEGORIES

 
SUB-CATEGORIES

Importing Sub-Category Data
This file contains one record for each sub-category. The following table provides field-by-field specifications that must be followed exactly as required.

NOTE: we recommend that you refer to the sub-category data entry screen (and its fields) when reviewing this information.

Field
Num
Field
Name		Field
Type
Max Length
Required?
Case
Sensitive?
Options
Allowed
HTML
OK?
Description
1
subcategory_numberPrimary
Key
30
Yes
 
 
 
This must be a unique numeric string for each record. DO NOT include spaces or any other non-numeric characters other than 0-9 or a dash. The store uses this field to uniquely identify each record in the database.
2
category_num_assignedRelational Key
30
Yes
 
 
 
Every subcategory in the store's database is assigned to a specific category. This field contains the "key" value of the department it is assigned to. This must EXACTLY match one of the existing category keys in the store's database. DO NOT include spaces or any other non-numeric characters other than 0-9 or a dash.
3
dept_num_assignedRelational Key
30
Yes
 
 
 
Every subcategory in the store's database is assigned to a specific category which is in turn assigned to a specific department. This field contains the "key" value of the department that this sub-category's assigned category is linked to. This must EXACTLY match one of the existing department keys in the store's database. DO NOT include spaces or any other non-numeric characters other than 0-9 or a dash.
4
display_posNumber
5
Yes
 
 
 
This must be a five position numeric string which is padded by leading zeros. This determines the display order for this item when it is shown to the customer during shopping. Examples: 00010, 00020, 00030, 00040, 00050
5
subcategory_nameString
100
Yes
 
 
 
A unique name displayed by the store during customer shopping.
Field
Num
Field
Name		Field
Type
Max Length
Required?
Case
Sensitive?
Options
Allowed
HTML
OK?
Description
6
thumbnail_imageString
80
 
Yes
 
 
Optional image name which MUST be preceded by the phrase "uploads/". This image file must be a GIF or JPG image that exists in (has been uploaded to) the store's "uploads" directory. The web server is case sensitive when locating files so be careful to match this field contents to the actual image file's name on the server. Example: uploads/Bauer_hh4000_LARGE.gif
7
link_typeString
10
Yes
Yes - ALL UPPER CASE
PRODUCTS
SINGLE
NONE
STATIC
CUSTOM
 
This tells the store what type of link to use when displaying this item. PRODUCTS links this item to a list of products. SINGLE links this item to a single product. NONE means this item is displayed as a section header (no link). STATIC means this item links to a static web page address defined in the "static_page_URL" field below. CUSTOM means this sub-category links to a custom web page (that uses the current skin) which displays the "custom_text" field below.
8
sub_links_assignedFlag
1
Yes
Yes - ALL UPPER CASE
Y
N
 
This tells the store whether any sub-links have been defined for this item. This is used in combination with the link_type field above to determine whether a section of the store still needs to be finished or not. Example: if this item links to PRODUCTS and this flag is N, then the store knows that a list of products has not yet been defined for this item and still needs to be done. Use Y for Yes and N for No.
9
static_page_URLString
90
  Yes when link_type field = "STATIC"
Yes
 
 
This field is ONLY used when this item's link_type field is set to STATIC. This field contains the web page address to link this item to when the store displays it to the customer.
10
spacer_typeString
6
Yes
Yes - ALL UPPER CASE
NONE
EMPTY
DASHED
DOTTED
 
This tells the store what to insert in front of this item when it is displaying it to the customer during shopping. NONE means do NOT insert anything before this item. EMPTY mean insert an empty line. DASHED means insert a dashed line. DOTTED means insert a dotted line.
Field
Num
Field
Name		Field
Type
Max Length
Required?
Case
Sensitive?
Options
Allowed
HTML
OK?
Description
11
subcategory_text String
15,000
 
 
 
Yes
This field is used to display text or notes to the customer when this item is viewed by the customer. This field can contain properly formatted HTML tags.
12
custom_text String
15,000
 Yes when link_type field = "CUSTOM"
 
 
Yes
This field is used when a sub-category is linked to a "custom web page". A custom web page uses the current skin to display a web page that shows the contents of this field. This field can contain properly formatted HTML tags.
13
meta_tagsString
15,000
   
If entered, it must be a set of properly formatted Meta Tag Commands!
 YES
If you want this store to insert "hidden" search engine Meta Tags into this sub-category's web page, then enter them into the field above. These Meta Tags will only apply to this sub-category, and they will override any "Global" Search Engine Meta Tags defined for the store.
14
delete_flagString
6
  Yes
DELETE or blanks
  
If you want this sub-category to be REMOVED from the database, then enter "DELETE" (without the quotes) into this field. Otherwise, leave this field blank to add/update the record. NOTE: deleting a sub-category record will also remove all of its assocaited products.
 SUB-CATEGORIES

 
PRODUCTS

Importing Product Data
This file contains one record for each product. The following table provides field-by-field specifications that must be followed exactly as required.

NOTE: we recommend that you refer to the product data entry screen (and its fields) when reviewing this information.

Field
Num
Field
Name		Field
Type
Max Length
Required?
Case
Sensitive?
Options
Allowed
HTML
OK?
Description
1
prod_numberPrimary
Key
30
Yes
 
 
 
This must be a unique numeric string for each record. DO NOT include spaces or any other non-numeric characters other than 0-9 or a dash. The store uses this field to uniquely identify each record in the database.
2
dept_num_assignedRelational Key
30
Yes
 
 
 
Every product in the store's database is assigned to a specific department. This field contains the "key" value of the department that this item is linked to. This must EXACTLY match one of the existing department keys in the store's database. DO NOT include spaces or any other non-numeric characters other than 0-9 or a dash.
3
category_num_assignedRelational Key
30
 
 
 
 
NOTE: This field is NOT used when a department links directly to a single product. Otherwise, this field is required when linked to from a category or sub-category in your store. When needed, this field contains the "key" value of the category it is assigned to. If used, this must EXACTLY match one of the existing category keys in the store's database. DO NOT include spaces or any other non-numeric characters other than 0-9 or a dash.
4
subcategory_numberRelational
Key
30
 
 
 
 
NOTE: This field is NOT used when a category links directly to a single product. Otherwise, this field is required when linked to from a sub-category in your store. When needed, this field contains the "key" value of the su-bcategory it is assigned to. If used, this must EXACTLY match one of the existing sub-category keys in the store's database. DO NOT include spaces or any other non-numeric characters other than 0-9 or a dash.
5
display_posNumber
5
Yes
 
 
 
This must be a five position numeric string which is padded by leading zeros. This determines the display order for this item when it is shown to the customer during shopping. Examples: 00010, 00020, 00030, 00040, 00050
Field
Num
Field
Name		Field
Type
Max Length
Required?
Case
Sensitive?
Options
Allowed
HTML
OK?
Description
6
prod_nameString
100
Yes
 
 
 
A unique name displayed by the store during customer shopping.
7
prod_id_numString
30
Yes
 
 
 
A unique ID number (also called a SKU number) that identifies which product this is.
8
thumbnail_imageString
80
 
Yes
 
 
Optional image file name which MUST be preceded by the phrase "uploads/". This image file must be a GIF or JPG image that exists in (has been uploaded to) the store's "uploads" directory. The web server is case sensitive when locating files so be careful to match this field contents to the actual image file's name on the server. Example: uploads/Bauer_hh4000_LARGE.gif
9
full_image_nameString
 80
 
 Yes
 
 
Optional image file name which MUST be preceded by the phrase "uploads/". This image file must be a GIF or JPG image that exists in (has been uploaded to) the store's "uploads" directory. The web server is case sensitive when locating files so be careful to match this field contents to the actual image file's name on the server. Example: uploads/Bauer_hh4000_LARGE.gif
10
short_descrString
500
Yes
 
 
Yes
This field is used for the product's short description. This field can contain properly formatted HTML tags. Max length is 500 bytes.  
Field
Num
Field
Name		Field
Type
Max Length
Required?
Case
Sensitive?
Options
Allowed
HTML
OK?
Description
11
long_descrString
15,000 
Yes
 
 
Yes
This field is used for the product's long description. This field can contain properly formatted HTML tags. Max length is 15,000 bytes.
12
weight Number
15
 
 
 
 
This field must be blank or contain the product's weight. A maximum of 3 decimal places is allowed. Example: 125.250 would represent one hundred twenty five and 1/4 pounds. This field can only contain the numbers 0-9 and a decimal point.
13
normal_priceNumber
15
Yes
 
 
 
This field must contain the product's price. It must be an amount greater than zero and contain no more than 2 decimal places. NOTE: if you want this product to be "free". you must enter 0.00 in this field.
14
sale_priceNumber
15
 
 
 
 
This optional field is only used when a product is on sale (otherwise it is left blank). This must be a positive number with no more than 2 decimal places.
15
on_saleFlag
1
Yes
Yes - UPPER CASE ONLY
Y
N
 
This flag tells the store whether this product is currently on sale or not. Enter Y for YES or N for NO.
Field
Num
Field
Name		Field
Type
Max Length
Required?
Case
Sensitive?
Options
Allowed
HTML
OK?
Description
16
auto_expire_saleFlag
1
Yes
Yes - UPPER CASE ONLY
Y
N
 
This flag tells the store whether or not to automatically expire this product's sale price on a specific date. Enter Y for YES or N for NO. When you enter Y, the store will use the date value in the next field to determine when to automatically change the product's on_sale flag from Y to N.
17
auto_expire_date Date
20
 
 
 
 
When a product is "on sale" and its auto_expire_sale flag is set to Y, this field is used to determine when to automatically change this product's on_sale flag from Y to N. This is a numeric representation of the web server's current time since "epoch" (00:00:00 on January 1, 1970 - also called Coordinated Universal Time or CUT - and is for the GMT zone). This field must be blank or contain a valid numeric date using only the numbers 0-9. Example: if this field contained the number 988754158, it would equate to: 05/01/2001 09:55 PM GMT. This field is only needed when the auto_expire_sale flag is Y.
18
show_add_to_cartFlag
1
Yes
Yes - UPPER CASE ONLY
Y
N
 
This tells the store whether or not you want the product's "add to cart" button displayed to the customer. Enter Y for YES and N for NO.
19
substitute_price_textString
1500
 
 
 
Yes
If you enter something in this field, the store will display this field's contents instead of the product's price. This field can contain properly formatted HTML tags.
20
additional_price_textString
1500
 
 
 
Yes
If you want the store to display information IN ADDITION to the product's price, enter it into this field. The store will display the contents of this field just under the product's price. This field can contain properly formatted HTML tags.
Field
Num
Field
Name		Field
Type
Max Length
Required?
Case
Sensitive?
Options
Allowed
HTML
OK?
Description
21
apply_sales_tax Flag
1
Yes
Yes - UPPER CASE ONLY
Y
N
 
If you want the store to calculate sales tax on this product when it's ordered by a customer, then use Y for YES. Otherwise, use N for NO.
22
vol_disc_activeFlag
1
Yes
Yes - UPPER CASE ONLY
Y
N
 
This flag tells the store if there are volume discounts active for this product. If this is set to Y, then the store will look in the remaining vol_disc... fields to determine how to display and apply volume discounts for this product. If this is N, then the store ignores the vol_disc... fields below.
23
vol_disc_displayFlag
1
Yes
Yes - UPPER CASE ONLY
P
A
 
This flag tells the store how to display volume discounts for this product. Use P to show them as a percentage, or A to show them as an amount.
24
vol_disc_on_sale_price Flag
1
Yes
Yes - UPPER CASE ONLY
Y
N
 
Volume discounts are normally applied ONLY to a product's "normal price". However, this flag can be used to apply volume discounts to the sales price too. Enter Y (YES) to apply the discounts to both the normal price and the sales price. Enter N (NO) if the discounts are only to be applied to the normal price.
When volume discounts are active for a given product, the vol_disc_qty_from#, vol_disc_qty_to#, and vol_disc_pcnt# fields below are used in conjunction with each other to form a matrix that is used to determine how volume discounts are to be applied. Please see the product's data entry page more information regarding how volume discounts work.
Field
Num
Field
Name		Field
Type
Max Length
Required?
Case
Sensitive?
Options
Allowed
HTML
OK?
Description
25
vol_disc_qty_from1Number
10
 
 
 
 
When active, enter a positive integer value containing only the numbers 0-9 and nothing else.
26
vol_disc_qty_from2Number
10
 
 
 
 
(same as previous field)
27
vol_disc_qty_from3Number
10
 
 
 
 
(same as previous field)
28
vol_disc_qty_from4Number
10
 
 
 
 
(same as previous field)
29
vol_disc_qty_from5Number
10
 
 
 
 
(same as previous field)
30
vol_disc_qty_from6Number
10
 
 
 
 
(same as previous field)
31
vol_disc_qty_from7Number
10
 
 
 
 
(same as previous field)
32
vol_disc_qty_from8Number
10
 
 
 
 
(same as previous field)
33
vol_disc_qty_from9Number
10
 
 
 
 
(same as previous field)
34
vol_disc_qty_from10Number
10
 
 
 
 
(same as previous field)
35
vol_disc_qty_from11Number
10
 
 
 
 
(same as previous field)
36
vol_disc_qty_from12Number
10
 
 
 
 
(same as previous field)
37
vol_disc_qty_from13Number
10
 
 
 
 
(same as previous field)
38
vol_disc_qty_from14Number
10
 
 
 
 
(same as previous field)
39
vol_disc_qty_from15 Number
10
 
 
 
 
(same as previous field)
Field
Num
Field
Name		Field
Type
Max Length
Required?
Case
Sensitive?
Options
Allowed
HTML
OK?
Description
40
vol_disc_qty_to1Number
10
 
 
 
 
(same as previous field)
41
vol_disc_qty_to2Number<