✨ 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 WooCommerce DHL Express: shipments as tables

SleekView joins wc_orders with the _dhl_express_product_code, _dhl_express_awb_number, _dhl_express_rate and _dhl_express_ship_date meta the plugin writes per order. Every DHL Express label becomes one filterable row.

♾️ Lifetime License available

SleekView table view for WooCommerce DHL Express

DHL Express service detail belongs in a column, not a metabox

WooCommerce DHL Express covers the premium air products Woo stores actually use: Express Worldwide, Express 12:00, Express 09:00 and Express Easy. Each label the plugin generates writes the product code, rate, AWB number and ship date into wp_postmeta or wc_orders_meta on the order it belongs to.

The default WooCommerce orders screen does not pivot any of that into columns. Pulling up today's Express 12:00 shipments, sorting by rate, or filtering to a US-bound view forces the dispatcher to open orders one at a time and read the DHL metabox.

SleekView reads the same DHL Express meta keys joined with wc_orders. Product code, rate, AWB number and destination country become real sortable columns. Filters scope to one service or one date window and stay saved as a named preset. Inline edits route through WooCommerce CRUD so order-status hooks still fire.

Workflow

How SleekView reads WooCommerce DHL Express data

1

Pick the source

Point SleekView at wc_orders joined with _dhl_express_product_code, _dhl_express_rate, _dhl_express_awb_number and _dhl_express_ship_date meta. One row per DHL Express shipment.
2

Compose columns

Add order ID, customer, service code, rate, AWB and destination country. Hide what each role doesn't need so finance and dispatch get different layouts on the same data.
3

Save and scope per role

Name views like "Today's Express", "Worldwide only" or "12:00 SLA queue" and gate by WordPress capability so support and dispatch each load the right preset.
4

Edit inline or bulk-update

Fix AWB typos, update status, bulk-mark shipped. Writes route through Woo's CRUD layer so order-status, email-notification and tracking hooks fire identically to manual admin edits.

Sample columns

A typical DHL Express shipments table

SleekView joins wc_orders with the DHL Express meta keys (_dhl_express_product_code, _dhl_express_awb_number) the plugin writes per order.
Source: wp_wc_orders + DHL Express order meta
Order Customer Service Rate AWB Destination
#60214 alex@studio.co Express Worldwide $84.20 1234567890 US 10001
#60215 ria@design.io Express 12:00 $112.50 1234567891 GB SW1A
#60216 tom@hello.dev Express 09:00 $148.00 1234567892 DE 10115
#60217 mia@brew.coop Express Easy $42.80 1234567893 FR 75001

Comparison

Default WooCommerce DHL Express admin vs SleekView

Default WooCommerce DHL Express admin

  • DHL Express product code is hidden in a per-order metabox, not the orders list
  • Sorting Express Worldwide vs Express 12:00 by rate is a per-order drill
  • Filtering to one destination country or service tier is not built in
  • AWB numbers live in _dhl_express_awb_number meta but never surface as a column
  • Reconciling the monthly DHL Express invoice against orders means CSV-exporting and joining by hand

SleekView

  • Reads wc_orders joined with _dhl_express_product_code, _dhl_express_rate and _dhl_express_awb_number
  • Service tier, rate and AWB as sortable columns alongside customer and date
  • Filter across Express Worldwide, 12:00, 09:00 and Express Easy in one dataset
  • Save filtered views per service, destination country or ship-date window
  • Inline edits route through Woo CRUD so woocommerce_order_status_changed still fires

Features

What SleekView gives you for WooCommerce DHL Express

Service tier as a column

Express Worldwide, Express 12:00 and Express 09:00 show up as a sortable column sourced from _dhl_express_product_code. A premium-tier drift review becomes a filter, not an audit.

Inline AWB and status edits

Fix an AWB number or flip status in the row. Writes route through Woo's CRUD layer so woocommerce_payment_complete and tracking notification hooks fire as expected.

Saved DHL filters per role

Combine service code, destination country and date range into a named preset. The dispatcher's morning view loads in one click instead of being rebuilt every shift.

Audience

Who uses SleekView for WooCommerce DHL Express

Shipping dispatchers

Today's Express shipments sorted by service code, with destination country and AWB visible. Print the filtered list against the MyDHL+ label batch without opening each order.

Finance and procurement

Export product code, rate and AWB columns for monthly DHL Express invoice reconciliation. Spot service-tier drift on rows where Express 12:00 was billed but Express Worldwide was sold.

Customer support leads

Filter by destination country or customer email to surface every DHL Express shipment for that scope. SLA-bound Express 09:00 promises stay enforceable when AWB is one column away.

The bigger picture

Why DHL Express shipments deserve a real Woo-admin table

DHL Express sells four or five distinct premium products and a single Woo store routinely uses three of them in the same week. Express Worldwide for general international air, Express 12:00 or 09:00 for SLA-bound priority, Express Easy for low-value cross-border. Each has a different rate card, a different cost structure and a different customer expectation.

The plugin records the product code on every order it labels, but the default Woo orders screen keeps that code locked inside a per-order metabox where dispatchers, finance and support each have to drill in separately. SleekView puts service tier, rate, AWB and ship date on one sortable table where the dispatcher's morning queue, finance's monthly reconciliation export and support's destination-country filter are all saved views on the same dataset. The plugin keeps owning the MyDHL+ API integration and the actual label generation.

SleekView is the operational table on top, indexed the way Woo already indexes wc_orders.

Questions

Common questions about SleekView for WooCommerce DHL Express

Yes. On HPOS SleekView reads wc_orders joined with wc_orders_meta for the DHL Express keys. On legacy stores it falls back to shop_order posts plus postmeta. The same column config works either way.

 

Whatever the plugin writes into _dhl_express_product_code: Express Worldwide, Express 12:00, Express 09:00, Express Easy and any regional codes. Each appears as its own filterable value in the service column.

 

Yes. Multi-select rows and apply a bulk-edit on _dhl_express_awb_number. The write path goes through Woo's CRUD so downstream tools reading the same meta key stay consistent.

 

No. SleekView writes the order status; the DHL Express plugin owns label production through its own metabox actions. That keeps API rate limits and label-cost responsibility with the plugin, not the table view.

 

Yes. Any _dhl_express_* meta key actually present in wc_orders_meta or postmeta shows up in the SleekView column picker. The agent UI lists keys in use so you don't guess names.

 

Queries hit indexed columns on wc_orders (id, status, date_created_gmt) and join meta keys via a single query rather than per-row lookups. Pagination is keyset where possible, so list renders stay sub-second.

 

Yes. The filtered view exports to CSV with the same columns shown. Order-erasure requests handled through Woo's privacy tools still cascade through CRUD, removing the rows and their DHL Express meta together.

 

Yes. Refunds are linked to parent orders by parent_order_id on HPOS or shop_order_refund post type on legacy. SleekView can show them as a related child table per order row or as their own filtered view scoped to a date range.

 

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