Guest checkout: what it costs and what the law requires

Guest checkout costs little and almost always pays: one field fewer to fill, one account fewer to run, one order that would otherwise die on the sign-up screen. The rule to respect is not technical, it is legal: the final button must say that payment is being made.

A mandatory account brings passwords, password resets, email verification and erasure requests; guest checkout asks only where to ship. The real cost is not technical: without an account the order is found through a number and an email, so you need an order lookup page and fraud checks that do not rely on user history.

What the law requires

Italy transposes those rules through the consumer code, Legislative Decree 206/2005. The practical consequence: the button label, the cost summary and the withdrawal instructions are part of the checkout, not of the terms page nobody opens.

The three costs of letting people buy as guests

• Support: guests write "I cannot find my order". You need a lookup page taking order number and email, not a login link.
• Marketing: without an account the email is collected at checkout with a separate, unticked box, as the ePrivacy Directive requires.
• Fraud: there is no account history, so checks lean on address, email, phone and the speed of the order.
• Returns: the 14-day withdrawal does not change, only the way you identify the case, with an order number instead of an account.

The minimum flow

Email, address, shipping, payment, confirmation. Five steps, one field per screen where possible, the total with shipping visible before payment. Strong customer authentication adds a step on the bank site: if the return does not restore the cart, the order is lost and the customer does not try again.

# il checkout chiede un account prima di vendere?
curl -s https://www.esempio.it/checkout | grep -ci "accedi\|registrati"

# il pulsante finale dichiara il pagamento?
curl -s https://www.esempio.it/checkout | grep -o "Paga ora\|Ordina con obbligo di pagamento"

# la spedizione compare prima del pagamento?
curl -s https://www.esempio.it/carrello | grep -ci "spedizione"

Blocks from the catalogue

The Checkout 01 block from commerci covers the screen structure, the Cart 01 block from the same publisher covers the summary; both are React and Tailwind, with the licence declared on the record and worth checking. For fields, the form category holds 32 blocks and form-1 from efferd is a short form to adapt for the shipping address.

The limitation to state

The blocks are interface only: no server-side cart, no payment, no strong customer authentication. With 4 checkout blocks in the catalogue, the part is adapted, not copied. The legal side, meaning the button label, the pre-contractual information and the withdrawal instructions, stays with the seller: no component generates it.

Mistakes that cost orders

• Asking for sign-up after the address is filled: the customer has spent two minutes already and leaves.
• Working out shipping at the last step: the total changes once the decision is made.
• Printing the error at the top of the page instead of next to the field that caused it.
• Letting the session expire during the bank redirect, so the cart is empty on return.
• Sending no confirmation with an order number: that is the only way a guest finds the purchase again.

Where to continue

The full picture is in creating an ecommerce site, the neighbourhood case in local ecommerce, the catalogue sections in blocks for ecommerce. If the choice is between a closed platform and components, the comparison is in WordPress, Wix or React components.