Set up and edit checkout settings

Set the checkout so it requires a shipping address only when a physical product is in the cart, collect phone numbers for high-value orders, and enable order notes. Lock in these settings before Friday and test a purchase to confirm the correct validation and the summary email displays order notes.

Before I hand this checkout to the ops team, make it easy to approve: surface any fields that add friction like optional accounts or forced phone numbers, show conversion lift estimates for removing or adding a field, make the guest checkout path obvious, and flag any existing apps that alter the checkout flow.

This morning checkout began requiring a phone number for every purchase; CS is seeing abandoned carts and I don’t know which app or recent setting caused it. Tell me the most likely causes, how to check which checkout scripts or settings enforce phone collection, and the fastest safe change to restore previous behavior without breaking fraud controls.

Over the last six months I tweak checkout fields to try to reduce fraud or improve fulfillment, and each change spikes abandonment for a week. I keep losing sales and trust. Which habit to change: a rollback window, user testing before release, or a change-approval step with conversion impact estimates? Recommend one repeatable habit that stops these costly spikes.