Print Trail for WooCommerce

Click the Installation link on this page.

Yes. Only the lines flagged as fulfilled by Print Trail are sent to Print Trail; you fulfil the rest as usual. The WooCommerce order completes independently of the non-Print Trail part.

Print Trail may split an order across production locations. Each fulfilment ships separately with its own tracking, and the order screen shows a row per fulfilment. Tracking notes are added as each fulfilment dispatches.

At checkout, the order's Print Trail items are sent to Print Trail as a draft. When the order is paid (it moves to Processing or Completed), the plugin confirms the draft. Print Trail then holds the confirmed order for a short countdown before production starts. Until then its items can still change; see the next two questions. An order that is pending payment, on hold, cancelled or refunded is never confirmed. If Print Trail is short of stock when a paid order is confirmed, the order is put on hold with a note naming the shortfall, and confirmation is retried.

Yes, until Print Trail starts production. Make the change on the WooCommerce order screen and click Update.

• Not yet confirmed: the whole order is sent again, including any change to the delivery address.
• Confirmed, not yet in production: changes to Print Trail items are sent: a quantity changed, an item removed or an item added. Print Trail updates the order and rebuilds its fulfilments, so fulfilment numbers can change. The order stays confirmed and its countdown starts again. Print Trail's summary of the change is added as an order note. An address change is not sent once the order is confirmed; make it in Print Trail.
• In production: the order can no longer change. The order note gives Print Trail's reason. Review the order in Print Trail, and cancel it there if it should not ship as it stands.

A partial refund of Print Trail items is sent to Print Trail the same way as an edit, until production starts. A refunded quantity comes off the line, and a fully refunded line is removed. Refunding every Print Trail item cancels the Print Trail order, while the rest of the WooCommerce order carries on. If the order is paid but confirmation was blocked by the line you refunded, the order is confirmed once the refund removes it. Once production has started, the refund cannot change the Print Trail order, and the order note gives Print Trail's reason. A refund that does not touch Print Trail items, such as a shipping refund or a refund of products Print Trail does not fulfil, leaves the Print Trail order alone.

Changing the WooCommerce order to Cancelled or Refunded asks Print Trail to cancel its order. Before production starts, the cancellation is immediate. If Print Trail has already started on the order, the WooCommerce order screen opens a confirmation dialog first, naming the fulfilments involved and what cancelling will and will not undo. You can back out or continue. If you continue, the plugin asks Print Trail to cancel everything it can. Any fulfilment that has already left the warehouse cannot be pulled back, so the order gets a note naming those fulfilments and their status, telling you the items are still on their way. If Print Trail cancels a confirmed order itself, the WooCommerce order is put on hold with a note, so you can refund the customer or re-order the items.

To sell a product on pre-order:

1. Flag the product (or variation) as fulfilled by Print Trail, and check that its Print Trail SKU is matched.
2. Tick "Manage stock?" on the product or variation, so the plugin can open and close sales for you. Without it the product is still labelled as a pre-order, but WooCommerce sells it according to the stock status you set.
3. In Print Trail, put the product on pre-order. You can also set a pre-order limit and a publication date.
4. Within about ten minutes, the product shows as a pre-order in WooCommerce. Its edit screen says so under the Print Trail SKU, and the Products list marks it in the Stock column.

• Product page: "Available for pre-order. Expected release: 1 December 2026." in place of the stock line, with the date in your site's date format.
• Button: "Pre-order" in place of "Add to cart" for simple products, on the product page and on shop pages. Variable products keep "Select options", and the selected variation shows the pre-order stock line.
• Basket and checkout: "Pre-order: expected release 1 December 2026" under the item, in the classic and the block basket and checkout.
• Order emails, the order received page and My Account: the same line under the item. Once Print Trail releases the item, it says "Pre-order: released".

Yes. The in-stock items ship straight away and the pre-order items follow when they are released, each with its own tracking.

The plugin flags the order with the unmatched SKUs and blocks confirmation until it is resolved, so an order is never shipped short.

That's fine. If a product has "Manage stock?" switched off (or stock management is disabled site-wide), the stock sync simply skips it — it never forces stock management on and never writes a quantity. Order fulfilment still works normally. Bear in mind that the shopper is not told about Print Trail stock at any point: WooCommerce's own stock figure is what gates the basket and checkout, so with stock management off a shopper can buy and pay for a product Print Trail has run out of. Print Trail checks its actual stock when the paid order is confirmed; if it is short, the order is placed on hold with a note naming the shortfall, and you decide whether to wait for a restock or refund. Stock sync also only ever writes a product/variation that manages its own stock; a variation whose stock is managed by its parent is left alone so two variations never overwrite the parent's shared quantity.

No. When the plugin registers its webhook, Print Trail returns the secret that signs your webhooks and the plugin saves it. If you think the secret may have been exposed, use "Rotate webhook secret" in the Print Trail Connection section: Print Trail issues a new one, and the old one is still accepted for 4 hours so deliveries already on their way are not refused.

Yes, but an API token only reaches orders created through its own channel. Orders sent under the old channel can no longer be read or updated with the new channel's token, so finish them, or keep the old channel's settings, before you switch.

Yes. The plugin declares HPOS compatibility and uses only the WooCommerce CRUD API for order data.