Prepaid Subscription Reporting

what changed two updates were made to how chord reports on prepaid subscription orders in april 2026 subscription classification — prepaid subscription parent orders (the upfront payment order) are now correctly counted as part of a subscription previously, they were excluded revenue recognition — revenue is now recorded on the prepayment order — the order where the customer actually paid previously, revenue was spread across each installment shipment order instead these are corrections to how data was being modeled your total subscription revenue hasn't changed — only when and where it appears in reports background how prepaid subscriptions work when a customer purchases a prepaid subscription plan, chord creates two types of orders the prepayment (parent) order — the single upfront transaction where the customer pays in full (e g , $440 for a 20 week plan) installment orders — the individual shipment orders generated automatically as the plan progresses (e g , 20 weekly orders at $0 each, since payment was already collected) previously, the prepayment parent order was excluded from subscription reporting and booked $0 in revenue instead, each installment order claimed its share (e g , $22 each) that meant revenue appeared on the wrong orders and was spread across shipment dates rather than the purchase date what you'll see in your reports subscription order counts will increase any report that counts subscription orders will now include prepayment parent orders, which were previously excluded the increase reflects the number of prepaid subscription purchases in your reporting window — not new sales revenue will shift to the prepayment date gross and net revenue that was previously spread across installment orders will now appear on the prepayment parent order example — $440 plan, 20 weekly installments order revenue (before) revenue (after) prepayment order (jan 1) $0 $440 installment #1 (jan 8) $22 $0 installment #2 (jan 15) $22 $0 … (×20 total) total across the plan $440 $440 the total is the same the difference is timing and placement reports spanning partial plan windows may look different if a reporting window includes the prepayment order but not all its installments (or vice versa), revenue will appear to shift in or out compared to previous snapshots this is expected — it reflects the corrected timing, not a revenue discrepancy what to do most brands don't need to take any action your overall revenue figures are correct the change affects how revenue is distributed across individual orders and dates if you or your team use custom reports or data exports that filter or aggregate prepaid subscription data, review the following subscription counts — expect higher counts in dashboards filtered by subscription orders this is accurate monthly revenue by subscription orders — expect larger values on prepayment dates and $0 on installment shipment dates, rather than an even spread subscription customer metrics — first subscription dates, subscriber counts, and cohort data may appear earlier than in prior snapshots, since prepayment orders are now included for analysts field level details all changes are on the chordoms transactional orders table field what changed order is part of subscription now true for prepayment parent orders previously excluded them gross revenue full plan value now on the prepayment parent installment redemption orders are $0 net revenue same as above — full value on prepayment parent, $0 on installments order is pre paid purchase no change order is pre paid redemption no change pre paid purchase total no change tracks cash received on the prepayment order pre paid redemption total no change tracks value drawn down per installment subscription pre paid subscription id no change if your reports sum gross revenue or net revenue across installment orders to measure prepaid revenue , update them to read from the prepayment parent order instead if you need shipment timed revenue allocation (e g , to model deferred revenue), use pre paid redemption total on installment orders this field is unaffected by the change