What this is
Tracksies HQ plays nicely with automation tools like Zapier, WP Fusion, and WooCommerce webhooks. This page explains what they connect to, when things fire, and how Tracksies fits into the picture without getting in the way.
If you’re worried about whether Tracksies will break your existing automations — it won’t. Tracksies adds to WooCommerce, it doesn’t replace the parts that other tools depend on.
—
Built-in plugin integrations
Tracksies detects and integrates with several third-party plugins automatically. Each integration has a feature toggle in Tracksies > Settings > Integrations so you only enable what you use.
| Plugin | Integration | Toggle | What it does |
|---|---|---|---|
| PitchPrint | Packing dashboard | integrations.pitchprint | Shows design previews, PDF/PNG/TIFF downloads, and customer file uploads in the packing detail panel. Supports both design projects (pitchprint_customization) and direct file uploads (_w2p_set_option). |
| ShipStation | Shipping tracking | integrations.shipstation | Reads tracking number, carrier, and ship date from the ShipStation WC plugin, and shows a deep-link “Shipping Label” button in the Packsie Documents section. Toggle on under Tracksies > Settings > Integrations — off by default. |
| Advanced Custom Fields | Priority rules | Auto-detected | ACF product and order fields available as priority rule conditions. |
| Meta Box | Priority rules | Auto-detected | Meta Box product and order fields available as priority rule conditions. |
| Studio Wombat (WAPF) | Priority rules | Auto-detected | Product add-on fields from order item meta available as priority rule conditions. |
| WP Whale (APF Pro) | Priority rules | Auto-detected | Product add-on fields from order item meta available as priority rule conditions. |
| WCPA (Acowebs) | Priority rules | Auto-detected | Product add-on fields from order item meta available as priority rule conditions. |
Priority rule plugins are auto-detected — the moment one of them is installed, its fields appear as available condition sources in the Priority Rules settings. Shipping and design integrations are opt-in toggles under Tracksies > Settings > Integrations (default off), so you only load the code for the ones you actually use. Enable the toggle, and the relevant features light up.
—
PitchPrint
What it does
When the PitchPrint integration is enabled, the packing detail panel in Packsie’s dashboard shows design files for each order item that has PitchPrint customisation data:
- Design projects — preview thumbnails (up to 4 pages, hover to zoom) plus download buttons for PDF, PNG, and TIFF formats
- File uploads — when customers upload their own files (PDFs, artwork) via PitchPrint’s uploader, download links appear for each file
PitchPrint’s raw meta fields (pitchprint_customization, preview, _w2p_set_option) are hidden from the generic item meta display when the integration is active, to avoid showing duplicate or unreadable JSON data to packers.
Enabling it
- Go to Tracksies > Settings
- Click the Integrations tab
- Switch on PitchPrint
The toggle is off by default because most stores don’t use PitchPrint. Only enable it if PitchPrint is installed and your products use it for customisation or file uploads.
Requirements
- PitchPrint plugin installed and active on your WooCommerce store
- Tracksies HQ with Packsie activated (for the packing dashboard)
—
Shipping tracking providers
Tracksies has its own native shipment tracking, and can read tracking data from ShipStation when you enable the integration toggle. Tracking numbers flow into your emails, My Account page, and order admin without any extra setup.
| Source | What Tracksies reads | Toggle required? |
|---|---|---|
| Tracksies native | _tracksies_shipments — full multi-parcel shipment data including item assignments. Entered via the tracking meta box on the order edit screen. | Always on (it’s our own data) |
| ShipStation | _tracking_number, _tracking_provider, _date_shipped (the meta keys the official WC ShipStation plugin writes) | integrations.shipstation — off by default |
When both are present, Tracksies’ own tracking wins — the assumption is that if you added a shipment via Tracksies, that’s the authoritative record. If only ShipStation data is present, that’s used.
What you actually get
Once tracking data is present from either source, Tracksies:
- Includes carrier + tracking number + “Track Package” link in the Shipped and Partially Shipped customer emails
- Shows the same info on the customer’s My Account > View Order page (plus a Track button on each row of the Orders list)
- Displays a tracking column on the WooCommerce Orders list
- Exposes tracking placeholders (
{tracking_number},{tracking_link},{tracking_button}, etc.) in the email template editor for use in any Tracksies email
When the ShipStation integration is on and the order is live in ShipStation, Tracksies also renders a Shipping Label (ShipStation) button in the Packsie order Documents section, next to Packing Slip and Invoice, linking directly to the ShipStation order page.
Why a toggle and not auto-detect?
Earlier Tracksies releases auto-detected any installed shipping plugin. We moved to opt-in toggles because:
- Staff clarity. Store owners should know exactly which external platforms their Tracksies install is reading from. Auto-detect hid that.
- Performance. A toggled-off integration loads no code at all — no need to spend cycles checking for meta that doesn’t exist.
- Email conflicts. Some shipping plugins send their own tracking emails. Without a toggle, stores could silently end up with duplicate “Track your order” emails when both Tracksies and the source plugin sent one. Explicit opt-in gives store owners the chance to disable the source plugin’s emails before enabling Tracksies’ integration.
Don’t see your shipping tool here?
Tracksies native tracking supports any carrier you add — pick from the built-in list (USPS, FedEx, UPS, DHL, AusPost, Royal Mail, Canada Post, Sendle, and more) or choose “Other” and paste your own tracking URL pattern. For most shops, Tracksies native tracking plus the ShipStation integration for label printing covers everything.
If you use a shipping platform that writes to standard order meta and you’d like Tracksies to read it, tell us at tracksies.com/support — we’ll consider adding it if the plugin’s meta keys are consistent and the install base is meaningful.
—
How WooCommerce integrations actually work
Before diving into specific tools, it helps to understand what they’re actually connecting to. Most WooCommerce integrations — Zapier, WP Fusion, AutomateWoo, make.com, and others — work through one or both of these mechanisms:
1. Action hooks (server-side events)
WooCommerce fires PHP action hooks whenever something happens: a new order is placed, a status changes, a customer is created. These hooks run on the server, completely independent of what anyone sees on screen. They fire whether you’re looking at the order, on holiday, or asleep. Automation tools listen for these hooks and react accordingly.
2. The WooCommerce REST API
This is the API that external services call to read and write data — fetching orders, updating statuses, creating products. It’s an HTTP interface that works regardless of the WordPress admin UI.
Neither of these has anything to do with what’s visible on the order edit screen. They’re server-side systems. This is why hiding WooCommerce metaboxes with Order Hub’s “Replace WooCommerce order panels” feature doesn’t affect integrations at all — the metaboxes are a visual layer on top of the data, not the data itself.
—
When do WooCommerce hooks fire?
Here’s a reference of the most common hooks that automation tools listen for, and when they fire. This is useful when you’re setting up Zapier zaps, WP Fusion rules, or any webhook-based automation.
Order hooks
| Hook | When it fires | Common automations |
|---|---|---|
woocommerce_new_order | A new order is created (before payment) | Log new orders, notify team |
woocommerce_payment_complete | Payment is confirmed for an order | Start fulfilment, send to warehouse |
woocommerce_order_status_changed | Any order status changes (old → new) | The big one — most automations trigger here |
woocommerce_order_status_processing | Order moves to Processing | Trigger packing workflow, notify staff |
woocommerce_order_status_completed | Order moves to Completed | Send review requests, update CRM, trigger loyalty |
woocommerce_order_status_cancelled | Order is cancelled | Update inventory, notify customer, refund |
woocommerce_order_status_refunded | Order is fully refunded | Update accounting, CRM cleanup |
woocommerce_order_refunded | A refund is created on an order | Update totals, notify accounting |
Tracksies custom status hooks
When Tracksies custom statuses are enabled, they register as proper WooCommerce statuses. This means they fire the standard woocommerce_order_status_changed hook just like any built-in status, plus their own specific hooks:
| Hook | When it fires |
|---|---|
woocommerce_order_status_wc-packed | Order moves to Packed |
woocommerce_order_status_wc-shipped | Order moves to Shipped |
woocommerce_order_status_wc-partially-shipped | Order moves to Partially Shipped |
woocommerce_order_status_wc-ready-pickup | Order moves to Ready for Pickup |
woocommerce_order_status_wc-picked-up | Order moves to Picked Up |
woocommerce_order_status_wc-partially-packed | Order moves to Partially Packed |
woocommerce_order_status_wc-partially-returned | Order moves to Partially Returned |
woocommerce_order_status_wc-returned | Order moves to Returned |
Every one of these also fires the generic woocommerce_order_status_changed hook with the old and new status as parameters. So if your automation listens for “any status change,” it will catch Tracksies statuses too.
Customer hooks
| Hook | When it fires |
|---|---|
woocommerce_created_customer | New customer account created |
woocommerce_update_customer | Customer profile updated |
profile_update | WordPress user profile updated |
Tracksies-specific hooks
These are hooks that Tracksies fires for its own features. Third-party automation tools won’t know about these by default, but WP Fusion and custom code can listen for them:
| Hook | When it fires |
|---|---|
tracksies_customer_synced | Customer profile created/updated from order data |
tracksies_customer_status_changed | Customer status changes (Active, VIP, Caution, etc.) |
tracksies_customer_vip_flagged | Customer promoted to VIP status |
tracksies_tags_recalculated | Customer tags recalculated |
tracksies_return_status_updated | Return request status changes |
—
Zapier for WooCommerce
How it works
Zapier connects to WooCommerce through the WooCommerce REST API and webhooks. When you create a zap with a WooCommerce trigger, Zapier either polls the API at intervals or sets up a webhook that WooCommerce fires when events happen.
The key point: Zapier talks to WooCommerce’s data layer, not the admin screen. It reads order data from the database via the API. It doesn’t care what metaboxes are visible, what plugins are installed, or what the admin UI looks like.
Common triggers that work with Tracksies
| Zapier trigger | What fires it | Works with Tracksies? |
|---|---|---|
| New Order | woocommerce_new_order | Yes — unaffected |
| Updated Order | woocommerce_order_status_changed | Yes — includes Tracksies custom statuses |
| New Customer | woocommerce_created_customer | Yes — unaffected |
| Order status → specific status | Status-specific hooks | Yes — Packed, Shipped, etc. all fire standard WooCommerce hooks |
Tracksies custom statuses in Zapier
Because Tracksies registers its statuses as proper WooCommerce order statuses, they appear in Zapier’s status dropdowns. If you set up a zap that triggers when an order moves to “Shipped,” it works exactly like a zap for “Completed” or “Processing” — same mechanism, same reliability.
If you’re using Zapier’s “Updated Order” trigger with a filter for specific statuses, the Tracksies status slugs are:
| Status | Slug for Zapier filters |
|---|---|
| Packed | wc-packed |
| Shipped | wc-shipped |
| Partially Shipped | wc-partially-shipped |
| Ready for Pickup | wc-ready-pickup |
| Picked Up | wc-picked-up |
| Partially Packed | wc-partially-packed |
| Partially Returned | wc-partially-returned |
| Returned | wc-returned |
Will hiding WooCommerce metaboxes break my zaps?
No. Zapier connects via the REST API and webhooks — server-side systems that have no relationship with the admin UI. The “Replace WooCommerce order panels” feature in Order Hub hides metaboxes with CSS. The underlying data, API endpoints, and hooks are completely unaffected.
—
WP Fusion
How it works
WP Fusion syncs WordPress and WooCommerce data with your CRM (ActiveCampaign, HubSpot, Mailchimp, Drip, and dozens of others). It hooks into WordPress and WooCommerce action hooks to detect changes, then pushes data to your CRM via the CRM’s API.
Does WP Fusion work alongside Tracksies?
Yes. WP Fusion’s WooCommerce triggers are all based on standard WooCommerce hooks, so they work perfectly with Tracksies installed. Custom statuses (Packed, Shipped, etc.) fire the same woocommerce_order_status_changed hook that WP Fusion listens to, so your existing CRM automations continue working.
| Event | Hook WP Fusion listens to | Works with Tracksies? |
|---|---|---|
| Order placed | woocommerce_order_status_processing | Yes |
| Order completed | woocommerce_order_status_completed | Yes |
| Order status changed | woocommerce_order_status_changed | Yes — includes Tracksies custom statuses |
| Customer created | woocommerce_created_customer | Yes |
| Customer updated | profile_update | Yes |
Planned: Tracksies customer data in your CRM
A dedicated Tracksies-to-WP-Fusion integration is on our roadmap. When it ships, it will push Tracksies customer intelligence data to your CRM — customer status (VIP, Caution), lifetime value, tags earned, and order frequency — so you can build CRM segments and automations based on Tracksies data (win-back sequences when a customer is at risk, auto-tagging VIPs in your email platform, and so on).
This isn’t live yet. We’ll update this doc and add the feature toggle when the integration is ready for release.
—
WooCommerce webhooks (for custom integrations)
If you’re building custom integrations or using a tool that accepts webhooks (make.com, n8n, Pabbly, custom scripts), WooCommerce has a built-in webhook system.
Setting up a webhook
- Go to WooCommerce > Settings > Advanced > Webhooks
- Click Add webhook
- Set the Topic — this is the event that fires the webhook
- Enter your Delivery URL — the endpoint that receives the data
- Choose the API version (use the latest)
- Save
Available topics relevant to Tracksies
| Topic | When it fires |
|---|---|
| Order created | New order placed |
| Order updated | Any change to an order (including status changes) |
| Order deleted | Order permanently deleted |
| Order restored | Order restored from trash |
| Customer created | New customer account |
| Customer updated | Customer data changed |
When a Tracksies custom status change happens, it triggers the “Order updated” webhook because it’s a standard WooCommerce status change under the hood. The webhook payload includes the full order object with the current status, so your receiving endpoint can filter by status.
Webhook payload and Tracksies data
The webhook payload is the standard WooCommerce order object (JSON). It includes all order data, line items, addresses, and meta. Tracksies data stored as order meta (tracking numbers, packed-by info, priority level) is included in the meta_data array of the payload.
—
Other automation tools
AutomateWoo
AutomateWoo triggers work identically to Zapier — they listen for WooCommerce hooks. Tracksies custom statuses appear as trigger options because they’re registered as proper WooCommerce statuses.
make.com (formerly Integromat)
make.com’s WooCommerce module uses the REST API, same as Zapier. All Tracksies custom statuses and data are accessible.
Accounting plugins (Xero, QuickBooks, etc.)
Accounting integrations typically hook into woocommerce_order_status_completed and woocommerce_order_refunded to sync invoices and refunds. These hooks fire regardless of what’s visible in the admin UI. Tracksies doesn’t change the order total, line items, tax, or any financial data — it adds intelligence on top.
Shipping plugins (ShipStation, Shippo, etc.)
Shipping plugins read order data via the REST API or WooCommerce hooks. They’re unaffected by Tracksies. If a shipping plugin adds a metabox to the order screen (like ShipStation’s label printing box), that metabox will be hidden by the “Replace WooCommerce order panels” feature — but only the two standard WooCommerce metaboxes (Order Data and Order Items) are hidden. Third-party metaboxes are left alone.
Important clarification: The “Replace WooCommerce order panels” feature only hides two specific metaboxes:
#woocommerce-order-data(addresses, general info)#woocommerce-order-items(line items, totals)
Any metaboxes added by other plugins (shipping labels, accounting sync buttons, custom fields) remain visible. And if you ever need the WooCommerce panels back, click “Show WooCommerce panels” at the bottom of Order Hub, or turn off the feature in Settings > Features.
—
Common questions
Will Tracksies break my existing Zapier zaps?
No. Zapier connects via the WooCommerce REST API and webhooks. Tracksies doesn’t modify either of those systems. Your existing zaps will continue to work exactly as they did before installing Tracksies.
Do Tracksies custom statuses show up in Zapier/WP Fusion?
Yes. Because they’re registered as proper WooCommerce order statuses, they appear anywhere WooCommerce statuses appear — automation tool dropdowns, webhook payloads, API responses.
Does hiding WooCommerce metaboxes affect any integrations?
No. The metabox hiding is CSS-only (display: none). The metaboxes are still in the DOM, all their PHP still runs, all hooks still fire, and the REST API is completely unaffected. It’s purely visual.
What about plugins that add buttons inside the WooCommerce metaboxes?
If a plugin adds a button or field inside the #woocommerce-order-data or #woocommerce-order-items metaboxes, that button will be hidden along with the metabox. Click “Show WooCommerce panels” at the bottom of Order Hub to reveal them, or turn off the “Replace WooCommerce order panels” feature in Settings > Features if you need them permanently visible. Third-party metaboxes (ones with their own metabox ID) are never hidden.
I use a plugin that adds its own metabox to the order screen. Will that be hidden?
No. Only the two standard WooCommerce metaboxes are hidden. Any metabox registered by a third-party plugin has its own unique ID and is not affected.
Can I trigger automations on Tracksies-specific events (like a customer becoming VIP)?
Not yet with off-the-shelf tools — Zapier and WP Fusion listen for standard WooCommerce hooks, not Tracksies-specific ones. We’re building a WP Fusion integration that will push Tracksies customer data (status, tags, LTV) to your CRM, which will unlock this. In the meantime, if you’re comfortable with code, you can hook into tracksies_customer_status_changed or tracksies_customer_vip_flagged with a custom plugin or snippet to trigger your own automations.
My automation tool says it can’t find the custom status I need.
Make sure the Custom Order Statuses feature is enabled in Tracksies > Settings > Features. Then check your automation tool’s WooCommerce connection — you may need to refresh it or reconnect for new statuses to appear in dropdowns.
—
If something goes wrong
Automation stopped firing after installing Tracksies
This is almost certainly a coincidence — Tracksies doesn’t modify WooCommerce’s hook system or REST API. Check that your automation tool’s WooCommerce connection is still authenticated (API keys haven’t expired), and that the specific trigger event is still happening (the order status is actually changing to the status your automation expects).
Webhook not delivering for custom statuses
WooCommerce webhooks fire on “Order updated,” which includes all status changes. If your webhook isn’t firing for a Tracksies status change, check that the webhook is set to “Order updated” (not a more specific topic that only covers built-in statuses). Also verify the webhook is active in WooCommerce > Settings > Advanced > Webhooks.
WP Fusion not syncing Tracksies fields
The dedicated Tracksies-to-CRM integration is still in development. In the meantime, WP Fusion’s standard WooCommerce integration works fine alongside Tracksies — order triggers, status changes, and customer data all sync normally. Tracksies-specific fields (customer status, tags, LTV) will become available for CRM syncing once the integration ships.
Need more help? Check our FAQ & Troubleshooting guide or contact support.