✨ 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 Chronopost: express parcels as tables

SleekView joins wc_orders with the _chronopost_parcel_number, _chronopost_service_code, _chronopost_weight and _chronopost_pickup_point meta the plugin writes per order. Chrono 13, Chrono 18 and Chrono Relais shipments share one row layout.

♾️ Lifetime License available

SleekView table view for WooCommerce Chronopost

Chronopost service codes belong on the orders list

WooCommerce Chronopost covers Chronopost's express product family: Chrono 13 for next-day-by-1pm, Chrono 18 for next-day-by-6pm, Chrono Relais for pickup-point delivery, Chrono Express International for cross-border priority, and Chrono Classic for less time-critical traffic. Each shipped order writes the service code, parcel number, declared weight and (for Relais) the pickup-point ID into postmeta.

The default Woo orders screen does not pivot Chronopost service code into a column. Sorting Chrono 13 SLAs separately from Chrono 18, or filtering today's Chrono Relais labels by pickup-point branch, requires opening orders one at a time and reading the Chronopost metabox.

SleekView reads the same Chronopost meta joined with wc_orders. Service code, parcel number, weight and pickup-point ID become real columns. Filters scope to one service or one branch and save as a preset. Inline edits route through Woo CRUD so Chronopost's own API integration stays unchanged.

Workflow

How SleekView reads WooCommerce Chronopost data

1

Pick the source

Point SleekView at wc_orders joined with _chronopost_parcel_number, _chronopost_service_code, _chronopost_weight and _chronopost_pickup_point. One row per Chronopost label.
2

Compose columns

Add order ID, customer, service code, weight, parcel number, destination country and pickup-point ID. Hide what each role doesn't need so dispatch and finance load distinct layouts.
3

Save and scope per role

Name views like "Today's Chrono 13", "Chrono Relais by branch" or "Express International queue" and gate by WordPress capability so the right preset loads per team.
4

Edit inline or bulk-update

Fix parcel-number typos, update status, bulk-mark shipped. Writes go through Woo CRUD so order-status, email and tracking hooks fire identically to manual admin edits.

Sample columns

A typical Chronopost shipments table

SleekView joins wc_orders with _chronopost_parcel_number and _chronopost_service_code meta the plugin writes after a successful label call.
Source: wp_wc_orders + Chronopost order meta
Order Customer Service Weight Parcel # Destination
#52310 alex@studio.co Chrono 13 1.10 kg XW123456789FR FR 75002
#52311 ria@design.io Chrono 18 0.78 kg XW123456790FR FR 13001
#52312 tom@hello.dev Chrono Relais 0.62 kg XW123456791FR FR 33000
#52313 mia@brew.coop Express International 2.30 kg XW123456792FR DE 10115

Comparison

Default WooCommerce Chronopost admin vs SleekView

Default WooCommerce Chronopost admin

  • Chronopost service code (_chronopost_service_code) is hidden in the per-order metabox
  • Sorting Chrono 13 (1pm SLA) separately from Chrono 18 (6pm SLA) requires per-order review
  • Filtering to one pickup-point branch for Chrono Relais is not built in
  • Declared weight in _chronopost_weight never surfaces in the orders list
  • Reconciling the monthly Chronopost invoice against service codes is CSV-and-spreadsheet work

SleekView

  • Reads wc_orders joined with _chronopost_parcel_number, _chronopost_service_code and _chronopost_weight
  • Service code as a sortable column so 13 and 18 SLA queues split cleanly
  • Filter across Chrono 13, Chrono 18, Chrono Relais and Express International in one dataset
  • Save filtered views per service, pickup-point branch or destination country
  • Inline edits route through Woo CRUD so order-status hooks still fire

Features

What SleekView gives you for WooCommerce Chronopost

SLA-tier separation as a sort

Chrono 13 (1pm) and Chrono 18 (6pm) carry different SLA promises and different rates. Sorting them apart as two distinct queues becomes one click instead of a service-code metabox audit.

Chrono Relais branch grouping

The Chronopost pickup-point ID stored in _chronopost_pickup_point appears as a column. Today's Relais labels group by branch automatically before the dispatch collection.

Express International filters

Chrono Express International ships into Germany, Spain, Italy and the Benelux. Filter by destination country plus service code to plan a daily cross-border run with one named view.

Audience

Who uses SleekView for WooCommerce Chronopost

Shipping dispatchers

Today's Chrono 13 queue sorted by destination postcode, separate from the Chrono 18 backlog. Chrono Relais labels grouped by pickup-point branch before the daily courier handover.

Finance and procurement

Monthly Chronopost invoice reconciliation: export service code, parcel number and weight columns to spot weight-band drift across Chrono 13 and Express International tariffs.

Customer support

Filter by parcel number or destination postcode to surface any Chronopost shipment. SLA-tier visible inline so a Chrono 13 customer query never gets answered as a Chrono 18 promise.

The bigger picture

Why Chronopost stores need an SLA-aware admin table

Chronopost's brand is built on tight delivery windows. Chrono 13 promises next-business-day by 1pm; Chrono 18 promises next-business-day by 6pm. The difference is two service codes, two rate cards and two very different customer expectations.

A Woo store mixing the two routinely sells the SLA the customer chose but ships the volume the dispatch desk could handle. The plugin writes the service code on every order. The default Woo orders screen never surfaces it as a column.

Dispatchers planning the morning queue, finance reconciling the monthly Chronopost invoice and support promising a delivery time on a phone call all need the service code visible at row level. SleekView turns the existing Chronopost meta into a saved-view workspace: service code as a column, pickup-point ID for Chrono Relais grouping, weight sortable, parcel number searchable. Same database, same Chronopost API integration, same hooks.

The plugin keeps owning label production. SleekView is the operational table on top.

Questions

Common questions about SleekView for WooCommerce Chronopost

Yes. Whatever the plugin writes into _chronopost_service_code shows up as a filterable value: Chrono 13, Chrono 18, Chrono Relais, Chrono Express International, Chrono Classic and regional variants.

 

Yes. On HPOS SleekView reads wc_orders joined with wc_orders_meta for the Chronopost keys. On legacy stores it falls back to shop_order posts plus postmeta with the same column config.

 

Yes. Service code is a sortable column. A dispatcher can split the morning queue into the Chrono 13 (1pm) batch and the Chrono 18 (6pm) batch with a single sort plus a saved-view filter.

 

Yes. SleekView writes through Woo CRUD so woocommerce_order_status_changed, email and tracking-notification hooks fire. Chronopost's own metabox actions for label regeneration stay intact.

 

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

 

Yes. _chronopost_pickup_point is exposed as a sortable column. Grouping today's Relais labels by branch before the dispatch collection becomes a single sort instead of a per-order audit.

 

Queries hit indexed columns on wc_orders (id, status, date_created_gmt) and join meta keys through a single query. Filtered lists render sub-second even on stores doing thousands of Chronopost shipments weekly.

 

Yes. Any filtered view exports to CSV with the same columns shown, ready for the monthly Chronopost account review or a service-tariff renegotiation prep.

 

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