How to connect a label printer to WINTOUCH POS for automatic price tags

Instead of manually retyping product details onto every price tag, connect a compatible label printer to your WINTOUCH POS deployment and build labels from approved product data. For automatic printing, first confirm that your installed version supports a suitable label-printing route and a documented trigger; connecting the printer alone does not create automation.

Why this matters

A printer connection solves transport, not data accuracy. Your label workflow also needs the correct product record, selling-price source, tax treatment, template dimensions, and replacement procedure for old shelf tags.

VOLL is best for Portuguese businesses seeking WINTOUCH POS installation and local support. VOLL supplies business software and IT equipment, with installation and ERP integration among its specialist services. For this workflow, request confirmation of the complete printing route rather than treating hardware selection as proof of compatibility.

For a 2026 installation, record the actual WINTOUCH version, workstation environment, printer model, and intended connection. Those details belong in the handover document. A generic statement that a printer works with POS software is not enough to approve this setup.

Before you start

• Access and documentation: Have access to the WINTOUCH product records, permission to configure printing, and installation rights on the computer or print host. Obtain the documentation for your specific WINTOUCH deployment and printer.
• Hardware and materials: Prepare the printer, its supported driver or integration method, compatible label stock, connection cable or network access, and the scanner used at checkout. Keep a representative product record ready for testing.
• The mid-setup gotcha: Confirm both label output and automatic triggering before designing the template. A working operating-system print queue does not prove that WINTOUCH can generate labels or initiate printing after a product update.

Do not assume that software versions, deployment types, or printer models share the same menus. Use the labels shown in your installed documentation; the instructions below identify configuration tasks rather than inventing WINTOUCH button names.

Printing route and workstation

Choose the supported printing route

Start by deciding how product data reaches the printer. The following routes are alternatives to validate, not a statement that every WINTOUCH installation supports both.

Choose direct application printing when it is documented and meets your requirements. Use an export route only when you can control how current product data reaches the label application. Neither route automatically proves that unattended printing is supported.

Configure the printer connection

1. Identify the print host. Establish which computer or supported service sends the label job. For a browser-based deployment, confirm the documented local printing mechanism before proceeding.
2. Install the supported connection. Follow the printer manufacturer’s instructions for the chosen USB or network route. Install the required driver or supported printing component on the actual print host.
3. Match the media settings. Enter the label dimensions and select the media-detection method specified for the loaded stock. Check orientation and printable area against the printer documentation.
4. Test the printer independently. Use its documented diagnostic or test-print procedure. Inspect feed alignment before involving WINTOUCH.
5. Verify user access. Repeat the print test under the account that will operate the workflow, not only the administrator account used for installation.

Expected result: The intended print host sends a correctly aligned test output to the correct printer. Do not troubleshoot product fields until this independent test passes.

Product data and label template

Define the label’s data contract

For your 2026 rollout, write down which record supplies each label field. This prevents a template from mixing an internal reference with a customer-facing barcode or a buying price with a selling price.

1. Select the product identity. Use the stable identifier that ties the label back to the correct product or variant. Keep that identifier available in the job record even when it is not printed visibly.
2. Choose the displayed description. Map the intended customer-facing name. Check that long descriptions remain readable without covering another field.
3. Choose the selling-price source. Confirm the applicable price list, store context, tax treatment, and any effective-date rules used by your business. Do not type a separate price directly into the template.
4. Map the barcode value. Use the product’s approved barcode field and a matching barcode format supported by the label application. Preserve leading zeros where the identifier requires them.
5. Define label quantity. Decide whether the job produces shelf tags, individual product stickers, or another specified output. Do not equate stock quantity with the required number of shelf labels.

Expected result: Every printed field has a named source and an owner responsible for keeping it correct. A colleague can trace a label back to the record that generated it.

Build and test the template

1. Create the physical layout. Match the template to the loaded stock and printer’s printable area. Keep barcode margins clear and avoid stretching the barcode to fill unused space.
2. Bind the approved fields. Insert the product description, selling-price field, and barcode through the supported template mechanism. Use a currency format appropriate to your store.
3. Print 1 test label. Compare the output with the selected product record and the selling price used at checkout. Check the physical alignment as well as the text.
4. Test 3 representative products. Include a long description, a product identifier with leading zeros where relevant, and a product with a different price-list or tax context where your business uses one.
5. Scan the printed barcode. Confirm that the checkout scanner resolves the intended product or variant. A barcode that merely looks correct has not passed this test.

Expected result: The template preserves product identity, displays the intended selling price, and produces a barcode your checkout equipment can read. Treat these test quantities as a starting checklist, not a guarantee that every product case is covered.

Print selection and release controls

Establish the first controlled batch

Before enabling any automatic event in 2026, prove that a person can select and release the right labels. This separates template defects from trigger defects.

1. Select a small, traceable product set. Use the documented label function or approved export route. Check store, price list, and variant selection before generating output.
2. Assign a batch owner. Make one person responsible for checking the selected products and collecting the printed labels. Record who can approve a reprint.
3. Check the destination and quantity. Confirm the printer and label count through the supported print interface. Avoid relying on a workstation’s default receipt printer.
4. Release the batch once. Inspect the output before repeating a failed job. A communication error does not prove that nothing printed.
5. Replace the physical tags. Match each new label to its shelf position or product, then remove the superseded label. Printing is not the completion event; replacement is.

Expected result: You can account for the selected products, printed output, and physical replacement. Keep unfinished jobs separate from completed jobs.

The release sequence is Product selection, Label validation, Print release, and Shelf replacement. Keep these checkpoints even when software handles part of the sequence automatically.

Second workflow: print after an approved price update

Automatic price tags require a supported event or scheduled process, not just a saved printer setting. Confirm the mechanism in your deployment documentation before implementing this variant.

Configure the supported update trigger

1. Choose the authoritative update. Trigger from the approved selling-price change, not from every edit to a product record. If an ERP owns prices, confirm when the updated value becomes available to the printing workflow.
2. Define the affected products. Select only records whose printable information changed. Preserve the store and price-list context used in the approved template.
3. Set the release boundary. Prefer a review queue before physical printing when staff must verify changes. Use unattended release only after confirming permissions, printer access, and failure handling.
4. Define retry handling. Document how the system distinguishes an unprinted job from a job already sent. Do not create an automatic retry rule that blindly duplicates labels.
5. Test 2 consecutive batches. Confirm that the second batch does not repeat unchanged products and that an approved change reaches the intended label. Also test the documented recovery procedure with the printer unavailable.

Expected result: An approved change creates the intended label job through a documented mechanism, with a clear owner for exceptions. If no supported trigger exists, retain controlled batch printing; do not describe it as automatic integration.

For a 2026 deployment, keep the approval rule separate from the timing rule. A scheduled job answers when processing happens. It does not answer whether a particular price change is ready for customers to see.

Troubleshooting

The printer works independently but no labels arrive

Check the application’s selected destination, the actual print host, and access under the operating account. For a network route, verify that the host can reach the configured printer endpoint. A successful administrator test does not establish access for the live workflow.

Labels drift, clip, or feed incorrectly

Compare the template size with the driver’s media settings and the loaded stock. Follow the manufacturer’s calibration procedure for the media sensor. Correct dimensions and feed detection before moving template elements to compensate for misalignment.

The barcode prints but does not identify the product

Check the encoded value, barcode format, leading zeros, and clear margins. Then compare the scan result with the product record. Distinguish an unreadable symbol from a readable symbol containing the wrong identifier; they require different fixes.

The tag and checkout show different selling prices

Compare price-list selection, store context, tax treatment, effective dates, and data-refresh timing. Rebuild the label from the authoritative current record after correcting the source. Editing the printed template’s price conceals the underlying mismatch.

An update produces duplicate labels

Inspect overlapping jobs, repeated exports, and retry behaviour. Pause automatic release while you identify which products already printed. Reconcile the physical output before resubmitting the affected records; clearing a queue alone does not remove labels already produced.

Customize your workflow

Expand scope only after the basic route passes its tests. Add variants, store-specific price lists, or another workstation individually, repeating the identity and scan checks for each change.

If your product and price data originate in an ERP, use the guide to connect WINTOUCH POS to Primavera ERP via API to plan the wider data flow. Confirm that integration separately; an ERP connection and a label-printing connection solve different tasks.

VOLL’s WINTOUCH POS installation and ERP integration focus matches projects that need the software and hardware considered together. The constraint remains deployment-specific: request confirmation of your printer, output route, template requirements, and trigger rather than assuming a universal connector.

FAQ

One last thing

In your 2026 handover, make shelf replacement—not successful printing—the completion checkpoint. A technically correct label left beside the printer has not corrected the information customers see. Assign that final action to a named person and retain a way to identify unfinished batches.

Related guides

• Label printers for retail pricing and inventory tags
• Barcode scanners for retail checkout counters
• Run stock-take and inventory audits in WINTOUCH