Live carrier status for every shipment through your own 17TRACK or AfterShip account, with order status rules and a customer delivery timeline.
Tested on 2 buildsUpdated Nov 3, 2026Version 1.0.0CS-Cart, Multi-Vendor 4.17.2 – 4.21.x No core file edits
Built for
Parcel Status Updates: every carrier scan from your own 17TRACK or AfterShip account, order status rules and a delivery timeline for customers1 of 7
What it does
For stores that ship with tracking numbers and want to stop checking carrier websites by hand. The add-on connects CS-Cart shipments to your own 17TRACK (API v2.2) or AfterShip (Tracking API 2024-04) account. You pay the service for its plan; the add-on adds no fee per parcel. All flows were tested against mock servers that answer like both APIs, including signed webhooks and error answers; a live account test is still open.
How it works
Choose 17TRACK or AfterShip, paste your API key, test the connection and add the webhook URL shown on the settings page to the service. New shipments with a tracking number are registered at once. Carrier scans arrive by signed webhook; an hourly cron job registers shipments made through the API, checks parcels without updates and stops old ones. Set one order status per parcel status, limited to the order statuses you allow. Vendors see the parcels of their own orders.
Features
Works with your own 17TRACK or AfterShip account and API key
Shipments with a tracking number are registered automatically
Signed webhooks with a secret URL token, cron polling as fallback
Order status rules for in transit, out for delivery, ready for pickup, failed attempt, problem and delivered
Rules only change orders in the statuses you allow; Delivered can wait for every parcel
Delivery status tab with progress bar, expected date and carrier events for customers
Parcel dashboard with filters, search, refresh, parcel page and activity log
Parcel status on the admin order and shipment pages
Carrier codes for USPS, UPS, FedEx and DHL, other carriers detected by the service
Multi-Vendor: vendors see and refresh the parcels of their own orders
Hook for other add-ons on every status change
What you get
Package
kv_parcel_status-1.0.0.zip, installed through Add-ons → Manage add-ons
Updates & support
12 months included. Download new versions from your account and install them in Add-ons → Manage add-ons or the Upgrade Center.
License
1 production installation. Staging, dev and localhost are free and unlimited. The add-on keeps working after the update period ends. How licensing works
For developers
Uses 6 CS-Cart PHP hooks, and provides 1 hooks of its own. No core files are changed.
Compatibility
We list only the builds we install and test on. “Tested” means the full test plan was run on that build; “Supported” means the build is inside the supported range and uses the same hooks.
CS-Cart version and edition compatibility
CS-Cart version
CS-Cart
CS-Cart Ultimate
Multi-Vendor
Multi-Vendor Ultimate
4.22 and later
Testing next
Testing next
Testing next
Testing next
4.21.2
Supported
Supported
Supported
Supported
4.20.x
Supported
Supported
Supported
Supported
4.19.x
Supported
Supported
Supported
Supported
4.18.x
Supported
Supported
Supported
Supported
4.17.2
Tested
Supported
Tested
Supported
Before 4.17.2
Not supported
Not supported
Not supported
Not supported
Last tested build: Multi-Vendor 4.17.2, Nov 3, 2026Tested on: Multi-Vendor 4.17.2, CS-Cart 4.17.2
Requirements
PHP
CS-Cart or Multi-Vendor 4.17.2 to 4.21.x, PHP 7.4 to 8.3 with the curl extension
Requirement
An account with 17TRACK (Tracking API) or AfterShip (Tracking API). Both have plans by number of tracked parcels; check the service's prices. The add-on does not include tracking quota
Requirement
HTTPS on the storefront is recommended: the service calls the webhook URL of your store
Requirement
A cron job (recommended): fallback when a webhook is missed, and for shipments made through the API or imports
Core changes
None. Hooks and template overrides only
1.0.0
Nov 3, 2026
Latest
Added 7
Shipments with a tracking number are registered with the store owner's 17TRACK (API v2.2) or AfterShip (Tracking API 2024-04) account.
Signed webhooks with a secret URL token; hourly cron job as fallback, for API shipments and to stop old parcels.
Order status rules per parcel status, limited to allowed order statuses; Delivered can wait for every parcel of the order.
Delivery status tab and status link on the customer's order page.
Parcel dashboard, parcel page with carrier events, activity log, import of earlier shipments; parcel status on the admin order and shipment pages.
Multi-Vendor: vendors see and refresh the parcels of their own orders.
Hook kv_parcel_status_changed for other add-ons.
Tested on Multi-Vendor 4.17.2, CS-Cart 4.17.2. First release.
Do I need a 17TRACK or AfterShip account?
Yes. The add-on talks to the service with your own API key. Both services have plans by number of tracked parcels; the add-on adds no fee per parcel.
Which carriers are supported?
Whatever your tracking service supports for your account. The add-on sends the carrier code for USPS, UPS, FedEx and DHL (and Australia Post, Canada Post and Swiss Post on AfterShip). For other carriers the service detects the carrier from the number, or you add a line under Carrier codes.
Has it been tested with a live account?
All flows were tested against mock servers that answer like the 17TRACK and AfterShip APIs, including signed webhooks and error answers. A test with a live account is still open; if your account answers differently, contact support.
What if a webhook is lost?
The cron job checks every parcel that had no update for the set number of hours (6 by default).
Does it change order statuses on its own?
Only through the rules you set (by default: Delivered sets Complete), only for orders in the statuses you allow, and through the normal CS-Cart status change. Every change is in the activity log.
What happens with canceled orders?
Nothing: Canceled is not in the default list of statuses the rules may change.
An order has two parcels. Is it completed after the first one?
No. By default the Delivered rule waits for every parcel of the order.
I changed a tracking number. What happens?
The parcel is reset and registered with the new number: at once on CS-Cart 4.18 and later, and on 4.17 when the order or shipment form is saved. The cron job also catches numbers changed through the API.
Is the customer page cached by the full page cache?
No. The order page is personal and never cached; the add-on prints nothing on cached pages.
Does it work with CS-Cart Ultimate storefronts?
Yes. The settings apply to the whole installation and the customer tab appears on every storefront.