SleekView for WooCommerce Pre-Order Pro: pre-orders & release queues as tables
Read pre-order data from shop_order posts (or HPOS wc_orders) with their _pre_order_status and release-date postmeta, joined to product release dates. Manage release waves, charge queues, and customer notifications without opening each order.
♾️ Lifetime License available
Pre-order operations, finally a single queue
Pre-order plugins layer on top of WooCommerce orders by setting an order or item-level pre-order status (commonly _pre_order_status in wp_postmeta or wc_orders_meta) and storing the expected release date as _pre_order_release_date on the product. The default admin view treats these as regular orders, so a release-day operation involves filtering Orders by date and status, opening each one, and triggering charges manually. That works for one launch a quarter; it does not work for a brand running monthly drops or a multi-product subscription store.
SleekView reads the order tables directly and exposes pre-order meta as first-class columns. A release-day view filters to active pre-order status, sorts by release date, and shows product name, customer email, total, and pre-order release status in one table. Inline-flip a batch from pending to charging, trigger the plugin's charge hooks, and watch status update as the queue clears. Custom meta keys, like internal launch wave tags or assigned-fulfilment owner, become filterable columns instead of buried database rows.
SleekView writes through WooCommerce's CRUD layer where the plugin exposes it, so charge attempts, customer notification emails, and inventory adjustments fire exactly as if a human had clicked through each order. Same hooks, same side effects, dramatically less manual work on launch day.
Workflow
How SleekView reads your pre-order data
Pick the order source
wc_orders on HPOS or shop_order posts on legacy. SleekView detects which path is active and exposes the matching pre-order meta keys.
Compose release-queue columns
product), customer email, _pre_order_status, _pre_order_release_date, total, and any custom launch-wave or deposit meta you write.
Save per-launch views
Charge, cancel, fulfil inline
Sample columns
A typical pre-order release queue view
shop_order posts (or wc_orders on HPOS) with their _pre_order_status and product release-date meta.
wp_wc_orders (or wp_posts post_type=shop_order) + wp_postmeta (_pre_order_status, _pre_order_release_date)
| Order # | Product | Customer | Pre-order status | Release date | Total |
|---|---|---|---|---|---|
| #10412 | Vinyl LP, Limited Run | alex@studio.co | Active | May 14 | £38.00 |
| #10411 | Hardcover Pre-Order | ria@design.io | Active | May 14 | £22.50 |
| #10410 | Vinyl LP, Limited Run | tom@hello.dev | Charged | May 14 | £38.00 |
| #10409 | Hardcover Pre-Order | mia@brew.coop | Cancelled | May 14 | £22.50 |
Comparison
Default WooCommerce Pre-Order Pro admin vs SleekView
Default Pre-Order Pro admin
- Pre-orders show up in the regular Orders list with no distinct release-queue view
-
_pre_order_statusand_pre_order_release_datelive inwp_postmetabut are not surfaced as columns - Release-day charging requires opening each order or using a bulk action with no preview
- No way to filter active pre-orders by release date and group by launch wave
- Custom internal-launch meta is not visible in the order list
SleekView
-
Release-queue view filtered to active pre-orders sorted by
_pre_order_release_date - Inline-edit pre-order status with charge hooks firing through CRUD
- Custom launch-wave meta exposed as a filterable column
- Save per-launch views ("May 14 vinyl drop", "Q3 hardcover wave")
-
Join to the
productpost type for product names and release dates inline
Features
What SleekView gives you for WooCommerce Pre-Order Pro
Release-date queue
Filter to active pre-orders, sort by _pre_order_release_date, and see exactly what is queued for the next drop. Group by release date to plan launch waves without spreadsheet exports.
Bulk charge triggers
Flip a batch of pre-orders from pending to charging in one inline action. Writes route through the plugin's CRUD layer so charge attempts, notifications, and inventory updates fire as if you had clicked through each order.
Custom launch-wave tags
Add a custom launch_wave meta key as a column and use it to filter and group orders by internal release plan. Useful for staggered drops or limited-edition runs.
Audience
Who uses SleekView for WooCommerce Pre-Order Pro
Fulfilment teams
Release-day queue with product, customer, shipping country, and pre-order status inline. Bulk-flip to charged as inventory clears the warehouse, no per-order click-through.
Finance
Forecast view: active pre-orders by release date with total revenue per wave. Reconciles against the bookkeeping calendar without exporting to a spreadsheet.
Marketing
Per-launch wave view filtered by launch_wave for retention follow-ups. Export the customer list to feed thank-you emails or upsell campaigns after the drop.
The bigger picture
Why release-wave operations need a real queue view
Pre-order operations have a different shape from regular ecommerce. Orders come in over weeks and have to be processed on a single planned date, usually with deposit-charging or full-charge logic, customer notifications, and limited inventory that has to be reconciled across the queue. WooCommerce's default order admin was built for a steady stream of independent orders, not for a wave that has to land simultaneously.
Without a dedicated queue view, release day becomes a spreadsheet-and-coffee marathon: filter orders by date, copy IDs into a tracker, open each order, trigger charge, watch for failures, update notes. SleekView turns the same data into a real queue: active pre-orders sorted by release date, grouped by launch wave, with charge status, deposit balance, and shipping country visible inline. Bulk-flip to charged as inventory clears the warehouse; cancel the failures inline with refund hooks firing through the plugin; export the wave for the post-release retention email.
Same database, same plugin logic, dramatically calmer launch days.
Questions
Common questions about SleekView for WooCommerce Pre-Order Pro
Both. On HPOS stores, SleekView reads wc_orders and wc_orders_meta where the pre-order plugin writes its status and release-date meta. On legacy, it reads shop_order posts and wp_postmeta. The same SleekView config works across both schemas without rewriting columns.
Yes. Inline status writes route through WooCommerce's CRUD layer (or the plugin's own wrapper where exposed), so any hooks the pre-order plugin attaches to status transitions, like wc_pre_orders_charge_completed style triggers, customer notifications, and inventory adjustments, fire as expected.
Yes. wc_order_items (HPOS) or order item rows (legacy) can be exposed as a related child table, useful when an order contains multiple pre-ordered products with different release dates. Most teams use the order-level view for triage and the item-level view for fulfilment.
If your pre-order plugin records a deposit amount and a remaining balance, both live in wp_postmeta (often _pre_order_deposit and _pre_order_balance) and become columns in the view. Build a separate "balance due" view to track outstanding amounts before the release date.
Yes. The join to the product post type brings in _pre_order_release_date at the product level. Filter the view by product release date when planning a wave even before any orders enter the active-pre-order state.
Yes. Cancelling a pre-order from SleekView routes through the standard order-status change hook, so refund logic, inventory release, and customer notifications fire as if you had cancelled through the WooCommerce admin. SleekView does not bypass plugin logic on bulk operations.
 
Yes. If the plugin records charge results in wp_postmeta (commonly _pre_order_charge_result or similar), that key surfaces as a column. Failed-charge rows can use a coloured status pill to draw the eye, then you can drill in for retry.
Yes. SleekView filters and sorts hit indexed columns on the underlying order tables (id, status, date_created_gmt, customer_id). Custom-meta filters use postmeta or orders-meta joins, which are slower than core indexes; keep heavy aggregates off triage views and on detail screens to keep query plans fast.
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.
Lifetime ♾️
Most popular
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
€749
Continue to checkoutBrowse more
- Woocommerce Conditional Shipping
- Wp Simple Pay
- Tradegecko Wp
- Woocommerce Order Export
- Yith Essential Kit
- Woocommerce Referrals
- Woocommerce Stripe Gateway
- Woocommerce Braintree
- Woocommerce Clearpay Afterpay
- Etsy Shop Importer
- Woocommerce Allegro Pl
- Woocommerce Facebook Feed
- Woocommerce Shipping Multiple Addresses
- Mailchimp For Woocommerce
- Woocommerce Min Max Quantities