Skip to content

2.15.0

Released: TBD

Highlights

  • Four operational open-document reports (Sales Order, Backorder, Picklist, Purchase Order) showing quantity ordered vs fulfilled vs remaining — Phase 2 of the Peachtree-parity effort.
  • No schema migration — derived from existing order/PO line quantities.

Added

  • Open-document status reports — salesOrderReport, salesBackorderReport, picklistReport, and purchaseOrderReport: per-line quantity ordered, fulfilled (quantity_invoiced / quantity_received) and remaining. Backorder and Picklist keep only lines with quantity still to ship; PO report excludes closed POs. CSV-exportable. See Open-Document Status Reports.
  • Report parity tracker — Peachtree Report Parity now at 41 of 84 done (was 37).

Changed

  • None (all additive).

Fixed

  • None.

Migrations

  • None. Reports aggregate existing tables (order_details/orders, purchase_order_details/purchase_orders, items, unit_of_measures); no alembic revision and no new Path/Resource.

Frontend impact

  • Four new read-only queries under Path.REPORTS, each generateCsv-capable:
  • salesOrderReport / salesBackorderReport / picklistReport → GenericReportPage of SalesOrderLine; backorder & picklist return only quantityRemaining > 0.
  • purchaseOrderReport → GenericReportPage of PurchaseOrderLine (open POs only).
  • Group by orderNumber / purchaseOrderNumber; quantityRemaining drives the fulfil/pick worklist.
  • New GraphQL types: SalesOrderLine, PurchaseOrderLine.

Versioning notes

  • Bumped with uv run python scripts/bump_version.py 2.15.0 --changelog-stub. Additive schema only — no deploy-order constraint. Third release in the Peachtree-parity series (after 2.13.0, 2.14.0).