Compatibility
Will your printer and POS work?
Check both sides of the connection: the printer must use a supported protocol, and your software must be able to send jobs to the node. Bench results below cover specific devices. No commercial POS integration is qualified yet, and an advertised Epson or Star identity does not bypass a vendor's certified-printer requirements.
Start here
Check the print path before choosing hardware.
Use this as a screening checklist, then test your exact configuration before putting it into service.
For a raw network-printing integration: a USB ESC/POS printer and software that sends raw ESC/POS to a manually entered port 9100 address are candidates for testing. Our tested reference setup below does not qualify every printer or POS in those categories. If your POS only accepts printers from its certified list, do not assume a discovery profile will make it work. An integrator can also use the local HTTP print API.
ESC/POS is the only print language this firmware implements. USB connectivity by itself does not establish compatibility. Check the printer command language, power, cable and any hub as well as its model number.
Read the supported integration recipe for the network requirements and the separate HTTP path for cash drawers.
Bench results
Tested on our bench.
These are individual reference devices, not approvals of a whole brand or product family. Match the device details and review each limit.
DYMO M25 25 lb USB scale
Weight readings tested on the reference unit.
The reference unit returned ounce readings and status codes 2, 4 and 5. Other units and statuses have not been observed on this hardware. It sleeps after about three minutes without a weight change; missing readings must not be treated as zero weight.
Source: 0922:8009 · captured 2026-08-07 · firmware test fixture fixture_dymo_m25.h
Generic 80 mm thermal receipt printer
Receipt printing and status tested on the reference unit.
The reference printer identifies itself as POS-X, USB ID 0416:5011. It printed a raw port 9100 job and reported paper, cover and drawer status through DLE EOT. This unit needed eight feed lines before cutting. These results do not qualify every POS-X printer or every generic 80 mm printer.
Source: 0416:5011 · :9100 job accepted 2026-09-05 · bench-bringup.md §printer bring-up
USB keyboard-wedge barcode scanner (Netum family)
Scans tested in HID boot-keyboard mode.
The tested unit uses a single-interface HID boot keyboard. A wedge scanner and an ordinary keyboard are byte-identical to the node: binding follows the configured scanner policy, not brand detection. Check the scanner mode and test actual barcode reads; this is not a claim that every Netum model works.
Source: 9901:0301 · Class_03 SubClass_01 Prot_01 · bench-bringup.md §the scanner
Unbranded RJ12 cash drawer
Drawer pulse and open/closed state tested.
The reference drawer opened through the attached printer and reported open/closed state with inverted polarity. Configure drawerOpenLevel for the actual wiring. Raw port 9100 drawer commands are blocked; opening a drawer requires the separate HTTP drawer endpoint.
Source: Hardware conformance on node pn-d938, 2026-08-23: 118 passed, 0 failed
Discovery profiles
Emulated identity, unverified against a POS.
These names describe identities the node can advertise. They are not a list of tested printers or supported POS systems.
Treat these profiles as UNVERIFIED AGAINST A REAL POS . A POS may discover the name and still reject the connection or print incorrectly.
Epson TM-m30
Discovery tested; POS acceptance unverified.
The node advertised this identity over mDNS in a bench test. No point-of-sale system has ever completed an add-a-printer flow against this profile in our qualification evidence. The actual Epson TM-m30 printer has not been tested here.
Source: mDNS identity confirmed on hardware 2026-09-05 · firmware pn_profile.c
Epson TM-T88V
Discovery strings only; POS acceptance unverified.
The profile supplies manufacturer and model discovery strings. Model-specific query responses are incomplete. Do not choose this profile expecting a POS-certified printer connection.
Source: firmware pn_profile.c — the source comment reads UNVERIFIED AGAINST A REAL POS
Epson TM-m10
Discovery strings only; POS acceptance unverified.
The 58 mm identity: the node reports this model on its own when the configured print width is 42 columns or fewer, and the profile pins it. Square's compatibility matrix lists the TM-m10 for USB and Ethernet, and Uber Eats, Lightspeed and Paytronix name it, but a vendor listing the physical printer is not evidence that it accepts this identity. The actual Epson TM-m10 printer has not been tested here.
Source: firmware pn_profile.c · vendor lists in docs/printer-whitelists-2026-10-07.md Table 1
Epson TM-U220
Discovery strings only; POS acceptance unverified.
The impact-printer identity: the node reports it on its own for an impact printer, and the profile pins it. Square's compatibility matrix lists the TM-U220 for Ethernet; Toast lists a legacy TM-U220B bought from Toast, Lightspeed K-Series offers a TM-U220 driver and Cuboh lists the TM-U220B for LAN. Whether a vendor whose list reads TM-U220B accepts a bare TM-U220 is unknown. No POS has been seen to accept this identity.
Source: firmware pn_profile.c · vendor lists in docs/printer-whitelists-2026-10-07.md Table 1
Epson TM-m30II
Discovery strings only; POS acceptance unverified.
The second-generation name. Square lists TM-m30 (I and II) and Shopify lists the TM-m30II; Lightspeed, Deliverect, Cuboh, BentoBox, Loyverse and Paytronix name it too, usually with a suffix such as -NT or -SL. Whether a bare TM-m30II satisfies a list written with a suffix is unknown, and no POS has been seen to accept this identity.
Source: firmware pn_profile.c · vendor lists in docs/printer-whitelists-2026-10-07.md Table 1
Epson TM-m30III
Discovery strings only; POS acceptance unverified.
The current-generation name on most lists. Shopify, Zettle, SumUp, Cuboh, Lightspeed and Deliverect list the TM-m30III for LAN; DoorDash lists it for Bluetooth only, which the node does not have. A POS that then expects TM-m30III-specific behaviour, such as Epson's Server Direct Print or ePOS-Device, will find the node does not implement it. No POS has been seen to accept this identity.
Source: firmware pn_profile.c · vendor lists in docs/printer-whitelists-2026-10-07.md Table 1
Epson TM-T88VI
Discovery strings only; POS acceptance unverified.
The current TM-T88 name. Square, Shopify, Lightspeed and Oracle MICROS list the TM-T88VI, and Lightspeed K-Series writes it as TM-T88V (VI). As with the TM-T88V profile, model-specific query responses are incomplete. No POS has been seen to accept this identity.
Source: firmware pn_profile.c · vendor lists in docs/printer-whitelists-2026-10-07.md Table 1
Star TSP143 / TSP100
Experimental discovery profile; POS acceptance unverified.
This profile uses generic print-discovery keys and supplies no ESC/POS model-query replies. It does not add StarPRNT support or establish compatibility with a Star printer or POS system.
Source: firmware pn_profile.c — self-labelled UNVERIFIED AGAINST A REAL POS
Protocol roadmap
In development, and not yet supported.
None of these works on a node today. If your current setup requires one of these protocols, do not buy a node expecting it to replace that connection today.
In development
- CloudPRNT
- In development; the client is implemented in firmware source but not yet in a released firmware image. The node acts as a CloudPRNT printer: it polls a CloudPRNT server over HTTP, either our cloud by default or one you run, such as an online-ordering system that already speaks CloudPRNT on your LAN or on the internet, and prints the jobs on its USB ESC/POS printer. The media types it accepts are plain text and our own print-lines JSON; Star image and markup formats are not accepted, and Star's MQTT method is not implemented. It has not been tested against any third-party CloudPRNT server, including Flipdish, BentoBox, Olo and Craver.
- Text-to-print
- In development, on the same channel as CloudPRNT: text a phone number and the message prints on your node, from phones you link or through an optional public keyword per node. The cloud route that turns a text into a print job exists in our code, but no inbound number has been set up, so there is nothing to text yet.
- ePOS-XML
- In development, and not a working print path yet. The firmware captures incoming requests for development; it does not print them.
Not yet supported
- StarPRNT
- Not yet supported. A printer that speaks only StarPRNT or Star Line mode cannot be driven today, and the node refuses it. Star output support is under consideration. If your printer has an ESC/POS mode, that mode still needs evaluation with its exact model and firmware; the setting alone does not qualify it.
- ZPL
- Label printers. Not yet supported.
- TSPL
- Label printers. Not yet supported.
- EPL2
- Label printers. Not yet supported.
- CPCL
- Mobile label printers. Not yet supported.
Delivery marketplaces
DoorDash, Uber Eats and Grubhub tablets pair printers over Bluetooth.
The node has no Bluetooth, so no node can print marketplace tablet orders today. The route to look at is each marketplace's POS integration, where orders land in your POS and print from whatever the POS already prints to.
Each marketplace tablet accepts a short list of Star or Epson models and pairs them over Bluetooth. DoorDash's merchant FAQ names the Star TSP654, Star TSP143 and Epson TM-M30III, all Bluetooth, and says orders will not print on an unsupported model. Uber Eats Orders pairs a Star or Epson printer over Bluetooth and then has you pick its model from a list. Grubhub documents three Star TSP143III models (Ethernet, Wi-Fi and Bluetooth) and HP ePrint; its Ethernet and Wi-Fi models are Star printers found by Star's own discovery, which the node does not answer either.
All three marketplaces also offer a POS integration: the order is injected into your POS and printed by the POS (DoorDash lists this path at no extra charge; confirm the others' current terms). A node behind a POS that prints to a typed port 9100 address is then printing the POS's ticket, not the tablet's, and the POS still has to accept the node as a printer, as described above.
Vendor pages checked October 7, 2026: DoorDash merchant FAQ, DoorDash printer troubleshooting, DoorDash order protocols, Uber Eats printing help, Grubhub: how to print orders. Vendor lists change; re-check the page before acting on it.
Check your setup
Send the details before buying.
We can review your proposed connection and identify what still needs a test. A review is not a compatibility certification.
- POS software name and version, plus its operating system.
- Printer model, firmware, USB interface and command language.
- Whether the POS lets you enter a raw port 9100 printer address.
- Power supply, cable, hub and Wi-Fi setup.
- Any cash drawer, scanner or scale the station must also use.
To test your software without hardware, request simulator evaluation access. The simulator covers the core print protocols; it does not qualify a physical printer. Current board details and availability are on the Proxy Node Raw page.
What the bench evidence does and does not establish
The capture and replay traces were produced by an operator's laptop on our bench network, not a commercial POS terminal. They test that traffic path without proving a POS integration.
The results above are from manual bench sessions. The hardware workflow is manually dispatched when a physical bench is available; its existence is not evidence that each release has passed a hardware test. Qualify the exact firmware, board and peripherals you intend to deploy.