Advance Partial Shipment for WooCommerce

1. Overview

Advance Partial Shipment for WooCommerce lets you ship one WooCommerce order in several parcels. For each parcel you choose which items and how many of each, then record a provider, a tracking number, a status, dates and notes. The original order is never split or edited. The plugin keeps track of what has shipped, what is left, and tells the customer.

It is for shops that often cannot send a whole order in one go: backorders, made-to-order items, stock in several places, or orders that are too big for one parcel. The owner works in a box on the order screen. The customer sees the parcels, with a four-step timeline, on their order page, and can look a parcel up by tracking number on a page you publish with a shortcode.

The plugin is listed on the Plugins screen as "Advance Partial Shipment for WooCommerce". This page describes version 3.4.0.

How it works

1. On every order edit screen a Partial Shipment box appears in the sidebar, below Order actions.
2. You add a shipment: pick a provider, type the tracking number, set the quantity of each item and save. The quantities you can enter never exceed what is still unshipped (ordered minus refunded minus already shipped).
3. The plugin recalculates the order status. With the defaults, a partly shipped order becomes Partially Shipped and a fully shipped one becomes Completed.
4. The customer gets a New Partial Shipment email with the items, the provider, the tracking link and a QR code. Later changes to the parcel can send a Partial Shipment Update email.
5. You move each parcel through Ready, Picked, Dispatched and Delivered with one click. The customer's timeline follows.

At a glance

How the three plugins fit together

Three WpExperts Hub plugins work with the same shipment data. Each of the three documentation pages carries this same section, so you can read it on whichever page you start from.

Shared data

The free plugin and Advance keep their records in the same two database tables, partial_shipment and partial_shipment_items (each with your WordPress table prefix, for example wp_partial_shipment). They also share the order status wc-partial-shipped ("Partially Shipped"), the WooCommerce settings tab wxp_partial_shipping_settings (shown as Partial Shipment) and three option keys: partially_shipped_status, partially_auto_complete and partially_enable_status_popup. A value you save with one of the two plugins is the value the other one reads.

Only one of the free plugin and Advance runs at a time

If both are active, the free plugin does nothing. When its file loads, the free plugin checks whether Advance (wphub-partial-shipment/wphub-partial-shipment.php) is active, on the current site or network-wide. If it is, the free plugin registers none of its screens, settings or hooks. Advance also switches the free plugin off. On the next request to wp-admin it silently deactivates wc-partial-shipment/woocommerce-partial-shipment.php and shows a one-time notice. On multisite, WordPress 7.1.2 deactivates it this way only when it is network-activated. A copy that is activated on a single site stays active but idle, and Advance still shows its "was deactivated" notice on each wp-admin page of that site until you deactivate the free plugin yourself. Neither step deletes shipment data. Deactivating Advance later does not switch the free plugin back on; activate it yourself on the Plugins screen.

Switching between the two

From the free plugin to Advance. Activate Advance. It keeps the existing rows, so every order the free plugin recorded now has one parcel, Shipment #1, with no provider and no tracking number. The free plugin stores no shipment status, so that parcel shows as Ready (as "Ordered" on the customer's order page) until you change it. On activation Advance also changes the tables: it removes the unique key on order_id so an order can have several parcels, removes the old shipment_primary_id column and adds the new columns. Advance can also create Delivered parcels for older Completed orders in the background; that one-time run is on by default in Advance.

From Advance back to the free plugin. Deactivate Advance, then activate the free plugin. It adds up each item's quantity over all parcels and shows that total in its Shipment popup and badges. It ignores tracking numbers, providers, statuses and notes, and leaves them in the table. When you save new quantities in the free plugin's popup, the difference is applied to the order's first parcel. When a total is lowered, the most recent parcels are reduced first.

What the add-on needs

The add-on works only together with Advance and WP All Import. It does not work with the free plugin, because it creates and updates parcels through Advance, and the free plugin has no parcels, tracking numbers or statuses. The add-on names Advance in its Requires Plugins header, so WordPress 7.1.2 refuses to activate it while Advance is missing or inactive. An add-on that is already active switches itself off on the next request to wp-admin and shows a notice.

What it does not do

• It never contacts a carrier. It does not check tracking numbers, fetch tracking events or change a status by itself. Statuses change when you click, edit, or use the REST endpoint or an import.
• It does not create shipping labels, shipping rates or pickups.
• It does not split an order into several WooCommerce orders. The order stays whole and the parcels are separate records.
• It does not mark items as shipped when you set an order to Completed by hand. The free plugin does that; Advance does not.
• It does not add "Partially Shipped" to WooCommerce's list of paid statuses. The free plugin does; Advance does not. WooCommerce 11.1.2 grants download access for Completed orders, and for Processing orders only when Grant access to downloadable products after payment is on. Advance changes none of this.
• It makes no PDF files itself. Packing slips and delivery notes need the free PDF Invoice for WooCommerce plugin.
• It registers no privacy exporter or eraser for personal data tools (see Privacy).
• Nothing in its code reads or writes the separate order fulfilments feature that ships with WooCommerce 11.1.2.

2. Requirements

3. Installation

1. Download the plugin zip from your account on wpexpertshub.com.
2. In WordPress open Plugins → Add New Plugin → Upload Plugin, choose the zip file, click Install Now and then Activate.
3. Open Plugins → WpExperts Hub Licences, paste your licence key and click Activate licence. This is optional for using the plugin and needed for updates. See Licence and updates.
4. Open WooCommerce → Settings → Partial Shipment and check the settings. A Settings link is also shown under the plugin name on the Plugins screen.
5. Open any order that has physical items. The Partial Shipment box is in the sidebar.

Licence and updates

The plugin bundles the WpExperts Hub licence and update client (licence/class-wpxh-licence-client.php, version 2.0.0). It works as follows.

• The screen. Plugins → WpExperts Hub Licences lists every WpExperts Hub plugin that bundles this client on your site, one card each, with an Active or Not active label and the installed version. You need manage_options to open it. Advance's own link under the plugin name on the Plugins screen reads Activate License or Deactivate License and opens the same screen.
• Activate. Paste the key from your purchase email (also shown in My Account → Downloads on wpexpertshub.com) and click Activate licence. Only letters, digits and hyphens are kept; anything else you type is dropped. The key and an "active" status are stored on your site only when the licence server says yes.
• Deactivate. Click Deactivate licence on the card (the key is shown masked, for example the first four and last four characters). Do this before you move the plugin to another live site. The key is removed from your site even when the licence server cannot be reached, so the site is never stuck.
• Lost your key. On a card without an active licence, open Can't find your key? Email it to me, enter the email address used for the purchase and click Send licence key. The server sends the email.
• Updates. New versions arrive through the normal Dashboard → Updates and Plugins screens. The update information is requested from the licence server in one batched request and cached for 12 hours (one hour after a failed request). The client installs whatever package address the server returns. According to the client's own documentation, the server returns an address only for sites with an active licence. Without one, WordPress shows "Automatic update is unavailable for this plugin. Activate your licence to enable updates."
• The plugin works without a licence. No feature of the plugin checks the licence. Its status is read only by the licence client itself (the screen, the reminder and the update requests) and by the link text under the plugin name. The key only unlocks update packages.
• Reminder. On the Plugins screen, administrators see a notice, "Activate your WpExperts Hub licence to receive updates for: ...", while any plugin using the client has no active licence. It has a Manage licences link and cannot be dismissed.

What is sent to wpexpertshub.com, and when, is listed in Privacy.

What activation creates

• Two database tables, partial_shipment and partial_shipment_items (with your table prefix), created only if missing and then brought up to date. See Database tables.
• Two options: wphub_partial_shipment_db_version (the schema number, currently 3) and wphub_partial_shipment_activated (the activation time, written once).
• No roles, no pages and no capabilities. No cron event until you choose a data retention period. No background job until the first backfill run starts.

Upgrading from the free plugin

If the free Partial Shipment for WooCommerce is active, Advance deactivates it on the first request to wp-admin and keeps its data. The rules, and what the existing records look like afterwards, are in How the three plugins fit together. The three options the two plugins share keep their values. The settings screen is the same tab (WooCommerce → Settings → Partial Shipment) with more cards.

Updating

Update through the normal WordPress screens. On the first request after an update (any request, including REST and cron, not only wp-admin) the plugin compares the stored schema number with the schema number it expects (currently 3) and runs the table upgrade steps when they differ. Schema 2 added the delivered_date column (version 3.2.1). Schema 3 made the order_id index non-unique for tables first created by the free plugin (version 3.3.0). Your settings and shipments are kept. Licence activations made with the older licence client are kept, because the new client reads the same option names.

Multisite

The plugin can be activated on one site or network-wide. The tables use the table prefix of each site, so every site has its own shipments, and each site creates its tables on its first request after activation (the schema check runs on init). Settings and the licence are stored per site. The licence screen is added to a site's admin Plugins menu; the client adds nothing to the network admin. On multisite WordPress 7.1.2 deactivates the free plugin on behalf of Advance only when the free plugin is network-activated (see How the three plugins fit together).

Deactivating and deleting

Deactivating removes the daily retention cron event and the pending background backfill actions. All shipments, options and tables stay. Advance has no uninstall routine, so deleting the plugin from the Plugins screen removes only its files. The tables, the options listed under Options and the licence options stay in your database until you remove them yourself. Back up first if you do.

4. Quick start

1. Install and activate Advance. Optionally activate your licence under Plugins → WpExperts Hub Licences.
2. Open WooCommerce → Settings → Partial Shipment. Check Shipment Email Trigger (default: email at once when a shipment is created) and the other defaults. Click Save changes.
3. Optional: under Shipping Providers add your own carriers, one per line, as Name|https://example.com/track/%1$s.
4. Open an order. In the Partial Shipment box, under Add a Shipment, choose a provider, type the tracking number, adjust the quantities and click Save Shipment.
5. Use Mark Picked, Mark Dispatched and Mark Delivered on the shipment as it moves along.
6. Check the emails under WooCommerce → Settings → Emails (New Partial Shipment and Partial Shipment Update).
7. Optional: create a page with the shortcode [wphub_shipment_tracking] so customers can look up a parcel by tracking number.

5. Features

Where a feature depends on WordPress or WooCommerce code, this page says so and names the version that was checked (WordPress 7.1.2 and WooCommerce 11.1.2).

The Partial Shipment box

Open any order at WooCommerce → Orders. In the right-hand column, directly below Order actions, is the Partial Shipment box. The plugin keeps it in that position even if you have rearranged the boxes before. The box appears on both the High-Performance Order Storage screen and the legacy order screen. Only users with edit_others_shop_orders see its contents.

• A new order that has not been saved yet shows "Save the order first, then add its shipments here."
• No shipments yet shows "No shipments yet — add one below."
• Shipment history lists every shipment, oldest first, under a progress line such as "3 of 5 items shipped" with a bar. The numbers are physical units, net of refunds.
• Each shipment shows its number ("Shipment #2"), a status badge and these buttons: Packing Slip and Delivery Note (only when the PDF Invoice for WooCommerce plugin is usable), Edit and Delete. Below are the shipment date, the provider and the tracking number (a link when a tracking link can be built), the estimated delivery date when set, the three Mark buttons, the customer note and the internal note when they exist, and the list of items with quantities.
• Add a Shipment is the form at the bottom. When the order status is Pending payment, Cancelled, Refunded or Failed it is replaced by "Shipments cannot be added while the order is "Pending payment"." (with the real status name). Existing shipments on such an order can still be edited and deleted.

Everything in the box works without reloading the page. After each action the box redraws itself, WooCommerce's order items table above reloads (so the shipment badges update) and the order status field in the Order details box changes to the status the plugin has just set. A line under the box shows the result, for example "Shipment added successfully." or "Something went wrong.". When the plugin had to reduce your quantities it adds "(quantities reduced to what is available)". Pressing Enter inside a form field saves that form.

Adding a shipment

Click Ship all items to fill every box with its maximum, then Save Shipment. The two buttons are hidden when nothing is left to ship ("No shippable items left for this order.").

Each shipment gets a visible number: the highest number already used on the order plus one. Deleting the newest shipment frees its number for the next one. Numbers are never renumbered.

Editing and deleting a shipment

Edit opens the form "Edit shipment #N" in place of the shipment. It has the same fields as the Add form. Each item box goes from 0 to what this shipment already holds plus what is still unshipped on the order, and shows "current of maximum". Click Update to save or Cancel to close the form.

• The provider list preselects the stored provider. When the stored link matches no provider in the list (for example a custom link), Other… is preselected and the link is shown in the box.
• Unlike the Add form, an edit does not insist on a tracking number.
• Setting every item to 0 is refused: "A shipment needs at least one item. Delete the shipment instead." If none of the items you entered has anything left, you see "None of those items has any quantity left to ship."
• The shipment date field carries only a day. Saving the same day again keeps the time of day the shipment already had.
• On success: "Shipment updated successfully."
• Which edits email the customer is explained under Customer emails.

Delete asks "Delete this shipment? This cannot be undone." and then removes the shipment and its item rows ("Shipment deleted successfully."). The order status is recalculated. The webhook, if configured, receives a deleted event.

Shipment statuses

Every shipment has one of four statuses. The names differ slightly between what you see and what the customer sees.

To change a status in one click, use Mark Picked, Mark Dispatched or Mark Delivered in the shipment. The status the shipment already has is shown as a plain label instead of a button. There is no Mark Ready button; to move a shipment back to Ready use Edit and change Status. The Mark buttons report "Shipment status updated." or "Invalid shipment or status." They change only the status and its delivery date. They do not change the order status, because no quantity changes.

A shipment that was added with the status Delivered selected in the form, or created by the one-time background run, has no delivered_date. The customer then sees its shipment date as the delivery date.

Tracking numbers, providers and tracking links

A shipment stores two things: the tracking number, and a tracking URL template. Choosing a provider stores that provider's URL template. The provider's name is not stored separately. Wherever the name is shown (the box, emails, the customer page, the REST read response, webhooks), the plugin finds it by comparing the stored URL with its provider lists, first for the order's country and then for every country and your custom providers. If you later change or delete a custom provider, older shipments that used it keep their link but lose the name: they show the tracking number with its link, without a provider line.

A tracking link is the template with %1$s (or %s) replaced by the tracking number, URL-encoded. A template without a placeholder is used as it is. A template with a placeholder but an empty tracking number gives no link.

Built-in providers

The built-in directory has 58 providers for 20 countries. The list offered on an order is the one for the order's shipping country, or its billing country when there is no shipping country. Orders for any other country get only your custom providers.

The tracking addresses in this list are fixed in the plugin. Carriers change their tracking pages from time to time; if one stops working, add a corrected provider with the same name under Custom Providers. A custom provider with the same name as a built-in one replaces it. Developers can change the whole list with the wphub_shipment_tracking_providers filter.

Your own providers

Under WooCommerce → Settings → Partial Shipment → Shipping Providers, type one provider per line as Provider Name|Tracking URL, for example My Courier|https://example.com/track/%1$s. Custom providers appear on every order, whatever the country. When you save, a line without a name, without the pipe or without an address starting with http:// or https:// is dropped and a notice says how many lines were ignored.

Quantities, refunds and virtual items

• Net quantity. For each order line, the quantity that can ship is the ordered quantity minus the refunded quantity. What is still available is that number minus what other shipments of the order already hold.
• Virtual items. A line whose product is virtual is never shipped, never counted in the progress line, in the order status calculation or in the Fulfillment Report, and never shown on the customer's shipment cards. A line whose product was deleted after the order was placed still counts as a physical item.
• Over-shipping is prevented. Creating or editing a shipment first takes a lock for the order. Two people (or an import and a person) shipping the same order at the same moment can neither ship more than was ordered nor receive the same shipment number.
• Refunds after shipping. After a refund the shipped total is capped at the net quantity. When a refund removes the units that were still waiting to ship, the plugin re-checks the order and, with the defaults, completes it.

Order status automation

With the plugin active, the order status follows the shipments. The plugin recalculates after every shipment is added, edited or deleted, after the bulk action and the backfill, and after a refund on an order that already has a shipment. It does not recalculate after a Mark button, after the daily data retention clean-up, or after a refund on an order with no shipments.

Each change adds an order note that starts with "Order Partially Shipped by advance partial shipment.", "Order marked auto Completed by advance partial shipment." or "Order Processing by advance partial shipment.", followed by WooCommerce's usual "Order status changed from ... to ...". Because the plugin only moves an order to a status that exists, switching Add Status "Partially Shipped" off never turns orders into "Pending payment".

Item badges

Each physical item gets a badge that tells how much of it has shipped. Virtual items get none. You can change the four labels under Status Labels (see Settings).

Badges compare the shipped quantity with the quantity ordered. They do not subtract a partial refund, so an item with 3 ordered, 1 refunded and 2 shipped shows "Partially Shipped: 2" even though nothing more is owed. The order status calculation does use the net quantity.

• On the order screen a Shipment column is added to WooCommerce's order items table, with the badge ("Shipped: 2") on every product line.
• In the order preview popup on the Orders list, a Status column shows a coloured badge with the shipped quantity (the label is in its tooltip). This is controlled by Display status in order popup.
• On the Orders list a Shipment column follows Status. It shows one badge for the whole order (Not Shipped, Partially Shipped, Shipped or Refunded) calculated from the sum of the physical quantities, or a dash when the order has no physical items.
• For customers the badges appear next to each item on their order page, only after the order has at least one shipment. See What customers see.

Bulk action: Create shipment for all items

On the Orders list, tick orders, open Bulk actions, choose Create shipment for all items and click Apply. For each selected order that is not Pending payment, Cancelled, Refunded or Failed and still has something to ship, the plugin creates one shipment holding every remaining physical item. A notice then says "1 shipment created." or "N shipments created.".

Mark existing orders as shipped

This tool creates a Delivered shipment for every unshipped physical item on orders with the statuses you choose. It is meant for orders that were shipped before you installed the plugin. It is silent: no customer email and no webhook. It does run the order status calculation, so an order in a status you selected can be moved (for example Processing to Completed when automatic completion is on, which makes WooCommerce send its usual email).

• Automatic run (on by default). On the first wp-admin page load after activation, the plugin schedules one background run for orders created before the activation time, using the selected statuses (Completed unless you choose others). A site that upgrades from an older Advance version, which has no recorded activation time, treats the time of the first admin page load after the upgrade as the activation time. The run finishes once and is not repeated, unless you change Automatic run or Order statuses and save, which arms it again. The first time you save this screen counts as a change, because the statuses list is stored then for the first time. It is safe to repeat: it only covers quantities that no shipment holds yet.
• Run now. Mark orders as shipped now starts a run for orders of any date, using the statuses currently selected in the box above it, even if you have not saved them. If a run is already in progress you see "A backfill is already running. It will continue in the background."
• How it runs. Through WooCommerce's Action Scheduler (group wphub-partial-shipment, hook wphub_partial_shipment_backfill_worker), 25 orders per batch with a 30-second pause between batches. Progress is shown under the button: "Running in the background — N order(s) processed so far." and later "Done. Marked N order(s) shipped and created N shipment(s)." You can watch the queue under Tools → Scheduled Actions.
• It adds, it does not duplicate. Only the remaining quantity of each item is shipped. Orders that are fully shipped get nothing.

Customer emails

Advance adds two customer emails to WooCommerce. Both go to the order's billing email address, are enabled by default, and can be edited, disabled or switched between HTML, plain text and multipart under WooCommerce → Settings → Emails. The settings screen shows each email's state with a Manage email button.

What is in the email

A greeting with the billing first name, a sentence such as "Just to let you know — we've partially shipped your order #123, and it is now being processed:" (or "we've shipped your order" when the order is Completed; the update email says "we've made some modification in your partially shipped order"), a heading with the order number and date, a table of the shipment's items (product name, the SKU in brackets when there is one, and the quantity), a table with the provider, the tracking number and the tracking link, the customer note when there is one, and a "Track your shipment" block with a "View live tracking →" link and a QR code of the tracking link. When no tracking link can be built the block links to the customer's order page ("View your order →") instead. WooCommerce's usual order-meta and customer-details blocks and the email's "Additional content" follow.

The plain-text version has the same shipment information as text (the tracking link on a "Track your shipment:" line) and no QR code. It also lists the order's totals (the rows WooCommerce builds for an order, such as subtotal, shipping, payment method and total) and the customer's order note. The QR code in the HTML email is an image loaded by the customer's email program from https://api.qrserver.com, a third-party service, with the tracking link in the address. The wphub_shipment_email_qr_url filter changes the image address; return an empty string to leave the QR code out.

When an email is sent

The setting Shipment Email Trigger decides. Shipments created or changed silently never send an email. The background backfill and an import set to "Never send emails" are silent. The box, the bulk action and the REST endpoint are not.

Each shipment records that its New email was triggered (email_sent), even when the email is disabled or the order has no billing address, so the Picked rule fires only once.

What customers see

On My Account → Orders → View, below the order details table, each shipment appears as a card, oldest first:

• A title "Shipment #N" with the shipment date and time, and a status badge (Ordered, Picked, Out for delivery or Delivered).
• "Delivered" with a date for delivered shipments (the delivery date, or the shipment date when none was recorded), or "Expected Delivery" with the estimated delivery date for the others, when one is set.
• A four-step timeline: Ordered, Picked, Out for delivery, Delivered. Steps already passed are marked done and the current one is highlighted.
• The provider and the tracking number as a link to the carrier. When the provider is not recognised, the tracking number and, if a link can be built, a "Tracking URL" line.
• A table of the items in the shipment (Product, Qty), without virtual items, and the customer note when there is one.

Next to each physical item in the order's item list, once the order has at least one shipment, the customer also sees the item badge with your labels (for example "Shipped: 2"). The plugin adds this on pages where the item list is shown through WooCommerce's order details template and the page is a WordPress page, which includes the View order page, the order received page and the pay-for-order page. The front-end stylesheet loads only on My Account and order-received pages (and wherever the tracking shortcode is used). The internal note is never shown to customers. Customers can follow a parcel without logging in only through the tracking page below.

The tracking page: [wphub_shipment_tracking]

Create a page, add a Shortcode block with [wphub_shipment_tracking] and publish it. Visitors type a tracking number and see the matching shipment as the same card that appears on the order page.

• The form. A box labelled "Track a shipment by tracking number" (hint "e.g. ZXZ123456789") and a Track button. It sends a normal form post to the same page and needs no login and no nonce, so cached pages work.
• Matching. The number must match a stored tracking number exactly. The final match is case-sensitive, so type it exactly as in the email.
• A number used on several orders. The visitor sees "This tracking number is used on more than one order. Please also enter your order number." and an Order number box appears. The order number (or the order ID) must match one of the orders. This stops one customer seeing another customer's order.
• One order. When the number belongs to one order and no order number was typed, that order's matching shipment is shown.
• Rate limit. By default 20 lookups per visitor address per 10 minutes. Over the limit the visitor sees "Too many lookups. Please wait a few minutes and try again." until 10 minutes after the last counted lookup. Developers change it with the wphub_tracking_rate_limit filter (see Filters).
• Messages. "Please enter a tracking number.", "No shipment found for that tracking number." and "No shipments found for this order."
• Attribute order_id. [wphub_shipment_tracking order_id="123"] shows every shipment of that order under the form when the page loads, before any lookup. The page is public, so use this only where showing that order to every visitor is intended.

The page shows items, quantities, provider, tracking number, dates and the customer note of the matching shipment. It does not show the customer's name or address.

Packing slips and delivery notes

When the free PDF Invoice for WooCommerce plugin is active, each shipment in the box has Packing Slip and Delivery Note buttons. Each opens a PDF for that shipment in a new tab (the file name is, for example, packing-slip-1234-56.pdf: the order number and the shipment's database id). Your company details, logo and footer note come from the PDF Invoice settings.

• Packing Slip. Bill to and ship to, order number and date, a shipment information bar (shipment number, shipment date, provider and tracking number, only those that exist), a table of this shipment's items (number, item name with SKU and item options, quantity), and the order's shipping method and payment method.
• Delivery Note. Ship to and bill to, the same shipment information bar, a table of all physical lines of the order with Ordered, Prev. Shipped (earlier shipments of the order), This Note and Remaining (net of refunds), and a box with the customer note.
• The links need edit_others_shop_orders and a valid security token. If something is missing you see "The PDF Invoice for WooCommerce plugin is required to print packing slips and delivery notes. Please install and activate it." or "Shipment not found for this order."
• A theme can override the two layouts (see Templates).

Fulfillment Report

Open WooCommerce → Fulfillment Report (needs manage_woocommerce; switch it off under Enable Fulfillment Report). It shows how your orders are being fulfilled in a date window.

• Filters. Status (All statuses or one order status), From, To and Order ID, with Apply and Reset. With no dates the window is the last 30 days up to today, in your site's time zone and in whole days. A reversed range is swapped and impossible dates are ignored. All statuses leaves out Cancelled, Refunded, Failed, trashed and draft orders (a developer filter, wphub_report_excluded_statuses, changes this); you can still pick Cancelled, Refunded or Failed one at a time. Trashed and draft orders are not in the Status list.
• Cards. Orders in scope, Complete, Partial, Not shipped, Total shipments, Backlog (unshipped qty), Avg days to first shipment, Avg days to completion, and "At risk (unshipped/partial > 7 days)" with its backlog in units.
• Table. Order (linked, with the customer name), Created, Status, Shipments, Ordered, Shipped, Backlog, State (Complete, Partial or Not shipped), Days since order and Days to first ship, 50 orders per page.
• How it counts. Only physical items count. Backlog is the net quantity (ordered minus refunded) minus what has shipped, never below zero. "Avg days to completion" averages (last shipment date minus order date) over orders whose status is Completed (or the custom statuses "shipped" or "delivered" if you have them) and that have shipments. Orders with nothing physical left to ship and no shipments are left out.
• Limit. The report covers at most the 500 most recent orders of the window and says so ("The report covers the 500 most recent orders of this window. Narrow the date range or the status to see the rest.").
• CSV. Download CSV exports the same filtered orders (up to 500) as wphub-fulfillment-YYYYMMDD-HHMMSS.csv with the columns Order, Customer, Created, Status, Shipments, Ordered, Shipped, Backlog, State, Days since order and Days to first shipment. Customer names that start with a character a spreadsheet could read as a formula (=, +, -, @, tab or carriage return) get a leading apostrophe.

Data retention

Under Data Retention you can have old shipments deleted in the background. The default is Do not delete. With 3 months, 6 months, 1 year or 2 years chosen, a daily job (wphub_partial_shipment_cleanup) deletes shipments whose shipment date is older than 90, 180, 365 or 730 days, up to 200 per run, with their item rows. The first run is about an hour after you save the setting.

REST endpoint

The endpoint lets another system read, create, change, re-stage or delete shipments. It is off by default. Turn on Enable API, open the settings screen to see the API Key, and send the key in the X-WPX-Key header (or as Authorization: Bearer KEY) to the address shown under API Endpoint, /wp-json/wxp-shipment-data/wxp-data/. Regenerate creates a new key and the old one stops working. Parameters, responses and examples are in REST endpoint (reference).

Outgoing webhooks

Enter an address under Outgoing Webhook URL and the plugin posts a signed JSON message whenever a shipment is created, updated or deleted. Click Send a test event to check your receiver; the result is shown as "Test event delivered: your server answered HTTP 200." (or the code your server returned). Delivery is not retried, and addresses on your own network (private or loopback addresses, or ports other than 80, 443 and 8080) are refused by WordPress's safe HTTP function. The payload and the signature check are in Webhook (reference).

Importing shipments with WP All Import

The separate paid add-on, Advance Partial Shipment Extension for WP All Import, imports parcels from a CSV or XML file. It calls the same functions as the box, so the quantity checks, order status automation, emails and webhooks all apply.

6. Settings

All settings are on one screen: WooCommerce → Settings → Partial Shipment. It needs manage_woocommerce. The screen starts with a header card (the plugin name and version, short links to Documentation, Support, the Fulfillment Report when it is enabled, and the licence screen, and a counter of Partially Shipped orders with a "View orders" link), followed by one card per group below. Click Save changes at the bottom to save every card at once. Checkbox settings are shown as switches.

Three of the keys below (partially_shipped_status, partially_auto_complete and partially_enable_status_popup) are shared with the free plugin and keep their values when you switch between the two.

Shipment Status

Controls how and when orders are marked as shipped.

Status Labels

Customises the labels of the item badges. A live Preview row shows the four badges as they are currently saved, with sample numbers (Shipped: 2, Partially Shipped: 1, Not Shipped: 3, and Refunded). Change the wording, save, and the preview follows. The labels are used on the order screen, the Orders list, the order preview, the customer's order page and the preview itself. They do not rename the "Partially Shipped" order status, and the shipment statuses (Ready, Picked, Dispatched, Delivered) are not editable here.

Shipping Providers

Email Settings

Fulfillment Report

Data Retention

API & Webhooks

Mark existing orders as shipped

Settings that live elsewhere

• The two emails are configured under WooCommerce → Settings → Emails: enable or disable, subject, heading, additional content and email type.
• Packing slip and delivery note details (company name, address, logo, footer note) come from the PDF Invoice for WooCommerce plugin's own settings.
• Licence is managed under Plugins → WpExperts Hub Licences.

7. Screens

8. Developer reference

Everything here was taken from the plugin's code (version 3.4.0). Names beginning with wxp_ and wphub_ both occur, because the plugin kept some older names for compatibility.

Shortcodes

The form posts wphub_track_number and, when needed, wphub_track_order. It also prints a nonce field (_wphub_track_nonce, action wphub_tracking_lookup) that the server does not check, so that cached pages keep working.

AJAX and admin-post actions

The AJAX actions are wp_ajax_ only (logged-in users). They all need the capability edit_others_shop_orders and the nonce wphub_oes_nonce, sent in the field nonce. They answer with wp_send_json_success() or wp_send_json_error(). A success reply carries message, html (the redrawn box) and status (the order status without the wc- prefix). wphub_add_shipment and wphub_edit_shipment also return clamped (true when the quantities were reduced).

In the form, the address typed under Other… sits in a box named shipment_url_other. The page script copies it into shipment_url before the request is sent, so the server never needs the second field. The admin-post actions are for logged-in users too (admin-post.php?action=...).

The Orders list bulk action uses the value wphub_create_shipments and redirects back with the query argument wphub_bulk_created (the number created).

REST endpoint (reference)

Route. /wp-json/wxp-shipment-data/wxp-data/ (namespace wxp-shipment-data, route wxp-data). Methods GET and POST. Parameters can be in the query string, a form body or a JSON body.

Authentication. Not a WordPress user. The request must carry the API key, and Enable API must be on. The key is looked for, in this order, in the Authorization: Bearer KEY header, the X-WPX-Key header and the key parameter (the last is kept for old integrations and is not recommended, because addresses end up in server logs). Some servers drop the Authorization header; use X-WPX-Key then.

Parameters

Actions

Creating through the endpoint is not silent: the New Partial Shipment email follows the Shipment Email Trigger setting, the created webhook fires, quantities are reduced to what is available, and the order status is recalculated.

Sample read response

Shipments are keyed by their visible number. Quantities inside items come back as text.

{
  "order-id": 123,
  "shipment": {
    "1": {
      "tracking_url": "https://www3.royalmail.com/track-your-item#/tracking-results/%1$s",
      "tracking_num": "ZXZ123456789",
      "items": { "456": { "name": "T-shirt", "sku": "TSHIRT-RED", "qty": "2" } },
      "id": 45,
      "provider": "Royal Mail",
      "tracking_link": "https://www3.royalmail.com/track-your-item#/tracking-results/ZXZ123456789",
      "status": "dispatched",
      "date": "2026-10-06",
      "eta": "2026-10-09",
      "delivered_date": "",
      "customer_note": ""
    }
  }
}

Examples

# Read
curl -H "X-WPX-Key: YOUR_KEY" "https://example.com/wp-json/wxp-shipment-data/wxp-data/?order-id=123"

# Create a shipment of two T-shirts
curl -X POST -H "X-WPX-Key: YOUR_KEY" -H "Content-Type: application/json" \
  -d '{"order-id":123,"action":"update","tracking_num":"ZXZ123456789","tracking_url":"https://www3.royalmail.com/track-your-item#/tracking-results/%1$s","items":[{"sku":"TSHIRT-RED","qty":2}]}' \
  https://example.com/wp-json/wxp-shipment-data/wxp-data/

# Mark shipment 45 as delivered
curl -X POST -H "X-WPX-Key: YOUR_KEY" -H "Content-Type: application/json" \
  -d '{"order-id":123,"action":"status","shipment-id":45,"shipment_status":"delivered"}' \
  https://example.com/wp-json/wxp-shipment-data/wxp-data/

Webhook (reference)

• Events. created (a shipment was created and was not silent), updated (an edit through the plugin, or a status change through a Mark button, the REST status action or an import), deleted (any deletion, including the data retention clean-up; the message is sent before the row is removed). The background backfill is silent and sends none. Sending a test event is a separate button.
• Request. POST to your address with Content-Type: application/json, the header X-WPHub-Event (the event name) and, when an API key exists, X-WPHub-Signature: sha256=HEX, where HEX is the HMAC-SHA256 of the raw request body using the API key as the secret.
• Sending. Through wp_safe_remote_post() without waiting for the answer (non-blocking). There are no retries and no log. WordPress refuses private and loopback addresses and ports other than 80, 443 and 8080 (a port is also accepted when it is the site's own).

{
  "event": "created",
  "order_id": 123,
  "shipment": {
    "id": 45,
    "shipment_id": 1,
    "tracking": "ZXZ123456789",
    "tracking_url": "https://www3.royalmail.com/track-your-item#/tracking-results/%1$s",
    "date": "1791158400",
    "status": "ready",
    "eta": "2026-10-09",
    "customer_note": "",
    "provider": "Royal Mail",
    "tracking_link": "https://www3.royalmail.com/track-your-item#/tracking-results/ZXZ123456789",
    "delivered_date": ""
  },
  "items": [ { "item_id": 456, "qty": 2 } ],
  "order_total": 59.9,
  "customer_email": "customer@example.com",
  "sent_at": "2026-10-06 09:30:00"
}

date and delivered_date are the stored values (timestamp text, empty when not set). sent_at is the UTC time. The test event has order_id 0, an empty shipment and items, a site field with your home address and a sent_at time, and nothing else.

Verify a message in PHP:

$body     = file_get_contents( 'php://input' );
$expected = 'sha256=' . hash_hmac( 'sha256', $body, $api_key );
$given    = isset( $_SERVER['HTTP_X_WPHUB_SIGNATURE'] ) ? $_SERVER['HTTP_X_WPHUB_SIGNATURE'] : '';
if ( ! hash_equals( $expected, $given ) ) {
    http_response_code( 401 );
    exit;
}

Actions

add_action( 'wphub_partial_shipment_created', function ( $shipment_pk, $order_id ) {
    error_log( "Shipment {$shipment_pk} created for order {$order_id}" );
}, 10, 2 );

// Re-run the status automation for an order.
do_action( 'wphub_partial_shipment_status', 123 );

Filters

// A custom provider on every order.
add_filter( 'wphub_custom_shipment_providers', function ( $providers ) {
    $providers['My Courier'] = 'https://example.com/track/%1$s';
    return $providers;
} );

// Raise the tracking page limit to 60 lookups per 10 minutes.
add_filter( 'wphub_tracking_rate_limit', function () {
    return array( 60, 10 * MINUTE_IN_SECONDS );
} );

// Do not allow new shipments on On hold orders either.
add_filter( 'wphub_partial_shipment_disable_statuses', function ( $statuses ) {
    $statuses['wc-on-hold'] = 'wc-on-hold';
    return $statuses;
} );

// Add a field to the webhook body (the signature follows).
add_filter( 'wphub_partial_shipment_webhook_payload', function ( $payload, $event, $shipment_pk, $order_id ) {
    $payload['site'] = home_url();
    return $payload;
}, 10, 4 );

// No QR code in the shipment email.
add_filter( 'wphub_shipment_email_qr_url', '__return_empty_string' );

Calling the plugin from PHP

The plugin's backend object is available as wphub_partial_shipment()->partial_shipment once WordPress has run init (priority 10). The add-on uses these methods. They are public methods of the plugin's backend class, not a separate API.

add_action( 'init', function () {
    $backend = wphub_partial_shipment()->partial_shipment;
    $created = $backend->create_shipment(
        123,                                              // order id
        'https://example.com/track/%1$s',                 // URL template, or '' for none
        'ZXZ123456789',                                   // tracking number
        array( 456 => 2 ),                                // order item id => quantity
        array( 'shipment_status' => 'picked', 'silent' => true )
    );
}, 20 );

Templates and override paths

The plugin loads its templates with wc_get_template(). In WooCommerce 11.1.2 that looks in the active theme (and child theme) under woocommerce/ first and then directly under the theme root, and uses the plugin's own file when it finds nothing. Copy a file from the plugin's templates folder to the path below.

Database tables

Both tables use your table prefix and the site's character set. They are created with CREATE TABLE IF NOT EXISTS; the extra columns are added by separate upgrade steps. wphub_partial_shipment_db_version holds the schema number (currently 3).

partial_shipment (one row per shipment)

partial_shipment_items (one row per item in a shipment)

The upgrade also removes columns that earlier versions had: shipment_primary_id from the items table (it came from the free plugin) and dispatch_date from the shipments table.

Options, transients, scheduled jobs and constants

The backend class also holds fixed limits as class constants: backfill batch 25 orders, report cap 500 orders, report window 30 days, "at risk" threshold 7 days, 50 report rows per page and 200 shipments per clean-up run.

The plugin sets no cookies and stores no post, user or term meta of its own. It adds no capabilities or roles.

WordPress and WooCommerce hooks the plugin attaches to

Only those that matter if you debug or override behaviour:

File layout

• wphub-partial-shipment.php: plugin header, loader, activation, schema check, free-plugin guard, customer item badges.
• classes/class-wphub-partial-shipment-backend.php: shipment logic, statuses, report, REST endpoint, backfill, providers, tracking shortcode.
• classes/class-wphub-partial-shipment-settings.php: the settings tab. class-wphub-partial-shipment-sql.php: tables and upgrade. class-wphub-partial-shipment-webhook.php: webhooks. class-wphub-partial-shipment-email.php and ...-update-email.php: the two emails.
• includes/order-shipment-meta.php: the Partial Shipment box.
• templates/: customer cards, email templates, packing slip and delivery note.
• assets/: admin.js and admin-settings.js, the admin and front-end stylesheets and the report stylesheet. languages/wphub-partial-shipment.pot: the translation template (text domain wphub-partial-shipment).
• licence/class-wpxh-licence-client.php: the bundled licence and update client.

The classes are found by an autoloader that maps a class name to a file in classes/ (lower case, underscores to hyphens, prefixed with class-). The plugin's own files, the free plugin's guard and the add-on all expect the plugin folder to be named wphub-partial-shipment.

9. Privacy

What is stored and where

• Shipment tables. partial_shipment and partial_shipment_items in your own database hold, per shipment: the order id, item ids and quantities, the tracking number, the tracking address, the shipment, estimated delivery and delivery dates, the status, whether the email was triggered, and the customer note and internal note. The tables hold no customer name, email address or postal address; those stay in the WooCommerce order. The notes are free text that your staff type, so they can contain personal data.
• Options. The settings, the API key (a secret that also signs webhooks), the webhook address, the state of the backfill, queued admin notices and, once activated, the licence key. They are listed in Options, transients, scheduled jobs and constants.
• Who sees what. A customer sees the shipments of their own orders on their account pages and in the emails sent to the billing address. Anyone who has a tracking number (and, when the number is used on several orders, the order number) can see the items, quantities, provider, tracking number, dates and customer note of that shipment on your tracking page. The internal note is shown only in wp-admin.

Cookies

The plugin sets no cookies. The tracking page limits lookups by keeping a short-lived record (a transient named wphub_track_rl_ followed by an MD5 hash of the visitor's IP address) that counts lookups. It lasts for the rate limit window, 10 minutes by default, and each counted lookup restarts the window. The address itself is not stored.

Data sent to other servers

The requests to wpexpertshub.com also carry the standard headers WordPress adds to every HTTP request, including a User-Agent of the form WordPress/7.1.2; https://your-site (WordPress 7.1.2 shown), and are sent over HTTPS with certificate checking on. No order, customer, shipment or visitor data goes to wpexpertshub.com. The plugin sends nothing for analytics and loads no external scripts or fonts. Tracking links in emails and on the order page lead to the carrier's own website.

Retention, deactivation and deletion

• Retention. Shipments stay until you delete them or switch on Delete old shipment data, which deletes by shipment date (see Data retention). The default keeps everything.
• Deactivation removes the daily clean-up event and the pending backfill actions. It deletes no data.
• Deleting the plugin removes the plugin files only. There is no uninstall routine, so the two tables, the options, and the licence options stay in the database. Remove them yourself if you want them gone, after a backup.
• Personal data tools. The plugin registers no exporter and no eraser, and no suggested privacy policy text. The shipment tables are therefore not part of WordPress's personal data export and erase tools. If your staff write personal data in notes, delete or edit those shipments yourself when a request comes in.

For your own privacy policy: tracking numbers and links can reveal that a parcel is on its way to a customer, the shipment emails can load a QR image from api.qrserver.com unless you remove it, and a webhook, if you use one, passes the customer's email address and order total to the address you chose.

10. Troubleshooting

11. FAQ

12. Changelog

Reproduced from the plugin's readme.txt. The 3.0.0 entry mentions bulk printing of packing slips from the Orders list; version 3.4.0 has no such bulk action (its only bulk action is Create shipment for all items; packing slips are printed per shipment). The 3.2.0 entry mentions a "shipment edit page"; the code has the Edit form inside the order's Partial Shipment box and no separate page.

3.4.0 - 2026-10-06

• Fix - Two admins (or an import and an admin) shipping the same order at the same moment could ship more than was ordered or get the same shipment number: creating and editing a shipment is now serialised per order.
• Fix - Fulfillment Report: orders placed on the last day of the date range - today, in the default view - were missing from the report and its CSV export. The range now covers whole days in the site's time zone; reversed or invalid dates are handled.
• Fix - Saving ANY change on the Settings screen re-armed the one-time background backfill, which then marked old completed orders as shipped again. It is re-armed only when the backfill options themselves change.
• Fix - A negative quantity (for example -2) shipped that many units; a non-numeric "qty" value caused a fatal error (HTTP 500); an item that belongs to another order, or a virtual item, could be shipped through the AJAX request.
• Fix - Editing a shipment with every quantity set to 0 reported "updated" while changing nothing; it now asks you to delete the shipment instead.
• Fix - Editing a shipment reset its time of day to midnight (shipment date) and, with the Fulfillment Report, skewed "days to first shipment".
• Fix - Lines whose product was deleted after the order was placed could not be shipped from the order box, bulk action or backfill, but still counted for the order status: such orders stayed "Partially Shipped" forever. They are shippable now.
• Fix - REST API: an "edit" request without tracking_num / tracking_url erased the stored tracking details; new shipments through the API (update / ship_all) are refused for Pending, Cancelled, Refunded and Failed orders, like on the order screen (HTTP 409).
• Fix - With "Mark auto completed" switched off, a fully shipped order stayed "Partially Shipped"; it returns to Processing so you can complete it yourself.
• Fix - "When shipment is marked as Picked": a shipment created already Picked, or set to Picked in the edit form or through the API, never emailed the customer. It now does, once. The "shipment updated" email is no longer sent for edits the customer cannot see (internal note).
• Fix - Upgrading from versions before 3.2.0 dropped the old per-shipment comments; they are now kept as the customer note.
• Fix - Tracking page: a lookup needs no nonce any more (cached pages carried a stale one and the form silently did nothing); a tracking number shared by several orders asks for the order number instead of showing another customer's order; lookups are rate limited.
• New - Settings screen redesigned: sections as cards, live preview of the item labels, API endpoint / key with Copy, "Regenerate" API key, "Send a test event" for the webhook, the backfill "Run now" button uses the statuses currently selected, and a header with shortcuts.
• New - Settings are validated: an invalid webhook URL keeps the previous one, custom provider lines that cannot work are dropped with a notice.
• New - Packing slip and delivery note show the shipment number, date, provider and tracking number; the delivery note gains a "Remaining" column (net of refunds).
• New - Shipment box: "Edit shipment #N" heading, item quantities with "x of N" and a "Ship remaining" shortcut in the edit form, translatable "Items to ship" title, labelled form fields and a status region for screen readers; the report scrolls sideways on phones, shows a notice when it is capped at 500 orders and has right-to-left styles.
• New - The order screen of a brand-new (unsaved) order says to save it first; developers get the wphub_partial_shipment_before_insert action.
• Tweak - Customer pages: right-to-left styles for the shipment cards and timeline, tracking form wraps on narrow screens.

3.3.0 - 2026-09-27

• Security - New licence client: licence data is exchanged as JSON only (the old client unserialized server responses) and a failed server request can no longer cause a fatal error.
• Enhancement - One "Plugins → WpExperts Hub Licences" screen manages the licences of all WpExperts Hub plugins (previously only one plugin's licence page could be opened when several were installed). Existing activations are kept.
• Enhancement - Updates are delivered through the standard WordPress update screen for sites with an active licence; "Email me my key" added.
• Fix – REST API: a request with any key while no API key was stored caused a fatal error (TypeError in hash_equals()), and the read endpoint raised a PHP 8 deprecation.
• Fix – Fulfillment Report CSV export contained the whole admin page HTML before the CSV rows; it is now streamed before any output, nonce-protected and safe against spreadsheet formula injection. The status filter, pagination and CSV link were also reset to the last order's status.
• Fix – Report backlog now ignores refunded units, "All statuses" no longer counts cancelled / refunded / failed orders as backlog, and day calculations use the site timezone.
• Fix – Upgrading from the free plugin: its table had a UNIQUE order key, so a second shipment for the same order could not be saved. The index is migrated automatically (schema 3).
• Fix – When the "Partially Shipped" status was disabled, orders were silently switched to "Pending payment"; the auto-complete setting also blocked the partially-shipped status. Status automation now only uses registered statuses and never touches refunded/cancelled/failed orders.
• Fix – Refunds are taken into account after shipping: refunding the remaining unshipped units completes the order, and refunded units can no longer leave an order "over-shipped".
• Fix – Custom tracking URLs containing "%" (e.g. %20) caused a fatal error in emails, the order box and the customer view; custom providers were missing for countries without built-in providers and for orders without a shipping address; "&" in custom provider URLs was saved as "&".
• Fix – Emails: the plain-text version showed the admin "View order" link to customers and had no tracking details; missing order items caused fatals; refunded quantities were subtracted twice; broken nested table markup; PHP 8.2 dynamic-property deprecation; custom headings from WooCommerce → Emails are now respected.
• Fix – A shipment could be edited through another order ID (AJAX/REST); the "N/A (no provider)" choice could not be saved; bulk "Create shipment for all items" included virtual items and pending/cancelled orders and showed no result notice.
• Fix – Background backfill skipped orders when marking them shipped changed their status; data-retention cleanup no longer moves old orders back to Processing; background jobs are unscheduled on deactivation.
• Fix – Packing slip / delivery note: hardened the PDF Invoice integration (no fatals when it is inactive, order/shipment validated), duplicated customer names, fatals for deleted products, bold/UTF-8 fonts (DejaVu Sans), removed the unused page-number script.
• Fix – Customer timeline showed "ordered" in lower case; shipments saved without a stage now show "Ready".
• Tweak – REST API: new status action, item_id matching, optional status/date/ETA/notes on create/edit, and provider / tracking link / status / dates in the read response. Webhook payload adds provider, tracking link and delivered date, plus a wphub_partial_shipment_webhook_payload filter.
• Tweak – WooCommerce admin assets are no longer re-enqueued on every admin page; the front-end stylesheet only loads on My Account / order-received pages and the tracking shortcode; admin script strings are translatable.
• Tweak – Schema migrations also run outside wp-admin (REST/cron). Requires PHP 7.4+ (was 8.0), tested with WordPress 7.1 and WooCommerce 11.1.

3.2.3 - 2026-09-15

• Fix – The delivered_date column added in 3.2.1 could never actually be created: the migration wrapped its SQL type declaration (varchar(30) NOT NULL DEFAULT '') in esc_sql(), which mangled the literal '' default into invalid SQL and silently failed the ALTER TABLE on every install. As a result, marking any shipment **Delivered** since 3.2.1 has been failing the database update outright (visible as a "Mark Delivered" click that reported success while nothing was actually saved). The column now installs correctly and existing sites self-heal on the next admin page load.
• Fix – set_shipment_status() (used by the "Mark Picked / Dispatched / Delivered" quick actions) always reported success even when the underlying database update failed. It now correctly reports failure so the admin UI shows an error instead of a false "Shipment status updated."
• Fix – The database-migration version check now uses an internal schema-revision number instead of the plugin's marketing version, so a routine version bump can never accidentally cause a pending schema migration to be skipped (or a completed one to be silently marked as done without actually running).

3.2.2 - 2026-09-09

• Fix – The “New Partial Shipment” and “Partial Shipment Update” emails were missing from **WooCommerce → Settings → Emails** because the email classes were registered too late (after WooCommerce had already built its email list). They are now registered during plugin bootstrap, so both emails appear in the mailer and work again without any workaround.

3.2.1 - 2026-08-11

• New – Data Retention under **Settings → Partial Shipment**: automatically delete shipment data older than **3 months / 6 months / 1 year / 2 years** in the background (daily). Default: Do not delete.
• New – **Delivered Date**: shipments marked **Delivered** now show their delivery date on the order view and tracking page instead of hiding the expected-delivery label. The new delivered_date column is added automatically during upgrade.
• Fix – Fulfillment Report: the **Shipments** column (and Total shipments card) now counts distinct shipments instead of their line items, so an order with one multi-item shipment shows 1.
• Fix – Tracking page: searching a tracking number now shows only the matching parcel (not every shipment on the order), and a PHP "Undefined array key" warning was removed.
• Tweak – Tracking page shipment boxes now use the same layout as the order-details page (shared template: status badge, timeline, provider/tracking, items table, customer note).
• Tweak – Shipment database migration now runs once per plugin version instead of on every admin page load.

3.2.0 - 2026-08-10

• New – Editable **Shipment Date** on each shipment (order meta box and shipment edit page).
• New – **Custom Shipping Providers** under **Settings → Partial Shipment → Shipping Providers**: add your own providers ("Name|Tracking URL") that appear in every provider dropdown.
• New – Per-shipment **Comments** field on the Add/Edit shipment forms, shown on the **Delivery Note**, in the shipment emails (HTML + plain), and on the customer's order view.
• Fix – The "Not Shipped" status in the order details now shows the quantity still to be shipped (e.g. "Not Shipped: 5") instead of "Not Shipped: 0".

3.1.1 - 2026-08-08

• New – Optional Fulfillment Report: enable or disable the **WooCommerce → Fulfillment Report** dashboard from **Settings → Partial Shipment → Fulfillment Report**. When disabled, the menu is hidden and the report page is not registered.

3.1.0 - 2026-08-06

• New – Configurable "Shipment Email Trigger" under **Settings → Partial Shipment → Email Settings**: send the notification email immediately when a shipment is created (default) or defer it until the shipment is first marked **Picked**. In deferred mode no email is sent on create/edit, Dispatched/Delivered never email, and each shipment is emailed at most once. Works for both partial and complete shipments.
• Info: new per-shipment email_sent column is added automatically during upgrade (no manual steps).

3.0.1 - 2026-08-05

• Fix – Refund-aware fulfilment: shipped/available quantities are net of refunds, so refunded items are never re-shipped and auto-status uses the net quantity. Fully-refunded items show a "Refunded" label instead of "Not Shipped: 0".
• Fix – "Mark orders as shipped now" no longer gets blocked by a finished backfill run; saving the backfill settings re-arms the one-time auto-backfill with the newly selected statuses; and the date boundary now uses second (not day) precision so same-day pre-activation orders are no longer skipped.
• Tweak – Marked as tested with WooCommerce 11.0.

3.0.0 - 2026-08-02

• New – Per-shipment fulfillment status (Ready/Picked/Dispatched/Delivered) with one-click marking.
• New – Dispatch date and estimated delivery (ETA) per shipment.
• New – Internal & customer-facing notes per shipment.
• New – Outgoing webhooks (created/updated/deleted) with configurable JSON endpoint.
• New – Bulk actions on the Orders list: create shipment for all remaining items & bulk-print packing slips.
• New – Public on-site tracking page via [wphub_shipment_tracking] shortcode.
• New – Shipment progress timeline on the Order view page.
• New – WooCommerce Fulfillment Report dashboard (time-to-ship, time-to-complete, backlog) + CSV export.
• New – Tracking link + QR code added to the shipment (shipped/update) customer emails.
• New – wchub → wphub naming cleanup across the email/notes/settings/DB.
• Info: new per-shipment DB columns shipment_status, shipment_eta, internal_note, customer_note are added automatically during upgrade (no manual steps).

2.6.1 - 03/12/2024

• Fix - Compatibility updates.
• Fix - Order-edit meta box improvements (inline edit/delete, progress, ship-remaining).

2.6 - 02/04/2024

• Fix - Minor tweaks.

2.5 - 12/03/2024

• Fix - Status check before updating.

2.4 - 02/12/2023

• Fix - HPOS compatibility.

2.3 - 20/07/2023

• Fix - Shipment Provider filter updated.

2.2 - 27/06/2023

• Tweak - Disable add shipment for specific order status.

2.1 - 06/06/2023

• Tweak - Fixed date issue on dashboard.

2.0 - 20/03/2023

• Tweak - Compatibility and security updates.

1.9 - 18/01/2023

• Tweak - Code improvement.

1.8 - 22/10/2022

• Tweak - Shipment provider list updated.

1.7 - 16/09/2022

• Tweak - Shipment provider added using a select box.
• Tweak - Code improvement.

1.6 - 02/09/2022

• Tweak - Compatibility and security updates.
• Tweak - Code improvement.

1.5 - 16/08/2022

• Script init fixed.

1.4 - 07/08/2022

• Providers list updated.

1.3 - 29/07/2022

• Shipment hooks added.

1.2 - 15/07/2022

• Shipment providers list added.

1.1 - 27/06/2022

• Email issue fixed and example code added.

1.0 - 21/05/2022

• Initial release.

13. Support

Email support@wpexpertshub.com. Please include:

• Your order ID from wpexpertshub.com.
• The plugin version (3.4.0 on this page), your WordPress and PHP versions, and your WooCommerce version.
• What you did, what you expected, what happened, and the exact message you saw.
• For email problems, the order id and the Shipment Email Trigger setting. For REST or webhook problems, the request you sent (without the API key) and the reply.

There is also a contact form at wpexpertshub.com/contact-us. The plugin's settings screen links to it.