Use this guide when the Yuzu Print Extension button does not appear, a document does not print, auto-print does not run, or the wrong printer is used.
Start with one known order
Before changing multiple settings, test with one order that you know exists in Yuzu and already has documents generated.
Open the order in the platform your team uses.
Run a manual print if the workflow supports it.
Read the extension notification.
Change one setting at a time.
Test again with the same order.
The Yuzu print button does not appear
Check these first:
The extension is installed and enabled in Chrome.
You are signed in to the supported platform in the same Chrome profile.
The platform tab was refreshed after saving extension settings.
The platform is selected or detected in the extension settings.
You are on a supported workflow for that integration.
If using a custom domain, the domain is saved in the extension settings.
The order is not found
This is usually an App ID or order-ID matching issue.
Use the source app ID when the IDs printed from the platform match source IDs for the app that sent the order to Yuzu.
Use the Yuzu org/team ID when the IDs being printed are unique inside your Yuzu team.
If you use 3PL mode, check the App ID inside the merchant mapping, not only the main extension settings.
The print request succeeds but nothing prints
Check these next:
The printer is online in Yuzu.
The Printer UUID is correct if Static Printer ID is enabled.
The document tags match exactly if Tag-Based Routing is enabled.
The order has documents generated in Yuzu.
The printer is loaded with the right paper or labels.
Documents print to the wrong printer
Open Yuzu Print Extension settings.
Check Specify Printer Override.
Use Static Printer ID when everything should go to one printer.
Use Tag-Based Routing when tags such as
Invoice,Gift message, andStickershould go to different printers.Re-copy printer IDs from the Yuzu printer list if needed.
Save and retest with one order.
Auto-print does not run
Check these first:
Auto-print is enabled for the exact workflow you are testing.
Manual printing works for the same order.
The order is at the workflow stage where your integration supports auto-print.
The order has not already been skipped because of a successful print setting.
3PL merchant mapping is live and complete, if used.
Keep auto-print off until manual printing works.
3PL mode does not print for a merchant
Check the merchant mapping:
Merchant name or code matches what the platform shows.
Mapping is live, not draft.
API key belongs to the correct Yuzu team.
App ID matches that merchant's order IDs.
Printer routing is correct for that merchant's documents.
For Mintsoft, add mappings for both short and long merchant names if workflows can show different versions.
Notifications are distracting operators
During setup, leave warnings visible. After testing, use Understand Yuzu Print Extension notifications to decide which warnings can be hidden safely, such as ignored-order warnings in workflows where those skips are expected.
When to contact support
Send these details when you need help:
Platform and workflow name.
Example order ID or order number.
Whether manual print or auto-print failed.
The exact extension notification text.
Screenshot of the platform page with private data hidden.
Screenshot of the relevant extension settings with API keys hidden.
Whether 3PL mode, custom domain, Static Printer ID, or Tag-Based Routing is enabled.