Skip to main content

Accounting Order Details in Period

Updated today

πŸ“‹ Summary:

The Accounting Order Details in Period bookmark provides a comprehensive, granular view of all wine sales orders within a specific timeframe, displaying critical transactional data across multiple dimensions like order status, channel type, product details, and customer information. This detailed report is an essential tool for finance teams, sales managers, and wine club administrators who need to track precise revenue metrics, understand sales channel performance, and reconcile order-level financial transactions during a current period. By presenting a comprehensive breakdown of net sales, shipping costs, taxes, and total order amounts, this bookmark enables winery leaders to conduct deep financial analysis, identify sales trends, and make data-driven decisions about inventory, pricing, and customer engagement strategies. Users can easily customize this report by adjusting filters, adding or removing columns, and saving a personalized version that meets their specific analytical needs.

This summary was generated by AI.

πŸ“ Public Bookmarks Folder: Accounting Reports

πŸ“Œ Quick Stats:

  • πŸ”» 0 filter(s) applied

  • πŸ“Š 21 dimension(s) displayed

  • πŸ“ˆ 9 measure(s) displayed

  • πŸ“„ Report Page: Build Beyond Limits | Advanced Reporting

⚠️ Date Picker Required: This report uses time-sensitive measures that respond to the date picker. The bookmark does not save date picker settings. Please adjust the date picker to ensure the report shows the data for your desired time period.

πŸ”„ Filter Behavior: When you select this bookmark, your existing filters will be replaced with the bookmark's saved filters.


πŸ”» Filters Applied

βœ… No filters applied - this bookmark shows all available data.


πŸ“‹ Columns Displayed

πŸ“Š Dimensions:

  • Order Number β€” The actual order number of the order (normally represented in numeric format but we will use it as a string)

  • Order Submitted Date β€” This is the to local time zone converted date of the order_submitted_at (UTC timestamp)

  • Completed Date β€” This is the to local time zone converted date of the order_completed_at (UTC timestamp)

  • Fulfillment Date β€” Date when this event occurred

  • Order Status β€” Indicates the status of the order, likely something like Paid or Completed. We will use this status on several occassions to standardize on the order status and to run formulas based on payment and order status. Therefore we may need to map to our standard.

  • Payment Status β€” Indicates the status of the payment likely something like Paid, Authorized or Cancelled. We will use this status on several occassions to standardize on the order status and to run formulas based on payment and order status. Therefore we may need to map to our standard.

  • Shipping Status β€” The status of the fulfillment of the order. likely values are Fulfilled, Not Fulfilled, Partially Fulfilled, or No Fulfillment Required.

  • Order Type β€” The order_type is the channel or order type the transaction happened in. Order Type is the lowest level of the transaction channel. Commerce7 has limited channels (POS, Club, Web, Inbound), while WD allows for free text creation of order types. The channel in Commerce7 is equivalent to the order type in WD. VST doesn't have a field for channel but has a set of booleans (isClub, IsWeb, etc.) that allow us to create an order type.

  • Channel Type β€” This is a mapped field and is an enolytics ENUM. (eg. Club, Tasting Room or Website)

  • Sales Attribute β€” This is a WineDirect specific field. Sales attribute are discreet dropdown values helping to categorize the order. It is not often used.

  • Order Delivery Method β€” The order delivery method indicates whether the order was shipped or if it was picked up (obvious values are Pickup, Ship or Carry Out)

  • First Name β€” Contact first name as defined in the contacts table

  • Last Name β€” The name of the actual club as specified in the respective CRM. (eg. 3 Bottle Pinot Noir Club). A customer can belong to multiple clubs at once but the club itself can only exist once within the winery data.

  • Ship To State β€” Abbreviated state code of person shipment is being sent to

  • Item Name β€” The name of the product as defined in the CRM

  • Product Type β€” The product type of the product. This will be very important going forward as we will need to distinguish between wine, bundles and non-wine types. The product types are the result of enum tables and may have to be mapped to allow us to have efficient transformations.\nTypes can be:\n- Wine\n- Bundle\n- General Merchandise\n- Tasting\n- Reservation\n- Event Ticket\n- Gift Card\n- Collateral\n- Rebate

  • Item SKU β€” The unique product sku (stock keeping unit) as defined in the CRM

  • Item Quantity Fulfilled β€” order items level parameter indicating the number of items fulfilled in the order (C7 only)

  • Sold Price β€” The price at which the item was sold, after discounts.

  • Original Price β€” The List (retail) price of the item, as written by the CRM at the time the order was completed. This normally is the value of the product_price at the time that the order was created. The combination of item_original_price and item_sold_price will allow us to calculate the discount for the item.

  • Inventory Pool β€” The name of the physical inventory location, aka inventory pool (eg. warehouse, tasting room)

πŸ“ˆ Measures:


ℹ️ Additional Details

  • πŸ“ Public Bookmarks Folder: Accounting Reports

  • πŸ”‘ Bookmark ID: 53acc1a5-99b6-4384-9995-67b0d5b5a931

Did this answer your question?