Order Line Revenue vs. Transactional Sales Report
The two Most-Used Explores OLR and Transactional Sales Report have slight differences. It is important to know which one to use and why.
Last updated
Was this helpful?
The two Most-Used Explores OLR and Transactional Sales Report have slight differences. It is important to know which one to use and why.
Last updated
Was this helpful?
There are many ways to evaluate and look at data. Daasity has always taken a customer-first approach to our data model. The majority of Merchants rely upon and are used to Shopify, which has a modified financial first approach to how they report sales.
In order for you to have the flexibility to view your reporting from either angle, we've made available two separate explores: the Transactional Sales Report explore and the Order & Order Line Revenue explore
The has additional information joined to it, which allows analysis similar to the . It also will contain all of your Sales Sources, NOT just Shopify
There are some differences in how Shopify's logic is applied to various elements in an Order, including Shipping Fees, Taxes and Discounts.
If you see a difference in your OLR and Transactional Sales Report Numbers After still accounting for the differences below - Email support@daasity.com - and grant Daasity access to you Partner Portal and We can dig deeper into specific Orders
The largest delta that is typically noticed is the treatment of Refunded values.
Shopify records the Refund the way your finance team would want to record it - On the day the refund occurred.
Transactions containing refunds are treated as simply another transaction. If a customer makes a purchase, that transaction is recorded with a transaction number. If that customer returns the items, the return is simply another transaction and NOT connected to the original order.
Use the Transactional Sales Report Explore for all reporting using the logic stated above.
If an Order is Edited in Shopify (Manullay changed in Shopify, for example by a Customer Service Rep) Shopify will treat this as a New Order and The Transactional Sales Report add another Order Code (Order Line) for this Order. There is NO way to tie these oders back to Daasity.
The Order Line Revenue Explore will Make these changes within the Original Order - and Keep the Order as One Line (Order Code).
Net Sales will NOT match Shopify when using the Order Line Revenue Explore.
The Order Line Revenue explore is based on a customer-first data model which ties the Refund back to the order in which the item was purchased. This is a typical methodology for Customer level reporting, cohort reports and Lifetime value reporting. This also allows the item to be mapped back to exactly which items were originally purchased.
An order contains 1 row in the database. The order has various attributes such as Sales, Items, Taxes and Refunds, all connected to that original order.
Transactional Sales Explore
Order Line Revenue Explore
Reporting on Sales to match Shopify
X
Sales that include refunds over a time period, such as monthly
X
Customer Reporting
X
Individual item-level reporting
X
The Order Line Revenue Explore has one row per SKU in an order. The Transactional Sales Report has one line per transaction.
If a product is refunded it appears in the database as a separate transaction. This makes it more difficult to tease out what actually happened with an order. It is best to use Order Line Revenue if you are researching one order.
The Order Line Revenue Explore Shopify considers a Valid Order to be anything that is NOT deleted or a Test Order. The Order Line Revenue Explore matches this definition.
If you look at unfiltered sales data in Order Line Revenue, that data will include cancelled, fraud, voided, and free orders. You can Use the Daasity Valid Order Flag to remove these.
You can use a ” that Removes any Oders that are cancelled, voided, fraud, and free orders.