Margin Master

Data Aging: fix date divergence and clarify sync outcome messages

Shipped in Margin Master 2026.904.35423 · September 5, 2026

Fixed two issues where the "Last Synced" date on the Data Aging window could advance without actually updating catalog data, and revised warning messages to report what is provable rather than accusing the sync of failing when data may be current.

What changed

Last Synced date no longer advances when no tables ran

The "Last Synced" date on the Data Aging screen will no longer move forward after a sync that didn't actually run any tables.

Last Synced date requires all tables to succeed when no rows moved

If a vendor sync finds no changes but some tables failed, the date will no longer incorrectly advance, preventing stale data from appearing up-to-date.

Sync bookkeeping failures reported separately and no longer block date stamp

If vendor data syncs successfully but cannot be recorded in the history, you'll see a notification explaining that your data is current even though the sync history looks out of date.

Divergence warning messages revised to report facts, not verdicts

Warning messages on the Data Aging screen now explain that your catalog may already be up-to-date even when dates disagree, rather than claiming the sync failed.

Point-of-sale data divergence warning added

The Data Aging screen now warns you when the POS import date and import history don't match, just like it does for vendor syncs.

Sync outcome decision logic extracted and unit tested

See all Margin Master releases