zplCloud

zplCloud Blog

Set Up a Cloud Label Print Workflow in Minutes - From Hardware to Employee Printout

^XA^FDSheet → Label → Print.^XZ

3 min read zplCloud Team

One Workflow, End to End

This post stitches the pieces together: a complete cloud label print workflow, from the printer in its delivery box to a label in an employee's hand. And because data is where most projects stall, we keep the datasource deliberately simple: a Google Spreadsheet.

You'll need about 20 minutes and three other posts (linked below):

  • Zebra Cloud Setup - Speed Run - unbox to production label.
  • Print View - the responsive UI for your employees.
  • zplCloud App - printer setup/reset from Android.

Step 1 - Hardware (see the speed run)

  • Unbox the Zebra printer, load media, power on, connect to the network.
  • Connect it to zplCloud: Weblink one-liner or zplCloud Proxy agent.
  • Apply a printer profile so darkness, speed and media match.

→ 10 minutes, fully covered in the Zebra Cloud Setup - Speed Run post.

Step 2 - Design the Label

  • Open the designer, start from a template or blank.
  • Add the fields that change per label: article number, name, quantity, destination.
  • Bind them to columns of your data - the same column names you'll use in the spreadsheet.
  • Use the live PNG / PDF / SVG preview to check before anything prints.

Step 3 - Google Spreadsheet as the Datasource

No ERP, no database, no export scripts. A Google Spreadsheet is the simplest possible master data. Two simple paths:

A) Copy & paste (zero code)

  • Fill your spreadsheet: one row per label, columns = label fields.
  • Export / copy the rows into the designer's test data or a batch job and print.

B) Tiny script (Google Apps Script → zplCloud API)

  • Your spreadsheet becomes the live driver: an Apps Script reads the current row(s) and calls the zplCloud print API with the field values.
// Google Apps Script - send the active row to zplCloud
const payload = {
  host: "192.168.1.50",   // your printer (or leave empty to print via Weblink)
  port: 9100,
  payload: "^XA^FO20,20^A0N,60^FDHello " + row.artikel_nr + "^FS^XZ"
};
UrlFetchApp.fetch("https://api.zplcloud.com/api/print/raw", {
  method: "post",
  contentType: "application/json",
  headers: { "X-Api-Key": API_KEY },
  payload: JSON.stringify(payload)
});

That's the whole integration - a spreadsheet, a script, a cloud print API.

Step 4 - Print View for Employees

  • Create a Print View from the design.
  • Choose the fields your employees may edit (e.g. quantity, destination) and lock the rest (e.g. article number).
  • Share the link - or print a QR code and put it next to the printer.

Step 5 - The Employee Prints

1. Employee scans the QR with their phone.

2. The responsive form opens - optionally with a barcode scanner button to scan the article.

3. Live PDF preview confirms the label.

4. One tap: print - the job goes through Weblink to the printer in the warehouse.

The Whole Picture

StageToolTime
---------
1. Hardware + cloud connectWeblink / Proxy + printer profile10 min
2. Designdesigner (template + fields)5 min
3. DatasourceGoogle Spreadsheet + Apps Script / copy & paste5 min
4. Employee UIPrint View + QR2 min
5. Printoutemployee scans, fills, printsseconds

Why "Just a Spreadsheet" Is the Point

The fanciest workflow dies if data entry is hard. A Google Spreadsheet is something every office already understands - no training, no tickets, no IT backlog. It's simple on purpose: start with the spreadsheet, and swap in your ERP later - the label and the print path stay the same.

Hardware → spreadsheet → label in hand. That's the whole workflow.

More articles