Walkthrough
Promotion Walkthrough
Complete promotion walkthrough with configuration, expected results, and recovery guidance.
SoundSync
Promotion Walkthrough
-
Choose the supported type
Use the promotion workspace and distinguish checkout-backed offers from proposed behavior.
-
Scope
Select products, discount/reward rules, dates, and usage limits.
-
Price
Keep paid checkout at or above $9.99 after discounts.
-
Preview
Check eligible and ineligible products and configured stacking.
-
Publish
Confirm the intended backing and storefront presentation.
-
Review results
Inspect performance and reward/fulfillment state under the same scope.
SoundSync
Promotions
Check the offer with an eligible and an ineligible cart
For a scheduled deal, save the product scope, discount, start/end time, and publication state. For a promo code, also review the code, usage limits, customer restrictions, and expiry. A campaign draft created from a deal still needs its own audience and send approval.
Use a qualifying product and a nonqualifying product in separate previews. Confirm that the rule changes only the intended lines and that the final paid cart stays at or above $9.99 after discounts and before tax. Discounted lines and BOGO gifts can be below that amount. A code or draft that saves successfully is not proof of checkout backing.
Verify the reward, not only the discounted total
For BOGO or post-purchase rewards, inspect the qualifying order and the exact reward product or issued coupon. Preserve the link between the reward and its purchase when diagnosing a refund. Product bundles and subscription bundles have their own definitions; do not substitute a descriptive bonus card for actual included access.
If an offer does not apply, check dates, scope, eligibility, exhaustion, and stacking before changing the base price. Compare promotion activity with the order record; do not infer a successful payment from a redemption counter.
SoundSync
Contract and detailed settings
Read the full guide
Field definitions, permissions, and current limitations.
Test safely
Use permitted test identities and the intended environment. Inspect allowed and rejected outcomes. Keep private customer data, serials, credentials, payment details, and verification links out of published examples.
