promotion:How to Verify Retail Promotion Execution Against the Approve

Retail promotion verification compares approved plan conditions, store-level execution evidence and sales outcomes, then closes exceptions with a named owner and closure evidence.

To verify retail promotion execution against the approved plan, compare three separate layers: the approved plan conditions, the store-level execution evidence and the sales outcome. Each layer answers a different question. A display photo can show that a display was in place at that moment. It cannot show that the promotion lifted sales. Treat each piece of evidence at its real strength, and resolve exceptions with a named owner and closure action.

Promotion execution verification: plan conditions, store evidence, sales outcome
Three layers of promotion verification: plan conditions, store execution evidence and sales outcome.

The three layers of promotion verification

What each verification layer can and cannot establish
Layer Question it answers Typical evidence What it does not prove
Plan conditions What was approved, for which products, stores and dates? Approved activity brief, target store list, eligible SKU list, date range, mechanic, display specification That anything happened in store
Store execution What was observed at the store during the activity period? Visit records, task completion, display photos, stock and price observations Sales uplift, causality or continuity between visits
Sales outcome What changed in sales, and against which baseline? Sales data by store and SKU for the agreed periods That the promotion caused the change

Step 1: Confirm the approved plan conditions

Verification starts with the approved plan, because store execution can only be assessed against a defined standard. When the plan is vague, reviewers compare opinions instead of checking conditions. A workable plan record should state, at minimum:

  • Eligible products: which SKUs, pack sizes or variants the promotion covers, and which are excluded.
  • Activity period: the start and end dates, including whether set-up and teardown days count.
  • Target stores: a named list or a clear rule that generates one. Keep the assigned list and the completed list as separate figures.
  • Display requirements: location, format, minimum size or number of facings, and the point-of-sale material required.
  • Mechanic and price: the shopper-facing price point or offer, and how it is funded.
  • Available stock: the minimum quantity or days of cover required at the store for execution to be considered supported.
  • Documented promotion conditions: who approves participation, which evidence is required, submission deadlines, and the rules under which a claim is accepted, partially accepted or rejected.

These fields are a planning checklist, not a description of a specific software interface. Teams can apply them in a spreadsheet, a form or a trade promotion management tool.

Step 2: Collect store-level execution evidence

Execution evidence should be tied to four identifiers: the store, the promotion or task, the responsible person and the timestamp. Without those, a visit record or photo cannot be matched to a claim later.

What a store visit record should capture

  • Store identifier and visit timestamp.
  • Promotion or task identifier, so the visit links to the right activity.
  • SKU-level availability: which promoted items were present or out of stock.
  • Display location and set-up state, with each required element noted.
  • Shopper-facing price observed at the shelf or display.
  • Stock on hand, or an estimate of remaining cover.
  • One or more photos, each with a note on what it is meant to show.

What photos can prove

A photo is a point-in-time record. Used carefully, it can support statements such as: a display was in place; the correct point-of-sale material was visible; the promoted SKUs were on the display; the stated price was shown. That is useful for checking display requirements and confirming a task was performed.

What photos cannot prove

A photo cannot show sales uplift, and it should never be recorded as if it does. It also cannot show:

  • Whether shoppers bought the promoted product, or how many did.
  • Whether the display stayed in place for the rest of the activity period.
  • Whether the price charged at checkout matched the price displayed.
  • Whether stock was continuously available between visits.
  • Whether any sales change was caused by the promotion rather than by seasonality, competitor activity, distribution gains or pricing changes elsewhere.

Treat task completion, reviewer acceptance and business outcome as three different states. A reviewer can accept that a task was completed; that acceptance is not a finding about sales.

Step 3: Review sales outcomes separately

Sales data answers a different question from execution evidence. Where outcome review is in scope, agree the ground rules first: the baseline period, the comparison period, the cost scope included, and how other influences will be treated. Without an agreed baseline and period, execution completion and sales changes on their own do not establish causal uplift. A promotion can be fully executed and show no measurable effect, and sales can rise without execution.

Exception handling for promotion execution

Exceptions are normal. The goal is not to eliminate them but to resolve each one with a named owner, a defined corrective action and evidence that the fix happened.

  1. Detect and log. Record the store, promotion, date, observed condition and the evidence that supports it.
  2. Classify. Decide whether the issue concerns presence (display missing), completeness (partial display), availability (out of stock), price (mismatch) or documentation (missing proof). The class determines who fixes it.
  3. Assign an owner. Name one person responsible for the corrective action, typically a field supervisor, a distributor account manager or a trade marketing coordinator depending on the organisation.
  4. Define the action and deadline. State what will change, by when, and what evidence will close the loop.
  5. Capture closure evidence. A follow-up visit record, a corrected display photo, a stock confirmation or a signed acknowledgement, matched to the same store and promotion.
  6. Decide the claim impact. Apply the documented promotion conditions to decide whether the affected store or period is accepted, partially accepted or rejected.
  7. Review the pattern. If the same exception repeats across stores, treat it as a planning or capability issue rather than a series of isolated store failures.

Decision criteria: accept, follow up or reject

Example decision rules for reviewing execution evidence
Situation Typical decision Reason
Photo matches the display specification, within the activity period, correct SKUs visible Accept execution for that store and visit Evidence supports display requirements only, not sales
Photo shows a partial display or missing point-of-sale material Open a corrective action with closure evidence The defined requirement was not met
Promoted SKU out of stock at the visit Flag an availability exception and check the stock cover requirement Execution may be technically present but unsupported
No visit record or photo for a claimed store Do not accept until evidence is provided or the documented missing-evidence rule is applied The claim is not supported by evidence
Sales rose with no execution evidence Keep execution findings and outcome findings separate An outcome cannot stand in for execution evidence

The exact rules are a business decision. Write them into the promotion conditions before the activity starts so every reviewer applies the same standard.

Common mistakes

  • Treating a display photo as proof of sales uplift.
  • Counting assigned stores as completed stores; keep target, eligible, executed and reviewed stores separate and state the reporting period.
  • Reviewing claims without a documented baseline or an evidence deadline.
  • Logging exceptions without an owner, so nothing closes.
  • Comparing sales across stores with different baselines, footfall or distribution without saying so.

A practical verification checklist

  • Approved plan on file with eligible products, activity period, target stores, mechanic, display specification and stock requirement.
  • Evidence requirements and claim rules documented before the activity begins.
  • Every visit record linked to store, promotion, person and timestamp.
  • Photos described by what they show, never by what they are assumed to prove.
  • Exceptions logged, owned, actioned and closed with evidence.
  • Outcome review run on an agreed baseline period with the cost scope stated.

Where trade promotion software fits

Software can standardise the visit record, evidence capture and review workflow, but it does not change what the evidence proves. Airpalm publicly describes mobile visits, route planning, store audits, sales orders, inventory and promotion management (source: airpalm.com, checked 9 October 2026). If you are evaluating a platform for this workflow, ask for a demonstration of its actual supported planning, execution, review and reconciliation scope, and validate role permissions, data sources and exception handling. Ask which parts are standard, which are configured and which require separate integration. Background on the wider discipline is available in TPM: what it is and how it works, with related reading on retail execution and promotion reconciliation.

Frequently asked questions (FAQ)

Does a compliant display photo mean the promotion claim will be accepted?

No. A photo can support the display requirement for that store at that moment. Acceptance depends on the documented promotion conditions, which normally also cover the activity period, eligible products, the observed price and the stock requirement, plus submission deadlines. Reviewers should record the photo as evidence of execution, never as evidence of sales.

How should we handle stores with no execution evidence?

Decide the rule before the activity starts and apply it consistently. A common approach is to leave the claim unaccepted until evidence is provided, while keeping target stores, eligible stores, executed stores and reviewed stores as separate counts for the stated reporting period. Log each missing-evidence case as an exception with an owner and a closure action.

Why can we not simply compare sales before and after the promotion?

A before-and-after comparison needs an agreed baseline period, a comparison period, a defined cost scope and a stated treatment of other influences such as seasonality or competitor activity. Execution completion and sales change on their own do not establish causal uplift, and no promotion review should promise a guaranteed return.

Who should own promotion execution exceptions?

Ownership depends on how the business is organised. Field supervisors, distributor account managers and trade marketing coordinators are common owners. What matters is that each exception has one named owner, a defined corrective action with a deadline, and closure evidence matched to the same store and promotion.

Put this guide into practice

This general-purpose worksheet is a starting point. Adapt its fields, responsibilities and rules to your business process.