Why We Ask Explainer
Every checkout field justified with its use and boundary, and the one field that is not there.
Every checkout field justified with its use and boundary, and the one field that is not there.
Search blocks by description or jump to a page.
The source for every Ecommerce block is included with Basic and Pro. Pick a plan to copy the code.
Already purchased? Log in
Why We Ask Explainer justifies every checkout field in ruled rows with a use and a hard boundary, email for receipts and the tracking link and nothing else by default, phone printed on the shipping label and nowhere else, shipping address deleted when the return window closes. The fourth row is date of birth, tagged Not collected, with the invitation to notice which stores do want it.
Fields are one array, each carrying an icon, the field name, and the boundary copy. The absent row as the closer is the trust move the block exists to make.
Reach for this block on the checkout page or in the account privacy settings wherever a buyer might wonder why a field is there. The absent row copy must match actual practice: if date of birth ever appears at checkout, this block calls it out.
A natural flow around it on an Ecommerce Pro page:
Before
After
One strong use is the three plus one checkout fields. Other justification panels:
Tip: “We have never called a customer to sell anything” is a provable claim and it does more work than any promise to respect your privacy.