Margin Master
What's New
Stay up to date with the latest features, improvements, and fixes
What's New in Margin Master
Stay up to date with the latest features, improvements, and fixes.
MarginMaster v2026.515.35634 v2026.515.35634
May 15, 2026 5 changes(2 deployments combined)-
ADDPOIN/SUBPOIN operations now processed correctly in batch mode
Fixed a critical bug where ADDPOIN and SUBPOIN operations (which shift a product's rounding bracket by N positions) returned an empty SQL modifier and were silently dropped during batch processing. The system now generates a specialized two-join UPDATE query that finds the original rounding bracket, calculates the shifted index (clamped to valid bounds), and applies the SetAmount from the new bracket position.
-
ADDPOIN/SUBPOIN rounding point shifts now work in batch mode
Fixed an issue where SKU exceptions configured with ADDPOIN or SUBPOIN (which shift the rounding bracket up or down by a number of points) were being incorrectly batched together, causing the point shift values to be ignored. The system now properly groups these exceptions by their raw add/subtract value (e.g., SUBPOIN3 vs SUBPOIN6) to ensure each point shift is processed separately. Added special SQL logic to shift the rounding level index by the specified number of positions and apply the corresponding bracket's price.
-
Fixed store selection error for Epicor SKU exceptions
Epicor POS systems use per-store main tables (e.g., Epicor_9496_mainTable) rather than a unified mainTable, which caused the SKU exception dialogs to fail to detect available stores. The application now falls back to the configured store list from application settings when per-store table structures are in use, ensuring store numbers are always available when creating or editing SKU-level pricing exceptions.
-
Corrected grouping logic for different POIN shift amounts
Changed the batch grouping key to use the raw AddSubtract value instead of the computed PlusMinusSql expression. This ensures that different shift amounts (e.g., SUBPOIN3 vs SUBPOIN6) are processed as separate groups rather than incorrectly batched together, preventing wrong shift amounts from being applied.
-
Improved SKU exception batch grouping logic
Modified the batch processing grouping key to use the raw ACTIONADDSUBTRACT value instead of the computed SQL modifier. This ensures that different POIN operations (like ADDPOIN3 vs ADDPOIN5 or SUBPOIN3 vs SUBPOIN6) are processed in separate batches with their distinct point shift values intact, while still allowing other modifiers like ADDDOLL or ADDPERC to batch efficiently.
