At a glance
Total discount value applied to orders in the period. The single most important promotional-economics KPI: it answers “how much did we give away to drive sales?”. On BigCommerce, this aggregates coupon codes, automatic cart-level promotions, customer-group price-list discounts, and Promotions API discounts into a single figure. Track in absolute terms here; track as a ratio on BC Discount %. The two cards together tell you whether discount spend is scaling with revenue or running away.
| What it counts | SUM(discount_amount) over the period. BC’s discount_amount field aggregates: coupon codes redeemed, automatic promotions (cart-level rules), customer-group price-list discounts (B2B Edition wholesale prices), and Promotions API discounts. Each is a distinct concept but all reduce the customer-paid total. |
| VAT / tax treatment | Discount is calculated on the post-tax-treatment subtotal in BC’s default mode. So a 10% discount on a £120 inc-VAT order = £12 discount. Tax recalculates on the discounted amount automatically. |
| Shipping | Shipping discounts (free-shipping codes, shipping-rate-discount promos) are separate from product discounts. BC tracks them in different fields; this card focuses on product discounts. Free-shipping promos do NOT count here; track via BC Shipping Methods. |
| Discounts | This card is the discount value. |
| Refunds | Discount value on refunded orders is NOT deducted by default (gross discount view). |
| Cancelled orders | Excluded; cancelled orders’ discount records are voided. |
Incomplete orders | Excluded. |
| Currency | Multi-currency without FX. |
| Channels / sources | All channels aggregate. Web typically dominates discount spend (most coupons distribute on web); B2B Edition wholesale price discounts also count here and can be substantial in dollar terms. |
| B2B Edition price-list discounts | A wholesale customer paying £80 for a £100 retail-priced item generates a £20 “discount” on this card, even though it’s a contractual wholesale price (not a promotional discount). This conflation can mislead. Filter to web-only or DTC if you want the promotional spend; the aggregate mixes promotions and wholesale pricing. |
| Discount sources breakdown | Available via Ask Viq: coupon codes, automatic cart promos, customer-group prices, Promotions API. Each has different operational implications. |
| Time window | 30D (rolling 30 days). |
| Alert trigger | None on absolute value; rate-based alert lives on BC Discount % at >25% margin pressure. |
| Roles | owner, marketing |
Calculation
Worked example
A US apparel brand on BigCommerce, 30-day window. Mixed channels.| Discount source | Discount value ($) | % of total discount | Orders affected |
|---|---|---|---|
| Coupon codes (e.g., NEWSLETTER10, FRIENDS20) | $14,200 | 53% | 1,420 |
| Automatic cart promos (BOGO, multi-buy) | $5,400 | 20% | 580 |
| Customer-group prices (B2B wholesale) | $4,800 | 18% | 95 |
| Promotions API (custom rules) | $1,800 | 7% | 240 |
| Loyalty / store credit applied | $560 | 2% | 88 |
| Total | $26,760 | 100% | 2,423 orders affected |
- Coupon codes (53%) are the biggest spend. Predictable, but worth scrutiny. Audit coupons by performance: a coupon with 1,000 redemptions and average order value below site AOV is destroying margin (customer would have bought anyway, you just gave away 10%). Stop these and reuse the budget on net-new-customer coupons.
- **B2B wholesale (18%, 21,960 (9.8% of DTC revenue). Don’t try to “reduce” B2B discount; it’s the wholesale price by contract.
- Automatic cart promos (20%) are AOV-lifting. BOGO, “spend Y” rules don’t have a customer-facing code; they trigger automatically. Cart promos typically lift AOV 8-15% but their margin cost is in this number.
- The 2,423 orders affected = 41% of orders received some discount. This is high; healthy stores typically see 25-35%. Above 50% means promotional dependency (customers wait for discounts to buy).
- Loyalty / store credit at 2% is low. Either the loyalty program is small, or it’s not converting credits to redemptions. Most healthy loyalty programs see 5-10% of total discount through credits.
- Audit coupon code performance. Coupons that AOV-match site AOV are non-incremental (customers would have bought without). Retire them.
- Test reducing automatic cart promos by 30% to see whether AOV holds. If AOV doesn’t drop, the promo wasn’t lifting it.
- Filter to DTC for actionable analysis. B2B wholesale is contractual and not a discount-management lever.
- Pair with BC Discount % to track ratio over time.
- Investigate orders-affected rate. 41% is high; experiment with reducing coupon distribution to drop to 30% and watch revenue.
- Cross-reference Revenue Over Time to confirm promo periods correlate with revenue lift (they often don’t, after hangover).
Sibling cards merchants should reference together
| Card | Why pair it with Total Discount |
|---|---|
| BC Discount % | The ratio version. Discount % normalises against revenue; this card is absolute. |
| Discount Over Time | Time-series of the same total. |
| Total Revenue | Denominator for ratio analysis. |
| AOV | Discounts mechanically lower AOV; pair to see the trade-off. |
| BC Top Coupons | Per-coupon breakdown; identifies which codes drive most discount. |
| BC AOV Discount | AOV by discount tier. |
| BC Channel Revenue Mix | Channel mix affects discount share (B2B has structural discounts). |
| Cancellation Rate | Heavy discounting can drive cancellations from speculative buyers. |
| Refund Rate | Discount-heavy purchases sometimes have higher refund rates. |
| Repeat Rate | Discount-attracted customers repeat at lower rates than full-price customers. |
Reconciling against the vendor’s own dashboard
Where to look in BigCommerce’s own dashboard: The native view is BC Control Panel → Marketing → Promotions for current promo definitions and Reports → Promotion Reports (or Analytics → Insights → Promotions on Plus / Enterprise) for historical performance. The aggregate sum should match this card directly. For coupon-level detail, Marketing → Coupon Codes shows redemption counts per coupon; the discount value column is comparable. Why our number may legitimately differ from the vendor’s:| Reason | Direction | Why |
|---|---|---|
| B2B wholesale inclusion | Either | We include customer-group price-list “discounts” (wholesale prices); BC’s promo report typically excludes them. |
| Time zone | Boundary days off | UTC vs store time zone. |
| Refund treatment | Either | Discounts on refunded orders included in our gross view; BC may net out. |
| Sync lag | Trivial | Webhook fanout. |
| Currency | Trivial | Per-currency aggregation. |
| Free-shipping promos | Either | We exclude shipping-only discounts; BC’s promo report may include them. |
| Card | Expected relationship | Notes |
|---|---|---|
klaviyo.klaviyo_coupon_revenue | Email-attributed coupons subset | Klaviyo only sees email-driven coupon usage; should be 20-40% of total coupon spend. |