Purchases
The Purchases page (sidebar: Invoices → Purchases) lists what your customers have bought — an enrollment, a lesson pack, a fee, or any other product. Each purchase tracks its own total and the charges billed against it, and generates the billing cycles that become line items on an invoice. If an invoice amount looks surprising, the purchase behind it is the place to check — it shows exactly what was billed for that period and why.
Lesson-pack purchases have their own tracking badges, filters, and renewal workflow — see Lesson Packs.
Purchase Statuses
The Purchases page groups purchases by status:
| Status | Meaning |
|---|---|
| Active | The purchase is in effect and can still be billed |
| Canceled | The purchase's invoice was voided, so it's no longer billed. If the invoice was voided with Don't bill again, the row is tagged written off instead (see Written-Off Purchases) |
| Deleted | The purchase was deleted — shown with a deleted {date} badge |
A live (non-deleted) purchase whose customer or product has separately been deleted stays in its real status group, but carries its own badge — customer deleted or product deleted — so it isn't mistaken for a deleted purchase.
Viewing a Deleted Purchase
Deleted purchases aren't hidden — they stay on the Purchases page under the Deleted group, and the header count includes them. Opening a deleted purchase's detail page still works: it shows a Deleted badge with the deletion date in place of the normal status, and the three-dot menu offers Restore Purchase instead of Delete Purchase.
Deleting a Purchase
You can delete a purchase from:
- The detail page — open the purchase, click the ⋯ menu, choose Delete Purchase, and confirm
- The Purchases list — right-click (or open the row's ⋯ menu) and choose Delete purchase
- A multi-selection — check the purchases you want to remove, then use the bulk action menu's Delete purchases
Deleting a purchase cancels any of its billing cycles that haven't been billed yet, so it drops out of future invoices. It doesn't touch invoices that have already been sent or paid.
A purchase that was written off when its invoice was voided doesn't offer Delete at all. See Written-Off Purchases.
A purchase that's already been fully paid cannot be deleted. Attempting to delete one (individually or as part of a bulk selection) returns an error naming the purchase, e.g. "Purchase #2781 has already been paid and cannot be deleted."
Example: Selecting 3 purchases to delete, where one has already been paid, deletes the other 2 and reports: "2 purchases deleted. Purchase #2781 has already been paid and cannot be deleted."
Deleting a lesson pack's renewal purchase is the right way to handle a family declining a renewal — it retires that pending renewal invoice at the same time, so nothing is billed for a pack the family didn't ask to continue.
Written-Off Purchases
When you void an invoice and choose Don't bill again ("The family doesn't owe this") (see Invoice Statuses → Void), the purchases on that invoice are canceled and marked as written off. A written-off purchase can't be deleted, because deleting it would let the next invoice run bill the period you chose not to bill.
A written-off purchase looks different in three places:
- The Purchases list tags the row written off instead of canceled. The row's Delete purchase action and the bulk Delete purchases action leave it out. If you select a mix of purchases, the bulk action counts only the ones that can be deleted.
- The purchase's detail page shows a notice, Not billed after invoice #N was voided, with a link to that invoice. The ⋯ menu offers Bill it again where Delete Purchase would normally be.
- The voided invoice keeps its own Bill it again button.
To bill the period again, click Bill it again on the notice or in the ⋯ menu. The purchase returns to normal, Delete Purchase comes back, and Conductly confirms with a message such as "Re-opened 1 period (July 2026) for billing (generate an invoice for that period to charge it)." Re-opening doesn't create an invoice. Generate one for that period as usual.
Bill it again does the same thing as the button on the voided invoice, so it re-opens every period that invoice wrote off, not just this purchase. If that would free more than this purchase, Conductly asks you to confirm first.
Bill it again is shown only if you can create invoices. If Conductly can't find the voided invoice behind an old write-off, the notice says the purchase was written off on "a previous invoice" and shows no button.
If you try to delete a written-off purchase some other way, Conductly refuses with "This purchase was written off when invoice #N was voided". A bulk delete skips it, names it (for example, "Purchase #32 was written off when invoice #N was voided."), and deletes the rest.
Example: You voided a family's July invoice with Don't bill again because they had already left. A week later they come back and want July billed after all. Open the purchase, click Bill it again, then generate the July invoice. You don't need to delete anything.
Restoring a Deleted Purchase
Restoring a purchase undoes the delete and re-opens its billing cycles so it can be invoiced again. You can restore from:
- The detail page — open the deleted purchase, click the ⋯ menu, and choose Restore Purchase
- The Purchases list, one at a time — open a deleted row's ⋯ menu and choose Restore purchase
- The Purchases list, in bulk — check one or more deleted purchases, then use the bulk action menu's Restore purchase (or Restore N purchases)
A selection that mixes active and deleted purchases offers both actions at once — Delete applies to the active ones you selected, Restore applies to the deleted ones.
Each restore asks you to confirm, since it reopens billing: "Restore this purchase? Its billing cycles will be re-opened."
A purchase can't be restored if Conductly has already created a newer purchase covering the same billing period since it was deleted — restoring it would double-bill that period. You'll see: "Purchase #123 cannot be restored because a newer purchase already covers its billing period." This is uncommon, but can happen if enough time passes between deleting a purchase and restoring it that the next billing cycle has already run.