UIEE.com Universal Information Exchange Environment
Home Specification Tables Products Contact
UIEE Definitions
Table 1: BOOKS Token Set
Required fields for parsing the BOOKS token set are the User Record Number (UR), Title (TI) and Price (PR) for For-Sale and Realization database records. (PR) is not required for Wants, For-Trade, or Remainders, but may be included. The Author (AA), Language (LG) and Weight (WT) fields are optional, but are strongly recommended for all record types regardless of content.

ID

Length

Field

Notes

AA 128 Author Represents the author's name as it appears on the Title page. Name imprint (L-F-M or F-M-L) defined by the sending software. L-F-M is standard and is therefore preferred.
AC 128 Compiler Optional field provided for compatibility. If present, appended to Author preceded by the term: "Compiled by"
AE 128 Editor Optional field provided for compatibility. If present, appended to Author preceded by the term: "Edited by"
AF 128 Forward Optional field provided for compatibility. If present, appended to Author preceded by the term: "Fwd by"
AI 28 Illustrator Illustrator's name if present, or a reference to the presence of illustrations ("Illustrated", "112 color illustrations," etc).
AN 64 Annotation Private data field, normally contains a Date/Time stamp but may contain text.
AP 28 Photographer Optional field provided for compatibility. If present, appended to Illustrator preceded by the term: "Photos by"
AT 128 Translator Optional field provided for compatibility. If present, appended to Author preceded by the term: "Trans by"
BD 14 Binding Simple, brief statement of binding type ("Hardbound," "Paperback," etc).
BN 13 ISBN Code Validated International Standard Book Number (10- or 13-char format supported).
CI 11 Catalog No Private data field. Used to store user-defined SKU or catalog number. Note: Some systems map the CI field to ISBN. This is not recommended unless Modulo-11 validation is performed (normally handled by the sending software).
CN 64 Condition Simple, brief statement of condition (e.g. "Near Fine," "Very Good." etc).
CO 7 Copies Numeric field representing total number of copies available. Format is nnnnnnn.
DP 15 Date Pub Represents the date published, normally a 4-digit year.
DT 24 System Date Optional field for system date stamp, normally in the form of "YYYY-MM-DD HH:MM:SS." Same as SD (preferred).
ED 14 Edition Simple, brief statement of edition ("1st," "First," "Revised," "Book Club," etc).
FP 256 Fixed Shipping Represents a specific method and fixed cost for shipping the item being offered. The method is separated from the cost by an equal sign (=). Multiple entries may be entered (contents must conform to the naming conventions used by the sales venue). Each entry specified must contain its own FP token on a separate line (Example: FP|USPS First Class = 2.50).
FU 10 Monetary Units Defines the type of currency used for the FP, FX, and FY tokens. This should normally be a 3-character abbreviation (Example: USD). Currency symbols should not be used as they are not universally recognized in all ISO symbol sets.
FX 64 Sales Tax Contains a string representing sales tax information. The string should appear in the form of [%%%.%%],[State],[Optional/Required],[Include/Exclude] (Example: FX/7.00%, New York, Required, Exclude). The State is the literal name of the state. The [Optional/Required] identifier defines whether sales tax is optional or required. The [Include/Exclude] identifier defines whether or not to include shipping and handling when calculating sales tax. If the FX token is not included, then sales tax is assumed to be omitted.
FY 10 Fixed Handling Fee Represents a string containing a flat handling fee (sometimes referred to as "Additional Shipping") that will appear as part of the checkout dialogue. Format is nnnnnnn.nn or nnnnnnnnnn. If this token is not included, then no handling fee will appear.
IM 256 Image This method provides an alternative to embedding object data when associating one or more images with a record. The contents normally point to a URL, but may also contain an image filename. Each IM line contains one URL or file name. The sequence of images from top to bottom in the UIEE record does not imply the usage of images in the record — this is handled by the image filenames (i.e. "003715a.jpg," "003715b.jpg," etc).
IS 15 Status Private data field representing status of a record ("Available," "On Hold," etc).
JK 14 Jacket Simple, brief statement of jacket presence and condition, normally preceded or followed by the term "dj" ("Very good dj," "dj missing," etc).
KE 19 Keyword Keywords should be kept in separate fields, not all in a single field. There is no limit to the number of keywords, but most software supports up to 10.
KW 19 Keyword Same as KE, provided for compatibility (KE is preferred).
LG 10 Language Identifies the originating language applicable to the item being described. The UIEE 2.44 specification strongly recommends that a Language field should always be included as part of every UIEE record, whether or not the receiving system will make use of it. Entry may be literal (e.g. "English," "French," etc) or may correspond to the ISO-639/2 List of Recommended Language Identifiers, as per the MARC specification, in which case either the ISO-639-1 (two-character codes) or ISO-639-2 (three-character codes) may be used, with preference given to the ISO-639-2/T code set.
LO 15 Location Private data field, used for inventory control, provided for compatibility purposes.
MT 27 Main Topic Primary relational topic, for which Keywords (KE) represent subsets. When importing, information preceded by the MT prefix is mapped directly to the Main Topic field. When uploading, Main Topic is normally treated as a keyword.
MV 10 Market Value Private numeric data field used to store appraisal value. Format is nnnnnnn.nn
NC 128 Comments General comments identifying attributes and detractors. Use Notes (NT) for physical description and reference information.
NT 16384 Notes Comprehensive physical description and any/all relevant information regarding contents. Note: Comments may transpose into Notes if field length exceeded.
PC 10 Purchase Cost Private numeric data field used to store cost value. Format is nnnnnnn.nn
PG 14 Pages Normally represents page count in the form of "312p" or similar.
PP 27 Place Pub Represents the location printed usually a city ("New York, "Racine," "Garden City," etc).
PR 10 Price REQUIRED Represents the sell price of the record. Format is nnnnnnn.nn or nnnnnnnnnn.
PT 14 Printing Simple, brief statement of printing ("1st printing," "6th printing," etc).
PU 28 Publisher Concise publisher's name ("Grosset & Dunlap," "Dell," "Time-Life" etc).
RE 15 Record No Same as UR (see below). UR is preferred, provided for compatibility.
SD 24 System Date Optional field for system date stamp. Interchangable with DT, SD is preferred.
SE 128 Series Optional field provided for compatibility. If present, appended to Title.
TI 128 Title REQUIRED Represents the title of the book as it appears on the title page. If the title exceeds 128 characters, then an ellipse (...) should appear at the end. The full title may optionally be included in Notes.
TP 15 Size/Type Simple, brief statement of physical size ("8vo," "Folio," "16cm x 22cm," etc)
UR 15 Record No REQUIRED Represents the unique database record number, usually consisting of the database record number prepended with the database name (e.g. "MYBOOKS001234"), or an SKU conforming to the character requirements (e.g. "A12_B34_C56"). This field should only contain the characters A-Z, 0-9, and/or an underscore (_). Hyphens, spaces, and any spurious punctuation should be pre-stripped by the sending software. Record numbers should always appear in UPPER CASE.
WT 16 Weight Represents the unpackaged weight of the item being described (e.g. "14 oz", "1 lb 7 oz," etc). For a numeric-only value without any specified units of measurement, the value is assumed to be ounces. The UIEE 2.44 specification strongly recommends that a Weight field should always be included as part of every UIEE record, whether or not the receiving system will make use of it. Close conformity to these requirements permits automated shipping cost determination by receiving systems.
UIEE Definitions
Table 2: ANTIQUES Token Set

Please check back for availability
UIEE Definitions
Table 3: AUCTION Token Set
Required fields for parsing the AUCTION token set depend upon the company hosting the auction. In general, the User Record Number (UR), Auction Account Id (FA), Opening Bid (FB), Category Code (FC), Auction Description (FD), Auction Duration (FN), Auction Title (FT) and Auction Venue (FV) are always required and are so noted. However, other fields may be required as well. The software parsing the UIEE record must conform to the requirements of the receiving system. With the exception of the Description field (FD), UIEE auction fields are strictly text-only and should never contain direct HTML. The Language (LG) and Weight (WT) fields are optional, but are strongly recommended for all record types regardless of content.

ID

Length

Field

Notes

AA 128 Author Used only for books or other published works, intended primarily for indexing purposes, represents the author's name as it appears on the Title page. Name imprint (L-F-M or F-M-L) defined by the sending software. L-F-M is standard and is therefore preferred.
AN 64 Annotation Private data field, normally contains a Date/Time stamp but may contain text.
BN 13 ISBN Code Used only for books or other published works, intended primarily for indexing purposes, contains validated International Standard Book Number (10- or 13-char format supported).
CI 11 Catalog No Private data field. Used to store user-defined SKU or catalog number. Note: This field should not be used as the auction identifier, as the text does not have to be unique. The UR field serves as the auction identifier (see below).
CO 7 Copies or Quantity Numeric field representing total number of copies or quantity available. Format is nnnnnnn. Normally set to 1, may contain any quantity for Dutch auction if supported.
DT 24 System Date Optional field for system date stamp, normally in the form of "YYYY-MM-DD HH:MM:SS." Same as SD (preferred).
FA 128 Auction Account Id REQUIRED Contains the precise auction account identifier or login string. This is a case-sensitive field.
FB 10 Auction Opening Bid REQUIRED Represents the price at which the auction will open. Format is nnnnnnn.nn or nnnnnnnnnn.
FC 256 Auction Category REQUIRED Represents the category under which the auction will be listed. This field may contain a numeric code corresponding to a particular company's category assignments, or it may contain an explicit [Category # Subcategory] routing string. If text is used, categories and subcategories should be delimited by the pound (#) symbol (Example: Consumer Electronics # Video Games # Sony Playstation # Games # Arcade). If the auction company allows more than one category under which an auction may be listed, multiple FC entries may appear (additional fees may apply).
FD 65535 Auction Description REQUIRED Contains a description of the item being offered at auction. In general, HTML may appear in this field if supported by the auction venue, but it must conform to the UIEE specification rules. Note that an auction template may be embedded in the UIEE file to provide HTML document display control, and that the %%DESCRIPTION%% tag can serve as the reception point for information in the Description field.
FE 1 Allow Checkout Editing This is a logical field which specifies whether or not the user will permit the winning bidder to directly edit or enter the total payment amount at the conclusion of the auction. The value is either a 1 (Yes) or a 0 (No) and is logically related to the presence of the Auction Checkout Instructions token (FI), if present (see below).
FI 1024 Auction Checkout Instructions Contains an explicit message to the winning bidder at the conclusion of the auction. Depending on the hosting company's policies, this may or may not appear as part of the auction, but in general will always be visible to the winning bidder at the close of the auction. Note that this field does not supercede any account-specific instructions, returns policy, etc as may be defined in the user's auction account. This field may be limited by the receiving venue to less than the stated 1024 character maximum.
FN 4 Auction Duration REQUIRED Represents the number of days the auction will run. Format is nnnn. Typical values are 3, 5, 7, and 10, but may be any value between 1 and 9999.
FO 256 Auction Option Represents a selectable option or special feature offered by the auction company (additional fees may apply). Each option specified must contain its own FO token on a separate line (Example: FO|Boldface Title). For options requiring redirection to an image or other object component, the name of the component should appear on the same line (Example: FO|Gallery Image d0012754.jpg).
FP 256 Auction Shipping Represents a specific method and fixed cost for shipping the item being offered. The method is separated from the cost by an equal sign (=). Multiple entries may be entered (contents must conform to the naming conventions used by the auction venue). Each entry specified must contain its own FP token on a separate line (Example: FP|USPS First Class = 2.50).
FR 10 Auction Reserve Price Represents the minimum bid for which the auction will close at the end of its duration (additional fees may apply). Reserve price may or may not be visible in the auction, depending on the policies of the hosting company. Format is either nnnnnnn.nn or nnnnnnnnnn.
FS 10 Auction Sell Price Represents the bid amount for which the auction will close immediately (additional fees may apply). May or may not be visible in the auction depending on the policies of the hosting company. Format is nnnnnnn.nn or nnnnnnnnnn.
FT 128 Auction Title REQUIRED Contains the visible title of the auction as it should appear when presented by the receiving site. NOTE: Although this field may contain 128 characters, it is usually strictly limited internally to 45 characters by most auction companies.
FU 10 Auction Monetary Units Defines the type of currency used for the FB, FR, FS, FX, and FY tokens. This should normally be a 3-character abbreviation (Example: USD). Currency symbols should not be used as they are not universally recognized in all ISO symbol sets.
FV 32 Auction Venue REQUIRED Defines the particular venue or company that will host the auction. Only one FV token is permitted per UIEE record.
FX 64 Auction Sales Tax Contains a string representing sales tax information. The string should appear in the form of [%%%.%%],[State],[Optional/Required],[Include/Exclude] (Example: FX/7.00%, New York, Required, Exclude). The State is the literal name of the state. The [Optional/Required] identifier defines whether sales tax is optional or required. The [Include/Exclude] identifier defines whether or not to include shipping and handling when calculating sales tax . If the FX token is not included, then sales tax is assumed to be omitted from the checkout/end-of-auction dialogue.
FY 10 Auction Handling Fee Represents a string containing a flat handling fee (sometimes referred to as "Additional Shipping") that will appear as part of the checkout/end-of-auction dialogue. Format is nnnnnnn.nn or nnnnnnnnnn. If this token is not included, then no handling fee will appear.
IM 256 Image This method provides an alternative to embedding object data when associating one or more images with a record. The contents normally point to a URL, but may also contain an image filename. Each IM line contains one URL or file name. The sequence of images from top to bottom in the UIEE record does not imply the usage of images in the record — this is handled by the image filenames (i.e. "003715a.jpg," "003715b.jpg," etc).
KE 19 Keyword intended primarily for indexing purposes, keywords should be kept in separate fields, not all in a single field. There is no limit to the number of keywords, but most software supports up to 10. Note: Some auction policies strictly limit the use of keywords. Consult provider before including.
KW 19 Keyword Same as KE, provided for compatibility (KE is preferred).
LG 10 Language Identifies the originating language applicable to the item being described. The UIEE 2.44 specification strongly recommends that a Language field should always be included as part of every UIEE record, whether or not the receiving system will make use of it. Entry may be literal (e.g. "English," "French," etc) or may correspond to the ISO-639/2 List of Recommended Language Identifiers, as per the MARC specification, in which case either the ISO-639-1 (two-character codes) or ISO-639-2 (three-character codes) may be used, with preference given to the ISO-639-2/T code set.
LO 15 Location Private data field, used for inventory control, provided for compatibility purposes.
MT 27 Main Topic Primary relational topic, for which Keywords (KE) represent subsets. When importing, information preceded by the MT prefix is mapped directly to the Main Topic field. When uploading, Main Topic is normally treated as a keyword. Note: Some auction policies strictly limit the use of keywords. Consult provider before including.
MV 10 Market Value Private numeric data field used to store appraisal value. Format is nnnnnnn.nn
PC 10 Purchase Cost Private numeric data field used to store cost value. Format is nnnnnnn.nn
PR 10 Price Represents the sell price of the non-auction record. Format is nnnnnnn.nn or nnnnnnnnnn. Used only for rollback after auction concludes without a winning bidder.
PU 28 Publisher Used only for books or other published works, intended primarily for indexing purposes, contains concise publisher's name ("Grosset & Dunlap," "Dell," "Time-Life" etc).
RE 15 Record No Same as UR (see below). UR is preferred, provided for compatibility.
SD 24 System Date Optional field for system date stamp. Interchangeable with DT, SD is preferred.
TI 128 Title Used only for books or other published works, intended primarily for indexing purposes, represents the full title of the book as it appears on the title page.
UR 15 Record No REQUIRED Represents the unique database record number, usually consisting of the database record number prepended with the database name (e.g. "MYSTUFF001234"), or an SKU conforming to the character requirements (e.g. "A12_B34_C56"). This field should only contain the characters A-Z, 0-9, and/or an underscore (_). Hyphens, spaces, and any spurious punctuation should be pre-stripped by the sending software. Record numbers should always appear in UPPER CASE. Note: Record Number is also used to remove parallel records listed in retail venues when an auction is launched. Hence, Record Number should not be changed when launching an auction, especially if submitting to a record redirection or forwarding service.
WT 16 Weight Represents the unpackaged weight of the item being described (e.g. "14 oz", "1 lb 7 oz," etc). For a numeric-only value without any specified units of measurement, the value is assumed to be ounces. The UIEE 2.44 specification strongly recommends that a Weight field should always be included as part of every UIEE record, whether or not the receiving system will make use of it. Close conformity to these requirements permits automated shipping cost determination by receiving systems.
UIEE Definitions
Table 4: RETAIL Token Set
In many respects the RETAIL token set is a subset of the AUCTION token set. However, there are additional fields for supporting venues. These include Size/Units (RS), Type (RT), Year (RY) and Universal Product Code (UC). The Language (LG) and Weight (WT) fields are optional, but are strongly recommended for all record types regardless of content.

ID

Length

Field

Notes

AA 128 Author Used only for books or other published works, intended primarily for indexing purposes, represents the author's name as it appears on the Title page. Name imprint (L-F-M or F-M-L) defined by the sending software. L-F-M is standard and is therefore preferred.
AN 64 Annotation Private data field, normally contains a Date/Time stamp but may contain text.
BN 13 ISBN Code Used only for books or other published works, intended primarily for indexing purposes, contains validated International Standard Book Number (10- or 13-char format supported).
CI 11 Catalog No Private data field. Used to store user-defined SKU or catalog number. Note: This field should not be used as the listing identifier, as the text does not have to be unique. The UR field serves as the listing identifier (see below).
CO 7 Copies or Quantity Numeric field representing total number of copies or quantity available. Format is nnnnnnn. Normally set to 1, may contain any value.
DT 24 System Date Optional field for system date stamp, normally in the form of "YYYY-MM-DD HH:MM:SS." Same as SD (preferred).
FA 128 Retail Account Id REQUIRED Contains the precise retail account identifier or login string. This is a case-sensitive field.
FB 10 Base Price REQUIRED Represents the minimum base price at which an item can be sold. Format is nnnnnnn.nn or nnnnnnnnnn. Used primarily for discount price, but can also specify the opening bid price for the same item in a redirected auction.
FC 256 Retail Category REQUIRED Represents the category under which the item will be listed. This field may contain a numeric code corresponding to a particular company's category assignments, or it may contain an explicit [Category # Subcategory] routing string. If text is used, categories and subcategories should be delimited by the pound (#) symbol (Example: Consumer Electronics # Video Games # Sony Playstation # Games # Arcade).
FD 65535 Retail Description REQUIRED Contains a description of the item being offered at retail. In general, HTML may appear in this field if supported by the retail venue, but it must conform to the UIEE specification rules. Note that a retail template may be embedded in the UIEE file to provide HTML document display control, and that the %%DESCRIPTION%% tag can serve as the reception point for information in the Description field.
FE 1 Allow Checkout Editing This is a logical field which specifies whether or not the user will permit the buyer to directly edit or enter the total payment amount at the conclusion of the sale. The value is either a 1 (Yes) or a 0 (No) and is logically related to the presence of the Retail Checkout Instructions token (FI), if present (see below).
FI 1024 Retail Checkout Instructions Contains an explicit message to the buyer at the conclusion of the sale. Depending on the hosting company's policies, this may or may not appear as part of the listing, but in general will always be visible to the purchaser when the item is purchased. Note that this field does not supercede any account-specific instructions, returns policy, etc as may be defined in the user's retail account. This field may be limited by the receiving venue to less than the stated 1024 character maximum.
FO 256 Retail Option Represents a selectable option or special feature offered by the retail company (additional fees may apply). Each option specified must contain its own FO token on a separate line (Example: FO|Featured Item). For options requiring redirection to an image or other object component, the name of the component should appear on the same line (Example: FO|Featured Image d0012754.jpg).
FP 256 Retail Shipping Represents a specific method and fixed cost for shipping the item being offered. The method is separated from the cost by an equal sign (=). Multiple entries may be entered (contents must conform to the naming conventions used by the retail venue). Each entry specified must contain its own FP token on a separate line (Example: FP|USPS First Class = 2.50).
FR 10 Auction Reserve Price Used only to pre-define a reserve price for retail venues that support auction redirection of retail items. Format is either nnnnnnn.nn or nnnnnnnnnn.
FS 10 Auction Sell Price Used only to pre-define a sell price for retail venues that support auction redirection of retail items. Format is nnnnnnn.nn or nnnnnnnnnn.
FT 128 Retail Title REQUIRED Contains the visible title of the item as it should appear when presented by the retail site. NOTE: Although this field may contain 128 characters, it is usually strictly limited internally to 45 characters by most auction companies.
FU 10 Monetary Units Defines the type of currency used for the FB, FR, FS, FX, and FY tokens. This should normally be a 3-character abbreviation (Example: USD). Currency symbols should not be used as they are not universally recognized in all ISO symbol sets.
FV 32 Retail Venue REQUIRED Defines the particular venue or company that will host the listing. Only one FV token is permitted per UIEE record.
FX 64 Retail Sales Tax Contains a string representing sales tax information. The string should appear in the form of [%%%.%%],[State],[Optional/Required],[Include/Exclude] (Example: FX/7.00%, New York, Required, Exclude). The State is the literal name of the state. The [Optional/Required] identifier defines whether sales tax is optional or required. The [Include/Exclude] identifier defines whether or not to include shipping and handling when calculating sales tax . If the FX token is not included, then sales tax is assumed to be omitted from the checkout dialogue.
FY 10 Retail Handling Fee Represents a string containing a flat handling fee (sometimes referred to as "Additional Shipping") that will appear as part of the checkout dialogue. Format is nnnnnnn.nn or nnnnnnnnnn. If this token is not included, then no handling fee will appear.
IM 256 Image This method provides an alternative to embedding object data when associating one or more images with a record. The contents normally point to a URL, but may also contain an image filename. Each IM line contains one URL or file name. The sequence of images from top to bottom in the UIEE record does not imply the usage of images in the record — this is handled by the image filenames (i.e. "003715a.jpg," "003715b.jpg," etc).
KE 19 Keyword intended primarily for indexing purposes, keywords should be kept in separate fields, not all in a single field. There is no limit to the number of keywords, but most software supports up to 10.TD>
KW 19 Keyword Same as KE, provided for compatibility (KE is preferred).
LG 10 Language Identifies the originating language applicable to the item being described. The UIEE 2.44 specification strongly recommends that a Language field should always be included as part of every UIEE record, whether or not the receiving system will make use of it. Entry may be literal (e.g. "English," "French," etc) or may correspond to the ISO-639/2 List of Recommended Language Identifiers, as per the MARC specification, in which case either the ISO-639-1 (two-character codes) or ISO-639-2 (three-character codes) may be used, with preference given to the ISO-639-2/T code set.
LO 15 Location Private data field, used for inventory control, provided for compatibility purposes.
MT 27 Main Topic Primary relational topic, for which Keywords (KE) represent subsets. When importing, information preceded by the MT prefix is mapped directly to the Main Topic field. When uploading, Main Topic is normally treated as a keyword.
MV 10 Market Value Private numeric data field used to store appraisal value. Format is nnnnnnn.nn
PC 10 Purchase Cost Private numeric data field used to store cost value. Format is nnnnnnn.nn
PR 10 Price Represents the list price of the retail item. Format is nnnnnnn.nn or nnnnnnnnnn. Also used for rollback after auction concludes without a winning bidder.
RE 15 Record No Same as UR (see below). UR is preferred, provided for compatibility.
RS 64 Size/Units Defines a commodity size or unit of measurement for which the stated Price applies. Examples include "per 100" "per bag" "set of 3" etc. May also contain an explicit disclaimer (Example: "Price is for the entire box"). If omitted, defaults to "each."
RT 15 Type Represents a specific, named type or class of merchandise. Differs from a keyword in that this field is not intended for public retrieval, but serves as an index key for the merchant. Examples: "Remainder" "Consignment" "Store" "Warehouse" etc.
RY 4 Year Mfg Represents the year the item was manufactured. Used for indexing purposes by the listing venue (Description and/or Title usually contain this information as well).
SD 24 System Date Optional field for system date stamp. Interchangeable with DT, SD is preferred.
TI 128 Title Used only for books or other published works, intended primarily for indexing purposes, represents the full title of the book as it appears on the title page.
UC 30 Universal Product Code Represents a unique UPC code. Any code appearing here should only be entered for a valid, registered Universal Product Code Identification Number which has been encoded into a UPC-A or EAN-13 bar code symbol on the product.
UR 15 Record No REQUIRED Represents the unique database record number, usually consisting of the database record number prepended with the database name (e.g. "MYSTUFF001234"), or an SKU conforming to the character requirements (e.g. "A12_B34_C56"). This field should only contain the characters A-Z, 0-9, and/or an underscore (_). Hyphens, spaces, and any spurious punctuation should be pre-stripped by the sending software. Record numbers should always appear in UPPER CASE.
WT 16 Weight Represents the unpackaged weight of the item being described (e.g. "14 oz", "1 lb 7 oz," etc). For a numeric-only value without any specified units of measurement, the value is assumed to be ounces. The UIEE 2.44 specification strongly recommends that a Weight field should always be included as part of every UIEE record, whether or not the receiving system will make use of it. Close conformity to these requirements permits automated shipping cost determination by receiving systems.
UIEE Definitions Table 5: CUSTOM Token Set
The CUSTOM token set is a self-defining format intended only for test purposes or special cases requiring unusual or proprietary field assignments. No direct UIEE parsing is performed other than valid token recognition and no field lengths apply. All tokens are alphanumeric and field assignments are based on the requirements of the destination database. There are six "tiers" whose tokens start with A, B, C, D, E, and F respectively. The 2nd character is a digit from 0 to 9, providing a total of 60 available fields. Generally, the usage of each field tier should conform to a recognizable criteria, such as grouping of text fields, numeric fields, logical fields, etc.

ID

Length

Field

Notes

A0-A9 n/a Tier 1 Fields Legal tokens are A0, A1, A2, A3, A4, A5, A6, A7, A8 and A9.
B0-B9 n/a Tier 2 Fields Legal tokens are B0, B1, B2, B3, B4, B5, B6, B7, B8 and B9.
C0-C9 n/a Tier 3 Fields Legal tokens are C0, C1, C2, C3, C4, C5, C6, C7, C8 and C9.
D0-D9 n/a Tier 4 Fields Legal tokens are D0, D1, D2, D3, D4, D5, D6, D7, D8 and D9.
E0-E9 n/a Tier 5 Fields Legal tokens are E0, E1, E2, E3, E4, E5, E6, E7, E8 and E9.
F0-F9 n/a Tier 6 Fields Legal tokens are F0, F1, F2, F3, F4, F5, F6, F7, F8 and F9.