Use this guide to print Yuzu documents from Helm WMS. Helm supports single-order printing, batch order printing, auto-print on supported single-order workflows, and 3PL mode for teams that fulfil orders for multiple merchants.

Before you start

Install Yuzu Print Extension in Chrome.
Open Yuzu Print Extension settings and select Helm as the platform.
Create your Yuzu API key and decide which App ID to use. See Create a Yuzu API key and choose an App ID.
Configure where documents should print. See Find printer IDs and set a printer override.
If different document types need different printers, set up tag routing. See Set up tag-based printer routing in Yuzu Print Extension.
If several benches need the same settings, share the extension configuration. See Share Yuzu Print Extension configuration between benches.
Review extension success and error messages. See Understand Yuzu Print Extension notifications.

Supported workflows

Helm workflow	Manual print	Auto-print
Create Shipment (Packing)	Yes	Yes
Speedy Single Print	Yes	Yes
Order Edit/View	Yes	Yes
Batch Order Selection	Yes	No

3PL mode: Yes. Use Set up 3PL mode in Yuzu Print Extension to map each Helm client or merchant name to the right Yuzu App ID and API key.

Custom domains: No. Helm custom domains are not currently supported by the extension. The shared guide Use a custom domain with Yuzu Print Extension applies only to supported platforms.

Choose the right App ID

Use one of these App ID patterns:

Use the source app ID when the order IDs shown in Helm match the source app IDs in Yuzu.
Use the Yuzu org or team ID when the order IDs printed from Helm are unique within that Yuzu team.

If you are not sure which one applies, run one manual test print on a known order before enabling auto-print.

Configure printing for Helm

Open Yuzu Print Extension settings.
Select Helm as the platform.
Enter your API key and App ID.
Choose the printer routing your bench uses:
- Use Static Printer ID to send every document to one printer.
- Use Tag-Based Routing when documents such as Invoice, Gift message, and Sticker should go to different printers.
Save the extension settings.

For detailed printer setup, use Find printer IDs and set a printer override and Set up tag-based printer routing in Yuzu Print Extension.

Print manually from Helm

In Helm, open the workflow your team uses.
For single-order workflows, open or scan the order so the Helm order details are visible.
For Batch Order Selection, select the orders you want to print in the orders list.
Click the Yuzu print button.
Wait for the extension notification or check the print history to confirm the request was sent.

Helm packing workflow with the Yuzu print button beside shipment actions

Helm orders table with selected orders and the Yuzu batch print button

Enable auto-print for Helm

Auto-print is available for these Helm workflows:

Create Shipment (Packing)
Speedy Single Print
Order Edit/View

Batch Order Selection does not support auto-print. Use manual print after selecting orders.

To enable auto-print:

Open Yuzu Print Extension settings.
Select Helm as the platform.
In the auto-print section, enable auto-print only for the Helm workflows your bench uses.
Keep manual print available for exception handling and first-run testing.
Save the settings.

Helm orders table with Yuzu Print Extension workflow options open

After enabling auto-print, test one known order in each workflow before using it on a live packing bench.

Use Helm with 3PL mode

Helm supports 3PL mode. Use Set up 3PL mode in Yuzu Print Extension when one Helm account fulfils orders for multiple Yuzu merchants.

In 3PL mode, each Helm client or merchant name needs a mapping to the correct Yuzu App ID and API key. When an operator prints from Helm, Yuzu uses the merchant shown on the Helm order or row to choose the matching mapping.

Recommended setup:

Turn on 3PL mode in the extension settings.
Add a mapping for each live Helm client or merchant name.
Keep mappings in draft while testing.
Test one order for each merchant.
Move the mapping to live after the test print succeeds.

If a merchant name is missing or different from the mapping, the extension may skip the print or show a missing merchant warning. Add the exact Helm client or merchant name shown in the workflow.

Test Helm printing

Run these checks before publishing the setup to operators:

Manual print from Create Shipment (Packing).
Manual print from Speedy Single Print.
Manual print from Order Edit/View.
Manual batch print from Batch Order Selection with more than one selected order.
Auto-print from each enabled single-order workflow.
3PL test print for each mapped merchant, if 3PL mode is enabled.
Printer routing test for Invoice, Gift message, and Sticker if tag-based routing is enabled.
Confirm success in the extension notification or print history.

Troubleshooting

Yuzu button does not appear: Refresh Helm, confirm Helm is selected in extension settings, and open one of the supported Helm workflows listed above.
Batch auto-print is not available: This is expected. Batch Order Selection supports manual printing only.
Order not found in Yuzu: Check whether the App ID should be the source app ID or the Yuzu org/team ID. See Create a Yuzu API key and choose an App ID.
Documents print to the wrong printer: Check the Static Printer ID or Tag-Based Routing settings. See Find printer IDs and set a printer override and Set up tag-based printer routing in Yuzu Print Extension.
A 3PL order does not print: Check that the Helm client or merchant name has a live mapping in 3PL mode. See Set up 3PL mode in Yuzu Print Extension.
No notification appears: Check whether notifications are enabled and review the extension print history. See Understand Yuzu Print Extension notifications.
Another bench needs the same Helm setup: Export and import the extension configuration. See Share Yuzu Print Extension configuration between benches.

Use Yuzu Print Extension with Helm