Use this guide to create the Yuzu API key used by the Print Extension and decide which App ID to enter.
Before you start
You need access to the Yuzu team that owns the orders you want to print.
You need permission to create API keys.
Open Yuzu in the same browser profile where you manage the extension: https://app.yuzu.so
Create an API key in Yuzu
From the Yuzu home page, click Settings in the bottom-left corner.
Open API Keys.
Click Add API key.
Give the key a clear name, such as
Warehouse print extensionor the bench name.Create the key.
Copy the API key immediately.
Yuzu only shows the full API key once. If you leave the page without copying it, create a new key and remove the unused one.
Choose the App ID
Yuzu Print Extension supports two App ID patterns.
Use the source app ID when the order IDs shown in the platform match the source IDs for the app that sent the order to Yuzu.
Use the Yuzu org/team ID when the IDs being printed are unique within your Yuzu team.
Use the same App ID pattern for manual printing and auto-print testing. If the extension says the order was not found, check the App ID before changing printer routing.
Add the API key and App ID to the extension
Open Yuzu Print Extension settings.
Select the platform your team prints from.
Paste the API key into the API key field.
Enter the App ID.
Save the settings.
Test the key
Open a known order in the platform you print from.
Click the Yuzu print button.
Confirm the extension shows a success notification or a clear error.
If the order is not found, re-check the App ID choice.
If the request is unauthorized, create a new API key and update the extension.
Troubleshooting
The API key was lost: Create a new key. The full key cannot be viewed again later.
The extension says unauthorized: Replace the saved API key with a fresh key from the correct Yuzu team.
The order is not found: Check whether this setup should use the source app ID or the org/team ID.
Multiple benches need the same setup: Use Share Yuzu Print Extension configuration between benches, but only send configuration to trusted teammates because it can include sensitive credentials.
