This table should include records of historical orders for all products in your store. Each row corresponds to one order.
Time Period: 12 months
Why do we need this? We use this information to train our pricing models including calculating the elasticities of your products and projecting future performance. We look at orders at a line item level as well as an order level to see relationships between items within a basket and at a customer-level
|Must be unique. Id of the larger order. This should be the same for all line items in an order.
|Datetime when the purchase was made.
|Optional array of order line item objects. You must include order line items here if you are not providing them separately.
|Id of the customer making the purchase. We use this for calculating active users and measuring new user growth. Ideally, a customer always has the same customer id.
|Is the customer a member/ subscriber?
|Datetime when the purchase was fulfilled.
|Country where purchase was made.
"United States of America"
|Id for the store where the purchase was made - brick and mortar store id, ecomm region, etc.
|Any fields that we should know about but aren’t in our schema?
|Delivery fee, if applicable
|Tip for service
|This should be the sum of all fees. If there are no fees, it should be 0.
|These are discounts at the basket level and should not include item-specific discounts
|Final price paid net of taxes and fees