Branch on the button, use your own fonts

The quiz pattern works properly now: two buttons on one step can send visitors down two different paths. And your own font files — the ones already sitting in your Shopify admin — are available everywhere you pick a typeface.

Route by the button they clicked

"Which describes you? [Runner] [Cyclist]" — until now logic could branch on a field's answer, but not on which button a visitor pressed, so a step like that had nowhere to send them.

There's a new Button condition in the logic editor. Pick a button on the step, pick the step it leads to, and the rule reads plainly: Button clicked → Runner. The buttons are listed by name, so you're never staring at an ID.

It works everywhere routing already works — the rule simulator drives it, the canvas draws the edge, and a duplicated form keeps its branches pointing at the right buttons.

"Otherwise" is now yours to add

Adding your first rule used to seed an Otherwise branch you couldn't remove. Because an "otherwise" always matches, it quietly overrode what your other buttons were configured to do — a button set to redirect would be closed instead, by a rule you never wrote.

The fallback is now an explicit Add otherwise control. Leave it off and each button does its own thing; add it when you actually want a catch-all. Any form already carrying a seeded fallback can drop it — the card has a Remove button now.

While we were in there: the operator picker only offers comparisons that make sense for what you're comparing, and disappears entirely when there's only one.

Redirect buttons work on popups

A button set to redirect fired reliably in inline embeds but not in popups, and a redirect button on a final "thanks" screen could be swallowed altogether. Both are fixed — the visitor lands where you sent them, from any placement, including the last screen of the form.

Your fonts, from your Shopify Files

Upload your brand's font files to Content → Files in your Shopify admin, and Formtoro will find them. They appear under Your store's fonts at the top of every font picker in the builder, ahead of the Google Fonts list, and each one previews in its actual typeface so you can confirm we matched the right file to the right weight.

Nothing to paste, no CSS, no separate hosting — the files stay on Shopify and are served from your store.

See Custom fonts for how to name the files so weights and italics are read correctly.

Split with Image, and previews before you commit

The block picker has a new Split with Image step: a bleed-edge image beside your capture content. It was previously only offered when creating a form; now you can add one to any form, and a too-narrow popup widens itself to fit — without narrowing anything or overwriting a width you chose.

Every template in the picker now previews on hover, rendered by the real form renderer in your theme and your colors, at the width the step will actually be. It's the step you're about to insert, not an illustration of it.

Smaller things

• Klaviyo list pickers are searchable. Both the shop-wide default and the per-form picker now filter as you type and page through long catalogs, instead of one long flat list.
• Field renames reach your integrations. Renaming a field in the builder now updates its label in the Klaviyo and Shopify metafield mapping tables.
• Discount code picker searches your whole catalog. Searching now runs against Shopify rather than the first page we'd loaded, and pasting an exact code verifies it directly.
• Permission-aware forms list. Duplicate, Archive, Restore and Create no longer appear for teammates who can't use them, and a refused action explains itself instead of replacing the page with an empty red banner.
• A clear reason when brand detection can't run. If your store's Shopify permissions predate theme access, the brand step now tells you so — with a reconnect link — instead of showing a blank result.