Article Type: How-To / Feature Guide Audience: End Users, Application Designers, Administrators Module: Fuuz Platform Applies to Versions: 2025.12+
Overview
Fuuz supports three primary printing approaches: standard browser printing, Chrome kiosk (silent) printing, and advanced gateway-driven printing. Choose the option that matches your label volumes, device complexity, and automation needs.
Guidance: For low volume and single-printer scenarios, use browser or kiosk printing. For multi-printer routing, automation, or high throughput, use the Fuuz Gateway.
Note: Using the Fuuz Gateway does require specific licensing, you must have the gateway installed (Build, QA and Prod) for testing. Suggest using a Docker+Portainer.io template configuration.
Prerequisites
Browser printing: A modern browser (Chrome/Edge/Firefox) and a configured default printer.
Kiosk printing: Google Chrome installed, desktop shortcut access, and a configured Fuuz screen with Auto Print + Auto Window Close in the related Flow Action.
Gateway printing: Installed Fuuz Gateway with appropriate printer drivers (e.g., TCP/network), reachable printers, and application flows that pass routing parameters.
Option 1: Standard Browser Printing
Press Ctrl+P (Windows) / Cmd+P (macOS), or use your browser’s menu to print any screen, report, or document. No Fuuz configuration required.
Tip: Set the correct paper size and margins in the OS printer driver to avoid scaling issues.
Option 2: Chrome Kiosk (Silent) Printing
When to Use
Single workstation + single barcode printer.
Low-to-moderate label volumes where an operator can interact between machine cycles.
Create a Chrome Shortcut
Open Fuuz to the target screen (e.g., control panel) and click the Share icon to copy the page URL.
Copy your Chrome shortcut to the desktop → Right-click → Properties.
In Target, append kiosk flags and the Fuuz URL: "C:\Program Files\Google\Chrome\Application\chrome.exe" --kiosk --kiosk-printing https://your-fuuz-url
Click OK and restart Chrome (or reboot).
Configure the Fuuz Screen
In the Flow Action that renders the document, enable Auto Print.
Enable Auto Window Close (e.g., close after 1 second) to return the operator to the working screen.
Expected Behavior: Document opens briefly → Fuuz triggers print → Chrome silently submits to the default printer → the document window auto-closes → operator returns to the working page.
Log in with email/API key, password, and subdomain; select tenant.
Driver & Printer Setup
Install TCP printer driver (or other supported drivers).
Configure printers by IP; map to work centers or routing parameters (user, workstation, work order, pack type).
App Flow Integration
Pass routing parameters in your Fuuz flows to direct print jobs to the correct device.
Monitor status and device health in the Gateway UI.
Note: Complex setups may require assistance from Fuuz engineers or partners; submit a support ticket for configuration help.
Troubleshooting
Common Issues
Wrong printer used: Ensure a single default printer is set (browser and OS). For multi-printer stations, disable auto-print or use Gateway routing.
Incorrect label size: Adjust printer driver properties (paper size, margins) and test. Fuuz does not override device driver settings.
No output on ZPL devices from PDFs: Update printer firmware or use vendor features like PDF Direct. If not supported, consider generating native printer code (ZPL/IPL) via custom flows.
Diagnostic Tips
Test print from OS first to verify driver + media settings.
Check the Fuuz Flow Action flags (Auto Print / Auto Close).
For Gateway, confirm device online status and correct IP mapping.
Fuuz has no control over the printer driver configurations - you may need to consult the hardware vendor for more detailed information if your print is not scaled or rendering properly.
Various printing device manufacturers may have different requirements, which could include firmware, drivers, or even hardware to make their printers compatible with PDFs.
Best Practices
Standardize label sizes and printer models across workcenters.
Use kiosk mode for hardened shop-floor stations; lock down OS/browser settings.
For shared printers, require operator confirm before print or implement Gateway routing.
Document printing topology and maintenance (firmware, drivers, media).
Disclaimer
Chrome kiosk features and third-party driver behavior may change. MFGx cannot guarantee ongoing compatibility and provides assistance via paid engagements if alternative solutions are required.
Revision History
Version
Date
Editor
Description
1.1
2025-12-23
Craig Scott
Enhanced with prerequisites, Flow Action flags, kiosk flags, gateway routing, and troubleshooting.
Here are some details on different methods you can use to print documents from Fuuz. Option 1: Standard Browser Printing Within your web browser, you can utilize the Ctrl+P option, as well as the print function available from the browser tool menu on ...
How to Create APIs Using Data Flows in Fuuz Estimated Time: 5–7 minutes Skill Level: Intermediate Overview This guide explains how to create RESTful APIs using Data Flows in Fuuz. Unlike the GraphQL-based method covered in a previous tutorial, this ...
Estimated Time: Under 5 minutes Skill Level: Beginner to Intermediate <br> Here’s the revised how-to article with the use of “cons” or conversational filler words removed, making it more formal and suitable for a knowledge base: How to Create a ...
Article Type: Configuration / How-To Audience: Application Designers, Developers, Partners Module: Screen Designer Applies to Versions: 2024.1+ Estimated Time: 15-20 minutes 1. Overview JSON Form Fields provide a quick and efficient way to create ...