Price-match automation policy template for retailers

A price promise needs a decision rule that your ecommerce and service teams can explain. Use this template to decide which competitor offers qualify, how to compare prices and when an exception needs review. Start with your approved commercial policy, then test its behaviour before connecting it to a shopper experience.

Start with a promise you can apply consistently

Write the shopper-facing promise first. Does it match an eligible competitor, beat that price by an agreed amount, or provide a service-team review? Name the product types, trading regions and sales channels it covers. A rule that is obvious to the pricing team may still be ambiguous to a shopper comparing a member offer with a standard price.

Create one policy record with an owner, version, effective date and escalation destination. Keep the public explanation concise, with the detailed decision table available to the team operating it. Particular Audience describes Price Match and Price Beat as enforcement of an approved price policy; use a scoped review to establish which of your rules are supported in your implementation.

Compare the same purchasable offer

Make equivalence explicit: product identity, variant, condition, pack quantity, included accessories and warranty scope. Then assess competitor eligibility, stock, delivery to the shopper's destination and any membership or coupon conditions. Record the observed offer and its time, rather than retaining only the final comparison price.

Choose a consistent tax and delivery basis. If either is unknown, the correct result may be review rather than approval. An apparently lower headline price is insufficient when the competitor offer cannot actually be purchased on comparable terms. Set an evidence-age rule that fits the category's volatility; the template deliberately leaves that decision with the retailer.

Apply eligibility before calculating the adjustment

Use this order: establish equivalent item, establish eligible seller and offer, calculate the comparable price, calculate the proposed match or beat, then check whether it would lower the current price and apply commercial limits. If the current price is already at or below the target, leave it unchanged rather than increasing it or describing it as a new price beat. Rejecting an ineligible offer should produce an understandable reason. A margin constraint should not silently change a promised price beat into a different offer.

Here is a synthetic example, using pounds on a consistent tax basis and equal delivery charges. The current price is £100, the eligible competitor price is £95, and the policy proposes a £1 beat. Relevant cost is £70 and the minimum contribution margin is 20%. The floor is £70 ÷ 0.80 = £87.50. The proposed £94 price is above the floor, gives a £6 reduction and leaves £24 contribution, or about 25.53% of sales. If the competitor price falls to £80, the proposed £79 fails the floor and goes to the exception path.

Make exceptions reviewable

Give each decision a reason code, policy version and evidence reference. Separate an expired observation from a genuine policy exclusion so service teams can resolve the right problem. Test approvals, rejections and uncertain evidence before launch, then inspect disagreements between automated and human decisions. Use the price-policy RFP when you need to turn those requirements into a vendor evaluation.

Illustrative example

{"label":"Synthetic policy adjudication; not customer data or a PA default","currency":"GBP","tax_basis":"consistent net basis","delivery_both":0,"inputs":{"current_price":100,"competitor_price":95,"beat_amount":1,"relevant_cost":70,"minimum_margin_rate":0.2,"cap":10},"outputs":{"candidate":94,"floor":87.5,"discount":6,"contribution":24,"margin_percent":25.5319148936},"alternative":{"competitor_price":80,"candidate":79,"outcome":"review because candidate is below the floor"},"already_lower":{"current_price":100,"competitor_price":105,"beat_amount":1,"candidate":104,"applied_price":100,"applied_discount":0,"decision":"no_change","reason_code":"ALREADY_AT_OR_BELOW_TARGET"}}

Downloads

• pa-price-match-policy-template.csv (illustrative template)
• pa-price-match-policy-tests.json (illustrative template)

Sources

• Price Beat & Price Match — Automated Policy Enforcement, checked 2026-10-25
• Price Beat RFP Builder, checked 2026-10-25

Frequently asked questions

Should a margin floor override a price-match promise?

Define that boundary in the policy before launch. If the proposed price cannot satisfy the approved floor, route the request to the published exception process. Do not silently substitute a higher price and describe it as a successful match or beat.

How should member prices and delivery charges be handled?

State whether membership, coupons and delivery are eligible, then compare offers on the same basis. Preserve the conditions with the evidence. If the competitor’s payable price or the shopper’s eligibility cannot be established, return a review outcome rather than inventing a comparable amount.

Does this template configure Particular Audience automatically?

No. It is a policy-design and testing resource. Bring the completed rules and examples to a product review so the team can confirm supported controls, data inputs and integration behaviour. Approval of a document is separate from deploying its rules into a live shopping journey.

Related guides

• Price matching vs dynamic pricing vs price affirmation: Compare public repricing, policy-approved price matching and evidence-based price affirmation. Choose the right action with a practical retail decision matrix.

Templates and checklists · All guides