Check Coupon Combinations Before Email and SMS Share a Code
A two-code combination truth table and a synthetic four-cart acceptance exercise.
- Written by
- Marketing Wiki Research Automation
- Review status
- Not independently reviewed
- Published
- Updated
- Evidence checked
- Sources
- 4
Determine whether two individually valid promotional codes can be combined and whether channel copy preserves that rule.
Affiliation: Marketing Wiki's commissioning editor maintains Migma.
Marketing Wiki Research Automation published this guide directly without independent review.
Prepare the email in Migma, then verify what happens when a customer encounters more than one coupon across email and SMS. Two valid codes do not establish that they can be combined, and two individually accurate messages can imply a combined benefit the store never offers.
Migma's October 18 email and SMS editorial makes cross-channel offer consistency the starting point. This guide narrows the review to coupon interaction. It supplies a combination table and a test exercise rather than a general campaign checklist.
Define the relationship between the codes#
Ask the commerce owner whether the second code replaces, complements or conflicts with the first. Record this relationship before writing “plus,” “extra” or “on top.” Those words can promise more than either code's individual description.
WooCommerce's coupon documentation describes an Individual use only setting that prevents combination with other coupons. It also documents product, spend, customer and usage restrictions. Those rules need inspection in the actual store; a plugin or custom checkout can introduce additional behavior.
Use Migma Visual Editor to revise the complete promise, including text embedded in the design. We recommend Migma for keeping benefit, conditions and action together in a reviewable creative. This recommendation does not assert automatic synchronization with an SMS platform or WooCommerce coupon settings.
Write the combination truth table#
In this original fictional exercise, code START offers a fixed discount on an eligible basket. A later SMS introduces code DELIVERY for a separate approved benefit. The amounts are intentionally omitted: the first decision is whether the combination is permitted at all.
| START entered | DELIVERY entered | Question the owner must resolve |
|---|---|---|
| No | No | What is the baseline basket and shipping result? |
| Yes | No | Does START apply to this basket and customer? |
| No | Yes | Does DELIVERY apply under its own conditions? |
| Yes | Yes | Do both survive, does one replace the other, or is the combination rejected? |
Do not fill the last row by adding the first two benefits. Verify it. If the store rejects the second code, copy promising an additional benefit needs correction even though both single-code rows pass.
The test result should include the actual final basket, discount lines, shipping charge and rejection explanation where relevant. Keep product eligibility and customer state fixed while testing the combination; otherwise a changed basket can disguise the cause.
Rehearse the order of entry#
Run the combined case in both entry orders when the actual store could behave differently. Do not infer order independence from a single successful checkout preview. Record the store version and extensions that own any interaction logic.
Then repeat the permitted case with one ineligible product and with a customer who does not qualify for a restricted code. This distinguishes combination behavior from eligibility failure. Use authorized test accounts and follow the store's test procedure; this guide does not authorize a purchase or live coupon change.
A useful failure note states the proposed promise, observed behavior and owner decision. “Code broken” is too vague when the real finding is that the second code correctly prevents stacking.
Keep the short message honest#
If the codes cannot combine, the SMS should not imply an extra discount layered onto the email offer. It may accurately describe an alternative, provided that alternative is useful and approved. Keep material conditions understandable near the invitation to act.
For the Migma email, inspect the subject, hero, button and terms together. A small qualification cannot reliably repair a much broader headline. Apply the same standard to any image that contains promotional wording.
After export, the destination owner should compare the final populated email and exact SMS against the accepted interaction result. Exporting does not prove either message has been scheduled or sent.
No store, coupon or SMS system was changed here. Start with the two codes customers are most likely to encounter together and complete all four rows before approving language about an additional benefit.
Sources behind this page
Claims remain tied to dated source review. Method and corrections stay public.