WooCommerce Tip Jar plugins (and similar tipping/gratuity extensions) attach a customer-chosen tip to the order at checkout, typically as a fee row in wc_order_items with order_item_type = fee. The selected preset (10%, 15%, custom amount) is usually stored alongside in wc_orders_meta. The default Orders list shows the total but never separates the tip from the rest of the order, so a tip-aware merchant can't easily ask "what did we collect in tips this week".

SleekView reads wc_order_items filtered to the tip fee row, joins it to the order and customer tables, and surfaces the tip amount, tip preset, and tip percentage as real columns. Aggregate tip revenue by date, filter to orders with a tip over a threshold, or pivot by preset to see which tip option converts best. The data is already in the WooCommerce schema, it just needs the right view.

Inline edits route through WooCommerce CRUD for status changes, and through standard meta-update hooks for any tip-meta corrections. Saved views per role keep service teams (which staff member earned tips), finance (period totals for distribution), and management (uptake and average tip rate) looking at the same data through their own lens.

Tip Jar plugins exist because more WooCommerce stores now operate the way restaurants, salons, and service providers do, where a meaningful portion of order value comes from gratuity. The plugins handle the checkout interaction well, presenting tip presets and writing the chosen amount to the standard fee mechanism. What they don't handle is the operational reporting that comes after, because the default WooCommerce Orders screen rolls the tip into the order total without ever showing what portion of it came from gratuity.

A salon owner doing weekly tip distribution can't see per-period tip totals without exporting. A finance lead reconciling at month end can't separate tip revenue from product revenue for tax purposes without custom SQL. A manager testing whether the default tip preset converts better at 15% or 18% can't see uptake by preset without an analytics tool.

SleekView reads wc_order_items fee rows, joins them to the order meta, and surfaces tip amount, preset, and percentage as real columns. Same database, same hooks, dramatically less spreadsheet work for the people running the service.