✨ 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 for WPC Frequently Bought Together

SleekView reads the _wpc_fbt_products meta joined to the WooCommerce order items table and renders FBT orders as a sortable, filterable table with parent product, cross-sell pair and order total as real columns.

♾️ Lifetime License available

SleekView table view for WPC Frequently Bought Together for WooCommerce

Cross-sell config per product, no FBT order list

WPC Frequently Bought Together adds a Bought Together selector to product pages and lets shop managers define which products travel together. Each parent product carries a _wpc_fbt_products meta key listing its configured cross-sells. When customers add the suggested set, the order arrives with multiple product lines tied to the same parent.

The default admin shows the cross-sell list per product on the edit screen. There is no order list filtered to FBT orders, no column for the parent product that triggered the cross-sell, no sortable order total scoped to the FBT channel. SleekView reads the WooCommerce orders table joined to order items and tags any order whose items match a configured FBT set with a derived has_fbt flag.

From there, parent product, pair label, order total and order date all sit as columns. Filter to FBT orders only, sort by order total, or pull every FBT order tied to a specific parent without opening one.

Workflow

How SleekView reads WPC FBT data

1

Pick products and order items

Choose the product post type and the WooCommerce order items table. SleekView joins them with the _wpc_fbt_products meta key to flag FBT orders.
2

Compose the column set

Add parent product, pair label, order total, customer and order date. Hide what you do not need so the table matches a real merchandising workflow.
3

Save and scope the view

Name it ("FBT orders this week", "FBT for Linen Throw") and gate it by WordPress capability so merchandising, marketing and finance each see the right slice.
4

Edit inline or export

Bulk-flip order status, update fulfilment meta or export the filtered set to CSV. Edits route through WooCommerce CRUD so order hooks fire.

Sample columns

A typical WPC FBT orders table

SleekView joins the FBT meta with the WooCommerce order items table so parent product, pair label and order total sit as real columns alongside customer and date.
Source: wp_postmeta (_wpc_fbt_products) + wp_woocommerce_order_items + wp_wc_orders
Order Parent product Pair Total Customer Date
#5132 Linen Throw Throw + Mug $84.00 alex@studio.co May 14
#5131 Cedar Diffuser Diffuser + Refill $58.00 ria@design.io May 14
#5130 Linen Throw Throw + Pillow $148.00 tom@hello.dev May 13
#5129 Ceramic Mug Mug + Coaster $32.00 mia@brew.coop May 13
#5128 Linen Throw Throw + Mug $84.00 lia@hello.dev May 12

Comparison

Default WPC FBT admin vs SleekView

Default WooCommerce products screen with FBT settings

  • FBT setup lives per product, no cross-product order list
  • There is no has_fbt flag on the default WooCommerce orders screen
  • Parent product and pair label are not columns anywhere in admin
  • Bulk fulfilment on FBT orders means opening each order
  • No saved per-role view for merchandising or marketing

SleekView

  • Read directly from order items joined with the _wpc_fbt_products meta
  • Derived has_fbt flag, parent product and pair label as sortable columns
  • Inline-edit order status and fulfilment meta across many FBT orders
  • Save filtered views per role ("FBT orders this week", "FBT for hero SKU")
  • Switch between table and kanban views of the same FBT queue

Features

What SleekView gives you for WPC Frequently Bought Together for WooCommerce

FBT orders become a real list

A derived has_fbt flag tags every order that matches a configured FBT set. The cross-sell channel becomes filterable in one click.

Inline edits through CRUD

Bulk-flip status or update fulfilment meta from the row. Edits go through WooCommerce CRUD so order emails and stock hooks still fire.

Filter to the parent SKU

Combine parent product, pair label and date into a saved filter. FBT performance for a hero SKU becomes a single named view.

Audience

Who uses SleekView for WPC FBT

Merchandising teams

Filter to FBT orders for a hero SKU to see which pairs actually sell. The pair-label column ranks combinations customers really pick.

Marketing

Filter to FBT orders this week and sort by total to spot the strongest pairs for the next campaign.

Fulfilment ops

FBT orders carry multiple lines. The table makes it easy to filter and bulk-flip status across a batch in one pass.

The bigger picture

Why FBT orders need a row, not just a per-product setting

WPC Frequently Bought Together gives merchandising a clean way to configure cross-sells per product. The reporting side stayed inside the standard order export. SleekView reads the FBT meta and the linked order items and turns them into a flagged, filterable row in the orders table.

Merchandising stops scrolling for the pair that actually sold. Marketing stops guessing which campaigns moved the channel. Fulfilment stops opening every multi-line order.

The plugin still owns the selector and the checkout behaviour; the table turns the resulting orders into a measured channel a team can act on.

Questions

Common questions about SleekView for WPC Frequently Bought Together for WooCommerce

It joins the order items to the _wpc_fbt_products meta on the parent product. Orders whose items match a configured FBT set carry a derived has_fbt flag.

 

Yes. A pair_label column built from the two product slugs is exposed as a sortable column, so a view of top pairs is one saved filter and sort.

 

Yes. SleekView reads wp_wc_orders and wp_wc_order_product_lookup when High-Performance Order Storage is enabled.

 

Yes. Select rows, change status and SleekView writes through WooCommerce CRUD. Order emails and stock hooks still fire.

 

No. The table renders in WP Admin only and reads from existing tables. The front-end FBT widget is untouched.

 

Yes. Filter by parent product, then export the filtered set as CSV with the same columns the view shows.

 

Yes. Each saved view is gated by WordPress capability. Merchandising, marketing and finance can each have their own.

 

No. WPC's FBT settings stay where they are. SleekView adds the cross-product order table the admin never built.

 

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