• Trust
  • 提交请求

    • Need assistance with your Emarsys product?
    We'll get you the help you need!

     

    Emarsys client

     

    Emarsys client
    SAP for Me Login

    You can contact our support team via the SAP for Me.

    The Emarsys component: CEC-EMA

    		Login to the Help Portal and Submit your request. 
    1. Emarsys
    2. 入门
    3. Preparing for Integration

    Sales Data Batch Loads:: Standard Sales Data CSV file requirements
    更新

    To use our Sales Data Batch Loads solution, you need to format your sales data CSV file according to the specifications and guidelines described on this page.

    General

    • Your sales data file should be a simple .csv table, with each row describing the attributes of a single line item.
    • The name of the file has to match the pattern provided in the configuration.
    • The extension of the file has to be .csv.
    • You cannot upload files larger than 100 GB.
    • Use UTF-8 encoding.
    • Your file must start with a header row (e.g. the field names). The columns in the header of your sales data file must be in the order that was specified during configuration.
    • You can name the fields as you wish but they have to match your configuration.
    • Order updates are not allowed. Make sure you upload each individual order only once, and do not reuse the same transaction ID and transaction type combination. In the case of duplicate records, new transactions will replace the previous ones.
    • You need to load the full image of an order (not deltas) and make sure all the items included in a transaction are uploaded in the same file.
    • Use any standard CSV separator to separate fields in a row, such as a comma ',', a semicolon ';', a tab '\t', a space ' ' and a pipe '|'.
    • When using newline characters, make sure they are properly quoted.
    • You can use single or double quotes.
    • The optional fields must be included in the CSV file but their values can remain empty.
    • Do not upload more than 20 custom fields.

    Supported data types

    The following data types are supported:

    • string
    • date
    • float
    • integer

    Supported timestamp format

    Sales Data Batch Loads supports a subset of ISO 8601:

    • You need to provide time data with second precision.
    • You can provide fractional second information up to 6 digits
    • You need to provide timezone information:
      • either provide UTC timestamps explicitly or
      • use time with offsets.

    Sales Data Batch Loads can process the following examples:

    • 2022-06-16T12:18:51Z
    • 2022-06-16T12:18:51.545Z
    • 2024-04-11T07:00:24-07:00
    • 2024-04-11T07:00:24.2-07:00
    • 2022-06-16T12:18:51.123456Z

    Invalid examples:

    • Wed Apr 16 2022 21:44:48 GMT-0400 (Eastern Daylight Saving Time): this example does not represent an ISO 8601 standard.
    • 2023-07-15 12:00:00.000000 UTC: this example does not represent an ISO 8601 standard.
    • 2024-04-11: this example does not contain time data and timezone information.
    • 2022-06-16T12:18:51.1234567Z: more than 6 digits are used for fractional seconds in this example (Sales Data Batch Loads can process only 6 digits).

    Custom fields

    • A maximum of 20 custom fields can be uploaded.
    • Custom fields are optional.
    • The Sales Data Batch Loads solution also validates the data types of custom fields.

    Example CSV

    This is how a sample CSV file looks:

    Click here to download the sample CSV file.

    transactionType,transactionId,referencedOrderId,externalContactIdType,externalContactId,accountCurrency,transactionCurrency,transactionCreatedDateTime,transactionLastChangedDateTime,storeId,salesChannel,productId,quantity,amountInAccountCurrency,amountInTransactionCurrency,custom_color
order,123,123,email,3,EUR,EUR,2023-07-19T12:18:51.545Z,2023-07-20T12:18:51.545Z,12,online,111,1,120,120,black
order,234,234,email,3,EUR,EUR,2023-07-21T12:18:51.545Z,2023-07-22T12:18:51.545Z,12,online,222,5,1200,1200,orange
order,345,345,email,3,EUR,EUR,2023-07-23T12:18:51.545Z,2023-07-24T12:18:51.545Z,12,online,333,1.5,1200,1200,blue
order,456,456,email,3,EUR,EUR,2023-07-25T12:18:51.545Z,2023-07-26T12:18:51.545Z,12,online,444,140,1200,1200,purple
order,456,456,email,3,EUR,EUR,2023-07-25T12:18:51.545Z,2023-07-26T12:18:51.545Z,12,online,23,140,1200,1200,purple
    Click to copy

    Required fields

    The following fields are required for Sales Data Batch Loads:

     

    Field Type Necessity Description
    transactionType string mandatory
    • Describes an order or refund.
    • Possible values: order or refund
    • It has to be the same for each line item in a given transaction.
    transactionId string mandatory
    • The unique identifier of the order or refund.
    • For orders or refunds comprising multiple products, use the same transactionId for each line item.
    referencedOrderId string mandatory for the type refund
    • Identifier of the order to which the refund is referring.
    • It’s mandatory but the refund will still be processed and loaded if the referenced order cannot be found in Emarsys.
    • It has to be the same for each line item in the refund.
    externalContactIdType string mandatory
    • Type of identifier of the contact for the transaction. For example: email, phone number.
    • It has to be the same for each line item in a given transaction.
    externalContactId string mandatory
    • Identifier of the contact for the transaction.
    • It can be an email address, phone number, etc.
    • It has to be the same for each line item in a given transaction.
    account_currency string mandatory
    • Currency in ISO format.
    • It should be aligned with the central currency setting of your account configured during account creation.
    • It has to be the same for each line item in a given transaction.
    transaction_currency string mandatory Currency in ISO format.
    transactionCreatedDateTime timestamp mandatory
    • The timestamp when the transaction (order or refund) was created within the external system (POS system, Shopify, Adobe Commerce or SAP Commerce Cloud).
    • transactionCreatedDateTime should always precede the time when the purchase was loaded. Dates in the future are not accepted.
    • It has to be the same for each line item in a given transaction.
    transactionLastChangedDateTime timestamp mandatory
    • The timestamp when the transaction within the external system (POS system, Shopify, Adobe Commerce, SAP Commerce Cloud) was last modified.
    • transactionLastChangedDateTime should always precede the time when the purchase was loaded. Dates in the future are not accepted.
    • It has to be the same for each line item in a given transaction.
    productId string mandatory
    • The unique ID used for identifying the product.
    • The ID submitted here should be present in your Emarsys product database.
    • For orders comprising multiple products, each product (known as line item) must be submitted in a separate row with the same order ID.
    quantity float mandatory
    • The quantity of the purchased item(s).
    • For orders, always submit a positive value or zero.
    • For refunds, always submit a negative value.
    amount_in_account_currency float mandatory
    • The unit price multiplied by the quantity in the currency defined in your account.
    • For refunds, always submit a negative value.
    amount_in_transaction_currency float mandatory
    • The unit price multiplied by the quantity in the transaction currency defined.
    • For refunds, always submit a negative value.
    • Do not include the currency.

    Optional fields

    The following fields are optional for Sales Data Batch Loads:

     
    Field Type Necessity Description
    storeId string optional
    • The identifier of the store coming from your external system.
    • It has to be the same for each line item in a given transaction.
    salesChannel string optional
    • The sales channel of the transaction.
    • It has to be the same for each line item in a given transaction.
    这篇文章有帮助吗？
    0 人中有 0 人觉得有帮助
    返回页首