Use this guide to print Yuzu documents from Deposco while your team processes orders in the handheld workflow or from a selected batch/list view.
Before you start
Yuzu Print Extension is installed and enabled in Chrome.
You can open the Deposco account your team uses for fulfilment.
Your Yuzu API key and App ID are configured. For setup steps, use Create a Yuzu API key and choose an App ID.
Your printer routing is configured if different document types need different printers. For setup steps, use Find printer IDs and set a printer override or Set up tag-based printer routing in Yuzu Print Extension.
If you fulfil for multiple merchants, your 3PL mode settings are configured. For setup steps, use Set up 3PL mode in Yuzu Print Extension.
Supported workflows
Deposco workflow | What it prints | Manual print | Auto-print |
Handheld Device Workflow | The order currently loaded in the handheld flow | Yes | Yes |
Batch Order Selection | Orders selected in a Deposco list/table view | Yes | No |
3PL mode: Supported. Use Set up 3PL mode in Yuzu Print Extension to map each Deposco merchant or business unit to the right Yuzu API key and App ID.
Custom domains: Not supported for Deposco. Use Deposco on a supported deposco.com domain.
Choose the right App ID
Deposco can be configured with either App ID pattern that Yuzu supports:
Use the source app ID when the order numbers shown in Deposco match the source IDs for a specific Yuzu app.
Use the org/team ID when the order numbers printed from Deposco are unique within your Yuzu team.
If prints return “order not found,” check this choice first. Create a Yuzu API key and choose an App ID explains how to decide and where to enter the value.
For 3PL setups, configure this per merchant in 3PL mode rather than only in the main App ID field. Use Set up 3PL mode in Yuzu Print Extension for those steps.
Configure Yuzu settings for Deposco
Open the Yuzu Print Extension settings.
Select Deposco as the platform.
Confirm your API key and App ID are set, or confirm each 3PL merchant mapping has the correct API key and App ID.
Choose printer routing: use Static Printer ID for one printer, or Tag-Based Routing for documents such as
Invoice,Gift message, andSticker.If you use the handheld flow and want printing to run automatically, enable Auto-print on Handheld Device Workflow.
If you want to avoid repeat prints after a successful auto-print, enable Disable auto-print for order after a successful print for the handheld workflow.
If you use 3PL mode, leave Show error warning for missing merchant details enabled while testing.
Use the shared setup guides for API keys, App IDs, printer IDs, tag routing, configuration sharing, notifications, and 3PL mode:
Print from the Handheld Device Workflow
In Deposco, open the handheld workflow your team uses.
Load the order you want to process.
Confirm the order number is visible before printing.
Click the Yuzu print button when you want to print Yuzu documents for that order.
If auto-print is enabled for Handheld Device Workflow, continue the normal handheld flow and let Yuzu print when the order is ready.
Watch for the extension notification that confirms whether the print was sent, ignored, or failed.
If you are using 3PL mode, Yuzu also needs the merchant details shown on the Deposco order. If those details are missing or not mapped, the extension may warn that it cannot find the merchant mapping.
Print from Batch Order Selection
Open the Deposco list view your team uses for order processing.
Select the orders you want to print.
Confirm the selected rows show the expected order numbers.
For 3PL teams, confirm the selected rows show the expected business unit or merchant code.
Click the Yuzu print button in the Deposco action area.
Wait for the Yuzu notification or print history entry before moving to the next batch.
Batch printing depends on the selected rows in Deposco. If the wrong rows are selected, Yuzu will try to print the selected orders, not every order currently visible in the table.
Test or confirm it worked
Start with one known Deposco order that already exists in Yuzu.
Print manually from the Handheld Device Workflow.
Confirm the expected documents print from the expected printer.
If you use tag routing, confirm each document type prints to the intended printer.
If you use 3PL mode, repeat the test with one order for each mapped merchant.
Turn on Auto-print on Handheld Device Workflow only after manual printing works.
Run one handheld auto-print test and confirm there is only one successful print for the order.
Test a small batch from Batch Order Selection and confirm every selected order prints.
Troubleshooting
Yuzu button does not appear in the handheld workflow: Wait until the order is loaded and the normal Deposco action controls are visible. Refresh Deposco and reopen the workflow if the page was left open through a long session.
Auto-print does not run in the handheld workflow: Confirm Auto-print on Handheld Device Workflow is enabled, then load a fresh test order.
Order not found: Confirm the order exists in Yuzu, then check whether Deposco is sending an order number that should use a source app ID or an org/team ID.
Wrong merchant or missing merchant warning in 3PL mode: Check the 3PL merchant mapping for the Deposco merchant or business unit shown on the order.
Some selected batch orders do not print: Check that each row was actually selected and that each order exists in Yuzu. For 3PL teams, also check the business unit or merchant mapping for each selected row.
Documents print to the wrong printer: Check whether Static Printer ID or Tag-Based Routing is enabled.
Duplicate prints during testing: Enable Disable auto-print for order after a successful print for the handheld workflow, then retry with a new test order.
