Launch pages that only say ‘coming soon’ collect nothing. Use a form so fans can pre-order with a variant, quantity, and ship-to ZIP or postcode, then you invoice or charge when the container actually clears.
Daily digest is fine until you open charging.
Those two prevent a support nightmare.
Put the window next to the button.
Match emails to the dashboard before you take money.
A pre-order is a commitment to buy a thing that does not exist on the shelf yet. US FTC guidance cares about ship-by honesty; UK consumer law cares about clear delivery timing too. The HTML form is not the charge. It is the list of who wanted which variant and where it should go when you are ready to take money.
If you must take a deposit, do it on a hosted payment page after this row exists. Putting card fields on a static launch page is how you combine PCI pain with a slip date.
When the boat is late, you will be glad you stored quantity and variant separately from a tweet.
State a target ship window in the intro and update the page if it slips. Silence is what gets you chargebacks later.
Kickstarter is a channel. Your own domain is a list you still own in year three.
Best when you will invoice or charge later in a proper cart.
Use when you are already on Shopify and need card-now. This form is for sites that are not.
Fine for hype. Weak when sizes matter.
They take a cut and own the relationship. Run this form in parallel if you can.
Campaign microsites are often a single HTML folder on a CDN. export when the warehouse says go.
First-wave shipping: US ZIP labels and UK postcode labels are different print jobs. Split the CSV; do not invent one address format.
Depends on your terms and whether you took money. This form alone is usually interest plus details.
Say how in the copy. Honour it before you charge.
Hosted payment page after the row exists. Not this HTML.
Edit the page. Do not rely on buyers reading a tweet.