SleekView for WCFM Delivery: delivery jobs as tables
WCFM Delivery puts vendor orders into a delivery queue with assigned drivers, stops, and status transitions. SleekView reads the delivery tables directly so dispatchers can scope, sort, and reassign without per-order clicks.
♾️ Lifetime License available
Dispatch screens are queues, not list views
WCFM Delivery hooks into WCFM Marketplace orders and adds a delivery layer: each delivery job has an assigned driver, a status, a vendor (origin), and a customer (destination). Records sit alongside the order in wcfm_delivery_* tables, but the default admin presents them as a queue per status rather than a sortable, filterable list.
SleekView reads the delivery tables and joins them with wc_orders and the vendor user, so a delivery row shows order number, vendor, driver, distance, scheduled window, and current status side by side. Dispatchers can sort by scheduled time, filter by driver, scope to a delivery zone, or surface jobs that have been pending for longer than a configured threshold.
Status changes and driver reassignments write through WCFM Delivery's API where exposed, so the driver app notification still fires and the customer's tracking update still goes out. Bulk reassignment for shift changes or vehicle outages runs in seconds instead of one job at a time.
Workflow
From queue screens to a dispatch board
Read delivery tables
wcfm_delivery joined with wc_orders, wp_users for drivers, and vendor metadata for the origin.
Build dispatch columns
wp_usermeta.
Save shift views
Reassign and edit inline
Sample columns
A typical delivery dispatch view
wp_wcfm_delivery + wp_wc_orders + wp_users (role=wcfm_delivery_boy) + wp_usermeta
| Order | Vendor | Driver | Window | Distance | Status |
|---|---|---|---|---|---|
| #10428 | Atlas Studio | Alex P. | 10:00, 12:00 | 4.2 km | Delivered |
| #10429 | Riverside Workshop | Ria K. | 12:00, 14:00 | 8.1 km | En route |
| #10430 | Maker Den | Unassigned | 14:00, 16:00 | 3.0 km | Pending |
| #10421 | Old Lane Goods | Tom B. | 08:00, 10:00 | 12.4 km | Failed |
Comparison
Default WCFM Delivery admin vs SleekView
Default WCFM Delivery admin
- Status queues replace a real list view, so cross-status sorting isn't possible
- No view that combines vendor, driver, and scheduled time on one row
- Bulk reassignment of jobs to a different driver goes one at a time
- Driver workload (jobs per shift) isn't a sortable column
-
Delivery zones from
wp_usermetaaren't filters
SleekView
-
Read
wcfm_deliveryjoined withwc_ordersand driver users - Reassign jobs in bulk when a driver goes off-shift
- Filter by zone, driver, status, scheduled window in any combination
- Surface driver workload (active jobs, today's deliveries) inline
- Save dispatch views per shift, zone, or vendor cluster
Features
What SleekView gives you for WCFM Delivery
Dispatch board
Today's deliveries scoped by zone with driver, scheduled window, and distance inline. Sort by scheduled time and the morning shift plan writes itself.
Bulk reassignment
Driver goes off-shift, select their pending jobs, reassign to the cover driver in one action. WCFM Delivery's driver notification still fires.
Overdue queue
Jobs pending or en-route past their scheduled window surface in a saved view. Dispatchers escalate before the customer calls.
Audience
Who uses SleekView for WCFM Delivery
Dispatchers
Shift-shaped views of pending and en-route jobs with driver and zone context, so the daily dispatch ritual runs from one screen.
Driver coordinators
Per-driver workload and on-time-rate views with the columns to spot under-utilised or overloaded drivers before it becomes a delivery problem.
Customer support
When a customer asks where their delivery is, support pulls the per-order delivery view in one click and sees driver, location, and current status.
The bigger picture
Why dispatchers need lists, not queues
A delivery operation runs on lists. The morning shift lead needs today's deliveries sorted by scheduled window, with driver and zone visible. The driver coordinator needs each driver's workload across the week to decide who is over or under booked.
Customer support needs to look up a single delivery by order number and see status, driver, and reason for delay if any. None of those are queue screens, they are sortable filterable lists. WCFM Delivery is built well from a data perspective: jobs are records, drivers are users, status transitions are logged, and zones are structured meta.
The admin UX presents the data as queues because that is the metaphor the plugin's screens were designed around, which works for the simplest workflow (a driver looking at their next stop) but not for the operational workflows above. SleekView converts the same data into the list views each role actually uses. Dispatchers, coordinators, and support each save their own view once and run their daily work from it.
The data does not change, the plugin still owns the writes, and the metaphor finally matches the workflow.
Questions
Common questions about SleekView for WCFM Delivery
Yes, jobs live in WCFM Delivery's own tables (wcfm_delivery) linked to wc_orders and the driver user. SleekView reads these directly without going through the plugin's admin UI.
Yes. Driver reassignment writes through WCFM Delivery's API so the driver app notification fires and the customer's tracking page updates. Bulk reassignment processes selected jobs in sequence with the same hooks.
Delivery zones are stored as usermeta on the driver user (and as postmeta on vendors). SleekView surfaces zone as a column and as a filter so dispatch can scope a view to one zone for a given shift.
Where shift schedules are stored as usermeta, SleekView reads them and exposes them as a column. Where they're stored externally, the view lets dispatchers tag jobs to a shift through a saved column override.
Yes. Scheduled window and actual delivery timestamp are both on the delivery record. A driver-scoped view computes on-time rate over a rolling window, useful for performance reviews.
Failed deliveries have a status and a failure reason field. A saved view filters for failed in the last 7 days with reason and vendor inline, so support can act before the refund window.
Where a job aggregates items from multiple vendors, the delivery record references the primary vendor and the related vendors via a join table. SleekView surfaces both in the row so dispatch sees the full picture.
Driver data sits in wp_users and wp_usermeta like any user, and WordPress's data export tools cover it. SleekView respects WordPress capabilities, so role-scoped views only show drivers and jobs the operator is allowed to see.
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
- Checkout Field Editor
- Veeqo Wp
- Woocommerce Multi Currency Switcher
- Woocommerce Vendor Payouts
- Wp Simple Pay
- Surecart Subscriptions
- Woocommerce Aftership
- Woocommerce Deutsche Post
- Woocommerce Paytm Gateway
- Woocommerce Shipworks
- Wc Marketplace
- Woocommerce Shipping Easypost
- Woocommerce Pricing Deals
- Woocommerce Eu Vat Assistant
- Gumroad Wp