Two necessary e-commerce plugins for Payload CMS v3, born from production needs
A developer running 23 European e-commerce sites built and open-sourced the customer review and JSON-LD plugins that were missing from the Payload v3 ecosystem. Here's our assessment. The Answer Up…
A developer running 23 European e-commerce sites built and open-sourced the customer review and JSON-LD plugins that were missing from the Payload v3 ecosystem. Here's our assessment.
The Answer Up Front
For teams building e-commerce sites on Payload CMS v3, these two plugins are an immediate "yes." They solve common, unaddressed needs for customer reviews and SEO-critical structured data. Skip this if you're not using Payload. The bottom line: these are not speculative tools but solutions forged and validated in a live, 23-site production environment, making them a trustworthy starting point.
Methodology
This is a v0 review based on the developer's technical write-up. We are assessing a suite of two open-source plugins for Payload CMS v3: one for customer reviews and another for JSON-LD schema generation. This analysis is based entirely on the founder's claims and code snippets published on June 16, 2026. The source signal is a blog post detailing the build process and rationale. We have not independently installed the npm packages, benchmarked performance, or validated the generated JSON-LD against Google's testing tools. This review covers the stated functionality and the developer's rationale. It does not cover long-term maintenance, ease of installation, or potential conflicts with other plugins. Our assessment will be updated if independent testing reveals discrepancies with the author's claims.
What It Does
Based on the developer's post, the plugins address two distinct gaps for e-commerce sites using Payload v3.
A complete customer reviews system
The first plugin introduces a reviews collection to Payload. This collection is linked via a relationship to existing products and includes essential fields like a 1-5 star rating and author details. Crucially, it includes a moderation workflow with a status field for 'pending', 'approved', or 'rejected' reviews, allowing site administrators to manage submissions before they go live. This is a foundational feature for any e-commerce operation that was reportedly unavailable for Payload v3.
Solves specific Payload v3 implementation bugs
The developer highlights several non-obvious fixes required when building on Payload v3. For access control, the plugin correctly uses the req.user.roles array, a change from v2's req.user.role string that could trip up developers. To prevent users from approving their own reviews on submission, a beforeChange hook is used to forcibly reset the review status to 'pending' and a verified flag to false, ensuring all new reviews enter the moderation queue.
Generates critical JSON-LD for rich snippets
The second plugin focuses on Search Engine Optimization (SEO) by generating Schema.org compliant JSON-LD. The developer states it creates structured data for Product, BreadcrumbList, ItemList, and AggregateRating. This data is what powers Google's rich snippets, such as star ratings and pricing information appearing directly in search results, which is a significant driver of click-through rates for online stores.
What's Interesting / What's Not
The origin story is the most compelling feature. These plugins were built by a developer maintaining 23 live e-commerce sites. This context suggests they are practical, production-tested, and solve real-world problems rather than theoretical ones. The author’s transparency about specific v3 implementation bugs, like the roles array access control change, demonstrates a deep, hands-on understanding of the framework. This isn't just a plugin; it's an encoded solution to a series of painful discoveries.
What's not novel are the features themselves. A reviews module and a schema generator are table stakes for any e-commerce platform. The value here is not in the novelty of the idea, but in the targeted execution for a specific, modern stack (Payload v3) where these tools were conspicuously absent from the official ecosystem.
Pricing
Free and open-source. The plugins are published on npm. (Pricing snapshot: June 16, 2026).
Verdict
If you use Payload CMS v3 for e-commerce, these plugins are a non-decision. They fill a clear gap in the ecosystem with a solution that has been pressure-tested across dozens of live sites. The developer's detailed post on the "gotchas" they encountered and solved provides more confidence than a typical marketing page. While a v0 review can't verify every claim, the "scratch your own itch" development model makes this one of the more reliable bets you can make on an open-source tool.
What We'd Test Next
A v2 review would require hands-on testing. First, we would install the plugins from npm into a fresh Payload v3 project to evaluate the documentation and setup process. Second, we would use Google's Rich Results Test to validate the output of the JSON-LD plugin for accuracy and completeness across different schema types (Product, BreadcrumbList). Finally, we would test the review moderation workflow from the admin panel and attempt to submit malicious or malformed data to check the security hooks.
The investor read
This project is a signal of ecosystem health, not a standalone venture. The emergence of high-quality, community-built plugins for platforms like Payload CMS indicates that the core product is sticky and has reached a critical mass of developers willing to build on top of it. This is a bullish indicator for Payload's adoption curve. While these specific plugins are unlikely to be a venture-scale business, they represent the "picks and shovels" opportunity that surrounds any successful platform. An investor might see the author as a potential acqui-hire or a candidate to build a larger, commercial plugin suite or a specialized Payload development agency.
Pull quote: “These are not speculative tools but solutions forged and validated in a live, 23-site production environment, making them a trustworthy starting point.”
Every claim ties to a primary source. See our methodology.