New Sales By Order Reports

Follow us:

🍷 Introducing the New Sales by Order Reports β€” Your Sales Data, Crystal Clear. Sales by Order reports have been replaced with the Sales by Order Edit reports to give you insights into every detail and transaction.

Every edit. Every refund. Every timestamp. All in one place.

We’re excited to announce two updated reports rolling out to all Corksy wineries: Sales by Order (Edit) and Sales by Order (Edit) by SKU. These reports were built to make the full story of every order easier than ever to read β€” the original sale, and every change that follows.

Orders evolve β€” a bottle swapped out at the tasting room, a club shipment adjusted, a partial refund issued days after the sale. These reports lay all of that out clearly, line by line, so your reports read exactly the way your business actually ran.

See Every Edit, On the Day It Happened

The heart of these reports: edits and refunds appear as their own rows, with their own timestamps, tied back to the original order.

When an order is edited, the report shows a new line using the original order number plus an edit suffix (-1, -2, and so on). Negative amounts indicate a refund or removed item. Here’s a simple example of how it reads:

Order DateOrder NumberSubtotalWhat It Means
07/01/2026 9:03 PM100$100.00Original sale
07/02/2026 7:03 PM100-1-$20.00Edit #1 β€” a $20 refund the next day
07/05/2026 2:15 PM100-2$35.00Edit #2 β€” an item added to the order

Your daily totals reflect exactly what happened on that day β€” the original sale on July 1, the refund on July 2 β€” so end-of-day reconciliation, deposits, and accounting tie out cleanly and effortlessly.

On the by SKU version, every edit is broken down to the product level, so you can see precisely which bottle was refunded, swapped, or added:

Order DateOrder NumberProduct NameQtySubtotal
06/02/2026654896Estate Red Blend 20231$46.00
06/02/2026654896-1Estate Red Blend 2023-1-$46.00
06/02/2026654896-1Reserve Tempranillo 20221$52.00

One glance and you know: the customer swapped the Red Blend for the Tempranillo. The note column even carries your team’s comments on why.

New Unified Columns Across Both Reports

Both reports share one consistent, unified column structure β€” so Order-level and SKU-level exports speak the same language and are easy to work with side by side. We’ve also added the fields you’ve been asking for:

  • Payment Gateway Transaction ID β€” match any order directly to your payment processor for effortless reconciliation and refund tracing.
  • Order Note β€” payment notes and general order notes travel with every row, so context is never lost.
  • Created At & Last Modified Date β€” know exactly when an order was created and when it was last touched.
  • Transaction Status & Transaction Amount β€” see Purchase vs. Refund and the exact amount captured by the gateway.
  • Compliance Status & Compliance Number β€” DTC compliance results right in the report.
  • Logged In User & Sales Associate β€” full accountability for who rang the sale and who gets credit.

Smarter Bundle Reporting β€” Down to the Individual SKU

Bundles appear on these reports broken out into their individual component SKUs, giving you clear product-level visibility into exactly what left your inventory.

Here’s how it works:

  • Bundle pricing is proportionally distributed across each SKU in the bundle, based on each product’s share of the bundle value.
  • Discounts are distributed proportionally across the component SKUs the same way.
  • Taxes are distributed proportionally across the component SKUs the same way.
  • Refunds on bundles are also distributed proportionally β€” so if a bundle is refunded or edited, each SKU line reflects its fair share of the adjustment.

For example, a $90 three-bottle bundle shows as three individual SKU lines with their proportional share of the price, tax, and any later refunds:

Product SKUQtySubtotalProduct Tax
WR2023 (Red Blend)1$36.00$2.79
WW2024 (Chardonnay)1$30.00$2.33
WS2022 (Late Harvest)1$24.00$1.86

The payoff: SKU-level sales, depletion, bundle SKUs sold, and margin numbers you can read at a glance β€” bundle revenue is already allocated across products for you, with zero manual math for inventory or accounting.


Built-In Column Definitions β€” Right in Your Export

Every column, defined in plain English. Every Excel export includes a “Report Definitions” tab with clear definitions for every single column β€” right there whenever you need a quick reference. Here’s the full list:

Order Info

ColumnDefinition
Order DateThe date the order was placed.
Order NumberThe order number for this sale. On SKU-level reports, the same order number appears on each product line for that order.
Order TypeHow the order was created: POS, Website, Manual Order, Club, or Bulk.
Order SubtypeA more specific category within the order type, when one applies.
Order Delivery MethodHow the order is delivered, such as shipping or customer pickup.
Payment TypeThe payment method used for the order, such as credit card, cash, or check.
Transaction StatusThe payment outcome for the transaction: Purchase or Refunded.
Transaction AmountThe amount captured by the payment gateway for the order.
Payment Gateway Transaction IDThe reference ID from the payment gateway, used for reconciliation and refunds.
Order NoteNotes on the order, including payment notes and general order notes.
Fulfillment StatusWhether the order is unfulfilled, partially fulfilled, or fully fulfilled.
Compliance StatusDirect-to-consumer shipping compliance result: Compliant, Not Compliant, or Not Checked.
Compliance NumberThe compliance provider reference or tax ID for the order’s shipping compliance check.
Sales AssociateThe primary sales associate assigned to the order.
Logged In UserThe staff member signed in when the order was placed.
Inventory LocationThe inventory or sales location associated with the order.

Product

ColumnDefinition
CollectionThe collection the product belongs to.
Product NameThe name of the product sold on this line.
Variant NameThe product variant on this line, such as size or vintage.
Product SKUThe SKU (stock keeping unit) for the product on this line.
Product TypeThe type of product, such as wine, merchandise, or food.
Product Tax TypeThe tax category for this product at the SKU level, such as Wine or Food.
Quantity Sold by SKUThe number of units sold for this SKU on the line.
Bottle Size by SKUThe bottle or package size for this SKU.
Item WeightThe weight of the item as recorded when the order was placed.
Alcohol % by SKUThe alcohol percentage for this product.
Total LitersTotal volume in liters. On order-level reports this is the order total; on SKU-level reports it applies to the line.

Financials

ColumnDefinition
SubtotalThe merchandise subtotal before tax, shipping, tips, and discounts.
DiscountsTotal discounts applied to the row, shown as a negative amount.
ShippingShipping charges for the row.
HandlingHandling fees for the row.
Product TaxSales tax on products for the row.
CRV TaxCalifornia Redemption Value (CRV) or similar container deposit tax.
Shipping TaxTax on shipping charges for the row.
Custom TaxAny additional custom taxes applied to the row.
TipsTips collected on the order.
Custom Refund AmountCustom refund amount applied outside standard line refunds.
Revenue CollectedTotal amount collected for the row before net adjustments.
Net Revenue CollectedNet amount collected after discounts. Calculated as Subtotal minus Discounts.
COGSCost of goods sold for the line, based on the cost recorded when the order was placed.

Customer

ColumnDefinition
Customer NumberThe customer’s account number in Corksy.
Customer First NameThe customer’s first name.
Customer Last NameThe customer’s last name.
Customer EmailThe customer’s email address.
Customer PhoneThe customer’s phone number.
Customer Date of BirthThe customer’s date of birth, when collected.

Shipping

ColumnDefinition
Shipping First NameFirst name on the shipping address.
Shipping Last NameLast name on the shipping address.
Shipping CompanyCompany name on the shipping address, when provided.
Shipping EmailEmail address on the shipping address.
Shipping PhonePhone number on the shipping address.
Shipping Date of BirthDate of birth on the shipping address, when collected.
Shipping Address Line 1First line of the shipping street address.
Shipping Address Line 2Second line of the shipping street address, when provided.
Shipping CityCity on the shipping address.
Shipping StateState or province on the shipping address.
Shipping Zip CodeZIP or postal code on the shipping address.
Shipping CountryCountry on the shipping address.
Tracking NumberCarrier tracking number for the shipment. Multiple tracking numbers are separated by commas.

Billing

ColumnDefinition
Billing First NameFirst name on the billing address.
Billing Last NameLast name on the billing address.
Billing CompanyCompany name on the billing address, when provided.
Billing EmailEmail address on the billing address.
Billing PhonePhone number on the billing address.
Billing Date of BirthDate of birth on the billing address, when collected.
Billing Address Line 1First line of the billing street address.
Billing Address Line 2Second line of the billing street address, when provided.
Billing CityCity on the billing address.
Billing StateState or province on the billing address.
Billing Zip CodeZIP or postal code on the billing address.
Billing CountryCountry on the billing address.

System

ColumnDefinition
Created AtWhen the order record was created in Corksy.
Last Modified DateWhen the order record was last updated in Corksy.

⚠️ Important: Legacy Reports Version

With the new reports live, we will be deprecating and removing the legacy Sales by Order and Sales by Order by SKU reports and will be replaced with the new version with the Edits Version. The separate edit report has been moved to the Sales by Order and Sales by Order by SKU report. The new reports include everything the old ones did β€” plus edit tracking, gateway IDs, notes, and unified columns β€” so we encourage you to switch over now and update any saved workflows, bookmarks, or accounting processes before the cutover.

What you need to do:

  1. Start running Sales by Order and Sales by Order by SKU for your daily and monthly reporting today. If you used Sales by Order Edit or Sales by Order Edit by SKU, now just use the Sales by Order and Sales by Order by SKU report. It’s the same data.
  2. Update any spreadsheets or imports that reference the old column layout to the new unified structure (definitions are on the second tab of every export).
  3. If you previously tracked bundles as single line items, note that bundles appear on these reports as their component SKUs, with pricing, tax, and refunds distributed proportionally β€” adjust any bundle-level rollups accordingly.

Why We Built This

We wanted reconciliation to take minutes, not hours. The Edit reports show the full life of every order β€” the sale, the edits, the refunds β€” each on its own timestamped line, so your reports, your processor statements, and your accounting all read from the same page.

The result: reports that are easier to read, easier to trust, and easier to hand to your bookkeeper.

The new reports are available now under Reports in your Corksy dashboard. Questions? Reach out to our support team β€” we’re happy to walk you through your first reconciliation with the new format.

Happy reporting! πŸ₯‚

β€” The Corksy Team

We love helping wineries like you.
Sign up for our newsletter to receive updates and more:
Your information is protected by us.
Read our privacy policy

Table Of Contents

Ready to get started?
Β© 2026 Corksy. All rights reserved.