This the SKU number for an item. This can be any combination of numbers and characters. It is for ASP display purposes and database relation.

All punctuation marks and spaces are illegal except for hyphens "-"

This value is used for display in ASP text associated with BuyObjects, Display in Shopping Basket drop down list, and will be included in acknowledgement e-mail and HTML copies of orders. This is the value which will also appear in product browsing search results and showcase pages. The names should be three characters in length or more.

Though legal, for appearance reasons this column should not contain any punctuation marks and abbreviation marks including '&' while double quotes are illegal in all entries.

Older versions of the database support 40 character Fullnames while the latest version of the database supports 255 character fullnames.

This is site relative URL to a picture (jpg/gif) of the product. This entry should not begin with a '/'. This is typically a full scale image. This field is used only by ASP logic to display a picture and by the Database Integrity testing tool.

This field is option. If left null, the e-store framework will run in No-Format mode for this item.

Picture files can be uploaded using a tool found on the Items Admin Page.

The base directory location must be set for the Integrity tool to function correctly. This is the base address of the website AND not the base address of the image file directory. Also see Special Case tool option -O for possible configuration ideas if this database column is to be used to hold thumbnail displays of items.

If you will have a large number of product images, it is recommended that you collect these images in a single subdirectory off the /en/images/ subdirectory. For example: /en/images/productshots/.

If all product images are not the same size then all images must include additional information in the ProductFileA, ProductFileB, & Logo columns. This information tells the system what size the file is…

Example:

Image file named: mycat.jpg
Example for images all the same size:
ProductFileA = en/images/mycat.jpg
Example for images with different sizes:
ProductFileA = "!200!300!en/images/mycat.jpg"
*where 200 = width and 300 = height

This is a site relative URL to a picture (jpg/gif) of the product. This entry should not begin with a '/'. This is typically a thumbnail image. This field is used by ASP logic to display a picture and by the Database Integrity testing tool.

Picture files can be uploaded using a tool found on the Items Admin Page.

The base directory location must be set for the Integrity tool to function correctly.

If you will have a large number of product images, it is recommended that you collect these images in a single subdirectory off the /en/images/ subdirectory. For example: /en/images/productshots/.

If all product images are not the same size then all images must include additional information in the ProductFileA, ProductFileB, & Logo columns. This information tells the system what size the file is…

Example:

Image file named: mycat.jpg
Example for images all the same size:
ProductFileA = en/images/mycat.jpg
Example for images with different sizes:
ProductFileA = "!200!300!en/image/mycat.jpg"
*where 200 = width and 300 = height

This is a category that this specific product fits; for example: Frozen Strawberries might fall into the fruit category. This is used to create ASP generated product indexes. This is a required columns for e-store framework.

Entries in these columns in the Items table will control how your products appear in the browsing pages and search results. Using these settings control how products are grouped and displayed.

Category Column in the DB will be used to control the Category Drop down list. Place product group descriptions or names into this list (i.e. juice, candy bars, etc.). All items with matching ENTRIES will be displayed when that entry is selected from the drop down list. One entry per record row.

Though legal, for appearance reasons this column should not contain any punctuation marks and abbreviation marks including '&'

A number of hidden sort characters can be reseved and setup to control the order that categories appear in if normal alphabetical sorting will not yield the desired results.

One Item Product Categories: A Category name can contain the resevere character "@" which flags the category as containing only a single item. If this flag is present, the e-store framework will go straight to the showcase page from the category page. This flag can be placed anywhere in the name but it is recommended that it be placed at he end of the name so that it does not effect sorting. For information see: One Item Categories

This is a more specific category that a product fits; for example: Frozen Strawberries might fall into the fruit category and the frozen fruit subcategory. This is used to create ASP generated product indexes. This is a required columns for e-store framework.

Entries in these columns in the Items table will control how your products appear in the browsing pages and search results. Using these settings control how products are grouped and displayed.

Sub-Category DB column will be used to control a Subcategory Drop down list. Place Subcategory names into this list.

Though legal, for appearance reasons this column should not contain any punctuation marks and abbreviation marks including '&'

A number of hidden sort characters can be reseved and setup to control the order that subcategories appear in if normal alphabetical sorting will not yield the desired results.

This column contains information used by the system to control product browsing and may also be used for option controls:

Basic Syntax:
##column width override!column height override
	  
All columns must be present OR the trailing columns must be null. 
Any other contents will be ignored.

Example:
informationlink = ##3!20 will yield 3 columns x 20 rows
informationlink = ##3! will yield 3 columns x undefined rows

Syntax	Value/Result
column width override	If set to any value other than zero this will set the number of columns displayed in the current product matrix (this value overrides the e-store framework configuration). At the category and subcategory level this value has not effect. It only affects the matrix once you have drilled down to the product level. The first product encountered will set the results for all products in the list.
column height override	If set to any value other than zero this will set the number of rows displayed in the current product matrix (this value overrides the e-store framework configuration). At the category and subcategory level this value has not effect. It only affects the matrix once you have drilled down to the product level. The first product encountered will set the results for all products in the list.

This field controls fulfillment. This fulfillment can be either: digital (payload) fulfillment or shippable product fulfillment handled by one of SendSafes fulfillment subsystems.

For digital payload fulfillment, this field is the physical location of digital payload products which are downloaded after purchase. This is not a URL. It is a physical file location that must accessible by the robot. If this field is prefaced with an '@' sign this designates a digital fulfilment plug-in is to be used instead of SendSafe's integrated digital payload system.

This field can contain more than one or more file specification separated by commas. It can accept wild cards and special operators. For more information see Digital Payloads.

For shippable product fulfillment, this field is prefaced with an '#' sign, this designates that this item is to be fulfilled using one of the SendSafe shippable product fulfillment subsystem

This field when used for internal digital payload construction is used in one of two ways to collect the files that will make up a payload (see Option A and Option B). In  Option A this field must contain a complete path and filename (with optional wildcards). In Option B this field must contain only the filename (with optional wildcards).

• This column is relational to {Coupon} Table's column [ValidProductTypes]
• This column is used for category quantity pricing i.e. all products of type XYZ are $9.95 (see also DiscountsPlan)

This column can be expanded to 40 chars in length and still be supported by the import tools and the rest of the system. If quantity pricing is not used then this column can be made even longer. For quantity pricing relational links are built between producttypes and pricing keys which are stored in storeconfig.keyword char(40).

Examples of entries in this column are similar to category, and came be things like: games, paperback books, accessories, etc.

Note: Products can be flagged as Mutually Exclusive so that nothing else can be added to a shopping basket if this product in it... for more info see MutuallyExclusive

The product type can contain reserved keywords which further define the handling of this item. These reserved keywords are defined by:

Application("CustomizerItemTag") = I-CUSTOMIZER
Application("QuoteItemTag") = I-QUOTE
Application("RMAItemTag") = I-RMA
grouped quantity pricing = {1}
fixed quantity pricing = ##
deplexing lineitem = $DF$
DRM Unlock Code = $DRM$
Display this agreement file = $DDA=abc$
Flags item as a listing = $LST=1$ ... $LST=4$
Disable Add-to-WishList = $NW$

The product type can contain reserved syntax which defines the handling of this item. The reserved syntaxes are:

Product selection by skin: Bracket the skinname(s) with '/slashes/' if you what this item displayed for a specific skin. You can have multiple skins selected for an item: /skinname1/skinname2/skinname3/. It is recommended that this syntax be appended to the end of the productType.

Product selection by storefront: Bracket the storefront names(s) with '/slashes/' if you what this item displayed for a specific storefront. You can have multiple storefronts selected for an item: /store1/store2/store3/. It is recommended that this syntax be appended to the end of the productType.

This is a set of keywords which are searched by SQL database query to retrieve similar items. All keywords should be delimited beginning and end with '/' characters to allow for simplified SQL searching for whole words. This entry is used by the optional e-store framework when performing standard product searches.

See for information on how the optional e-store framework uses this DB column.

Keywords can also be used for search restrictions

Examples of what this field should look like:

keywords = /apple/fruit/red/

Rules:

1. bracket all keywords in between /..../
2. Standardize on not allowing plural words, only singular words

Example SQL:

Select ItemCodeId, Description, Keywords from Items WHERE keywords LIKE '/%apple%/'

Keyword searching can be customized to include context searching of keywords. The key words can be setup with syntax like: /Mapsco=A345/Wallpaper=Green/. The search system is then customized to provide searches by Mapsco or Searches by Wallpaper color. Contact CPrompt for more details on customizing the e-store framework to support context searching.

This field indicates whether sales tax can be changed for this item and which sales tax table to use. The determination if sales tax is charges on a specific ordered item is also dependent upon the tax configuration of the robot.

• If this value = 0 then no sales tax is charged for this product
• If this value = 1 then the base sales tax table is used
• If this value > 1 then one of N suplimental sales tax tables is used

This is the default shipping mode / method applied to this item. The Fixed/Locked entries codes are for restricting shipping methods on an item by item basis: See shipping default methods and restrictions for more details.

BASIC Default METHODS:
0 = Saturday, 1 = NextDay, 2 = SecondDay, 3 = Ground

FIXED/ LOCKED METHODS:
20 = Saturday, 21 = NextDay, 22 = SecondDay, 23 = Ground

FIXED/ LOCKED OR HIGHER METHODS:
30 = Saturday, 31 = NextDay, 32 = SecondDay, 33 = Ground

FIXED/ LOCKED OR HIGHER WITH GEOGRAPHIC LIMITS:
DefaultShipMode => 1000 THEN Geographic data from table.

Enter an integer value only or Enter NULL for no default. If no default (null) then the storefront shipmode default will apply.

This value can be set to <none> (which disables fixed shippig cost), or a dollars amount that over rides all other shipping cost calculations options, or a '+' prefixed dollar amount which will be added to the normal calculated amount. FixedShipCost is only used if you want to charge a fixed amount or add a surcharge for the product's shipping.

For Fixed cost shipping enter a dollar price (i.e. 5.95 for $5.95). If you want no shipping charges applied for an item then set the fixed shipping cost equal to zero (0). For example if you have a downloaded item for which you do not want shipping costs charged, then setting the FixedShipCost = 0 will accomplish this for you.

Any amount entered in this field will over ride or be added to exception shipping costs table, Zone Shipping costs table, and Ship by Weight & Zone.

The attributeList column serves two different functions:

1. It is used to group products for display in the (optional) e-store framework code's showcase page in the e-store framework.
2. It is used to create a dropdown list of attributes managed by BuyObjects (this function is legacy and not available in the e-store framework without customization).

Grouping Products - Each set of products to be grouped must have exactly the same code-string entered into this field. For groupings to work the control variable attributeGroupingEnabled in the optional e-store framework code must be set = true. Commas are illegal in this entry field.

For grouping of products to work, the "Enable Attribute Edit" option in the storefront config admin page must be set false (0).

Creating Dropdown Lists - Attribute string for this item. This is a legacy function better handled using the e-store framework and Free-Form-Parameters (FFP). This is a list of all valid attributes for this item separated by commas. An example would be: "Plain,Chunky,Extra Chunky". This attribute list is displayed in the Basket drop down list and selected BuyObjects. This value is used to generate ATTRIBUTE parameter for BuyObjects using ASP. The attribute list is also optionally used by the digital payload subsystem in collection of product files. For atrribute lists to work, the "Enable Attribute Edit" option in the storefront config admin page must be set true(1).

AttributeLlist would be used for products where you want the SKU and the price to be the same regardless the color or size or some other attribute. Leave this field empty for all items that do not have an attribute list.

This column should be set to a valid date when a new item is added. This field can be used by ASP list building code to display a list of all new items or it can be used as a parameter for SQL driven product searchs.

This field will also control the display of items in the (optional) e-store framework code. If the date is null then the product will not be displayed in search or browsing results (with the exception of the showcase page). The product can still be purchased (even though it is not displayed on the search and browsing pages). For this dateAdded control to work in the e-store framework code the control variable dateAddedActivationControl = true.

If you only want to restrict display of the product during searches, then used the searchRestrictions value instead of dateadded.

This field is used to assign price discounts to specific preferred customers (or club or group buying plans). The discount can be applied to ether all items or items of a specific type of items when used in combination with e-coupons see: RequiredDiscountPlan.

This field can be automatically set to a value defined in the MIMarketingInfo FFP (see discount pricing for details.

This field can be automatically set to a value configured in the storefront.config file when a specific item is purchased (i.e. the item being purchased is a Discount club membership or other programs). This automatic setting is controlled by the CLUB MEMBERSHIP ITEM key word in the storefront.config file.

1. Discounts are applied through e-store framework product browser.
2. Discounts are applied through the wishlist page.
3. Discounts are applied through the past purchase reordering page.
4. Discounts are often applied by enable/disable of the SpecialPrice field (this is how the product browser works).
5. Discount plans can be optionally used to control automated issuing of e-coupons (see also: RequiredDiscountPlan)
6. Discount plans can be used to control selective application of "Buy 1 Get 1 Free Sale" pricing)

You cannot mix SpecialPrice discount with quantity pricing and promotional sale pricing. SpecialPrice discounts will be overridden by either of this alternate pricing schemes. Percent off can be used with quantity pricing.

If coupons are used in combination with a discount pricing plan then the two discounts are combined together. First the discount plan will be applied to the item (this price will be displayed in the basket). After the customer submits the order, discount coupons will be checked and applied to the order further lowering the price. 

For global percent price adjustments, the standard format for this field is:

• "PERCENT=nn" where nn is the percent discount to apply (i.e. 0.10 = 10%)
• "SPECIALPRICING" where you which to use the values in the SpecialPricing DB column.

• Automatically perform "coupon handouts" via e-mail to customers that have not been back to the store in N months.
• To trigger automatic purchases of an item. For example the "Book of the Month" club. Where a specific product is automatically sent and billed to a customer if they do not make a book purchase each month.

Entries in this string are are comma delimited keywords. Keywords currently defined by SendSafe are listed below.

This code can be dynamically entered as the DEALERID parameter to BuyObjects using ASP html. All BuyObjects support this optional DEALERID parameter. The dealer code is usually selected from data contained in the customer record field AssignedDealerID and is generally regional i.e. Arizona salesman or Dallas Salesman codes.

This field may also be used in an SQL query that is generating ASP reports. This would provide an alternate means of listing dealers using a code that is familiar to the accounting department.

This field holds a coupon number if one was used on this Order. This is the CouponNumber which is the lookup key for the {Coupon} table.

Coupon pricing discounts are calculated in the Robot. Coupon discounts do not show up on the web page. Text should be added to the checkout page and the thank you page that indicates the customer will see the coupon adjustments to the price in the acknowledgement e-mail (issued by the robot).

This column is set to various status levels by the SendSafe Robot and (or) the ASPGUI. In the case of the ASPGUI this column also displays the status of orders that have not yet been submitted (i.e. the contents of unsubmitted shopping carts).

See also special order types.

Typical ASPGUI mode values are: 

This is a shopping basket under construction
   {UNDER CONSTRUCTION}

This is a completed order
   {COMPLETED}

This is an order which has been submited and accepted, but is not complete (see flags below - typically this is an RMA).
   {REQUEST ACCEPTED}

This is an order that has been submitted, processing by the backend Robot is pending
   {SUBMITTED PENDING}

This is a QuickBuy submitted order, processing by the backend Robot is pending
   {QB SUBMITTED PENDING}

This order contains wishlist items
   {WISHLIST}

Deleted order
   {DELETED}
   *Will not be counted in reports

This order contains preferences which are used for automated form completion for customer orders
   {PREFERENCES}
   *Will not be counted in reports

This order contains subscription preferences which are used for shipping addresses for subscription orders
   {SUBPREFERENCES}
   *Will not be counted in reports

The ASPGUI mode message will also include semicolon delimited additional status messages; exampled are:

• QBORDER - For QuickBuy submitted orders
• GIFTORDER - For gift list orders
• RMA - For RMA Credit orders (See also: RMA Processing)
• BACKORDERED - This flag is present if any of the lineitems in the order are flagged in the shipmethod column as backordered.
• RetryStatus=xx - For Orders that had problems and were (or are being) retried due to backend system failures. Retry count is a down counter which starts at 20 (EMGSTRANSACTION_RETRYCNT) and fails when count = 0.
• Coupon Status - For an order that included a coupon.
• CaptureAccepted - Charge capture has been completed on order which where mauthonly (charge holds)
• MAMSelected - Multi-Address-Mode for this order has been selected by the user. This flag is a temporary and may be removed during final processing of this order.

Legacy Information: Typical JavaGUI mode values are:
RECEIVED, PROCESSING, SHIPPED, CLOSED, CANCELLED.

This field is automatically field in when automated credit card processing is enabled. This field contains Approval, declined, or void plus the results of any AVS code.

Examples:
Approved: 21523PNI PNREF=V534421 (AVSC=A)
Approved: Nothing was charged: coupon or item was free.
Declined PNREF=VBVA60543252
Void: PNREF=VBVA60543252

This field may also contain:

1. AVS Information (Address Verification Codes)
2. PNREF Transaction Id Numbers (used by VeriSign)
3. (CHARGEHOLD) flag indicates this is a charge hold and not an authorize + capture.
4. CaptureAccepted + Approval code for capture.

This code is used to give sales credit to a specific dealer or salesman for this order. 

This code is used to give sales credit to a specific dealer or salesman for this order. 

Typical values are: 
This order has been completely fulfilled.
   {COMPLETED}

The field can also include semicolon delimited additional status messages; exampled are:

• E-RECEIPT PROC: - E-Mail Receipt Sent - followed by status: SENT or FAILED
• PAYLOAD - This order includes a payload
• FULFILLED - Order has been fully processed (not valid for B2B using plugin)
• RMA COMPLETE - RMA has been fully processed
• EXPORTED - The record has been exported to an Integrated Accouting system

See also: B2B Processing and RMA Processing

See also: B2B Processing

0 - Order processing has been suspended due to a fatal error
1 - Order pending Order Post Processing B2B or In-house fulfillment is pending
2 - Order Fulfillment transmitted B2B or In-house charge capture is pending
3 - B2B has responded with order shipped or In-house charge capture is complete
4 - Ship Acknowledgement e-mail (order fulfillment is complete)
10 - 17 RMA Processing in progress (see RMA Processing)
18 - RMA complete
19 - RMA items set for resale

**null indicates this order is not being processed by an automated fulfillment system.

See also: B2B Processing and RMA Processing

See also: B2B Processing and RMA Processing

This column is filled in when an RMA is complete OR an order has been cancelled (credit or void)

See also: RMA Processing

See also: B2B Processing and RMA Processing

If using the e-store framework, this value will contain an abreviated displayable string which contains the first N FFP values. This string is displayed in the basket and can be optionally used elsewhere. This string is limited to 60 chars and therefore may not contain all FFP parameters.

This string may also contain the keyword "{GIFTLIST SEED}" if this line item is a gift list entry.

This string may also contain an alternate price for delayed purchases if set to anything other than empty OR "none" (the ascii word).

For custom coded pages, this field is populated by the string entered into the ATTRIBUTE parameter when calling addItemToCart() or entered into the ATTRIBUTE form field when posted to addBasket.

If the e-store framework is not used AND instead widgets which support the attribute list dropdown function are used then this value is the Attribute value (from the attribute list) that the customer chose for this product. This field will be empty if no attributes exist or where chosen.

This is the shipping mode chosen by the customer for this item. These values are the same as the default shipping mode.

After fulfillment this field may contain the ship status (i.e. Carrier + Tracking number) for the items if B2B is setup or the store manaually updates this field (See also: B2B Processing) Example:
 SecondDay (1Z90E13W0244261645)
 Ground (1Z90E13W0343221214).

If you are adding tracking information manually, it is very important to always place parentheses around the the tracking number; failure to do so may result in charges not being captured and ship confirmation emails not being sent. The system automatically recognizes the carrier based on the tracking number AND creates the appropriate links to check ship status on the customer's order status page.

Multiple tracking number within a single shipping field is allowed. The syntax is: (TRACKING #)xN where N is the number items assigned to this tracking#. Each tracking number entry + quantity is delimited by a space.

i.e. (TX737847438)x5 (TX263537728)x10 ==> 5 items on this tracking#TX737847438 and 10 item on this tracking#TX263537728

If an item is backordered, it will contain the word "(BACKORDERED)" instead of a tracking number. This field is case sensitive.

This entry may also contain messages which note shipping exceptions. The note will contain information describing the exception handling that occurred on this item. The message is a User Configurable custom message. This field will hold up to 100 characters.

For normal order that have not been fulfilled, this field will contain the date that the lineitem was added to the shopping cart. It can be used to ascertain when an item was added to the basket vs. the time the basket was submitted.

For order that have been fulfilled via the B2B or Manual Fulfillment, this field will contain the date that the lineitem shipped.

For RMA return orders, this field will contain the date and time that the items where recieved back at your shipping dock.

This field is used for lineitem descriptions. This field is displayed on ascii emailed receipts instead of the items fullname.

This field contain a duplicate of the items fullname plus "where appropriate" additional information about this line item.

For subscription refills this line will include the transactionid# of the original (parent) subscription order (labeled as an so#).

For Sale items where the sale price was a result of a SendSafe controlled "buy one get one free" sale, this field will contain a prefix-string = "Sale Priced /" - example: "Sale Priced / Extra large green shirt." This sale price prefix-string is used by the robot to identify lineitems which have recieved sale pricing.

This field may also contain desposition codes (keywords) defining the condition of the item if this is an RMA Order (See also: RMA Processing) or template identification strings from Bid Templates

NOTP = No PTL

PTL = PTL

MULTIADDR = Multi-Shipping-Address mode

GIFTLIST = This item is part of a gift list

LIMCC = "CAV" (see below)

LIMEC = (see below)

PLSTINS = Line Item entered from PurchaseList page

TSTDUP = item has been checked for prior orders AND prior orders were found. A warning will be displayed.

{BXD}{TTX}{VVX} = RMA Price Adjustment Flags

PLSTINSZERO = Line Item entered from PurchaseList page with zero price (redownload).

ICRMABANDONCARTTICKLE = This is an optional flag which is sometimes used by the I-CRM system to make are lineitem as tickled (i.e.the customer recieved an I-CRM e-mail of some type).

LIMCC limits the types of payments allowed for this order. The flag can be sent in any lineitem by outside code at anytime. The flags are entered as a single string without delimiters and can be set to any combination of:
C = "COD Payment"
A = "American Express"
D = "Discover"
M = "MasterCard"
V = "Visa"

LIMEC can be used to disable E-Coupons for the current order. The flag can be sent in any lineitem by outside code at anytime and it will effect the entire order.

Order flags are often set in BuyObjects (see buy object sample page). The flag is set by POSTING the form field element "ORDERFLAGS" set to the value for the flags. LIMCC can also be set in prior purchase pages by using the ( SetLimCCFlags "VD") subroutine call in the parent page. The Prior Purchase pages will use the order flags from the most recent order. So there is often no need to set any order flags in this page.

• Gift card messages.
• FFPs Comment elements.
• Custom comments added programmatically via FORM.COMMENT field manipulation (SendSafe does not use this option internally)

Conflicts between Gift card messages and other messages exist. If FFP Comments OR Custom Comments are added to this column, these message types will prevent a gift message from being saved to this column. It is not advisable have gift items include FFPs with :Comment: elements.

All FFP comments are tagged with an HTML invisible code of: <!-SYSCOMMENT-> at the beginnning of the comment field and at the end of the system comment field (see also: vbTag - SYSCOMMENTTAG). This tagging is used to prevent overwriting by gift messages.

Note: For customer entered comments please see the [Find Order Notes] button on the order admin page.

This field is a unique code number that identifies each {Coupons} record. This number can be an combination of characters and numbers. This coupon number must be a minimum of 8 characters and no more than 100 characters in length. This number can only exist once in a database.

If this field contains the reserve word prefix "QBC-" then this is a QuickBuy Coupon.

If this field contains the reserve word prefix "AEC-" then this is a Automated E-Coupon Credit line.

For E-Credit lines, this number must be 10 numeric digits (0-9) or more depending upon the configuration of the system.

It is advised to never change a coupon's "value rules" since this could have an unexpected effect on previous orders that used this coupon.

If BuyN equals zero and percent discount equals zero THEN the coupon is worth the dollar value specified by the RemaingDollarValue.

If either of the values BuyN and (or) percent discount are set THEN they control the value of the coupon with RemaingDollarValue setting an upper limit (unless TotalDollarValue value is -1 THEN there is no upper limit).

This value cannot be used in combination with other discounts, if this coupon is to be a simple $x.xx off the order price (including taxes & shipping).

E-Coupons with a TotalDollarValue value = -1 are not limited by the RemainingDollarValue and are "Unlimited Cart Blanche" coupons.

Specific dollar value coupons are not possible if the coupon is to be a "shared coupon" used by any number of people. Shared coupons can only be configured with either Buy X get Y Free or percent off.

Typically this value is initially set to the same value as TotalDollarValue. This dollar amount is the actual control over how much value a coupon has over its lifetime of use. This value will override TotalDollarValue resulting in a coupon worth either more OR less than TotalDollarValue.

This field is automatically debited by SendSafe as the coupon is used. This field allows the coupon to be used on more than one order until its value has been used up. Its value is used up once this value equals zero.

E-Coupons with a TotalDollarValue value = -1 are not limited by the RemainingDollarValue and are "Unlimited Cart Blanche" coupons.

This type of coupon is only applied to individual orders one at a time. As such the discount cannot be spanned across multiple orders. 

This value cannot be used in combination with other discounts.

This form of discount is only valid when the ValidateProductTypes list has been filled out with a single product type. Results will be unpredictable i more than one product type is in the list.

This coupon is treated in terms or tax & shipping the same as a Fixed Dollars Amount coupon AND will cause the price of this item to be deducted from the total amount of the order (after taxes & shipping). i.e. shipping and tax are not included in the value of the coupon.

VALUE RULE: This field is used to create a Buy N get X free type of coupon. This value indicate how many free items can be ordered once N items have been purchased. Leave this value set to zero if this coupon has specific dollar value and not Buy N get X free. This coupon is only valid for a single order and cannot be spanned across multiple orders.

The value of GetX cannot exceed the value of BuyN (i.e. BuyN=1 and GetX=2 is not allowed and will result in coupons which will not operate as expected

This value cannot be used in combination with other discounts.

Please note: There is a 48 hour grace period applied to all coupon end dates.

This is a list of valid items for this coupon. This list can contain items.productTypes, items.ProductCodeId, items.keywords, or a Quota-List. Only one type or ProductCodeId is valid for a given coupon if BuyX GetN free is used. For other coupon this list may contain multiple product types or ProductCodeId separated by a comma OR a single Quota-List. This column is case sensitive; productypes or keywords must match in case.

ProductCodeId entered into the list must be enclosed in angle brackets i.e. <17283>.

keywords entered into the list must be enclosed in slashed i.e. /word/. If the keywords column contains the SKU (as recommened) then coupons can be limited by product sku via the keyword lists.

Quota-List entered into the list by prefacing the list name with a pound-sign (#) i.e. #MYQUOTALISTNAME.

Lists can mix all the methods of item identification except quota-lists i.e. This example includes productTypes, ItemIdCodes, and keywords:

"HOME ELECTRONICS,CAR AUDIO,<8>,<199>,<82>,/sku12345/,/books/"

WARNING! DO NOT Leave this database column empty or NULL.
If you want the coupon to be valid for all products types enter the string "<any>".

In all cases except Buy One Get One Free coupons, if this value is set to anything other than zero, it is used to calculate the discount with an upper limit set by TotalDollarValue & RemainingDollarValue. This value is not valid for IHC e-credit line accounts (set to 0 or 100 for all IHC accounts).

This is the e-mail address of the person that this coupon was issued to. This entry may be left blank. If this entry is filled in during coupon creation then the e-coupon will be automatically e-mail to the recipient during issuance.

For E-Credit lines this column should be blank unless QuickBuy E-Coupon behaviour is desired. Filling in an email address will result in the credit line coupon showing up in the e-coupon dropdown.

Template coupons should never contain a coupon number.

**AutoCoupon coupons are implicit templates and must also have CouponTemplate Check marked.

Example Entry: <1288>,<9378>,<123>
would match any of the ItemCodeID Codes: 1288,9378, or 123.

A single customer order will trigger issuing of all matching e-coupons for this data column and AutoCouponProductType.

Example Entry: <BOOKS>,<BIKES>,<BAGS>
would match any of the Product types: BOOKS,BIKES, or BAGS.

A single customer order will trigger issuing of all matching e-coupons for this data column and AutoCouponProductId.

This column contains a discount plan that the customer must belong to in order for an auto-coupon to be issued to them. This entry can be set to null to disable discount plan checking.

In all cases except "ECREDITLINE" e-credit line flag, this value does not restrict usage of the coupon, it only controls automated issuing of an auto-coupon.

This field must be set to "ECREDITLINE" if this coupon is used for IHC Credit Lines or an E-Coupon Credit Line (automated or otherwise). Failure to set this correctly can result in the Credit line account being used in the coupon entry field with different treatment of sales tax and differen display.

This column is used to store/retrieve custom identification information about a coupon. It is often used in AutoCoupon templates as a means of tagging e-coupons that were issued from that template.

This field is used to link coupons/credit lines to customer accounts for AEC and QBC coupons.

This field can define a coupon as a single use GLOBAL coupon. If this field is set to the reserved word "GLOBALSINGLEUSE" then this coupon will be limited to one use per customer. For BXGY coupons, this usage limitation will restrict redemption to a single eligible item in an order.

This field is used as the security code for IHC charges which use E-Coupon based IHC E-Credit lines (leading zeros are illegal). For security reasons, this codedescriptor checking occurs ONLY in the backend parts of the system.

Primary key for SID Record.

This is the customerID which identifies the account which will recieve access permission.

This identifies the type of account which is being granted permission. Set to 1.

This is a list of Admin pages which this user will have permission to read (view). The page names must be bracketed with '/' slashes
See for more information

This is a list of Admin pages which this user will have permission to write (modify and delete). The page names must be bracketed with '/' slashes
See for more information.

This is the index key for the record which is being controlled.

See also: Admin Record Locking Operation

This is the name of the primary table in which this record locator is located (first 20 chars only).

This code identifiys the type of lock:

• 0 = Automated lock
• 1 = Manual lock
• 3 = Permanent lock

This is the customerID which has last locked the record.

This is the time the record was last locked.

This is an automatically assigned number. It is used to establish the relationship between an {Order} record and its subordinate {OrderLineItem} records and this {CreditCard} record (see Customer Order data flow for more information).

This is the Credit card number. This number is stored in this separate database for security reasons. This field is automatically field in if CyberCash, IC Verify, or some other automated credit card processing is enabled. 

This is expiration date. This field is automatically field in if CyberCash, IC Verify, or some other automated credit card processing is enabled. 

ID Code for event:

• ecCIDLogin = 1
• ecBadCID = 2
• ecLockoutBadCID = 3
• ecLockoutBadPID = 4
• ecLockoutManual = 5
• ecPIDLogin = 6
• ecBadPID = 7
• ecPIDlogout = 8
• ecLockoutMsgDisplayed = 10
• ecLockoutBadURL = 11
• ecBadURL = 12
• ecFatalCodeAlert = 100
• Admin Record Added = 200
• Admin Record Modified = 201
• Admin Record Deleted = 202
• Admin Record Accessed = 203
• ecDownload = 503
• ecPwdRecoveryOk = 1000
• ecPwdRecoveryFailed = 1001
• ecPwdRecoveryLockout = 1002
• ecEmailAddrChange = 2000
• ecCustomerTracking = 10000
• ecVistorTracking = 10001
• ecVistorPageLoad = 10002
• ecVistorPBrowse = 10003
• ecVistorLBrowse = 11003
• ecVistorAddToCart = 10004
• ecCustomerPageLoad = 10012
• ecCustomerPBrowse = 10013
• ecCustomerLBrowse = 11013
• ecCustomerAddToCart = 10014
• ecCustomerClickCount = 10015
• ecVistorClickCount = 10016
• ecSQLBLoadMetric = 10017
• ecSQLLLoadMetric = 11017
• ecPrizeGiveaway = 20000

See also database maintenance

Issue Coupons = 1
E-Mail Password = 2
WatchDog = 3
Run Batch Program = 4
B2B E-Mail Relay Digital FulFilment = 5
B2B FulFillment = 6
B2B FulFillment Order Shipped E-Mail = 7
and many more internal jobs

• Issue Coupons = 1
• E-Mail Password = 2
• Watchdog (Woof) = 3
• Run Batch = 4
• E-Mail Relay = 5
• B2B = 6
• E-Mail From FulFillment that order has shipped = 7
• RMA Return Materials (container) Shipped = 8
• RMA NAG = 9
• RMA Checkin = 10
• RMA Disposition = 11
• Pricing Matrix Import Spreadsheet Prcessong = 13
• EMBroadcaster Job = 14
• EMBroadcasterJobTracking Job = 15
• Customer Import Job = 16
• Dealer Import Job = 17
• Coupon Import Job = 18
• Items Import Job = 19
• SubscriptionRefill Job = 20
• RMA ATO Accept = 21
• Order Line Item Import Job = 22
• Update CC# Job = 23
• Analyze bandwidth files Job = 24
• Replication Job = 26
• Export Job = 27
• Product EMBroadcaster Job = 28
• reserved = 29
• Encryption Repair Job = 30
• DB Test Job = 31
• StoreConfig import Job = 32
• I-CRM Job = 33
• Listing Repair Job = 34
• Generic SQL Job = 35
• UPS Zone File import Job = 36
• UPS Price File import Job = 37
• EventLog Archive Job = 38
• B2B FORMAT 1900 Fulfillment Job = 39
• B2B FORMAT 1900 Order Shipped Processing Job = 40
• In-House FulFilmment Processing Job = 41
• Voider Processing Job = 42
• GiftList Processing Job = 43
• DB Maintenance Job = 44
• Trigger Order Job = 45
• Delayed Item Qty Adjustment Job = 46
• Items table cloning Job = 47
• Blog Maint Job = 48
• Send email job = 49
• Total DB Export / Backup = 50

Note(s):

1. E-Mail Password Jobs are queued automatically when a customer requests that their lost UserId & Password be e-mailed to the address on-file.

{Run Once}
{Run Once At MM/DD/YYYY hh:mm:ss} a date and time the job will run ONCE
{Run Date MM/DD hh:mm} a reoccurring date and time when this job will run (each year)
{Run Every N hourofday} where N = hour of day 0 - 23 hour (each day)
{Run Every N day} where N = Day of Month 1 - 31
{Run Every N minutes} where N = Minutes

Note(s):

1. For jobs that are set to {Run Once} or {Run Once At xxx}; after the job executes sucessfully the job will deleted from the queue. If the job does not execute successful it will not be deleted, but instead marked as disabled.

0 = Not Enabled (Runnable)
1 = Enabled (Runnable) for Primary Robots
2 = Enabled (Runnable) for Backup Robots
3 = Enabled (Runnable) for Primary & Backup Robots

0 = Okay
Any other value = error code

Name of the statecontrol key which defines the information stored in keyvalue. See also: ZDI and EDI URL Parameters and Operation

1. svnWorkingTransactionID - The transactionid for the order under construction
2. svnlastEditedshiptoAddressId - Last edited ship address (used by multiple shipto address orders)
3. svnTempByPassLogon - When set prevents additional login requests from being displayed in the shopping cart.
4. svnCustIP - CustomerID saved during login
5. svnMultiaddrState - state of the multi-address flag (yes/no is this order a multiple address order)
6. svnItemsAddedViaPurchaseList - yes/no were items added to the cart from the page purchase (reordering) page.
7. svnLastEditedLineItemId - LineItemId of the last item edited in the basket
8. svnBURLAddBasketRetAnchor - return URL for the page from which the addbasket page was loaded
9. svnBURLReviewBasketRetAnchor - return URL for the page from which any basket page was loaded