✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView Feedback for EDD Recommendations

SleekView Feedback reads customer requests, bad pairing reports, and algorithm ideas tied to EDD Recommendations straight from the database, then renders them as upvotable cards with status pills like New, Investigating, Planned, and Shipped so customers see which recommendation tweaks are being worked on next.

♾️ Lifetime License available

SleekView Feedback board for EDD Recommendations

Why a recommendation engine needs a public board

EDD Recommendations watches every order in wp_edd_orders and writes the resulting bought-together signals into wp_postmeta under the _edd_recommendations key. That signal answers the question of what to show, but it has no idea whether customers actually liked the suggestions, found them helpful, or rolled their eyes at the same three pairings on every product page.

SleekView Feedback points at the same product posts plus any recommendation feedback post type you already collect through a thumbs up widget or a survey, and renders each row as a card. The card shows the title of the report, an upvote count, the customer first name from EDD, a category pill like Bad pairing, Missing pairing, Cold start, or Bundle idea, and a status pill that tracks where your team is with each tweak.

When another customer clicks Upvote on a report that matches their own experience, the count writes back to the same row, so your tuning roadmap reflects real customer demand instead of whoever wrote the loudest review. Operators see at a glance which pairings break the experience, which categories never get cross-sold, and which bundle ideas customers actually want.

Workflow

From recommendation signals to a live board

1

Connect SleekView to your recommendation data

Install SleekView and pick EDD Recommendations as the data source. The plugin reads product posts, recommendation meta, and any feedback post type you already collect through your widgets. Confirm the sample rows look right in the preview and the wiring is done.
2

Pick votes, category, and status fields

Choose a numeric meta key like request_upvotes for the vote total, then map a recommendation topic taxonomy as the category and your triage meta as the status. SleekView turns each distinct status value into a coloured pill across every card on the board.
3

Brand the cards to match the product page

Pick which fields show on each card. Title, vote count, customer first name, category pill, and status pill are on by default. Add product name, current pairing, or last review if you want richer cards. Tailwind classes flow through so the board mirrors your storefront.
4

Embed the board on a tuning page

Drop the SleekView block into a Recommendations Roadmap page linked from product page footers. Customers see upvote buttons, search, status filters, and category chips. Every click writes back to your meta, so the board and the recommendation widget stay aligned.

Sample board

Sample EDD Recommendations customer board

A live preview of how customer requests, bad pairing reports, and bundle ideas look once SleekView Feedback reads them out of EDD Recommendations and renders them as cards.
229 votes
Stop suggesting the same theme alongside its own child theme
Helen O. Bad pairing Shipped
183 votes
Recommend related fonts on the icon pack product page
@designhound Missing pairing Planned
144 votes
Cold start for new categories should fall back to top sellers
Soren V. Cold start Investigating
97 votes
Offer a graphic bundle when both icon and font are in the cart
Tara M. Bundle idea New
48 votes
Add price filter to the recommendations widget on the cart
Jonas K. Feature request Planned
8 votes
Recommendations carousel scrolls past the last item on mobile
@mobileqa Bug Closed

Comparison

Recommendation logs vs SleekView Feedback

Private recommendation logs

  • Bad pairing reports sit in support threads that nobody else can see or vote on
  • No upvotes, so a popular bundle idea looks the same as a single one-off complaint
  • Status changes happen in admin notes, customers never see when a tweak actually ships
  • Topic tagging is limited to product, not pairings, cold start, or bundle ideas
  • Operators export EDD reports just to spot which bad pairing keeps repeating

SleekView Feedback

  • Reads EDD Recommendations product meta directly from wp_postmeta without a sync job
  • Upvotes write back to a request meta key so the source of truth stays inside EDD
  • Status pills cover New, Investigating, Planned, Shipped, and Closed out of the box
  • Category chips map to pairings, cold start, bundle ideas, and UI without extra schema
  • Top-voted reports float to the top so the merchandising team always sees the loudest signal

Features

What SleekView Feedback gives you for EDD Recommendations

Upvotes that update EDD rows

Each Upvote click increments a meta key on the underlying request row, so SleekView, the EDD product screen, and any merchandising exports stay aligned without nightly syncs. Rate limiting and IP throttling keep the count clean when a popular pairing report hits social.

Filter by recommendation topic

Category chips pull straight from your recommendation taxonomy, so customers can drill into bad pairings, cold start, or bundle ideas in one click. Merchandisers use the same chips, sorting by votes or recency depending on the tuning sprint they are running.

Statuses customers trust

New, Investigating, Planned, Shipped, and Closed render as colored pills on every card. The same status meta drives a kanban view if you enable SleekView Kanban, so one column powers both the public roadmap and your private tuning queue.

Audience

Where a recommendations feedback board pays off

Merchandising teams

Pool customer reports on bad pairings and missing bundles so merchandisers see a clear ranking of what to tune next. Cards beat scrolling EDD product screens when the next tuning sprint needs concrete numbers and customer quotes.

Customer support teams

Use the board to give customers visibility on every confusing suggestion. Status pills cut down repeat tickets because customers can see their report is already Investigating without emailing support a second time.

Conversion optimisation owners

Group reports by product page or cart step so growth teams can spot which pairing leaks revenue. The board doubles as evidence when you pitch new bundles or a price filter to leadership.

The bigger picture

Why a tuning board beats silent recommendation widgets

EDD Recommendations is great at picking pairings from order data, but the widgets themselves cannot tell you whether customers loved the suggestions or quietly closed the tab. That feedback usually lives in scattered support threads, occasional product reviews, and a few admin notes that never reach the merchandising team in time. The result is a widget that improves slowly because the team behind it is missing half the picture.

SleekView Feedback gives the same product data a public surface that reads like a tuning roadmap. Cards with vote counts, status pills, and topic chips let customers report bad pairings or missing bundles in one click, and the data stays inside your EDD install. Merchandisers see real demand instead of guessing, and customers see real responses instead of generic widgets.

Over a few months the board becomes a transcript of how your store learns from its own catalogue, and that transcript converts hesitant visitors into repeat buyers far better than a static recommendation strip ever could.

Questions

Common questions about SleekView Feedback for EDD Recommendations

Yes. SleekView reads product posts, recommendation meta, and any feedback post type straight from the standard EDD tables, so the integration works with the current EDD Recommendations release. No proprietary endpoint is required and no customer data ever leaves your site.

 

The count writes back to a meta key on the underlying request row in wp_postmeta. SleekView debounces clicks per session and per IP so a single visitor cannot inflate the total. If you already use a different upvote meta from another plugin, point SleekView at that column.

 

The default board is read and upvote only to keep moderation light. If you want customer submissions, pair the board with a Gravity Forms entry, a Fluent Forms entry, or any custom post type. SleekView picks up new rows as soon as they hit the database.

 

Status comes from any column you point at, so a workflow meta key like merch_status drives the pills. Your team updates the status inside the EDD admin or a custom admin column, and SleekView reflects the change on the public board within the next cache window.

 

No. SleekView pages results server side and caches the rendered card list per filter, so a board with tens of thousands of products loads as quickly as one with a hundred. Upvotes use a lightweight admin-ajax endpoint that does not bootstrap a full template render.

 

Yes. SleekView respects post status, so draft and private reports stay hidden. You can also add a private meta flag and exclude it in the data source filter, which is helpful when reports name partner brands or expose unreleased bundles.

 

Canny and FeatureBase are good hosted boards, but they sit outside WordPress and need product data copied across systems, per-seat pricing, and SSO. SleekView Feedback uses the data already inside EDD, ships as a one-time license, and renders inside your existing theme with your own brand.

 

Yes. SleekView reads the post language meta WPML and Polylang already write, so a board on the English page only shows English pairing reports. You can also expose a language category chip if you want one shared board where customers filter across languages.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

EUR

once

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView