Frequently asked questions

No. You build fields in a visual editor with a live preview, then publish. Everfield loads through a Shopify theme app embed, so no theme files are edited and switching the embed off restores your theme exactly as it was.

The one thing people miss is pressing Save in the theme editor after switching the embed on — see Turn on the app embed.

Yes. The widget is plain, CSS-scoped HTML — no Shadow DOM and no iframe — so it renders as a native part of any Online Store 2.0 theme, including Dawn, Horizon, Prestige, Impulse, Turbo and custom builds.

If a theme lays the product page out in a way the automatic placement cannot read, you drag the Product Options block into position yourself on the product template. Third-party cart drawers that do use a Shadow DOM, such as Rebuy Smart Cart and CartX, are supported through a dedicated setting.

About ten minutes for a first working set of options: turn on the app embed, create an experience from one of the four starter templates, adjust the fields, publish, and test on your storefront. Create your first set of product options walks the whole path.

In Shopify, as native order data. Answers collected on a product page save as line item properties and appear under each line item on the order. Answers collected in the cart save as cart note attributes and appear under Additional details on the order.

Because they are ordinary Shopify fields, fulfilment and order-printer apps read them the same way they read variants. Two caveats worth knowing up front: Shopify's built-in order CSV has no line item properties column, and the stock packing slip template does not print them until you add a loop to it. See Find what customers entered on an order.

Nothing is lost, because it was never ours. Everfield does not store what customers type — the values live on your Shopify orders. Uninstalling removes the widget from your storefront; every past order keeps its data and stays exportable like any other order field. Uploaded files sit in your own store's Shopify Files and stay there too.

Yes. Values attach to the cart before checkout begins, travel through Shopify checkout untouched, and appear on the order in your admin. No checkout scripts or Shopify Plus requirement.

Yes. Run a product-page experience for per-item answers such as engraving text, and a cart experience for one order-level answer such as a delivery note. Note that only one published experience renders per placement — if two published product-page experiences both match a product, the first one that passes targeting is the one that shows. See Show options on specific products or countries.

No, and that is deliberate. The fields sit inside your theme's own add-to-cart form, so the answers attach when the customer presses your theme's Add to cart button — or Checkout, for cart options. A second save button would be one more thing for a customer to forget.

Twenty in total: fourteen that collect an answer — text, text area, number, quantity, phone, email, date, dropdown, radio buttons, swatch, toggle, file/image upload, checkbox group and product picker — and six display-only blocks for headings, paragraphs, dividers, spacers, custom HTML and size charts. The full reference is in Every Everfield field type explained.

Yes. Give a field or an individual choice an add-on price and the amount is collected through normal Shopify checkout. Charges go through a hidden, unlisted product in your catalogue with a variant per option and price, so every order line names exactly what was bought. (A second unlisted product — Bundle by default, renameable in Settings — also appears while the cart is set to show one merged line; it is what groups the lines together. Leave both alone.)

Two limits: you cannot charge from a cart-placement experience, and the “price per character” setting is a display-only estimate that is never billed. See Charge for an option.

Yes — that is conditional logic. Each field can carry up to five rules based on another field's answer or the selected product variant, combined with All rules match (AND) or Any rule matches (OR). A field hidden by a rule never sends a value to the cart. Conditional logic is available on Basic and above. See Show a field only when it is relevant.

In your own store's Shopify Files, on Shopify's CDN. The order carries the file URL, so fulfilment sees exactly what the customer uploaded and the file stays in your Shopify account. Files default to a 5 MB per-file cap. See Let customers upload a photo with their order.

Labels are free text, so you can write them in your store's language today. Structured multi-language translations for multi-locale stores are not built yet. Be aware that the label is also the key the answer is saved under on the order, so renaming a label changes the key on future orders.

Yes. Free includes 200 widget views a month, custom fields on product and cart pages, every field type, the starter templates and the live preview. The three paid plans — Basic $6.95, Advanced $19.95 and Unlimited Plus $24.95 a month — each start with a 7-day free trial. See Everfield plans, pricing and billing.

Two features are genuinely plan-gated: conditional logic needs Basic or above, and targeting needs Advanced or above. The rest of the difference between plans is the monthly widget-view allowance.

One view is counted each time your fields are rendered to a shopper on the storefront. Your current usage is shown on the dashboard and on the billing page. Today the monthly allowance is a fair-use guide rather than a hard switch — nothing stops working the moment you pass it, and we would contact you before anything changed.

No. The yearly price is exactly twelve times the monthly price. It exists so you can pay once a year instead of twelve times, not as a discount, and we would rather say so than let the toggle imply a saving that is not there.

Yes. Moving to Free cancels the Shopify charge. Your experiences and their settings are kept, and an experience that already uses a paid feature carries on working — the gate applies when you build something new.

In order of likelihood: the experience is still a draft; the app embed is off or unsaved in your published theme; targeting is excluding that product; another published experience is winning the placement; or your theme's layout defeats the automatic placement, in which case you drag the Product Options block into position yourself. Each one has a check and a fix in My product options are not showing.

Because nothing in the widget can be dismissed — there is no close button to press, so the number has nothing to count. Treat it as a placeholder rather than a signal. What Widget Views, Interactions and Conversion Rate each really measure is set out in Read your Everfield analytics.

Yes. Everfield detects the checkout button for known themes; if yours is not matched or sits somewhere unusual, turn off Detect cart position automatically on the Placement tab and enter your own CSS selector. Resync from the Cart selectors page after switching or updating a theme. See Add options to your Shopify cart page.

Open the app and use Contact support at the top right, or email hello@usenormalize.com. It speeds things up enormously if you include which theme is published, the name and status of the experience, and the product URL you tested.