![]() This is populated in all situations, including orders processed through guest checkoutįoreign key associated with the customer_group table. Depending on your configuration in Commerce Intelligence, this timestamp may be converted to a reporting time zone in Commerce Intelligence that differs from your database time zoneĮmail address of the customer placing the order. If no coupon is applied, this field is NULLĬreation timestamp of the order, stored locally in UTC. Join to sales_order_address.entity_id to determine the billing address details associated with the orderĬoupon applied to order. Taxes, shipping, discounts, and so on, are not includedįoreign key associated with the sales_order_address table. ![]() Gross merchandise value of all items included in the order. Although the precise calculation is customizable, in general the base_grand_total is calculated as base_subtotal + base_tax_amount + base_shipping_amount + base_discount_amount - base_gift_cards_amount - base_customer_balance_amount This typically reflects the Commerce store’s default currencyįinal price paid by the customer on the order, after all taxes, shipping, and discounts are applied. Common Columns Column NameĬurrency for all values captured in base_* fields (that is base_grand_total, base_subtotal, and so on). If your store accepts guest checkout, you can find more information about this use case. This table includes all customer orders, whether that order was processed through guest checkout. Usually, each row represents one unique order, although there are some custom implementations of Commerce that result in splitting an order into separate rows. The sales_order table ( sales_flat_order on M1) is where each order is captured.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |