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.
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 Date | Order Number | Subtotal | What It Means |
|---|---|---|---|
| 07/01/2026 9:03 PM | 100 | $100.00 | Original sale |
| 07/02/2026 7:03 PM | 100-1 | -$20.00 | Edit #1 β a $20 refund the next day |
| 07/05/2026 2:15 PM | 100-2 | $35.00 | Edit #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 Date | Order Number | Product Name | Qty | Subtotal |
|---|---|---|---|---|
| 06/02/2026 | 654896 | Estate Red Blend 2023 | 1 | $46.00 |
| 06/02/2026 | 654896-1 | Estate Red Blend 2023 | -1 | -$46.00 |
| 06/02/2026 | 654896-1 | Reserve Tempranillo 2022 | 1 | $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.
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:
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:
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 SKU | Qty | Subtotal | Product 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.
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:
| Column | Definition |
|---|---|
| Order Date | The date the order was placed. |
| Order Number | The order number for this sale. On SKU-level reports, the same order number appears on each product line for that order. |
| Order Type | How the order was created: POS, Website, Manual Order, Club, or Bulk. |
| Order Subtype | A more specific category within the order type, when one applies. |
| Order Delivery Method | How the order is delivered, such as shipping or customer pickup. |
| Payment Type | The payment method used for the order, such as credit card, cash, or check. |
| Transaction Status | The payment outcome for the transaction: Purchase or Refunded. |
| Transaction Amount | The amount captured by the payment gateway for the order. |
| Payment Gateway Transaction ID | The reference ID from the payment gateway, used for reconciliation and refunds. |
| Order Note | Notes on the order, including payment notes and general order notes. |
| Fulfillment Status | Whether the order is unfulfilled, partially fulfilled, or fully fulfilled. |
| Compliance Status | Direct-to-consumer shipping compliance result: Compliant, Not Compliant, or Not Checked. |
| Compliance Number | The compliance provider reference or tax ID for the order’s shipping compliance check. |
| Sales Associate | The primary sales associate assigned to the order. |
| Logged In User | The staff member signed in when the order was placed. |
| Inventory Location | The inventory or sales location associated with the order. |
| Column | Definition |
|---|---|
| Collection | The collection the product belongs to. |
| Product Name | The name of the product sold on this line. |
| Variant Name | The product variant on this line, such as size or vintage. |
| Product SKU | The SKU (stock keeping unit) for the product on this line. |
| Product Type | The type of product, such as wine, merchandise, or food. |
| Product Tax Type | The tax category for this product at the SKU level, such as Wine or Food. |
| Quantity Sold by SKU | The number of units sold for this SKU on the line. |
| Bottle Size by SKU | The bottle or package size for this SKU. |
| Item Weight | The weight of the item as recorded when the order was placed. |
| Alcohol % by SKU | The alcohol percentage for this product. |
| Total Liters | Total volume in liters. On order-level reports this is the order total; on SKU-level reports it applies to the line. |
| Column | Definition |
|---|---|
| Subtotal | The merchandise subtotal before tax, shipping, tips, and discounts. |
| Discounts | Total discounts applied to the row, shown as a negative amount. |
| Shipping | Shipping charges for the row. |
| Handling | Handling fees for the row. |
| Product Tax | Sales tax on products for the row. |
| CRV Tax | California Redemption Value (CRV) or similar container deposit tax. |
| Shipping Tax | Tax on shipping charges for the row. |
| Custom Tax | Any additional custom taxes applied to the row. |
| Tips | Tips collected on the order. |
| Custom Refund Amount | Custom refund amount applied outside standard line refunds. |
| Revenue Collected | Total amount collected for the row before net adjustments. |
| Net Revenue Collected | Net amount collected after discounts. Calculated as Subtotal minus Discounts. |
| COGS | Cost of goods sold for the line, based on the cost recorded when the order was placed. |
| Column | Definition |
|---|---|
| Customer Number | The customer’s account number in Corksy. |
| Customer First Name | The customer’s first name. |
| Customer Last Name | The customer’s last name. |
| Customer Email | The customer’s email address. |
| Customer Phone | The customer’s phone number. |
| Customer Date of Birth | The customer’s date of birth, when collected. |
| Column | Definition |
|---|---|
| Shipping First Name | First name on the shipping address. |
| Shipping Last Name | Last name on the shipping address. |
| Shipping Company | Company name on the shipping address, when provided. |
| Shipping Email | Email address on the shipping address. |
| Shipping Phone | Phone number on the shipping address. |
| Shipping Date of Birth | Date of birth on the shipping address, when collected. |
| Shipping Address Line 1 | First line of the shipping street address. |
| Shipping Address Line 2 | Second line of the shipping street address, when provided. |
| Shipping City | City on the shipping address. |
| Shipping State | State or province on the shipping address. |
| Shipping Zip Code | ZIP or postal code on the shipping address. |
| Shipping Country | Country on the shipping address. |
| Tracking Number | Carrier tracking number for the shipment. Multiple tracking numbers are separated by commas. |
| Column | Definition |
|---|---|
| Billing First Name | First name on the billing address. |
| Billing Last Name | Last name on the billing address. |
| Billing Company | Company name on the billing address, when provided. |
| Billing Email | Email address on the billing address. |
| Billing Phone | Phone number on the billing address. |
| Billing Date of Birth | Date of birth on the billing address, when collected. |
| Billing Address Line 1 | First line of the billing street address. |
| Billing Address Line 2 | Second line of the billing street address, when provided. |
| Billing City | City on the billing address. |
| Billing State | State or province on the billing address. |
| Billing Zip Code | ZIP or postal code on the billing address. |
| Billing Country | Country on the billing address. |
| Column | Definition |
|---|---|
| Created At | When the order record was created in Corksy. |
| Last Modified Date | When the order record was last updated in Corksy. |
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:
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