Skip to main content

Set up 3PL mode in Yuzu Print Extension

Use this guide when one warehouse platform account prints Yuzu documents for multiple merchants, and each merchant needs its own Yuzu API key or App ID.

Use this guide when one warehouse platform account prints Yuzu documents for multiple merchants, and each merchant needs its own Yuzu API key or App ID.

Before you start

  • Confirm your integration supports 3PL mode.

  • Have the Yuzu API key and App ID for each merchant you want to print for.

  • Know the merchant names or codes that appear in the warehouse platform.

  • Test each merchant with one known order before enabling auto-print.

3PL mode is supported for Deposco, Extensiv, Mintsoft, Helm, and Linnworks. If your integration article says 3PL mode is not supported, use the normal single-merchant setup for that platform.

Turn on 3PL mode

  1. Open Yuzu Print Extension settings.

  2. Select the platform your team uses.

  3. Enable 3PL mode.

  4. Add a merchant mapping for each merchant you print for.

  5. Enter the merchant name or code exactly as it appears in the platform.

  6. Enter that merchant's Yuzu API key.

  7. Enter that merchant's App ID.

  8. Mark the mapping as live when it is ready to print.

  9. Save the settings.

Yuzu Print Extension 3PL merchant mapping settings

Choose the App ID for each merchant

Each live merchant mapping needs the App ID pattern that matches that merchant's orders.

Use the source app ID when the IDs printed from the platform match the source IDs for that merchant's source app in Yuzu.

Use the Yuzu org/team ID when the IDs being printed are unique within that merchant's Yuzu team.

Use draft mappings while testing

Keep a merchant mapping as draft until you are ready for it to print live. Draft mappings are useful when you know a merchant will be added later but you do not want operators to print for that merchant yet.

While setting up 3PL mode, keep missing-merchant warnings visible. They help you find merchant names that need mappings.

Mintsoft merchant-name tip

For Mintsoft, create live mappings for both the short and long versions of merchant names when both may appear in workflows. For example, add mappings for Acme and Acme Candles Ltd if Mintsoft can show either value.

Mintsoft can show different merchant-name formats depending on the workflow, so test each workflow you use before enabling auto-print for operators.

Test each merchant

  1. Pick one known order for the merchant.

  2. Confirm the order exists in that merchant's Yuzu team.

  3. Open the supported platform workflow.

  4. Print manually first.

  5. Confirm the document prints from the expected printer.

  6. Repeat for each live merchant mapping.

  7. Enable auto-print only after manual printing works for each merchant.

Troubleshooting

  • Missing merchant warning: Add a live mapping for the merchant name shown in the platform, or update the existing mapping to match the visible name exactly.

  • Draft merchant does not print: Mark the mapping as live when it is ready to print.

  • Order not found: Check the App ID for that merchant mapping.

  • Wrong merchant prints: Check that merchant names or codes are unique and mapped to the correct API key and App ID.

  • Auto-print skips a merchant: Confirm the mapping is live and complete before testing auto-print again.

Did this answer your question?