• CONDITIONS & TROUBLESHOOTING • SETUP GUIDE

How to test Rivio rules and blocks before activating them for customers

By Rivio Support Team
2 min read

What you will achieve in this guide

Follow the feature-specific setup and testing instructions below. Check the supported pages and plan requirements before activating the feature.

EXPECTED SETUP TIME Varies by feature
COMPATIBILITY See requirements in this guide
TECHNICAL DIFFICULTY Zero Code Required

Prepare a controlled test that distinguishes saved configuration, activation, placement, and actual customer behaviour.

When to use this guide

Use this before introducing a new rule, visual block, upsell, or validation.

Before you begin

Open Apps → Rivio Checkout Customizer in the intended store. Use supported conditions from the current editor and record the exact amount, product, customer, or address basis before testing.

Worked example

Test a dispatch banner on a supported Thank you page and a separate payment hide rule using matching and non-matching cases.

Step-by-step instructions

  1. Record the feature, supported page, Shopify plan requirement, Rivio entitlement, and expected result.
  2. Use a development or test store where possible. A duplicate storefront theme does not isolate store-wide Functions or the active checkout configuration.
  3. Save the feature as a draft while configuring. For visual content, use a suitable draft checkout configuration where available; Functions require an appropriate controlled test environment.
  4. Prepare qualifying, non-qualifying, and boundary cases using named test products, customers, addresses, and orders.
  5. Activate only within the intended test environment and save the matching placement if the feature needs one.
  6. Run the actual checkout, completed-order, or account flow on desktop and mobile. Verify stored data, totals, and enforcement where relevant.
  7. Record the result, correct mismatches, and only then enable the intended production configuration.

Screenshot to add: The test configuration state, target page, and placement.

Verify the result

Test Expected result or check
Saved configuration only Does not prove activation or placement.
Editor preview Helps inspect layout but does not complete an order.
Matching and non-matching cases Behaviour agrees with the configured scope.

Screenshot to add: A test record showing qualifying, non-qualifying, and boundary outcomes.

Limitations

  • Unpublished storefront themes do not isolate store-wide app rules.
  • A draft setting is not evidence of customer-facing behaviour.
  • Do not assume a draft checkout configuration contains every app backend rule.

Troubleshooting

Problem What to check
The expected result does not appear Check the saved state, exact feature configuration, supported page, and matching test inputs.
The preview and actual page differ Use a real test checkout, completed order, or signed-in account; editor data is simulated.
A change has an unexpected effect Repeat the same test with one relevant setting changed. Review other active rules before adding another copy.

Need help?

Email support@rivioapps.com with your store domain, feature name, saved settings, target page, and the expected and actual results. Include the test cart, order, or customer context needed to reproduce the issue.