Kitgenix Order Tracking for WooCommerce

Kitgenix Order Tracking for WooCommerce adds shipment tracking to WooCommerce orders so store staff can record one or more parcels, allocate order items to shipments, include tracking details in customer emails and offer a self-service tracking page. The plugin is intentionally different from a live carrier-management platform. It stores the tracking number, selected carrier, tracking URL and staff-managed shipment status; it does not call courier APIs to obtain live delivery scans and it does not buy labels or book collections. That makes it suitable for stores that already fulfil orders through their preferred courier workflow but need a consistent place in WooCommerce to record and communicate tracking information. Built by Kitgenix. WooCommerce Shipment Tracking Features

• Add multiple shipments to one WooCommerce order.
• Store a tracking number and carrier for each shipment.
• Allocate specific order items and quantities to a shipment.
• Prevent allocated quantities exceeding what the customer ordered.
• Use built-in carrier tracking URL patterns.
• Create custom carrier entries for services not included by default.
• Track staff-managed shipment states including shipped, in transit, delivered, exception, returned and cancelled.
• Add tracking information to supported WooCommerce customer emails.
• Provide a dedicated partially-shipped workflow/status/email where configured by the plugin.
• Give customers a self-service order tracking page.
• Support a public tracking form with order-identification checks.
• Show tracking information in My Account for authenticated customers.
• Provide tracking analytics/reporting in wp-admin.
• Import/export tracking information in supported bulk workflows.
• Optional map presentation using OpenStreetMap tiles and Nominatim geocoding.
• Developer hooks/filters for extending carrier and tracking behaviour.
• Declare WooCommerce HPOS compatibility.

Multiple Shipments and Partial Fulfilment An order can contain more than one shipment. Each shipment has its own tracking number, carrier and status, making the plugin suitable for split parcels, backordered lines, replacements or orders dispatched from more than one fulfilment location. Items and quantities can be assigned to an individual shipment. Allocation is bounded by the quantities actually ordered, so the tracking UI cannot legitimately claim that more units were shipped than exist on the order line. The remaining/unallocated items can continue to represent what has not yet been included in a parcel. Shipment Statuses The plugin defines internal tracking states including:

• Shipped.
• In transit.
• Delivered.
• Exception.
• Returned.
• Cancelled.

These values are controlled by store staff or other code that integrates with the plugin. They are not automatically fetched from Royal Mail, DPD, UPS, FedEx or another courier. That distinction is important: a "Delivered" status in the plugin means the WooCommerce store has set that status, not that Kitgenix independently confirmed delivery with the carrier. Built-In and Custom Carriers The carrier manager includes a set of ready-made carriers with tracking URL patterns. The codebase includes services for the UK, Ireland and international markets, including Royal Mail, Parcelforce/related services represented in the carrier set, DPD, An Post, DHL, UPS, FedEx, USPS, Canada Post, Australia Post, NZ Post and others. A custom/Other carrier option is available where a courier is not built in. A custom tracking URL pattern can contain the tracking-number placeholder so customer links still lead to the relevant courier tracking page. Customer Email Notifications Tracking information can be inserted into WooCommerce email flows. The plugin also includes a dedicated email class/workflow for partially shipped orders so customers can be informed when only part of an order has been dispatched. Because tracking data is stored on the WooCommerce order, customer-facing output can reuse the same shipment records rather than staff copying numbers into several separate systems. Self-Service Tracking Page The frontend tracking experience lets a customer look up tracking information using supported order-identification details. Logged-in customers can see order-related tracking through My Account, while the public form validates the supplied order data before showing sensitive order context. The output intentionally limits customer information rather than exposing a full order record to anyone who guesses an order number. A shortcode is registered for the tracking form: [kitgenix_tracking_form] Tracking Analytics The plugin includes an admin analytics area for reviewing shipment/tracking activity. Reporting is based on the tracking data stored with WooCommerce orders; it is not a remote courier analytics product and does not profile visitors across websites. Optional Route Map Where enabled by the frontend template/settings, the tracking page can display a simple map between the store origin and customer destination. The browser uses the bundled Leaflet library with OpenStreetMap map tiles and can query the public Nominatim geocoding service to translate the displayed addresses into coordinates. The map is illustrative. The code draws a straight line between geocoded points; it is not a live courier route, vehicle location or turn-by-turn delivery route. No Google Maps API key is required by this implementation. Bulk Portability The plugin includes import/export functionality for tracking records so stores can move or update shipment information in bulk rather than editing every order manually. Administrators should test bulk imports on a staging copy first when mapping external fulfilment data, especially when orders can have multiple shipments or item allocations. Privacy and Data Shipment records are stored with WooCommerce orders. The plugin does not send tracking records to a Kitgenix tracking service. Clicking a courier link takes the customer to that carrier's own website, which then operates under the carrier's own privacy terms. If the optional route map is used, address text is sent from the customer's browser to the configured Nominatim endpoint for geocoding and map tiles are requested from OpenStreetMap infrastructure. Those services are documented in External Services below. What This Plugin Does Not Do

• It does not buy or print shipping labels.
• It does not book courier collections.
• It does not pull live tracking scans from carrier APIs.
• It does not automatically know when a parcel is delivered unless another user/integration updates the status.
• It does not replace a warehouse management or fulfilment platform.

Typical Uses

• WooCommerce stores that dispatch with several different couriers.
• Orders split into multiple parcels.
• Partial shipments where customers need to know which items have left.
• Support teams that want tracking visible in the order instead of private notes.
• Stores that want a branded self-service tracking lookup without a hosted Kitgenix account.

2.0.0 (31 August 2026)

• New: Redesigned the entire admin experience around the shared Kitgenix design system – a sticky topbar with an Analytics dropdown menu, live settings search, dark/light theme toggle, and mobile hamburger menu replaces the previous page header and tab strip.
• New: Added a redesigned central Kitgenix Hub page for discovering, installing, activating, and reviewing every Kitgenix plugin from one screen, including the new Image Optimizer plugin.
• Improved: Rebuilt the Analytics, Carriers, Bulk Tools, Support, and Log tabs around a consistent set of cards, toggle switches, colour-coded status badges, empty states, and a drag-and-drop CSV upload zone, replacing the previous form tables and plain links.
• Improved: The Tracking Analytics stat-tile grid – including orders in range, time-to-ship, lookups, and other metrics – now uses a fixed four-column layout on wider screens, with responsive fallbacks to two columns and then one column on smaller displays.
• Improved: The "Add tracking" modal on the WooCommerce order edit screen and the custom carrier edit modal now share a common accessible modal component with proper focus handling, Escape-to-close support, and accessible labelling.
• Improved: Custom carrier rows now use compact icon-only edit and delete action buttons with colour-coded enabled/disabled badges instead of plain text links.
• Improved: The Log tab now displays entries in a searchable, paginated table containing time, context, outcome, and a plain-English note instead of a plain text block.
• Improved: CSV bulk import failures now record the specific underlying reason – including unreadable files, files that cannot be opened, missing or invalid headers, and unexpected processing errors – in the Log tab alongside the existing on-screen message.
• Improved: Added a reference table to the Log tab explaining what each recorded category means and whether administrator action is required.
• Improved: The Support tab is now three focused cards – a donate card with a collapsible monthly-amount picker, a "what your support funds" summary, and a "get involved" panel for reviews and plugin links – replacing the previous stack of donate, trust, and community cards.
• Improved: Moved the Log tab directly before Support in the admin navigation for a more logical workflow.
• Improved: Refreshed the Kitgenix logo and favicon assets used throughout the admin menu icon, Kitgenix Hub header, and Analytics header.
• Fix: The "Follow Us" social links no longer appear twice on the Support tab, removing the previous duplication between the inline social block and sidebar.
• Fix: The "Shipments over time" sparkline no longer displays a bold solid line when there is no shipment data. Empty charts now render a thinner, muted baseline so the absence of data cannot be mistaken for a genuine flat trend.
• Fix: Number inputs across the Analytics and settings screens are no longer cramped to a fixed 50px width.
• Dev: Added a shared kitgenix-admin-components.js controller providing modal open/close handling, toast notifications, collapsible cards, copy-to-clipboard controls, and live table search. Both admin-analytics.js and admin-order-tracking.js now use the shared component controller.
• Dev: Three previously silent internal errors – Analytics date parsing, tracking-count lookups, and HPOS order-screen detection – are now recorded in the Log tab for easier diagnostics while remaining non-blocking and preserving existing behaviour.