“Five stars and a text box” is a fine review form for a t-shirt and a useless review form for a skincare cream. The reviewer for the cream wants to tell you about her skin type, how long she’s been using it, what changed. The reviewer for the t-shirt wants to tell you about the fit. One form can’t serve both.
The review form builder lets you design the form each kind of product actually needs, assign it to the products (by category, tag, or individually), and collect the reviews that help the next shopper decide.
The field types
Nine types, dragged into place in whatever order fits the form:
- Star Rating — the classic one-to-five.
- Short Text — for single-line questions or headlines.
- Long Text — the review body.
- Dropdown — space-saving single-select.
- Single Choice — radio buttons for one answer.
- Multiple Choice — checkboxes for multi-select.
- Scale (1-9) — a numeric slider-style field for gradient questions like “how spicy?”
- Yes/No — a two-option toggle.
- Photo Upload — customer-submitted images of the product (see Photo reviews for how they render).
Each field has its own label, required / optional flag, and placeholder text. Fields can be marked as demographic (see below) to feed the aggregate displays on product pages.
Demographic fields
Fields of the right type (Dropdown, Single Choice, Multiple Choice, Yes/No, Scale) can be flagged as demographic. That flag does two things:
- The answers appear in the aggregate “Reviewed by customers with [X]” blocks on product pages (see the Demographic aggregates feature).
- The field is surfaced as part of the reviewer’s profile summary, rather than their free-text response.
A skincare form might mark “Skin type” as demographic. An apparel form might mark “Body type” and “Usual size”. A food form might mark “Spice tolerance”. The aggregates let future shoppers filter to people like them.
One shop, many forms
You can build as many forms as your catalogue needs and assign each to the right products:
- All products (the default form, shown wherever no more-specific assignment applies).
- Specific categories — all products in Skincare use the skincare form.
- Specific tags — all products tagged “seasonal” use the seasonal form.
- Individual products — a specific SKU overrides its category’s form.
Resolution is most-specific-wins: a product’s own form beats its category’s form beats the default.
Are you considering Yotpo or Okendo?
Yotpo and Okendo are mature SaaS review platforms with strong form customisation as part of their enterprise product. They function this way: reviews live in their platform, forms live in their platform, monthly pricing tiers based on review volume or active customer count.
Trustie Pro’s form builder functions this way: it lives inside your WordPress admin, builds forms against your own database, no monthly volume fees, and the fields feed directly into Trustie’s moderation queue, aggregate displays, and schema output.
The fit: if you’re running an enterprise review program where form customisation is part of a broader SaaS stack (review-based advertising, loyalty programs, reviewer outreach), Yotpo or Okendo give you that. If you want per-category forms on your own site without a monthly tier, Trustie’s builder is designed for that.
Why shops build multiple forms
One form per shop forces a compromise — every question on every form, or no questions at all. Multiple forms let the apparel category collect fit data, the skincare category collect skin-type data, the coffee category collect roast data, and none of them collect questions that don’t apply. The reviews are shorter, more completable, and more useful to shoppers because each form asks only what matters for that kind of purchase.