✨ 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 AfterShip Tracking: synced shipments and delivery state as tables

SleekView reads the carrier slug, tracking number, and last-known delivery state AfterShip writes back to _aftership_* meta and renders one row per order. Filter to in-transit shipments, exception statuses, or unsynced orders.

♾️ Lifetime License available

SleekView table view for AfterShip Tracking for WooCommerce

AfterShip syncs the data. SleekView turns it into a row.

AfterShip's WooCommerce plugin pushes orders to the AfterShip dashboard and writes the carrier slug, tracking number, and last-known delivery checkpoint back to the order as meta. The plugin uses keys like _aftership_tracking_number, _aftership_tracking_provider_name, and a status field populated by AfterShip's webhook responses. The data flows in, but the WordPress Orders list shows none of it.

SleekView reads those meta keys and renders one row per order with carrier, tracking, and delivery state alongside customer email and order total. Support fielding a where-is-my-package call filters by email and sees the AfterShip-reported state inline. Ops auditing sync coverage filters to orders in completed with no _aftership_tracking_number populated. Exceptions, the ones AfterShip flags as failed delivery, become a saved view rather than a dashboard tab.

Inline edits write through WooCommerce CRUD so manually entered tracking for an off-platform handover (a freight pickup, a returns courier) fires the same order-update hooks AfterShip listens to. The plugin keeps owning the API; SleekView gives the data a WordPress-native surface.

Workflow

How SleekView reads your AfterShip data

1

Point at the orders source

Pick wc_orders (HPOS) or shop_order (legacy). SleekView lists the _aftership_* meta keys actually present in your installation so you select from real data.
2

Compose the AfterShip columns

Add carrier, tracking number, delivery state, and branded URL. Mix with order status, customer email, and total to assemble a single support-friendly row.
3

Save and gate by role

Name views (Sync gaps, Exceptions this week, Support lookup) and gate by capability. Each team opens directly into the slice they own.
4

Edit inline and audit

Inline-edit tracking for off-platform handovers, bulk-export per-carrier slices, and audit sync coverage daily. CRUD writes fire AfterShip's listeners as expected.

Sample columns

A typical AfterShip tracking view

Order rows from wc_orders joined with the AfterShip meta keys for carrier, tracking, and delivery state.
Source: wp_wc_orders + wp_wc_orders_meta (_aftership_*)
Order # Customer Carrier Tracking # Delivery state Synced
#22041 alex@studio.co DHL Express EE123456789DE Delivered Apr 24
#22038 ria@design.io USPS 9405511899223876543 In transit Apr 24
#22035 tom@hello.dev UPS 1Z999AA10123456784 Exception Apr 23
#22030 mia@brew.coop (none) (none) Not synced (none)

Comparison

Default AfterShip integration vs SleekView

AfterShip dashboard

  • AfterShip dashboard lives outside WordPress with its own login
  • Order list shows neither carrier nor tracking number
  • No in-admin filter for exception or stalled shipments
  • Manual tracking for off-platform handovers requires editing each order
  • Sync gaps surface only by absence of _aftership_tracking_number

SleekView

  • Carrier, tracking, and delivery state as real columns on every order
  • Saved view for exception statuses and stalled deliveries
  • Filter for unsynced orders as an early-warning view
  • Inline-edit tracking for off-platform handovers without leaving WP
  • Bulk export filtered slices to CSV for carrier or customer audits

Features

What SleekView gives you for AfterShip Tracking for WooCommerce

Exception filter

AfterShip flags failed delivery, address issues, and customs holds in its dashboard. SleekView surfaces those same states as a column you can filter, so the exception queue lives in WP Admin where customer support already works.

Sync gap detection

Save a view of orders in completed status with no _aftership_tracking_number populated. Sync failures, API blips, and unmapped carriers become visible before customers chase.

Off-platform tracking

Drop a tracking number directly into a row for a freight pickup or returns courier. CRUD writes mean AfterShip's listeners and any customer-email plugins see the change as if it came from the dashboard.

Audience

Who uses SleekView for AfterShip Tracking

Customer support

Search by email and see carrier, tracking, and last-known checkpoint inline. Reply with accurate state instead of a generic carrier search link, all without opening the AfterShip dashboard.

Logistics ops

Filter to exception states and group by carrier to spot which courier is producing the most failed deliveries this week. A weekly view becomes the carrier scorecard.

Finance reconciliation

Cross-reference shipped-and-delivered orders against the month's shipping cost report. Saved views feed the carrier invoice review without exporting from two dashboards.

The bigger picture

Why AfterShip data belongs in WP Admin

AfterShip is excellent at what it does: aggregate carrier data, normalise delivery states, and push branded tracking pages. Its dashboard is the right place for carrier mapping and analytics. But the day-to-day operational lookups, the where-is-my-package call, the exception triage, the sync-coverage audit, all happen in WordPress where the orders live.

Forcing support and ops to context-switch to AfterShip's dashboard for every lookup adds friction that compounds across hundreds of tickets a week. SleekView reads the meta AfterShip already writes back, the carrier, tracking, and delivery state, and surfaces it as a row in WP Admin. Saved views become the support tooling, the exception queue, the sync-gap audit.

AfterShip keeps owning the upstream platform, and the WordPress side gets the visibility it always lacked. Same data, dramatically less context switching.

Questions

Common questions about SleekView for AfterShip Tracking for WooCommerce

Yes. AfterShip writes status updates back to the same meta keys the plugin populates on initial sync, and SleekView reads from those keys. The column reflects the most recent state pushed from AfterShip.

 

Yes. Build a view of orders in completed status with an empty _aftership_tracking_number. Save it as Sync gaps and run it on a schedule. The gap stops being invisible.

 

Edits go through WooCommerce CRUD so the order-update hook fires. If your store sends a tracking email on update through AfterShip or another plugin, that email fires from a SleekView edit the same as from the per-order screen.

 

Yes. On HPOS the AfterShip meta moves to wc_orders_meta and SleekView reads from there. On legacy stores it reads from postmeta. Same view config either way.

 

AfterShip's re-sync action is exposed through the order action menu. SleekView surfaces order actions in the row's action menu, so re-sync fires per row. Bulk re-sync depends on whether the plugin exposes a batch action in your version.

 

Yes if the plugin writes the branded tracking URL back to meta. The link becomes a column you can copy or include in CSV exports, useful for support templates that include the branded URL.

 

No. AfterShip's dashboard remains where carrier mapping, delivery rules, and analytics live. SleekView is the WordPress-side row view for support and ops who shouldn't need to context-switch for every lookup.

 

Yes. Filter to exception state, group by carrier, and export to CSV. Useful for carrier scorecards and for chasing carriers about stalled shipments outside the AfterShip platform.

 

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