Intended Application
For transaction importing in which a single file may contain transactions from multiple locations and/or multiple transaction types. Supports either retail amount->point conversion via Kognitiv Loyalty transaction point formula, and also direct point entry in file.
Notes
- Any delimiter, except for a semi-colon and [tab], can be used to separate columns. The delimiter used is then specified at the time of file import.
- For checkbox value types; 1, Y, YES = True (Checked) || 0, NO, N = FALSE (Unchecked).
- Header record is expected. The first record will not be treated as data.
- Negative values in either the retail value or point amount columns will result in an error.
- If custom field data is supplied, the appropriate custom field external reference must be referenced in the header, in the appropriate column position(s).
- Standard point adjustment transaction type is not supported.
File Structure
|
DATA COLUMN |
DATA TYPE | DATA REQUIRED? | FORMATTING | NOTES |
|---|---|---|---|---|
|
Date/Time |
Yes |
MM/DD/YYYY HH:MM:SS |
Based on a 24 hour clock | |
|
Account Id* |
Alphanumeric(60) |
Yes |
|
|
|
Retail Value |
Decimal | Yes | 0.00 | |
| Point Amount | Decimal | Yes | 0.00 | |
| Transaction Translation Id | Alphanumeric | Yes | ||
| Location External Reference | Alphanumeric | Yes | ||
| Transaction Custom Field(s) | Varies | No |
* - Denotes that the data column helps comprise the transaction unique key for this import file specification.
Sample File
1: 2: 3: 4: |
TIMESTAMP|ACCOUNTID|RETAIL|POINT|TRANSID|LOCEXTREF|CASHIERID 10/10/2010 13:14:19|[email protected]|14.93|0.00|FOOD|DELI2|333 10/10/2010 13:15:49|[email protected]|11.49|0.00|MERCH|BOOKST|232 10/10/2010 13:49:50|[email protected]|0.00|2.00|VISIT|STADIUM|233 |
