Offline Sales CSV File Format

    FieldHeader RequiredValue RequiredFormatAdditional ValidationComments
    ORDER_ID

    🟢

    🟢integer 
    Order ID in the client's system. Retrievable from the DB upon request – not shown in UI anywhere
    LOTTERY🟢🟢stringMust match an active lottery
    Lottery key for example my_lottery
    DRAW_NO🟢🟢integerMust match an open draw
    If the keyword 'next' is specified, the next open draw will be used
    CUSTOMER_IDN stringText (max = 100)
    If provided we will try to find customer using this ID instead of email
    TITLE🟢 string"Ms", "Mrs", "Miss", "Mr" or "Dr" 
    FIRST_NAME🟢🟢stringText, no digits (min = 2, max = 44) 
    LAST_NAME🟢🟢stringText, no digits (min = 2, max = 36) 
    ADD_UNIT🟢 stringText a maximum of 97 characters for the concatenation of these three fields. 
    ADD_STREET_NUMBER
    🟢When email not given or when payment type is BD or the sites use standard address formatstring 
    ADD_STREET_NAME
    🟢When email not given or when payment type is BD or the sites use standard address formatstring 
    ADD_LINE_1🟢When email not given or when payment type is BD or the sites use international address formatstring 
    Customer's address in 1 line which replaces ADD_UNIT, ADD_STREET_NUMBER and AND_STREET_NAME
    ADD_LINE_2 When this field is set to optional in international address formatstring 
    Customer's apartment number, building name, etc (optional)
    ADD_SUBURB🟢When email not given or when payment type is BD or the sites use standard address formatstringText (max = 44) 
    ADD_STATE🟢When email not given or when payment type is BD or the sites use standard address format

    This field can also be optional if it is set to be optional in international format
    stringText (max = 44) 
    ADD_POSTCODE
    🟢When email not given or when payment type is BD or the sites use standard address formatstringText (max = 10)
    AU should be integer > 0
    Other countries - any text value
    COUNTRY🟢When email not given or when payment type is BD or the sites use standard address formatstring2 character ISO codeeg AU, GB
    EMAIL🟢 string^[^@]+@[^@]+\.[^@]+$
    Mandatory if no address data is provided
    PHONE🟢 stringText (max = 20)
    We will only collect a single number from this flow.
    DOB🟢 dd/mm/yyyyText (exactly 10)
    dependant on the configuration there may be restrictions on this field eg older than a restricted gambling age
    IS_SUBSCRIPTION ðŸŸ¢string"YES" or "NO"Subscription sale
    IS_AUTOPLAY ðŸŸ¢string"YES" or "NO"
    Autoplay sale
    TICKET_VALUE🟢🟢string"10" or "10.00" or "$10"
    Dollar amount of the price of Ticket Book
    SALE_DATE🟢🟢dd/mm/yyyyText (exactly 10)
    This is separate to Payment Date. We need payment date recorded against the transaction. Sale date exists for Suppliers to record when a sale occurred.
    PAYMENT_TYPE
    🟢🟢stringCC or CASH or MO or CHQ or BD
    Case insensitive. Note these payment methods will need to be available
    CC_TOKEN🟢When payment type is CCstringText (exactly 10)
    The CC token must have been created with the same payment gateway and credentials as configured
    CC_PAYMENT_GATEWAY
      string 
    When provided this will override the base configuration for the payment gateway. Usually has values of "stripe", "paystream", "eway".
    AFFILIATION🟢 stringMust match either an existing affiliate code or name
    Either the code or name of an existing affiliate.
    CAMPAIGN  string 
    Stored against the cart row in JL
    BANK_ACCOUNT_NAME When payment type is BDstring  
    BANK_ACCOUNT_NUMBER When payment type is BDstring  
    BANK_CODE When payment type is BDstring  
    GAME_OFFER When GAME_OFFER header is usedstringOne of the following:
    "standard_monthly",
    "standard_quarterly",
    "standard_biannually",
    "standard_annually"
    The type of game offer. This will always be "standard_monthly" unless the direct debit is not monthly.
    BILLING_DAY When GAME_OFFER is usedintegerone of the following:
    1, 8, 15, 23, 28
    Used to determine the direct debit collection day. Must be one of the available values (1,8,15,23,28).
    CAUSE🟢🟢stringMust match an existing cause key
    The key of a cause set up in the system i.e my_cause.
    ORGANISATION
      stringMust match the name of an existing organisation.
    The name of a sales organisation i.e "ACME Telemarketers".
    CHANNEL ðŸŸ¢stringMust match an existing channel key
    If this field is missing the channel assigned to the uploader is used for all records. If present, this column overrides the channel. If the channel field is supplied (optional) all records must supply a valid channel key.
    COMMS_EMAIL
      string"YES" or "NO"
    opt in to receive email marketing preference
    COMMS_SMS  string"YES" or "NO"
    opt in to receive SMS marketing preference
    COMMS_PUSH  string"YES" or "NO"
    opt in to receive Push notification preference
    COMMS_PHONE
      string"YES" or "NO"
    opt in to receive phone marketing preference
    COMMS_MAIL  string"YES" or "NO"
    opt in to receive direct mail preference
    EXTRA_*  stringExtra field column header names must contain non-special characters however, dashes and underscores are permitted.
    Extra column headers can only contain characters a-z, A-Z, 0-9 _ - . (full-stop). No spaces are allowed.
    Extra columns are a way to capture any additional sales data not otherwise explicitly defined in this file format. Extra fields are denoted by having a prefix "extra_" followed by the name of the field. For example, the column heading "extra_tshirt_size" would create a data field called "tshirt_size". There can be any quantity of extra_ fields supplied. All supplied records for extra data are stored as text fields.
    There are no specific text limits on the length of the header of the data but we suggest keeping under 255 characters.

     

     

     

    Was this article helpful?
    0 out of 0 found this helpful