Reference

Commands inside your ticket text.

PosPrinterDriver recognises text markers and converts them to ESC/POS instructions. Test each command on the actual printer model before production use.

Updated:

Formatting and actions

MarkerEffectNote
$intro$Line break or paper feedUse it to structure the ticket
$bold$ / $unbold$Enable or disable boldAppearance depends on the printer font
$small$ / variantsSmaller textAvailable variants depend on the app parser
$big$ / variantsLarger textCheck that it fits the width
$cut$Cut commandDepends on the cutter and settings
$cutt$Alternative cut commandTest which variant works on your model
$drawer$Open cash drawerRequires a compatible drawer and connector
$drawer2$Alternative drawer pulseMay correspond to the second pin or another variant
$logo$Print the configured logoConfigure and test the logo in the app first
$codepageN$Select code page NN must be supported by the printer and app

Sample ticket

text
$bold$ORDER #123$unbold$$intro$Table 4$intro$2 × Coffee         3,20 €$intro$$big$TOTAL       12,50 €$intro$$qr-6-https://example.com/p/123$$cut$
  • Validate the exact QR format with the installed version.
  • Control line length according to paper width and font size.

QR code

The reviewed parser recognises a QR marker containing size and content, and uses a specific error message for an invalid size. Encode or avoid separators that could be confused with the syntax.

  • Start with a medium size and a short URL.
  • Test text containing hyphens and non-ASCII characters.
  • Do not include secrets in a printed QR code.

Raw bytes

The ·number· syntax inserts individual byte values. This is an advanced feature: an incorrect value can change printer state or feed unnecessary paper.

  • Accept values from 0 to 255 only.
  • Do not build raw byte sequences from unvalidated user input.
  • Isolate and document model-specific sequences.