Testing a custom checkout

Designer changes vs. Altru updates

When changes are made in the designer but are not saved, the system will continue to pull information from Altru. This is intended behavior and ensures that data remains consistent unless updates are added in Altru.

Combinations

Currently, combination web forms are supported in the standard Altru display. Each item must be created individually if multiple offerings are required.

General settings and delays

Any changes made in the general checkout settings should normally appear after a short period of time. If updates are not reflected after a couple of minutes, please contact the support team to validate the settings of the organization setup.

Synchronization with Altru

If Checkouts are not synchronizing, it is most often because the names differ between the checkout setup and Altru. Ensuring that the names match exactly is the best way to avoid synchronization issues.

Preview vs. live Checkout

The preview feature is designed to provide a general idea of how the checkout will appear and behave. However, it is not connected to the live database, which means some functions will not work as they do in the real environment. Examples include:

  • Date and time updates may not display correctly.
  • Login features may not function as expected.

This limitation is intentional. Maintaining a preview that fully mirrors the live environment would be difficult to support over time. The preview should be considered a guide rather than a replica.

Preview pages have a yellow banner with the “This page is in preview mode. View the actual page” text.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.