A promotion can be configured correctly in your own store and still produce a different price on another channel. This can happen if dates are interpreted differently, a coupon is combined with an offer, or a channel cannot support an eligibility condition. The problem is not usually just technical: commercial rules may also be ambiguous, or responsibilities may be split without a shared approach.
To manage promotions across multiple ecommerce channels, separate three decisions: what offer should apply, which system determines the outcome, and how the rule is represented in each channel. This distinction helps identify incompatibilities before publication and determine what to do when a channel cannot reproduce the commercial intent exactly.
Why promotions produce different results
A promotional rule includes more than a percentage or amount. It may depend on products, categories, customers, quantities, dates, codes, availability, or usage limits. Each channel may interpret or support these components differently. When an offer is entered separately in several places, the chances increase that a condition will be omitted, changed, or left out of date.
Concepts that should remain distinct are also easy to confuse. The base price is the reference value before the offer; the promotional rule determines who can receive what benefit and under which conditions; and the displayed price is how the offer appears in a channel. There is also the final price resulting from the combination of applicable rules. Differences between channels can arise at any of these levels.
Before changing systems, diagnose the case with specific questions: Is the commercial rule written unambiguously? Did the channel receive the correct version? Was the final price calculated using the same precedence? Had the offer already expired or reached its usage limit? Recording the cause prevents a pending business decision from being treated as a synchronization failure.
Define the source of truth
There is not always a single system capable of managing price, eligibility, and publication across every channel. What matters is assigning clear ownership to each decision and preventing two systems from changing it without coordination. For example, one system may be responsible for approving the commercial rule, while another passes on the required data and each channel presents the offer according to its own capabilities.
Document which system determines each element: base price, access conditions, validity period, stacking, limits, and publication status. If the final price is calculated in a channel, make clear which rules it receives and which it applies locally. If the source of truth cannot send a particular condition, decide whether to adapt the promotion, limit it to certain channels, or not publish it there.
The decision should reflect how things actually work, not just a diagram. Define who can create, approve, change, and withdraw a promotion; who confirms that it reached each channel; and who responds to discrepancies. A source of truth without operational authority does not prevent conflicts: it needs accountable owners, controls, and a record of relevant changes.
Set precedence and discount-stacking rules
The question “Can these be combined?” needs an explicit answer for each type of benefit. An automatic offer, a coupon, a quantity discount, and a benefit for a customer group may all apply to one purchase. Without defined precedence, different channels may apply different rules first and display incompatible amounts.
Specify whether promotions are mutually exclusive, stackable, or stackable only under certain conditions. Also state the order of application when it matters—for example, whether a discount applies to the base price or to an already discounted price. Do not assume that a word such as “combinable” will be interpreted the same way by every team or system. It is better to describe the expected outcome for a specific purchase scenario.
For each rule, define:
- Eligibility: the products, categories, customers, or quantities that meet the conditions.
- Compatibility: the benefits that can coexist and those that are excluded.
- Precedence: which rule is evaluated first if several apply.
- Expected outcome: the final price and the messages that should be displayed.
- Limits: usage limits per customer, order, or period, where applicable.
If two rules cannot coexist in a channel, do not hide the limitation. Decide which offer takes precedence and communicate the difference internally before publication. Otherwise, the behavior may seem random to customer support teams and to people reviewing orders.
Model dates, time zones, and exceptions
Dates need precise definitions. Specify when the promotion starts and ends, which time zone applies, and whether the ending moment is inclusive or exclusive. A rule that ends at midnight can leave uncertainty about which orders qualify, especially if channels operate in different time zones or display information with a delay.
Also record exclusions in a verifiable way: excluded SKUs, unavailable products, ineligible customers, or excluded locations, where relevant. Avoid vague phrases such as “selected products” if the people implementing the rule cannot identify the selection. For usage limits, specify how failed attempts, cancellations, and returns are counted when they affect the promotion.
Rules should cover edge cases, not just the ideal customer journey. Check what happens when an order is started before expiry and confirmed afterward, when a cart changes, or when a code is used on a purchase that is later canceled. If the policy cannot be expressed in the same way across all channels, document the difference and determine its commercial impact.
Translate the intent for each channel
The technical representation is a translation of the commercial rule, not an opportunity to redefine it. Prepare a shared description and, for each channel, state which conditions it supports, which require adaptation, and which cannot be reproduced. A valid adaptation must preserve the intended outcome and be approved; if it changes who receives the benefit or what price they pay, it is a commercial decision.
Compare channel capabilities before committing to an offer: coupon application, exclusions, product selection, schedules, quantity restrictions, and price presentation. If a channel cannot support an essential condition, the options are to limit the promotion there, create an approved variant, or choose a different promotion mechanic. Publishing an approximate version without telling anyone is inadvisable: it can lead to unexpected prices and complaints.
To make oversight easier, use a promotion record with an identifier, version, conditions, planned channels, dates, and owners. Each publication should be traceable to that version. This makes it possible to check whether a channel received an old rule, applied an authorized adaptation, or has a configuration that differs from what was approved.
Validate before publishing
A useful review checks both the configuration and the visible results. Confirming that a promotion was created is not enough: test purchases that qualify and purchases that do not. Include an included product and an excluded one, a valid and an invalid code, a permitted and a prohibited combination, and relevant date and quantity limits.
In each channel, compare the final price with an expected result calculated from the approved rule. Also review the offer message, the conditions shown to the buyer, and the information received by the order-confirmation process. If the displayed price and the charged price differ, stop publication or the campaign until the cause is identified and a response is agreed.
Set release criteria: approvers, channels checked, test cases passed, and evidence of the published configuration. If a promotion cannot be validated in a channel, the decision is not to “assume it is fine.” Determine whether to correct it, restrict it, or postpone it.
Monitor changes and remove expired offers
Publication does not end the work. Watch for signs such as unexpected final prices, differences between channels, rules that remain active after expiry, update errors, or an increase in offer-related inquiries. These signs help distinguish an isolated incident from a systematic process problem.
Define what to do when a discrepancy occurs: who can pause an offer, how affected teams are informed, and how to determine which orders need review. Keep a change history and publication time so you can reconstruct which rule was active. Withdrawal also needs to be verified in every channel: marking a promotion as finished in one system does not prove that it has disappeared from every customer-facing surface.
Checklist for agreeing on responsibilities
Before launching a multichannel promotion, make sure the team can answer these questions clearly:
- Who approves the commercial intent, and who changes the rule?
- Which system determines price, eligibility, validity, and stacking?
- What precedence applies when benefits overlap?
- Which time zone, exclusions, and limits have been defined?
- Which conditions can each channel represent, and which adaptations are approved?
- Which test cases were run, and who authorized publication?
- How is an incorrect result detected, and who pauses or withdraws the offer?
If any answer depends on an individual's interpretation, the promotion is not ready. The most robust approach is to maintain an unambiguous commercial rule, assign authority over each data point, translate it with explicit limitations, and validate the outcome in every channel. This prevents differences from being discovered by surprise and turns them into decisions teams can prevent, explain, and correct.