In this guide

Guest checkout and account creation are different decisions
Guest checkout removes mandatory account creation from the purchase journey where the VirtueMart store configuration permits it. It does not remove the need for a usable delivery address, eligible payment method or legally required order information.
Optional account creation after a successful order is a separate capability. In Premium Checkout Suite, the customer explicitly opts in and the account is created only after the configured successful native order status. Joomla handles the secure password-setup email.
Keep these decisions separate when reviewing your checkout. A customer should understand whether they are completing an order, requesting an account, or doing both.
Start with the native VirtueMart configuration
- Review checkout and registration settings.In VirtueMart → Configuration → Checkout, clear Only registered users can checkout to allow guest checkout. Review On checkout, ask for registration separately: showing an account option is different from requiring an account. These labels are from the supported VirtueMart 4 configuration.
- Review shopper fields.Check which fields are published, shown in checkout and required for billing or alternative delivery.
- Review guest eligibility.Check the shopper-group, country, address, shipment and payment restrictions that apply to a guest’s actual cart.
- Check the native cart first.If a required method or validation rule fails in the native VirtueMart cart as well, resolve that configuration before treating it as a layout problem.
Premium Checkout Suite presents the supported native results. It does not grant a guest access to a method that VirtueMart has made unavailable.
Choose a layout that supports the field set
For a compact form, One Page checkout can keep the customer details, method choices and review together. If the order needs a more guided sequence, Multistep checkout presents focused stages before the final confirmation.
Both layouts can serve guests where enabled. A layout selection alone does not change the store’s registration policy. First confirm the native guest configuration, then inspect how that configuration appears in the chosen layout.
The One Page vs Multistep comparison explains how to evaluate the form length, customer familiarity and mobile experience.
Keep the guest form relevant
Ask for the information needed for the current order. Check whether an alternative delivery section is relevant and whether company-specific fields should apply to every shopper.
Use the supported conditional-field builder for approved show, hide and require conditions. Avoid hiding a required field with CSS or changing browser validation to force an incomplete form through. Server-side validation must continue to protect the native order requirements.
Changing a field’s visibility does not change tax liability, payment eligibility or the customer’s authorization to join a restricted shopper group.
Common issues and where to look
- The customer is asked to register
- Review the native registration requirement and whether a template or another checkout extension is taking over the customer route.
- No delivery or payment method appears
- Check the actual guest cart against country, address, shopper-group and other method restrictions in VirtueMart.
- A hidden field still blocks progress
- Inspect the shopper-field requirement and any supported conditional rule. Do not bypass the requirement using a template edit.
- No account appears after the order
- Confirm the customer opted in, the order reached the configured successful status and the email is not already linked to an existing account.
The troubleshooting documentation provides the product-specific checks.
Review the configured journey before launch
In a private test environment, inspect the guest form, required-field messages, delivery/payment choices and final review on a phone as well as a desktop. Reuse existing accepted order and payment evidence when the relevant behavior has not changed.
If you change the optional post-order account policy, review that affected path separately. Keep test customer details fictional and use only the payment provider’s supported test mode for a necessary payment test.
Follow the installation and setup documentation, or view the product, supported versions and current plans.
