Reimbursements page unified on the Order / Transaction column's date

Thank you for using LISMOA.

v1.2.1 unifies the Reimbursements page on the date shown in the "Order / Transaction" column, bringing it into perfect alignment with the Reimbursement and Inventory Loss columns shown on every P&L view. This release also includes table UI polish, an improved bulk-update log tooltip, and a fix for sign display on summary cards.

Reimbursements page sort and filter unified on the "Order / Transaction" column's date

Until now, the Reimbursements page was filtered and sorted by the reimbursement approval date, while every P&L drilldown source (Time Series, Products, SKUs, Parent Products) was anchored on the order placement date. Drilling into the Reimbursement column from those pages produced a Reimbursements view whose totals did not match what you clicked on (#1050 and 3 more).

In v1.2.1 the Reimbursements page is migrated to the date shown in the "Order / Transaction" column as its single axis. That date is either the order placement date or the transaction's posted_date depending on the row type, and both serve as the posting date for P&L. The default sort is the descending order of this column (previously Approval Date descending), and the from / to date filter now applies to the same axis. A drilldown from any P&L view now lands on the exact same set of rows that fed the P&L total.

How the axis date is determined

The date shown in the "Order / Transaction" column (used as the sort / filter / P&L posting-date axis) is derived per record source:

• Customer-return-driven rows: the sold_on date of the original linked order
• Warehouse damage / loss with a matched transaction: the transaction's posted_date
• Warehouse damage / loss without a matched transaction: no ID and no date are shown in the "Order / Transaction" column (rendered as -). These rows fall to the bottom of the descending date sort. The reimbursement approval date is still available on the existing Approval Date column

Extended "Order / Transaction" column

The transaction-status badge that previously sat to the right of the Approval Date column has moved to the right side of the redesigned Order / Transaction column. Warehouse damage / loss rows—which previously showed only a transaction ID—now stack the posted_date underneath the ID, mirroring how customer-return rows show the order's placement timestamp:

• Customer-return-driven rows: shopping-cart icon + order ID + order placement timestamp
• Warehouse damage / loss (matched transaction): receipt icon + transaction ID + posted_date
• Warehouse damage / loss (no matched transaction): nothing shown (- only)

For the customer-return-driven and matched-transaction rows, the date on the bottom row is what drives the sort order, the date-range filter, and the P&L posting date on the Reimbursements page. Each date carries a tooltip clarifying that it is treated as the P&L posting date. For the unmatched-transaction fallback rows, no date is displayed in this column; the reimbursement approval date remains visible in the Approval Date column.

Sortable Total Cost and Net columns

The Total Cost and Net columns on the Reimbursements page now support sorting, making it easy to surface the largest reimbursement deltas.

Inventory Loss drilldown removed

Inventory Loss totals also include a Customer return × damage × no reimbursement record pattern (reimbursement request never filed, or filed and rejected). Because no row exists in the reimbursements table for this pattern, drilling into the Inventory Loss column would surface an empty result. To avoid the confusion, the Inventory Loss column drilldown link has been removed from the Time Series, Products, SKUs, and Parent Products pages—the cell now renders as plain text. The breakdown for the with-reimbursement-record patterns is still reachable through the Reimbursement column drilldown.

Date range carried into drilldown

When you click the Reimbursement column from the Products, SKUs, or Parent Products pages, only the search keyword was previously carried over—the date range fell back to the default 30 days. From v1.2.1, the currently selected date range (from / to) is forwarded to the Reimbursements page as well, matching the behavior of the Time Series page drilldown.

A note on historical P&L

Because approval_date and posted_date can sit in different calendar months, historical P&L totals for warehouse damage / loss rows may shift when this release rolls out (customer-return-driven rows are unaffected). If your workflow depends on Reimbursements rows being ordered by approval date, please note that both the default sort and the date-range filter now operate on the posting date.

Improvements

• Sales trend graph cells on the Products, SKUs, Parent Products, and Subscribe & Save pages are now correctly center-aligned, and image cell rows no longer collapse (#1049 and 2 more)
• Single-line cells across the Recurring Costs, SB / SP search-term pages, and similar tables are now top-aligned with two-line cells under a shared rule (#1018)
• The bulk-update log's error-count tooltip is now hover + pinnable, the style is unified, and the timestamp column no longer wraps awkwardly (#1040 and 1 more)
• Summary cards for signed metrics (such as Net) preserve the minus sign instead of dropping it (expense metrics continue to display as absolute values) (#1055)

Fixes

• Fixed an internal error (NoMethodError) that could occur during order aggregation recalculation (#1036)

If you have any questions, please feel free to contact our support team. Thank you for choosing LISMOA.