Strategy Execution Cloud Tracking - Margin Master

Margin Master Handbook

Introduction
Part I · Installing
Part II · Introducing the Main Window
Part III · Initial Configuration
Part IV · Customizing the Workspace
Part V · Basic Application Functionality
Part VI · Learning Margin Master
Part VII · Advanced Topics
Part VIII · Updates, Troubleshooting & Help
Appendix
Part VI · Chapter 15 — Building Pricing StrategiesUpdated 2026-09-15

Strategy Execution Cloud Tracking

What is this?

Every time you execute a pricing strategy in Margin Master (Strategy > Execute Strategy), the application automatically sends a detailed record of the execution to the cloud. This includes a snapshot of each step's configuration and its results -- how many SKUs were affected, what price changes were made, and whether any errors occurred.

This cloud tracking gives your support team full visibility into your strategy history. They can see exactly what ran, when it ran, and what it did -- without needing to be on your machine. It also lays the groundwork for future features like restoring a strategy from a cloud snapshot.

Key behaviors:

  • Runs in the background -- Cloud tracking never slows down or delays your strategy execution. It happens after the strategy finishes, in a separate background task.
  • Silent on failure -- If the cloud is unreachable (no internet, server down), the strategy still completes normally. A warning is logged locally but nothing interrupts your workflow. Cloud tracking failure never causes a strategy to fail.
  • Automatic retention -- Only the last 5 executions per store are kept in the cloud. Older executions are automatically removed.
  • Per-step detail -- Each step's full configuration (pricing rule, rounding scheme, Min/Max settings) is captured as a snapshot so support can reconstruct exactly what happened.
  • Local logs -- In addition to cloud tracking, each execution writes local log files for offline review (see below).

Local Execution Logs

Each strategy execution also writes two local log files to disk, independent of cloud tracking:

File Content
{StoreName}_Detail_{timestamp}.log Per-step detail: rule text, SKUs affected, timing, Min/Max impact, and any errors. Also includes a performance analysis section appended automatically after execution.
{StoreName}_Summary_{timestamp}.log High-level summary: strategy name, total steps, total SKUs affected, duration, and completion status.

Location: C:\ProgramData\RetailerSoft\MarginMaster\Logs\StrategyExecution\

These files are useful when you need to review a specific execution offline, share results with support, or analyze performance of individual pricing steps. The performance section in the detail log is especially useful for diagnosing slow strategy executions.

Who is this for?

  • Users -- No action required. Execution tracking is automatic and invisible. You benefit indirectly because support staff can diagnose strategy issues remotely without asking you to reproduce problems.
  • Support staff -- Review execution history, diagnose pricing issues, and verify that strategies are running as expected.

How It Works (User Perspective)

  1. Execute a strategy normally via Strategy > Execute Strategy
  2. After all steps complete, the execution record is sent to the cloud automatically
  3. If the upload succeeds, a confirmation message appears in the local log: "Strategy execution tracked to cloud"
  4. If the upload fails (no internet, etc.), you will see a warning in the local log but nothing else changes -- your strategy results are unaffected

You do not need to enable, configure, or manage this feature. It is always active.

Loading...

Reconnecting to the server...

This usually takes a few seconds.