Advance Partial Shipment Extension for WP All Import

1. Overview

Advance Partial Shipment Extension for WP All Import adds a new item type, Shipment Imports, to WP All Import. With it you import parcels from a CSV or XML file into Advance Partial Shipment for WooCommerce: tracking numbers, providers, statuses, dates, notes and shipped quantities for orders that already exist. You no longer create each shipment by hand.

Each row of your file is one product line of a shipment. Rows with the same Order ID and Tracking Number are grouped into one shipment with several items. The add-on creates and updates the shipments through Advance's own functions, so Advance's quantity checks, order status automation, emails and webhooks apply as they do for shipments created by hand. The import itself never edits your WooCommerce orders or products.

The plugin is listed on the Plugins screen as "Advance Partial Shipment — WP All Import Add-On". This page describes version 1.5.0.

How it works

1. You start a new import in WP All Import, upload your file and choose Shipment Imports as the item type.
2. On the mapping step you drag columns of your file into the boxes of the Advance Partial Shipment Fields section (or type fixed text), and choose the email behaviour and the default status.
3. While the import runs, WP All Import creates a temporary post for each row. The add-on copies the mapped values into a buffer and deletes that post at once, so nothing is left behind.
4. When the last row has been read, the add-on groups the buffered rows into shipments and asks Advance to create them, or to update a shipment that already has the same order and tracking number.
5. The WP All Import log lists every shipment created, updated or skipped, with the reason, and ends with a summary.

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 does not create orders or products. Every Order ID in the file must be an existing WooCommerce order.
• It has no settings screen of its own. Its options live inside WP All Import's mapping step and are saved with each import.
• It does not work with the free Partial Shipment plugin, only with Advance.
• It cannot ship "the whole order" from a single row: every row needs a product (SKU or Order Item ID) and a quantity.
• It cannot delete shipments or remove items that are not in the file from other shipments. It only creates shipments and updates the ones it finds by order and tracking number.
• It does not contact carriers and does not check tracking numbers.
• It does not use WP All Import's other sections for the Shipment type (title, content, images, custom fields). Leave them empty.
• It does not change order statuses itself. Advance does that after each shipment, so an import can move orders to Partially Shipped or Completed.

2. Requirements

The two requirement checks (Advance, WP All Import) run only in wp-admin. WordPress 7.1.2 additionally refuses to activate the add-on while WooCommerce or Advance is missing or inactive, because both are named in its Requires Plugins header and are matched by plugin folder name. If a requirement disappears later, the add-on deactivates itself on the next wp-admin request and shows one of these notices: "Advance Partial Shipment WPAI Add-On requires the Advance Partial Shipment for WooCommerce plugin. The add-on has been deactivated." or "Advance Partial Shipment WPAI Add-On requires WP All Import (Pro recommended). The add-on has been deactivated."

3. Installation

1. Install and activate WooCommerce, Advance Partial Shipment for WooCommerce and WP All Import.
2. Download the add-on zip from your account on wpexpertshub.com, then open Plugins → Add New Plugin → Upload Plugin, choose the zip, click Install Now and Activate.
3. Optional but needed for updates: open Plugins → WpExperts Hub Licences, paste your licence key and click Activate licence. See Licence and updates.
4. In WP All Import start a new import (All Import → New Import) and follow the Quick start.

Licence and updates

The add-on bundles the WpExperts Hub licence and update client (licence/class-wpxh-licence-client.php, version 2.0.0). Advance bundles an identical copy; the two differ only in the text domain of their messages. Whichever plugin loads first defines the client, and it then serves both.

• The screen. Plugins → WpExperts Hub Licences lists every WpExperts Hub plugin that bundles the client, one card each, with an Active or Not active label and the installed version. You need manage_options. The add-on also adds a Licence link under its name on the Plugins 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. 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). Do this before moving the plugin to another live site. The key is removed from your site even when the licence server cannot be reached.
• 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.
• Updates. New versions arrive through the normal Dashboard → Updates and Plugins screens. The update information is requested in one batched request and cached for 12 hours (one hour after a failed request). The client installs whatever package address the licence server returns; according to the client's own documentation it returns one only for sites with an active licence. Without a licence WordPress shows "Automatic update is unavailable for this plugin. Activate your licence to enable updates."
• The add-on works without a licence. No feature of the add-on checks the licence. The key only unlocks update packages.
• Reminder. On the Plugins screen administrators see "Activate your WpExperts Hub licence to receive updates for: ..." with a Manage licences link while any plugin using the client has no active licence. It cannot be dismissed.

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

What activation creates

Nothing. The add-on has no activation routine: no tables, no options, no roles, no scheduled events. It registers a temporary post type, wphub_shipment, every time WordPress loads. Options appear only when you activate a licence, and temporary buffer options appear only while an import is running (see What the add-on stores).

Updating

Update through the normal WordPress screens. The add-on has no upgrade routine. Saved imports keep their mapping, because WP All Import stores it. Imports saved before version 1.4, which only had the old "send emails" checkbox, now follow Advance's Shipment Email Trigger (see Customer emails).

Multisite

The add-on has no multisite-specific code. It writes to the shipment tables of the site it runs on (Advance uses each site's table prefix), and WP All Import runs per site. The licence is stored per site.

Deactivating and deleting

Deactivating removes the "Shipment Imports" type from the list of item types. Shipments already imported stay in Advance. Saved imports keep their stored mapping inside WP All Import. The add-on has no uninstall routine, so deleting it removes only its files; any licence options stay in the database.

4. Quick start

1. Prepare a CSV or XML file with one row per shipped product line: the WooCommerce order ID, the product SKU (or order item ID), the quantity and, normally, a tracking number. Optional columns: provider or tracking URL, status, dates, notes.
2. Open All Import → New Import and upload the file. Under "Create or modify..." choose Shipment Imports from the list of item types.
3. Continue to the step where you drag elements (titled "Drag & Drop" in WP All Import Pro 5.1.0). Open the Advance Partial Shipment Fields section, which starts collapsed, by clicking its header.
4. Drag a column into each box you need, or type a value. Order ID, a product (Product SKU or Order Item ID) and Quantity Shipped are required in practice.
5. At the bottom choose Customer shipment emails (default "Follow the Shipment Email Trigger setting"; choose "Never send emails (silent import)" for historical data) and the Default shipment status (default Ready).
6. Continue through WP All Import's steps. It asks for a unique identifier; the add-on does not read it, so pick any value that differs for every row, for example the order ID with the SKU.
7. Run the import. Read the log: each shipment is listed as created, updated or skipped, and the last line summarises the run.

5. Features

This add-on only prepares data. Everything that happens to a shipment afterwards (quantity limits, order status changes, emails, webhooks) is done by Advance. Where this page describes that, it was checked in Advance 3.4.0.

The Shipment Imports type

The add-on registers a custom post type named wphub_shipment with the label "Shipment Imports". The type is registered with an admin interface but without a menu entry, and WP All Import lists such types among the item types under "Create or modify..." on the first step of a new import.

• Why a separate type. Importing shipments as an Order import would let WP All Import's order engine rewrite the real order (clear line items, reset status). The Shipment type avoids that: WP All Import creates one temporary post of this type per row, the add-on copies the row's data and deletes the post immediately, and the real shipments are created at the end of the import. Orders and products are not touched by the import itself.
• No title needed. The add-on tells WP All Import that this type does not need a title, so you do not have to map one.
• Where the mapping is. On the step where you drag elements, a section named Advance Partial Shipment Fields is added for this type only. It starts collapsed. It has a short "How it works" help box, an example file you can open, the mapping boxes in five groups, and the two import options.
• Previews. WP All Import's preview runs never create shipments. The add-on ignores them and clears whatever they buffered.
• Imports from cron and WP-CLI. They work like imports started in the browser. The add-on's log lines appear in those runs too.

Laying out the file

One row is one product line of one shipment. A shipment with three products takes three rows that share the same Order ID and Tracking Number.

order_id,tracking,provider,status,date,sku,qty
1042,1Z999AA10123456784,UPS,dispatched,2026-10-05,TSHIRT-RED,2
1042,1Z999AA10123456784,UPS,dispatched,2026-10-05,MUG-BLUE,1
1043,RM123456789GB,Royal Mail,delivered,2026-10-04,MUG-BLUE,3

With a CSV like this, map Order ID to {order_id[1]}, Tracking Number to {tracking[1]}, Shipping Provider to {provider[1]}, Shipment Status to {status[1]}, Shipment Date to {date[1]}, Product SKU to {sku[1]} and Quantity Shipped to {qty[1]}. The first two rows become one shipment of two items, the third row a second shipment on another order. XML files work the same way: each record is a row, and values are read from the record's top-level elements.

• Order ID is the WooCommerce order ID, the number in the order's edit address. On a standard WooCommerce site it equals the order number. If a plugin gives your orders other order numbers, use the ID, not that number.
• Which fields are needed. The add-on reads rows only when at least one of Order ID, Tracking Number, Product SKU, Order Item ID or Quantity Shipped is mapped; with none mapped the import creates nothing. For a useful import you need Order ID, a product (SKU or Order Item ID) and Quantity Shipped; Tracking Number is strongly advised.
• Header names. You do not have to rename your columns. A header such as "Tracking Number" is read as trackingnumber by WP All Import and the add-on finds it either way.

How mapped values are read

Every box accepts three kinds of value.

• A column. {Column} or {Column[1]}, which you get by dragging the element from the right-hand panel. The name is matched exactly first, then without regard to case and ignoring everything except letters and digits. If the name is not found but the token has a position, such as {something[3]}, the third value of the row is used. If neither works the value is empty.
• Fixed text. Royal Mail or delivered. Text without braces is used exactly as typed.
• Both mixed. Order {order_id[1]} shipped gives "Order 1042 shipped" (useful for notes).

Quantity Shipped

Whole units. The reader trims spaces (including non-breaking spaces) and accepts: 3, 3.0 (3), 2,5 (decimal comma, rounded to 3), 2.4 (2), 1,200 and 1.200 (thousands separators, 1200), 1 200 (1200). A value with a point or comma followed by exactly three digits is read as a thousands separator, so 2.500 is 2500, not two and a half. Zero, negative, empty and non-numeric values, and anything that rounds to 0 (0.4), skip that row's item and are reported in the log. A quantity larger than what is still unshipped is reduced by Advance to the available amount, without a log message.

Shipment Status

The text is trimmed and compared without regard to case.

Anything else, including an empty cell or an empty box, becomes the Default shipment status chosen at the bottom of the section (Ready unless you change it).

Dates

Shipment Date and Estimated Delivery Date use the same reader. It accepts a Unix timestamp (a number with at least 9 digits, used as it is) or one of these formats, tried in this order: Y-m-d (2026-10-05), d.m.Y (05.10.2026), d/m/Y (05/10/2026), m/d/Y (10/25/2026), d-m-Y (05-10-2026), j.n.Y (5.10.2026), d.m.y (05.10.26) and Y/m/d (2026/10/05). Anything else is tried with PHP's general date reader (for example "October 5, 2026").

• A slash date is read day first: 05/10/2026 is 5 October 2026. Only a date that cannot be day first, such as 10/25/2026, is read month first. If your file uses month-first dates that can be read both ways, convert them to Y-m-d before importing.
• Dates are read at midnight UTC so they show as the same calendar day in the order. The Shipment Date is stored as a timestamp; the Estimated Delivery Date is stored as Y-m-d.
• Empty Shipment Date: a new shipment gets today's date and time; an existing shipment keeps its stored date. A non-empty date the reader cannot understand is replaced by the current time.
• Empty or unreadable Estimated Delivery Date: left empty on a new shipment, and the stored value is kept on an existing one.

Provider and tracking URL

• A Tracking URL wins. It is used as typed (cleaned as a web address). Use %1$s where the tracking number goes.
• Otherwise the Shipping Provider name is looked up, without regard to case, in the providers Advance offers for that order's country, then in the lists of every country, then in your custom providers. The provider's tracking address is stored, which is how Advance shows the provider's name. A web address typed in the provider box is used as it is.
• If the name is not found, the shipment is still created, without a link, and the log says: WARNING: shipping provider "X" is not in the provider list (order #N); add it under Settings → Partial Shipment → Shipping Providers.

Matching orders and products

• The order. The Order ID is turned into a whole number and loaded with WooCommerce. If no such order exists the shipment is skipped (log: "SHIPMENT SKIPPED: order #N not found.").
• The order status. Advance does not allow new shipments on Pending payment, Cancelled, Refunded or Failed orders. The add-on applies the same rule to every group of rows for such an order, including a row that would only update an existing shipment, and skips it with the log line "SHIPMENT SKIPPED: order #N is "Pending payment" - shipments cannot be added to orders with this status."
• The product line. The Order Item ID is tried first: when it is a number and WooCommerce finds an order item with that id, that line is used. WooCommerce 11.1.2 looks the id up across the whole database, not only in this order, so an id from another order, or of a shipping or fee line, is accepted at this point. Advance then drops any line that does not belong to the order or is not a physical product line, and if nothing is left it refuses the shipment without a log line. Otherwise the Product SKU is compared with the SKU of each product line of the order, exactly as typed (case matters, variations use their own SKU), and the first match is used. A row that matches no line is reported ("SHIPMENT ITEM SKIPPED: could not match product for order #N (SKU: X).") and the other rows of the shipment continue.
• Quantity limits. Advance reduces each quantity to what is still unshipped (ordered minus refunded minus other shipments) and ignores virtual items and lines of other orders.

Grouping, creating and updating shipments

Rows are grouped when the import has read all of them, using the Order ID plus the Tracking Number. When there is no tracking number the Shipment Reference is used instead. When there is neither, all rows of that order form one group.

• One shipment per group. The first row of the group supplies the provider, tracking URL, status, dates and notes. The items of all rows are added together: the same product on two rows of one group gets its quantities added, and the log says "NOTICE: order #N lists SKU X more than once in this shipment: the quantities were added up."
• The number stored in the shipment. The tracking number; otherwise the Shipment Reference (it is stored in the shipment's tracking number field); otherwise IMP- followed by the order ID (for example IMP-1042).
• Finding an existing shipment. The add-on looks for a shipment of the same order whose tracking number equals that stored number. It does not matter whether that shipment came from a file or was created by hand. If one is found it is updated; otherwise a new one is created.
• What an update changes. The tracking number and tracking address, the status (see the warning above), the shipment date, estimated delivery date and notes when the cell is not empty, and the item list: the shipment ends up with exactly the items in the file for that group, so an item of that shipment that is missing from the file is removed from it. Quantities are checked against what is still available once the shipment's own quantities are set aside.

• Silent re-imports and Advance versions. With Advance 3.4.0 or later, a re-import set to "Never send emails" updates the shipment in place, so it keeps its number and id. With an earlier Advance version the add-on deletes the shipment and creates it again, which gives it a new number and id and sends a deleted and a created webhook if you use webhooks.
• Status and delivery date. A status of Picked, Dispatched or Delivered is applied to the shipment after it is saved, through Advance's own status change. For Delivered, Advance records the delivery date at that moment, which is the time of the import, not the Shipment Date in your file. The customer sees that date next to "Delivered".

Customer emails and webhooks

The box Customer shipment emails has two choices. The default is Follow the Shipment Email Trigger setting (auto). The other is Never send emails (silent import) (silent). In the default mode the import behaves as if you had created or edited the shipments by hand, following WooCommerce → Settings → Partial Shipment → Shipment Email Trigger of Advance.

• Imports saved before version 1.4 have no value for this box, so they use the default mode. They used to be silent because of an old checkbox that was off. Open each such import and choose "Never send emails (silent import)" if you want to keep importing silently.
• Webhooks. If you use Advance's outgoing webhook, a non-silent new shipment sends created. In silent mode no created event is sent. A shipment whose status is Picked, Dispatched or Delivered still sends an updated event in every mode, because the status is applied as a separate step.

What Advance does after the import

• Order statuses. After each created or updated shipment, even a silent one, Advance recalculates the order status. A fully shipped order can become Completed (and WooCommerce then sends its usual Completed order email), and a partly shipped order Partially Shipped, according to Advance's settings.
• Shipment dates and data retention. If Advance's Delete old shipment data is set, shipments whose Shipment Date is older than the chosen period are deleted by its daily job, including shipments you imported with an old date.
• Quantities. The import cannot ship more than ordered: Advance reduces quantities to what is available.

The import log

The add-on writes one line per event into WP All Import's log, with a time in brackets in front, whether the import runs in the browser, from a cron address or from WP-CLI.

Two cases leave no line. When a group has no usable item, its item lines are logged and the group counts as skipped. When Advance itself refuses a shipment (for example everything on the order is already shipped, or the order's lock could not be taken within 15 seconds), nothing is logged for that group and it is not counted as created, updated or skipped. If the totals do not add up to the number of groups in your file, look for those.

When WP_DEBUG is on, the add-on also writes lines starting with [WPAI Shipment] to the PHP error log.

Large files

• Rows are stored in the database in chunks of 200 rows (one option per chunk), so adding a row touches only the last small chunk. The readme says this makes a file of 8,000 rows take about ten seconds; that figure was not measured for this page.
• Creating the shipments is the last step of the import. It continues if you close the browser tab, and PHP's execution time limit is lifted for it.
• Memory use is kept flat by clearing WordPress's in-memory object cache every 200 groups where WordPress supports it.
• Whatever Advance does for each shipment (the order lock, status calculation, emails and webhooks) still happens one shipment at a time, so a very large import with emails switched on sends one email per shipment.

6. Settings

The add-on has no settings screen under WooCommerce or Settings. Everything it offers is in the Advance Partial Shipment Fields section of WP All Import's mapping step, and is saved with each import (WP All Import keeps it in the import's options under the key wphub_shipment). Every import has its own values. A new import starts with the defaults below.

Each mapping box is a one-row text area named wphub_shipment[key]. It takes a column, fixed text or both (see How mapped values are read). A box left empty means "nothing in the file for this field". The section's help text says Order ID, a product (Product SKU or Order Item ID) and the quantity are required; Order ID and Quantity Shipped carry a red asterisk.

Which shipment

What was shipped

Carrier

Status and dates

Notes

Import behaviour

7. Developer reference

Everything here was taken from the add-on's code (version 1.5.0). The add-on defines no actions or filters of its own, no shortcodes, no REST routes, no AJAX actions and no WP-CLI commands. It adds no capabilities or roles.

WP All Import hooks it uses

What the add-on stores

The buffer options are deleted when the import finishes. They can remain if an import dies half way; the next run of the same import empties that import's buffer when it starts. The add-on creates no tables of its own. It writes shipments into Advance's tables partial_shipment and partial_shipment_items only through Advance's functions, and reads partial_shipment directly in one place: to find an existing shipment by order and tracking number.

What it calls in Advance

The add-on uses Advance's backend object (Wphub_Partial_Shipment::instance()->partial_shipment; when Advance has not built it on this request, the add-on loads the backend class file from the wphub-partial-shipment folder and builds one itself).

It also reads the constant WPHUB_PARTIAL_SHIPMENT_VERSION to decide whether Advance can update silently (3.4.0 or later).

Functions

File layout

• wpai-shipment.php: plugin header, dependency checks, the post type, the registered add-on class, all helper functions and the import hooks.
• template.php: the mapping section printed on the WP All Import step.
• licence/class-wpxh-licence-client.php: the bundled licence and update client. languages/wpai-shipment.pot: the translation template (text domain wpai-shipment).

8. Privacy

What is stored and where

• Shipments. The data of your file ends up in Advance's tables partial_shipment and partial_shipment_items: order id, item ids and quantities, tracking number and address, status, dates and the two notes. See Advance's page for the full list. The notes are free text from your file, so they can contain personal data.
• The mapping. WP All Import stores your mapping and the two options in its own import record. The add-on adds nothing to it except the wphub_shipment settings.
• A temporary copy while an import runs. The rows of the file (order id, tracking number, provider, status, dates, notes, SKU and quantity) are kept in database options named wphub_shipment_import_... until the shipments have been created, and are then deleted. If an import dies half way they can stay until the same import runs again or you delete them.
• The file itself is handled by WP All Import, which keeps uploaded files in its own upload folder according to its settings. The add-on does not store the file.
• Licence options once you activate a licence: the key and its status.

Cookies

The add-on sets no cookies.

Data sent to other servers

The add-on itself makes no outside request except through its bundled licence client. It sends nothing for analytics and loads no external scripts, fonts or images. Customer emails, webhooks and the QR image in shipment emails are Advance's, not the add-on's; they are described on Advance's page, and an import triggers them in the same way as a shipment created by hand (unless you choose "Never send emails (silent import)", which stops the emails; webhooks follow the rules in Customer emails and webhooks).

The requests 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 import data goes to wpexpertshub.com.

Retention, deactivation and deletion

• Imported shipments follow Advance's rules: they stay until you delete them or Advance's Delete old shipment data removes them by shipment date.
• Deactivating or deleting the add-on leaves all imported shipments in place. It has no uninstall routine; only its files are removed, and the licence options stay in the database.
• The add-on registers no personal data exporter or eraser, and no suggested privacy policy text.

9. Troubleshooting

10. FAQ

11. Changelog

Reproduced from the plugin's readme.txt.

1.5.0 - 2026-10-06

• Fix - Large files: collecting the rows of the file was quadratic (4,000 rows took over a minute, 8,000 rows five minutes, and the single option outgrew max_allowed_packet). Rows are now stored in small chunks: 8,000 rows take about ten seconds. The last step of the import also keeps running when the browser tab is closed and does not stop at the web server's time limit.
• Fix - A negative quantity (for example -3) shipped that many units. Zero, negative or non-numeric quantities are now skipped and reported in the log; "2,5" and "1,200" are read as numbers.
• Fix - Fixed text in a mapping box (for example Royal Mail, delivered) was ignored; only a lone {column} worked. Fixed text and text mixed with columns now work, and column names are matched without regard to case, spaces or punctuation.
• Fix - A silent re-import ("Never send emails") deleted and recreated the shipment, giving it a new shipment number. With Advance Partial Shipment 3.4.0 it now updates in place.
• Fix - Orders that are Pending, Cancelled, Refunded or Failed are skipped (as on the order screen) instead of receiving shipments; the log says why.
• Fix - The import log of imports run from cron or WP-CLI contained no shipment messages; they now appear in every kind of run. Rows without an Order ID are reported.
• Tweak - The mapping screen is grouped (which shipment / what was shipped / carrier / status and dates / notes), marks the required fields, explains every box, shows an example file and works on small screens. A repeated product line in one shipment is added up and the log says so.

1.4.1 - 2026-10-05

• Fix – WooCommerce listed the add-on as incompatible with High-Performance Order Storage (HPOS) because it did not declare support. It now declares HPOS compatibility (it only reads orders through the WooCommerce order API).

1.4 - 2026-10-03

• Fix – Customers received no "New Partial Shipment" email from imported shipments: the old "Send customer shipment emails" checkbox was off by default, so every import ran silently. The import now behaves like a shipment created by hand and follows Settings → Partial Shipment → Shipment Email Trigger. The option is now "Customer shipment emails" with "Follow the Shipment Email Trigger setting" (default) or "Never send emails (silent import)". Saved imports that never had the checkbox ticked now send emails too — set them to "Never" to keep importing silently.
• Fix – With the trigger "When shipment is marked as Picked", importing a shipment with status picked never sent the email because the status was written straight into the row; it is now applied as a real transition (email once per shipment).

1.3 - 2026-09-27

• Enhancement - Licence activation and automatic updates (Plugins → WpExperts Hub Licences).
• Fix – The Shipping Provider column was saved with the import but never applied: shipments now get the provider's tracking URL (case-insensitive match on the order country, all countries and custom providers). An explicit Tracking URL column still wins.
• Fix – Estimated delivery dates were stored as timestamps, which the plugin showed as a wrong date (1970) and could not edit; they are now stored as Y-m-d. Unparseable ETAs are left empty instead of becoming "today", and dates are read at midnight so they show the day in the file.
• Fix – Re-importing a file with empty columns wiped the stored date / notes of existing shipments.
• Fix – WP All Import preview runs could create real shipments; they are now ignored.
• Fix – The row buffer used a non-expiring transient (autoloaded, and evictable by object caches in the middle of an import); it now uses a non-autoloaded option.
• Tweak – Only WP All Import (Pro or free) is required; the WooCommerce add-on is optional. Declared plugin dependencies, own text domain, translator comments, readme added.

1.2

• Dedicated "Shipment Imports" type; shipments grouped by order + tracking number.

12. Support

Email support@wpexpertshub.com. Please include:

• Your order ID from wpexpertshub.com.
• The add-on version (1.5.0 on this page), the Advance Partial Shipment version, the WP All Import version, and your WordPress, PHP and WooCommerce versions.
• A small sample of your import file (a few rows, with personal data removed) and a description or screenshot of your mapping.
• The WP All Import log of the run, which shows every skipped row and the reason.
• What you expected and what happened.