• ORDER VALIDATIONS • SETUP GUIDE

How to choose between Checkout interaction and Checkout completion validation

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

Choose when a validation is evaluated and test both early feedback and final checkout enforcement.

When to use this guide

Use this when a rule shows a message later or earlier than expected.

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

Use an existing minimum-order rule and test an invalid cart before and at the final payment action.

Step-by-step instructions

  1. Open the validation and confirm its invalid-state condition and message.
  2. Review Run location and select Checkout completion for final enforcement.
  3. If earlier feedback is intended, also select Checkout interaction using the available controls.
  4. Save and activate. Start an invalid checkout and trigger ordinary checkout interactions; record when the message appears.
  5. Attempt checkout completion in a test flow and confirm the invalid state is blocked.
  6. Correct the input, repeat the relevant interaction, and verify the final valid checkout can proceed past this rule.

Screenshot to add: The validation’s Run location controls.

Verify the result

Test Expected result or check
Interaction selected Observe earlier evaluation at supported interactions.
Completion selected Verify enforcement at the final completion action.
Corrected state This rule stops producing its invalid-state error.

Screenshot to add: The same invalid cart during interaction and at checkout completion.

Limitations

  • Showing an error early does not establish final enforcement unless its run location is configured.
  • An unavailable or incomplete input can affect evaluation timing.

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.