Skip to content

The same three questions on every jacket, answered in four places

FAQ Kit lets a Magento store write each FAQ once, assign it to products, categories, widgets or the whole store, and show it on every page it applies to – with one valid FAQPage per page, on Luma and Hyvä.

Extension

A clothing store gets the same three questions on every jacket. Does it run small? Can it go in the washing machine? How long do returns take? The answers end up in a product description here, a CMS block there, and a support inbox everywhere else – and when the returns policy changes, somebody has to find every copy. Adobe Commerce and Magento Open Source have no place where an answer is written once and shown wherever it applies.

What it is for

FAQ Kit is that place. Each question and answer is written once, in a FAQ Entries grid under Content, and assigned to what it concerns: the whole store, any number of categories, any number of products, or a reusable FAQ widget – optionally limited to one store view.

Product and category pages then show their FAQ block on their own, most specific first. A wool jacket inherits the washing FAQ assigned to the three wool jackets, the sizing FAQ assigned to the Jackets category and the returns FAQ assigned to the whole store. When the returns answer changes, it changes in one row.

What changes in the merchant's week is that a new FAQ is an assignment, not a round of copy and paste – and FAQs can be managed where the item is: the product edit form lists every FAQ that applies to the product and lets its own be added, quick-edited, switched off or removed without leaving the page.

How it can be used

A catalogue with families of products. A category's sizing note, a material's care instructions, a brand's warranty terms. The cascade runs product → category → store-wide, and a per-store-view setting decides whether the levels are merged or only the most specific level that has FAQs is shown. Merge suits stores where the general answers belong everywhere; narrow suits stores where a product-level answer should replace the general one.

A FAQ page you lay out yourself. FAQ widgets carry their own questions, accordion or list layout, collapsed state and pair limit, and are placed on any CMS page with the standard Insert Widget control. A shipping page can hold a shipping widget and a returns widget; a help page can hold five. The trade-off is stated below: there is no ready-made FAQ page with its own URL.

Structured data without hand-written JSON-LD. A page carries exactly one valid FAQPage, merged from every FAQ block on it, so a CMS page built from several widgets stays valid. It is switchable globally and per widget.

Luma and Hyvä Theme stores. The block is server-rendered, cached with the page and built on the native <details> element, so the same accordion works on both themes, without JavaScript and without a compatibility package.

Drafting help, when wanted. For merchants who would rather review drafts than write from a blank page, the free FAQ Kit AI Generator is an optional companion. FAQ Kit already shows its AI controls – Generate with AI on the grid, Generate FAQs with AI on the product, category and widget forms – greyed out, with a hint that names the companion, until it is installed. Installed with composer require webmaster-ramos/module-faq-kit-llm, it switches them on and drafts candidates from catalog content or pasted text, through the free LLM Provider gateway and your own provider key. Nothing is saved until you tick the candidates you keep. Remove the companion and FAQ Kit carries on exactly as before. Without it, FAQ Kit makes no external call and holds no key.

How it compares

Measured on 2026-09-15: thirty Marketplace listings opened in a browser, the price read off each edition.

The category is crowded and mostly inexpensive. Fifteen one-time listings run from USD 25.00 to 159.00 on Magento Open Source, with a median of 69.99 and a cluster at 99 – 120. Ten more are free. The best-known FAQ vendors sell by subscription: Aheadworks at 169.00 a year, Amasty at 229.00 the first year and 139.00 after, MageDelight at 199.00, Moogento at 250.00 – between 238 and 500 over two years.

What the category mostly sells is a FAQ page – its own URL, its own topics – plus, in the upper tier, questions submitted by shoppers. FAQ Kit is built the other way round, around the catalogue, and the measurement found these elsewhere rarely or not at all:

  • The cascade. No listing describes FAQs inherited product → category → store-wide, or a per-store-view choice between merging the levels and showing only the most specific one.
  • A FAQ block on the category page itself. Only Moogento does it, as one tab of a category-page suite at 250.00 a year.
  • Managing FAQs where the item is. One listing adds FAQs from the product form; none claims the category or widget form.
  • FAQPage on product and category pages at a one-time price. Amasty emits structured data on a subscription; the others that do so emit it on their own FAQ pages or in a widget only.
  • One package for Luma and Hyvä, without a separate add-on or a GraphQL module.

Where a competitor is the better buy, it is worth naming. If what you need is a FAQ page, Rootways FAQ at USD 59.00 shares FAQs across products and categories and has a page of its own, and FME's FAQs at 69.99 ships a Hyvä package; several free listings do the page alone. If shoppers should ask the questions, Amasty, Aheadworks, MageDelight, Scommerce, FME and ETECHFLOW all take customer questions, and FAQ Kit does not. If social proof matters, VDC Category FAQ at 99.00 is the one listing with a real rating – 4.86 from seven reviews.

What it does not try to be

It has no dedicated FAQ page with its own URL and topics, no storefront search over FAQs, no helpfulness voting, no customer questions, no customer-group visibility, no import and no GraphQL. It is not a help desk. A FAQ in two languages is two entries, one per store view. And it does not write FAQs for you – that is the companion's job, and the companion is optional. The rest is in the FAQ on the extension's page.