Check Printer Compatibility with Your POS
Check the exact printer model, connection, command language and status behavior your POS needs before replacing hardware or adding a local bridge.
Published 2026-07-24 · Updated 2026-10-07 · For restaurants →
Start with your POS software, not the printer price. A replacement needs the connection method, command language and status behavior that your installation expects. This page explains how to check those requirements and where a local bridge such as Proxy Node Raw can be evaluated. No commercial POS integration with Raw is qualified yet.
Start with the supported hardware list
A printer that accepts an ESC/POS receipt can still differ in character width, image support, cutting behavior and status responses. A shared protocol name is a starting point for testing, not a guarantee that every command works. Confirm the exact model suffix, interface and software version, including whether the printer connects through USB, Ethernet, Wi-Fi or Bluetooth.
Ask the POS provider who supports the printer connection and what information they need before authorizing a replacement. Changing the printer can affect installation, kitchen routing and drawer operation. Compare the complete working station and its support arrangements rather than assuming that the cheapest printer creates the lowest-cost installation.
Square's printer compatibility matrix lists printer models by connection method and Square device. Shopify's receipt-printer table lists supported models, connections and regional availability. Both references were checked October 7, 2026. Neither establishes compatibility with a Proxy Nodes device.
For Toast, Clover, Lightspeed or another provider, obtain the current list for your actual product and region. Do not assume every product sold under one POS brand has the same printer support. A vendor listing a physical Epson or Star printer is not evidence that it accepts an emulated identity.
Check four parts of the workflow
An incompatible printer can fail at several points. Work through each one rather than treating a successful discovery or test receipt as complete acceptance:
- Discovery. Does the POS accept a manually entered printer address, or only a model from its setup list? Check this before buying a bridge.
- Status. Test paper-out and cover-open behavior. Some printers cannot provide the status the application expects. A successful write does not prove paper came out.
- Cash drawer. Confirm wiring and pulse settings. Through Raw, drawer commands inside a port 9100 print job are blocked; an application must call the separate HTTP drawer endpoint.
- Workflow. Test kitchen routing, copies, cancellations and reprints with actual orders. Decide how staff resolve uncertain jobs without automatically creating duplicate tickets.
Your practical options
- Choose a currently supported printer. Obtain a quote for the exact model and interface recommended for your POS. For used hardware, verify condition, firmware, support and included parts rather than assuming an older model remains supported.
- Check for raw network printing. If your software accepts a printer address and ESC/POS on port 9100, a compatible USB printer and node are candidates. That still requires a receipt, status and recovery test.
- Evaluate a local API integration. An integrator can call Raw from a native client or an on-site backend. A hosted browser page cannot simply call an arbitrary LAN address; read the supported integration recipe.
- Compare complete costs. Include printers, nodes or print servers, power, cables, physical protection, installation, software work and spare equipment. Keep the working station available during evaluation.
What a node changes
Raw is a bare ESP32-S3 board running Nodeware. It connects a supported USB ESC/POS printer to a local network over 2.4 GHz Wi-Fi. Its documented interfaces are capabilities to evaluate, not certification for a particular POS.
The raw port accepts ESC/POS on TCP 9100 and answers supported DLE EOT status queries using the attached printer's readings. A printer that cannot provide a reading remains a limitation; the node cannot manufacture a reliable paper sensor or fix unsupported commands. The raw port is unauthenticated and belongs on a trusted, restricted network.
The local HTTP/JSON API provides printing, status and a separate drawer operation. Switching an existing POS to the node's address does not add the HTTP drawer call. An application that embeds drawer pulses in raw receipts needs an integration change, or drawer operation must be excluded from the evaluation.
Compatibility profiles change discovery information. They do not prove that Square, Shopify or another POS will accept the connection. ePOS-XML printing and a CloudPRNT client are in development, and neither is a working migration path today. The compatibility page separates tested peripheral behavior from unverified identities.
An unprovisioned node opens its setup Wi-Fi. With a supported printer attached and bound, it can print a setup QR slip; otherwise join the network manually. That slip is not the account claim code. Follow the setup guide for power, cabling and the separate account-claim process.
Each Raw unit must be flashed and print-tested before shipping. Earlier bench results do not qualify every newer release or hardware arrangement. Check current availability on the product page and qualify the exact shipping image with your parts. Simulator and conformance tools require evaluation workspace access; software tests do not replace physical acceptance.
Check the support arrangement
Before changing an installed station, review your actual POS agreement and support policy. Ask whether the proposed printer, bridge and connection remain supported, and who handles faults involving third-party equipment. We have not reviewed your contract and do not infer its terms from the POS brand. A bridge does not change obligations you have already accepted.
Evaluate a printer-plus-node setup when the documented local path fits and someone can qualify and support it. Keep the vendor-supported path when your POS requires a certified model or an unsupported protocol, you cannot modify the integration, or you need an immediately supported replacement. Local printing does not require internet, but your POS may still need its cloud to create orders or accept payments.
Frequently asked questions
- Can I use any thermal printer with my POS?
- Do not assume so. Check the exact POS device, software version, printer model and connection against the vendor's requirements. A shared brand or ESC/POS label is not a qualification.
- Why does my receipt print but my drawer stay closed?
- Check wiring and the application's drawer command. Raw filters drawer-pulse bytes on port 9100; drawer operation requires a separate POST /drawer/kick call and its own test.
- Does a compatibility profile bypass a certified-printer list?
- No. It changes discovery information, but no commercial POS acceptance result is qualified for those profiles.
- Does local printing work during an internet outage?
- The node's print path is local, but power, Wi-Fi, printer and client must remain available. Your POS may have separate cloud dependencies that prevent it creating a job.
Related: Epson TM-m30 alternatives · printing during an internet outage · kitchen setup.
Related reading
- Choosing an Epson TM-m30 AlternativeCompare the TM-m30III with generic ESC/POS printers: interface choices, POS compatibility, ownership cost and where a local print node fits.
- POS Not Printing When the Internet Is Down?Why cloud POS printing dies with your uplink, what the AWS and Square outages cost restaurants, and how to make receipts print offline — permanently.
- Kitchen Printer Setup: a No-Nonsense GuideSetting up a restaurant kitchen printer: thermal vs impact, Ethernet vs Wi-Fi, static IPs, routing by station, and surviving printer swaps.