Formatting and Importing Data
If you are using an integration not currently supported by Adobe Commerce Intelligence, you can still use the File Upload feature to get your data into your Data Warehouse. This topic covers the ideal data formats to be used for uploading ecommerce data.
Orders table
The orders table should contain one row for every transaction the business has conducted. Potential columns include:
Column name
Description
Order IDThe order ID should be unique for every row in the table. Also, this is typically the primary key for the table.
CustomerThe customer who placed the order.
Order totalThe total of the order. This may be a calculation-based column, where values in other columns - such as subtotal and shipping - make up the total for this column.
CurrencyThe currency the order was paid in. Include if relevant.
Order statusThe status of the order, such as
In Progress, Refunded, or Complete. The value of this column changes (if not complete). New and updated data can be imported using the Append Data feature on the File Uploads page.Acquisition/marketing channelThe acquisition or marketing channel that the customer who placed the order was referred from.
Order datetimeThe date and time the order was created.
Order updated atThe date and time the last modification to the order record was made.
Order detail/items table itemstable
The order_detail / items table should contain one row for each distinct item in every order. Potential columns include:
Column name
Description
Order item IDThe order item ID should be unique for every row in the table. Also, this is typically the
primary key for the table.Order IDThe ID of the order.
Product IDThe product’s ID.
Product nameThe name of the product.
Product's unit priceThe price for a single unit of the product.
QuantityThe quantity of the product in the order.
Customers table customerstable
The customers table should contain one row for each customer account. Potential columns include:
Column name
Description
Customer IDThe customer ID should be unique for every row in the table. Also, this is typically the primary key for the table.
Customer created atThe date and time the customer’s account was created.
Customer modified atThe date and time the customer’s account was last modified.
Acquisition/marketing channel sourceThe acquisition or marketing channel that the customer was referred from.
Demographic infoDemographic info such as age range and gender can be used to segment your reports.
Acquisition/marketing channelThe acquisition or marketing channel that the customer who placed the order was referred from.
Subscription payments table
The subscriptions table should contain one row for each subscription payment. Potential columns include:
Column name
Description
Subscription IDThe subscription ID should be unique for every row in the table. Also, this is typically the primary key for the table.
Customer IDThe ID of the customer who made the payment.
Payment amountThe amount of the subscription payment.
Start dateThe starting datetime of the period that the payment covers.
End dateThe ending datetime of the period that the payment covers.
recommendation-more-help
e1f8a7e8-8cc7-4c99-9697-b1daa1d66dbc