WooCommerce Checkout Add-Ons (the SkyVerge/Stuart extension and similar paid-add-on plugins) lets merchants attach paid options to checkout: gift wrap, priority shipping, extended warranty, donation. Each add-on saves to the order in two places. The chosen value appears in wc_orders_meta under the add-on's configured key, and the price impact appears as a fee row in wc_order_items with order_item_type = fee.

The default Orders screen shows the total but never breaks down which add-on contributed to it, and it never tells the merchant how many orders this month included the warranty add-on or the priority-shipping option. SleekView reads wc_order_items filtered to fees, joins back to wc_orders_meta for the add-on choice, and surfaces both as real columns. Filter to "warranty add-on selected", aggregate revenue per add-on, or pivot to see uptake by month.

Inline edits route through WooCommerce CRUD where the value is a known meta key, and through standard order-status hooks for status changes. Saved views per role keep fulfillment (which add-ons need to be picked), finance (per-add-on revenue), and product (uptake rate) looking at the same data through their own lens.

Checkout add-ons are one of the cleanest revenue levers a WooCommerce store has. A small fee for gift wrap, priority shipping, or an extended warranty converts at meaningful rates because the buyer is already in checkout and the cost feels marginal compared to the cart total. The mechanics are simple: each add-on attaches as a fee row to the order and the choice saves to meta.

What's harder is the operational and product use of that data, because the default Orders screen rolls all fees into the total without breaking down which add-on contributed what. Fulfillment can't see which orders need gift wrapping without opening each one. Finance can't reconcile warranty fees against the warranty provider without a custom SQL.

Product can't see uptake trends without an analytics tool. SleekView reads wc_order_items fee rows, joins them to the choice meta, and surfaces both as real columns. Fulfillment sees the gift-wrap queue, finance sees per-add-on revenue, product sees uptake rate.

Same database, same hooks, dramatically less reporting friction.