Skip to main content

Accounting Report # 2

Updated today

πŸ“‹ Summary:

The Accounting Report #2 provides a comprehensive, detailed view of all wine sales transactions, capturing critical financial and logistical data across multiple dimensions like order source, shipping details, product specifics, and customer location. This granular accounting report is particularly valuable for finance teams, winery controllers, and executive leadership who need to reconcile sales performance, track revenue streams, and understand the nuanced financial mechanics of direct-to-consumer wine sales. By displaying net sales, shipping costs, taxes, and other transactional details in one consolidated view, this report serves as a powerful financial diagnostic tool that allows wineries to drill down into their revenue composition, identify trends, and make data-driven strategic decisions about pricing, product mix, and sales channels. Users can easily customize this report by modifying filters, adding or removing columns, and saving their personalized version as a new bookmark to suit their specific analytical needs.

This summary was generated by AI.

πŸ“ Public Bookmarks Folder: Accounting Reports

πŸ“Œ Quick Stats:

  • πŸ”» 0 filter(s) applied

  • πŸ“Š 20 dimension(s) displayed

  • πŸ“ˆ 6 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 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)

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

  • Order Source β€” Indicates whether the order was created internally by the CRM or if it was created by an external source like TOCK or imported through the API as part of a data migration. The likely values will be 'Internal' and 'External'

  • 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.

  • 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)

  • 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

  • Quantity β€” The quantity of the item/sku in the order.

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

  • Order Club Name β€” Name of the club linked to the club order. that way we can link the revenue to that specific club.

  • Ship To First Name β€” First name of person shipment is being sent to

  • Ship To Last Name β€” Last name of person shipment is being sent to

  • Ship To City β€” City of person shipment is being sent to

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

  • Ship To Zip Code β€” Zip code of person shipment is being sent to

  • Department β€” Departments serve as broad categories to help organize Products internally, mainly for accounting purposes and to be displayed in Reports. We use departments extensively to identify tasters, display data in the Tasting Room Module for Tasting Details and Glass Pours.

πŸ“ˆ Measures:


ℹ️ Additional Details

  • πŸ“ Public Bookmarks Folder: Accounting Reports

  • πŸ”‘ Bookmark ID: bed4a9eb-b8c1-4585-b393-f855249c8e21

Did this answer your question?