Show known issues and FAQ-style reports on PrestaShop product pages to keep support context visible
Product Issue Reports is a module for PrestaShop stores that publishes the known problems of a product, with status, severity and workaround, on the product page and in a public tracker, and takes new reports from customers. It installs, adopts your theme's colours by itself, and the first issue is published minutes later.
It settles the most expensive repetition in support: the same known-problem question arriving by email ten times a week, answered privately every time, while buyers who never ask discover the limitation after paying and come back for a refund. The answer exists; it just is not where the question forms.
Publishing is simple, and the machinery underneath is complete. A Known Issues tab on the product page opens with totals, open and resolved counts and status badges; a public hub gathers the active issues of the whole catalogue with search, status and product filters, sorting and paging; and every issue owns a page you link to, carrying severity, affected and fixed versions, reproduction steps, a workaround, resolution notes and the expected fix date. Statuses run from pending through open, resolved and closed to won't fix, and the tab hides itself on products with nothing to show.
Customers and guests report problems themselves, from the tab or the hub, and nothing goes public unreviewed: submissions arrive as pending, throttled against repeat and bulk sending, and your team validates them in a filterable queue with bulk actions, ordered by the votes and report counts of real buyers. Issue content is written per language, the tab title is yours to name, and search engines index the tracker only where you allow it, with issue pages kept out by default. The full issue bodies stay out of the initial product render and load from your own shop only when the tab is opened.
Support stops retyping the same explanation and sends a link. Buyers who would have hit the fault blind buy knowing the workaround or wait for the fix date instead of demanding a refund, and the resolved list stays visible as standing proof that problems here get fixed.
Summary of what the module offers
Product Issue Reports answers the recurring product question once, in public, and turns buyer reports into an ordered queue. This page answers six questions:
- Where the answer lives: a Known Issues tab on the product page and a public tracker
- What an issue carries: status, severity, versions, workaround, fix information and a date
- How buyers report: a protected form from the tab or the hub, moderated before publication
- How the team works: a filterable queue ordered by votes, with bulk actions
- What search engines see: sitemap and indexation switches, off by default for issue pages
- What it costs the page: counts first, detail loaded only when the tab opens
Where does the customer find the answer?
On the product page itself: a Known Issues tab shows the totals, open and resolved counts and status badges, and expands into full detail on demand. Where a product has nothing to show, the tab hides itself.
Above the products sits one public hub for the whole catalogue: every active issue, searchable, filtered by status and product, sorted and paged. Each issue also owns a page of its own with a clean address, which is exactly the link your support team sends instead of retyping the explanation.
What does a published issue tell the buyer?
Everything the twentieth email used to ask: current status, severity from low to critical, the affected versions, reproduction steps, a workaround to use today, resolution notes, the version the fix arrived in and the expected date when it has not yet.
Statuses run from pending through open, resolved and closed to won't fix, and resolved issues remain visible. A tracker with a resolved history reads as honesty and competence, not as risk.
How do customers report a problem?
From the product tab or from the hub, signed in or as a guest: an email address, a title and optional reproduction details. The form is protected against abuse, with submission limits per sender and per address, so the queue receives reports, not noise.
Nothing appears publicly on arrival. Every report lands as pending with its first vote counted, and only a decision by your team publishes it. The storefront shows what you validated, never what someone typed.
How does my team stay on top of it?
In a filterable queue: product, title, status, severity, dates, votes. Bulk actions handle the routine, and the votes and report counts of real buyers order the work by impact rather than by whoever emailed last.
Issue content is written per language, so the German buyer reads a German workaround. The tab title is yours to name per language as well, and one switch turns customer reporting off entirely where you want a read-only tracker.
What about search engines and page speed?
Indexation is a decision, not an accident: sitemap inclusion is a switch, the hub is indexable when you allow it, and individual issue pages stay out of search engines unless you deliberately open them, and even then only when active and open or resolved.
The product page pays nothing: the tab renders grouped counts only, and full issue bodies load from your own shop the moment someone opens the tab, never sooner. No outside service is involved anywhere.
-
Referencemprissuesrevolution
-
In stock2147483647 Items
-
PrestaShop CompatibilityPS 1.7 – 9.x
-
Pricing ModelOne-time Purchase
-
Module TypeFront & Back-office
-
GDPR RelevantNo
-
Business GoalBuild Trust & Social Proof
-
External Account NeededNo
-
Module ComplexityFeature-Rich Module
-
Customer Journey StageRetain Customers
-
Works With PlatformNo External Platform
What customers say about us
Company reviews
5.0
★
★
★
★
★
(4 reviews)
Loading customer reviews...
No product reviews yet
Be the first to share your experience with this module.
Write a Review
Issues & FAQ Revolution lets you publish known issues, FAQ-style notices, compatibility notes, fixes, and workarounds for products in your PrestaShop store. Customers can check a public Known Issues hub or a product-page tab before opening a support ticket.
Have a question about this product?
Our experts are here to help. Ask anything about installation, compatibility, or specifications.
1301
questions
9
categories
2013
building modules since
1.6–9
PrestaShop versions
v2.5.192026-05-27
- AddedFinalize known issues hub SEO cleanup
- AddedEnrich known issue detail pages
- AddedAdd known issue detail pages
Loading full changelog...
Works Well With Product Issue Reports
Modules our team genuinely pairs with this one, and exactly why each belongs in the same setup.
Complement
Issue Tracker adds a public known-issues and product FAQ workflow, with a product-page issue tab showing open and total counts, status badges and resolved fixes, so shoppers see open problems and limitations before contacting support. That transparency is especially relevant for stores selling digital products with versions and updates.
Digital Revolution covers the digital product side as a separate tool, adding product setup, license control and a customer portal for protected downloads, versions, domains, demos, support access and subscriptions.
Used alongside each other, Digital Revolution structures how digital products and their versions are delivered while Issue Tracker communicates known issues and fixes around them. They are independent tools; together they suit software and module sellers, giving customers both a clear delivery and access experience and an honest, visible record of open and resolved problems for the products they buy.
Complement
Issue Tracker publishes a known-issues and product FAQ workflow, showing open and total issue counts, status badges and resolved fixes so shoppers understand current problems and limitations before they contact support. Communicating problems is one half of pre-sale clarity; explaining normal use and policies is the other.
FAQ Manager covers that as a separate tool, turning recurring questions about shipping, returns, compatibility and product use into structured, catalogue-connected content shoppers can read for themselves.
Used alongside each other, Issue Tracker handles transparency about open and resolved issues while FAQ Manager handles standard how-it-works guidance. They are independent tools; together they give product pages both honesty about limitations and clear answers to ordinary questions, so shoppers get a complete picture, fewer are surprised after purchase, and routine support contact drops.
Workflow
Issue Tracker gives shoppers a transparent, public view of known issues, with open and total counts, status badges and resolved fixes, so they understand problems before contacting support. Public transparency reduces some contacts, but customers still raise individual issues that need private, tracked handling.
Support Revolution covers that as a separate tool, a PrestaShop help desk with ticket history, customer identity and order context, plus optional guest tickets, for working cases properly.
Used alongside each other, Issue Tracker communicates widely shared problems openly while Support Revolution handles the individual, account-specific cases. They are independent tools; together they let shoppers check known issues before opening a ticket, which can cut duplicate contacts about the same problem and keep the help desk focused on the cases that genuinely need personal attention.
Complement
Issue Tracker keeps customers informed about current problems, with a product-page tab showing open and total issue counts, status badges and resolved fixes, so limitations are visible before purchase. Reporting present issues is backward- and present-looking; gathering what customers want next is a different, forward-looking need.
Feature Requests & Voting covers that as a separate tool, giving customers a visible board to suggest ideas and vote, with requests linked to products and a Back Office roadmap workflow.
Used alongside each other, Issue Tracker is transparent about what is currently open or fixed while Feature Requests & Voting collects and prioritises what should come next. They are independent tools; together they give customers an honest, two-sided picture of a product, its present state and its future direction, which builds trust and turns scattered feedback into a clearer roadmap.
30 days return right
Easy return - no questions asked
Plug & Play Modules
Install, set up and take profit
Dedicated Support First
Priority Help & Satisfaction Over Sales
You might also like
- New
