<\/span><\/h2>\n\n\n\nAnswering a support email rarely takes long. Two minutes, maybe three. That sounds like nothing. At three hundred enquiries a month it still adds up to two full working days \u2014 for information that has been settled for years. That is an example calculation, not a law of nature. Plug in your own numbers and the order of magnitude usually holds.<\/p>\n\n\n\n
The more expensive part never shows up in the support statistics. Most people don’t write at all. They close the tab.<\/p>\n\n\n\n
That is the uncomfortable bit. An abandoned checkout looks identical in every report, whether the price was too high, the delivery too slow, or a simple question left unanswered. The third case is the most annoying one, because it would have been the cheapest to fix.<\/p>\n\n\n\n
Then there is the money already spent before that moment. Clicks bought, landing page optimised, product photos reshot, newsletter sent. The entire marketing effort aims at getting someone onto the product page. And there it falls apart over a measurement nobody wrote down. The most expensive metre in e-commerce is the last one.<\/strong><\/p>\n\n\n\nReturns belong in the same bill. A share of them isn’t caused by bad products but by wrong expectations. Someone who doesn’t know a fit runs small orders two sizes. Someone who doesn’t know a spare part only fits model years from 2019 onwards orders anyway \u2014 and sends it back. Every one of those returns costs shipping, inspection, restocking and, in the end, margin.<\/p>\n\n\n\n
<\/span>The detour via Google<\/span><\/h2>\n\n\n\nPeople who find no answer in a shop rarely give up. They keep looking. Just somewhere else.<\/p>\n\n\n\n
The question goes to Google, into a forum, onto a review portal, into a YouTube video \u2014 or, in the worst case, into a competitor’s shop that already answered it. From the moment someone leaves the product page to do research, coming back is a matter of luck.<\/p>\n\n\n\n
The same principle works the other way round. Questions are search queries. “Can you clean X in the dishwasher” gets typed thousands of times. A shop that answers that question properly on its own pages, and marks the answer up in a machine-readable way, shows up in search \u2014 sometimes as an expandable result right under the listing. Nice side effect: the shop becomes the source instead of the last stop of a research trip.<\/p>\n\n\n\n
<\/span>Why a classic FAQ page rarely does the job<\/span><\/h2>\n\n\n\nMost shops already have an FAQ. It lives under “Service” or “Help”, is reachable through the footer, and covers shipping costs, return periods and payment methods. Useful for operations. Not much use for selling.<\/p>\n\n\n\n
The reason is mundane: nobody leaves a product page to hunt through the footer for an answer. Purchase doubt is impatient. It lasts maybe ten seconds, then the back button wins.<\/p>\n\n\n\n
The second problem is maintenance. An FAQ page that has grown over years turns into a long block of HTML nobody dares to touch. Product-specific questions don’t fit in there anyway. With twenty articles this could still be handled by hand. With two thousand it can’t. And every new article means another manual update \u2014 one more thing to remember, one more thing to forget.<\/p>\n\n\n\n
This is exactly where an FAQ extension parts ways with an FAQ page.<\/p>\n\n\n\n
<\/span>What an FAQ extension does differently<\/span><\/h2>\n\n\n\nThree things make the difference.<\/p>\n\n\n\n
The location.<\/strong> The answer sits where the doubt appears \u2014 on the product page, right next to the description and the reviews. No navigation, no searching, no switching tabs.<\/p>\n\n\n\nThe assignment.<\/strong> Questions aren’t attached to articles one by one, they are distributed by rule. A rule like “all articles from manufacturer X” or “everything with the property battery” automatically covers the article created tomorrow as well. Maintain once, keep the effect.<\/p>\n\n\n\nThe format.<\/strong> A question stops being a paragraph of text and becomes a data record. Records can be sorted, translated, output in several places and marked up for search engines. A paragraph of text can do none of that.<\/p>\n\n\n\n<\/span>PremsFaq: what the plugin actually does<\/span><\/h2>\n\n\n\nPremsFaq is an FAQ extension for Shopware 6.7. It is built along the problems described above rather than along a feature list. The structure is quick to explain.<\/p>\n\n\n\n
Groups and entries.<\/strong> Questions are organised into FAQ groups \u2014 something like “Care & cleaning”, “Compatibility” or “Delivery & assembly”. Each group has a name, an optional description and any number of entries. Groups and entries can be activated individually and ordered by priority. The most important question goes on top, not the one created first.<\/p>\n\n\n\nAssignment through dynamic product groups.<\/strong> This is the core. An FAQ group isn’t pinned to individual articles, it is linked to a dynamic product group from Shopware’s standard feature set. Define “manufacturer = X and category = outdoor” once and the matching questions appear on every current and future article in that selection. No rework when the range changes. No forgotten article.<\/p>\n\n\n\nFour content types instead of plain text.<\/strong> An answer isn’t always a sentence.<\/p>\n\n\n\nThe text<\/em> type covers the normal case, including formatting and links. The image<\/em> type adds a visual \u2014 position selectable (above, below, left or right of the text), size adjustable, optionally linked. Very handy for dimensions, size charts or plug shapes. The video<\/em> type embeds YouTube, Vimeo or a self-hosted video file, with an extended privacy mode that uses the providers’ cookie-free variants; the player controls can be shown or hidden. The document<\/em> type attaches a data sheet, an assembly guide or a care instruction directly to the answer, with its own title and description.<\/p>\n\n\n\nThe return reason “not what I pictured” doesn’t disappear because of text. A 40-second assembly video has a decent chance.<\/p>\n\n\n\n
Placement on the product page.<\/strong> Whether the FAQ appears as its own tab before the reviews, after the reviews, or directly below the product description is a plugin setting \u2014 no theme surgery required. Output is an accordion, so even fifteen questions don’t stretch the page.<\/p>\n\n\n\nShopping Experiences.<\/strong> Beyond the product page there are two CMS building blocks. One renders complete FAQ groups, the other renders individually picked questions. That makes it easy to enrich a category page with the three most common objections, or to build a landing page that backs up a campaign with substance. The answer itself is still maintained in exactly one place.<\/p>\n\n\n\nSEO without extra work.<\/strong> As soon as FAQ content appears on a product page, the plugin adds the matching schema.org structured data (FAQPage) to the page head automatically. Search engines read question and answer in plain text. Nobody has to hand-write JSON-LD or paste it into the theme.<\/p>\n\n\n\nMultiple languages with fallback.<\/strong> Questions, answers, document titles and document descriptions are translatable. Mandatory fields are only enforced in the system language. If a translation is missing, Shopware’s standard fallback kicks in instead of showing a gap. Translation can happen gradually \u2014 it isn’t a precondition for going live.<\/p>\n\n\n\nSales channels and permissions.<\/strong> The plugin can be activated per sales channel, which helps when B2B and B2C channels communicate differently. For the administration it ships its own permission roles (read, edit, create, delete). Support staff can maintain answers without getting access to prices or orders.<\/p>\n\n\n\nHeadless and extensible.<\/strong> All logic sits in a dedicated Store API route. A PWA or custom frontend requests a product’s FAQ data the same way the storefront does. The Twig templates are split into blocks throughout, so a theme or another plugin can hook in anywhere without overwriting files.<\/p>\n\n\n\nFor images and documents the plugin creates its own media folders during installation. The media library stays tidy.<\/p>\n\n\n\n
The return reason \u201cnot what I pictured\u201d doesn’t disappear because of text. A 40-second assembly video has a decent chance.<\/strong><\/p>\n\n\n\nPremsFaq comes in two tiers. The basic version covers text answers in a modest volume and works well for testing the principle in a live shop. The advanced version lifts the volume limits and unlocks image, video and document answers.<\/p>\n\n\n\n