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

SleekView joins wc_orders with the _colissimo_parcel_number, _colissimo_product_code, _colissimo_weight and _colissimo_pickup_point meta the plugin writes per order. Domicile, Signature and Point Retrait shipments all land on one table.

♾️ Lifetime License available

SleekView table view for WooCommerce Colissimo

Colissimo product, parcel number and pickup point need columns

WooCommerce Colissimo handles the La Poste / Colissimo product family: Colissimo Domicile (sans signature), Colissimo Signature, Colissimo Outre-Mer and Colissimo Point Retrait for pickup-point delivery. Each shipped order writes the product code, parcel number, declared weight and (for Point Retrait) the pickup-point ID into postmeta.

The default Woo orders screen does not pivot any of that. Pulling up today's Point Retrait parcels, sorting Domicile parcels by weight to spot mis-declared rows, or filtering to a Paris-only view requires opening orders one at a time and reading the Colissimo metabox.

SleekView reads the same Colissimo meta joined with wc_orders. Product, parcel number, weight and pickup-point ID become real columns. Filters scope to one product or one postcode band and stay saved as a preset. Inline edits to AWB and status route through Woo CRUD so the Colissimo plugin keeps owning the SOAP integration unchanged.

Workflow

How SleekView reads WooCommerce Colissimo data

1

Pick the source

Point SleekView at wc_orders joined with _colissimo_parcel_number, _colissimo_product_code, _colissimo_weight and _colissimo_pickup_point meta. One row per Colissimo shipment.
2

Compose columns

Add order ID, customer, product code, weight, parcel number, postcode and pickup-point ID. Hide what the role doesn't need so dispatch and finance load different layouts on the same data.
3

Save and scope per role

Name views like "Today's Point Retrait", "Domicile Paris" or "Outre-Mer only" and gate by WordPress capability so finance and dispatch each get their own column set.
4

Edit inline or bulk-update

Fix parcel-number typos, update status, bulk-mark shipped. Writes go through Woo's CRUD layer so order-status emails and tracking-notification hooks fire identically to manual edits.

Sample columns

A typical Colissimo parcels table

Joins wc_orders with Colissimo meta keys (_colissimo_parcel_number, _colissimo_product_code) the plugin writes after a successful label call.
Source: wp_wc_orders + Colissimo order meta
Order Customer Product Weight Parcel # Destination
#48201 alex@studio.co Domicile 0.84 kg 8Q12345678901FR FR 75011
#48202 ria@design.io Signature 1.20 kg 8R12345678902FR FR 69002
#48203 tom@hello.dev Point Retrait 0.62 kg 8L12345678903FR FR 33000
#48204 mia@brew.coop Outre-Mer 2.10 kg 8C12345678904FR RE 97400

Comparison

Default WooCommerce Colissimo admin vs SleekView

Default WooCommerce Colissimo admin

  • Colissimo product code (Domicile, Signature, Point Retrait) sits inside the per-order metabox, not a column
  • Filtering to Point Retrait pickup-point orders means scrolling through every order
  • Declared parcel weight in _colissimo_weight is invisible until the order is opened
  • Pickup-point ID (_colissimo_pickup_point) never surfaces in the list view
  • Reconciling La Poste invoices against actual product codes is a CSV-and-spreadsheet exercise

SleekView

  • Reads wc_orders joined with _colissimo_parcel_number, _colissimo_product_code and _colissimo_weight
  • Pickup-point ID as a real column, sortable and filterable
  • Filter across Domicile, Signature, Point Retrait and Outre-Mer in one dataset
  • Save filtered views per product, postcode band or ship-date window
  • Inline edits route through Woo CRUD so order-status emails still fire

Features

What SleekView gives you for WooCommerce Colissimo

Colissimo product as a column

Domicile, Signature, Point Retrait and Outre-Mer become a sortable column sourced from _colissimo_product_code. Spotting a Signature parcel mis-tagged as Domicile is a sort, not an audit.

Pickup-point ID surfaced

_colissimo_pickup_point appears next to the customer column. Dispatchers grouping Point Retrait labels by branch can sort once and print, no per-order drill required.

Postcode-band filters

Filter by destination postcode prefix (Paris 75, Lyon 69, Marseille 13) to plan Domicile deliveries by region. The filter saves as a named preset for daily reuse.

Audience

Who uses SleekView for WooCommerce Colissimo

Shipping dispatchers

Today's Colissimo queue filtered by product and sorted by postcode. Point Retrait labels grouped by pickup-point ID before the courier collection, with parcel numbers visible in the row.

Finance and procurement

Monthly La Poste invoice reconciliation: export product code, declared weight and parcel number columns to compare against the carrier statement. Spot weight-band mismatches in one sort.

Customer support

Filter by parcel number, customer email or postcode to find any Colissimo shipment in one query. Domicile-versus-Signature confusion ends when the product column is visible inline.

The bigger picture

Why Colissimo stores need a Woo-admin table that knows the product

Colissimo's product mix is unusual: Domicile and Signature for home delivery, Point Retrait for La Poste pickup-points, Outre-Mer for the French overseas territories. Each has different tariffs, different SLAs and very different operational handling. A typical French Woo store uses three of these in the same week, sometimes the same hour.

The plugin writes the product code on every order it labels, but the default Woo orders screen treats it as per-order detail rather than a column. Dispatchers planning a Point Retrait collection, finance reconciling the monthly La Poste invoice and support tracking a Domicile delivery all want the same dataset shown three different ways. SleekView turns the existing Colissimo meta into a saved-view workspace: same database, same SOAP integration, same hooks.

The plugin keeps owning the carrier API. SleekView is the table on top, indexed the way Woo already indexes wc_orders and joined to the meta keys the plugin already writes.

Questions

Common questions about SleekView for WooCommerce Colissimo

Yes. SleekView reads the parcel number and product code meta the plugin writes after the SOAP call succeeds. Which API version the plugin uses (SOAP, REST migration) doesn't change the column mapping.

 

Yes. The pickup-point ID stored in _colissimo_pickup_point is exposed as a sortable, filterable column. Grouping a day's Point Retrait labels by branch becomes one sort instead of a manual review.

 

Yes. Outre-Mer parcels for Réunion, Martinique, Guadeloupe and other territories appear with their own product code value in the column. Filtering Outre-Mer only is straightforward for tariff-band reconciliation.

 

Yes. SleekView writes through Woo CRUD so woocommerce_order_status_changed, email triggers and inventory hooks fire. The Colissimo plugin's own per-order actions stay intact for label regeneration.

 

_colissimo_weight from the order is shown directly. Billed weight from the carrier invoice isn't stored locally by the plugin, so the comparison happens by exporting and joining against the La Poste statement.

 

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

 

Queries hit indexed columns on wc_orders and join meta keys through a single query. Stores doing thousands of Colissimo labels a week render the filtered list well under a second on standard Kinsta or WP Engine hardware.

 

Yes. The filtered view exports to CSV with the same columns shown, ready for the annual account-manager conversation or a tariff-renegotiation prep meeting.

 

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