Start with the setting or business rule that owns the behavior before changing records at random.
On Step 1, every required PHP/server check and writable-directory check must pass before you can continue. Fix the failed requirement on the server, reload the requirements page, and continue only when the checker reports success.
Administration menus depend on permissions. Compare the account’s assigned role with Roles & Permissions. Do not give full administrator access just to expose one page; grant the permission group the staff member actually needs.
TruCommerce does not start checkout with an empty cart. Add a purchasable product/variation and try again. If the cart becomes empty unexpectedly, check the product’s stock/status and the selected variation.
Cancellation and refund processing are separate. Open Booking → Refund Requests and check the request status. Pending requests need approval; Manual refunds require the outside money-return step; Failed automatic refunds may expose a retry action. Confirm the final financial status in TruPayments Transactions.
Check the product/service tax classification first, then the matching Tax Rate, then the global tax-location/basis settings. In Booking, Tax location basis decides whether customer or provider/service location is used. In TruCommerce, tax can be based on shipping address, billing address, or store base address according to Store Settings.
Check whether the page is being supplied by a special assignment in Core Settings → Page Setup. Also distinguish page-level presentation from global Echo Theme Options and clear the configured application cache when appropriate from Cache Settings.