How to Export Shopify Discount Reports for Marketing and Finance Reconciliation
Build one reusable Shopify discount export your marketing and finance teams can both work from, scheduled to their inboxes every week and month.

Discount programs look fine until the end of the month. Marketing has a story about which codes won. Finance has a story about what the program cost. Both stories come from the same orders, but they almost never come from the same file, and the small gaps between the two versions are where margin quietly leaks.
The fix is unglamorous: one export, the right fields, a cadence that matches how each team actually works. This guide walks through how to set that up and how to read what comes out.
Start with the question each team is really asking
Marketing wants to rank promotions. Which codes drove orders. Which ones brought in new customers. Which ones are still live but nobody is using. The lens is campaign performance.
Finance wants to reconcile. How much did the program give away. How much came back as refunds. Does the discount total tie to the Sales report and to the payouts. The lens is net impact.
Shopify's native "Sales by discount code" and "Discounts by order" reports each answer part of this, but they answer different parts, and neither one travels well to a bookkeeper. The practical move is to build one export that carries both lenses in one file and lands in both inboxes on a schedule.
Build one report, deliver it in two cadences
A weekly version keeps marketing honest. A monthly version keeps finance honest. Both come from the same saved report in Data Export, cloned once and given a different date filter and recipient list.
| Attribute | Weekly marketing | Monthly finance |
|---|---|---|
| Date filter | Last 7 full days | Last full calendar month |
| Recipients | Marketing team inbox | Finance team plus bookkeeper |
| Delivery day | Monday morning | First business day of the new month |
| Primary use | Campaign ranking, catching zombie codes | Reconciliation against Sales reports and payouts |
| Fields trimmed out | Taxes, shipping, refund fields | None |
| Format | CSV or Excel | CSV or Excel |
Running one template in two cadences means a field change in the master propagates to both deliveries. It also means the two teams argue from the same numbers, which is the whole point.
Fields that make the export usable by both teams
The useful fields come from three layers of the order: the discount itself, the money, and the context.
| Field | What it returns | Why both teams need it |
|---|---|---|
| Order ID, Order date, Order status | Order identity and timing | Join key, filter, exclusion of cancelled orders |
| Discount code, Discount title | What was applied | Marketing uses it to rank; finance uses it to group |
| Discount method, class, type | Automatic or code, product/order/shipping, percentage/fixed/BXGY | Separates a 10% code from a free shipping offer |
| Discount amount | Dollar value given up | The headline cost figure |
| Subtotal, Shipping, Taxes, Total | Order financials | Ties the file to Shopify's Sales and Finance reports |
| Refunded amount, Refund date | Returned value and when | Turns gross discount cost into net discount cost |
| Sales channel, POS location | Where the discount was applied | Separates online from in-store behavior |
| Discount count per order, Stacked flag | How many discounts hit the order | Handles the combinable-discount problem |
The last row is the quiet one that saves hours of spreadsheet work later.
Handle combinable discounts inside the report, not afterward
Shopify writes one row per applied discount per order. An order that uses a welcome code and a free-shipping code shows up twice. Summing the discount column across that raw data double-counts the order and inflates the program cost.
The clean fix is to add a count of discounts per order inside the report itself, then flag any order where the count is greater than one. From there, finance can filter to clean single-discount orders for per-code reconciliation and look at stacked orders as their own segment. Marketing gets a truer read on which codes stand on their own and which ones only look strong because another code was propping them up.
Picking a "primary" discount for each stacked order, usually the one with the largest absolute discount amount, lets you still attribute the order to a single code for ranking purposes. The rule is explicit, which matters more than the specific rule you pick.
Two metrics worth calculating from the export
Most campaigns can be judged from the fields above without much math. Two numbers are worth adding because they change which code looks like the winner.
Discount cost % = Discount amount / Total sales × 100
This answers "how much of each sales dollar did this code give up." A code can drive the most orders and still be the most expensive one per dollar of revenue. Running this against the sample month below:
| Code | Orders | Discount value | Total sales | Discount cost % |
|---|---|---|---|---|
| WELCOME10 | 640 | $55,000 | $320,000 | 17.2% |
| FREESHIP75 | 310 | $7,400 | $148,000 | 5.0% |
| SUMMER20 | 450 | $61,000 | $215,000 | 28.4% |
Marketing would rank WELCOME10 first on orders. Finance would flag SUMMER20 first on margin. Both are right. Neither one alone is the answer.
The second number worth adding is net discount value, which subtracts the discount share of refunded orders from the gross discount figure. It is the difference between what you promised and what you actually paid out after returns, and for codes attached to high-return categories it can move the ranking again.
Validate the export against Shopify's own totals
The first run of any new export should be checked against Shopify directly. Five minutes of reconciliation saves weeks of chasing the wrong lever.
| Check | Compare to | Pass condition |
|---|---|---|
| Order count | Shopify Orders page for the same date range | Match |
| Discount amount, single-discount orders only | Shopify's reported discount total for the same filter | Match within a cent |
| Total sales | Native Sales report | Match |
| Refund alignment | Native Finance refund total | Match |
| Code coverage | Active codes in the Shopify Discounts section | All used codes present |
When a check fails, the usual culprit is a mismatched date basis (order date vs processed date) or an excluded order status (draft or cancelled accidentally left in). Fix the filter, rerun, and the numbers line up.
Schedule the export and stop thinking about it
Inside Data Export, build the custom report once from the fields above, save it with a clear name, and set a weekly schedule to a shared marketing inbox or folder. Clone the saved report, change the date filter to the previous full calendar month, and set a monthly schedule to finance and the external bookkeeper.
The first two or three cycles usually surface a couple of zombie codes, meaning codes still active in Shopify but no longer used by anyone, and one or two stacked campaigns that nobody had looked at code by code before. That is the moment the routine pays for itself.
Frequently Asked Questions
Can refund data live in the same discount export as campaign data?
Yes. Refunded amount and Refund date sit at the order level and can be added to a discount report at order grain, which is what makes one file usable by both teams.
How are stacked discounts handled inside the report?
By adding a discount-count field per order and a stacked flag. Both are built during report configuration from the base fields Shopify already provides.
Can a scheduled discount report go to an external bookkeeper or accountant?
Yes. Scheduled reports can be delivered to any email address, which is useful when a monthly file needs to land with the internal finance team and the external accountant on the same day.
Which date field should the discount export filter on?
Order date for campaign review. Order date or refund date for reconciliation, depending on how finance recognizes revenue. Mixing the two in one file without labeling the date basis is the main reason an export stops matching Shopify's own totals.
Can one export cover multiple Shopify stores?
No. The report runs per store. Each store needs its own saved report and schedule.
Closing
A discount program gets honest the day marketing and finance stop arguing from different spreadsheets. One export, scheduled, reconciled once against Shopify's own numbers, is usually all it takes. The hard conversations about which codes to retire, which to stack, and which to expand are still hard, but they start from a shared set of numbers, which is the only version of this exercise that actually leads to better decisions.
Try Data Export free for 15 days
Custom reports, 100+ prebuilt reports and scheduled delivery on every plan, from $12 per month.
