Download Receipt Studio · Product website · Contribute
Receipt Studio is a local-first Windows desktop point-of-sale and structured thermal-receipt designer. It manages shops, products, customers, sales, templates, and printers without an external database or cloud account. It supports Rongta-compatible ESC/POS output over raw TCP, installed Windows printers, receipt-width PDF export, backups, and diagnostics.
Completed sales receive collision-checked random receipt identifiers rather than reusable sequential numbers. Payment methods can be managed under Settings → Payment methods. QR blocks generate genuine scannable codes in the designer, PDF output, system printing, and ESC/POS printing; their payload can contain the receipt number, total, shop name, or a custom variable-based value.
An XML-formatted project and release reference is available in README.xml. The project is released under the MIT License.
Receipt Studio also supports fixed-size product-label design and printing. Label profiles can use Windows-installed USB printers or raw network ZPL/TSPL printers. Included media presets are 4×6, 4×4, 3×2, 2×1.5, and 2×1 inches plus common metric sizes. Width and height can always be entered manually for custom sheets. Label printers are intentionally separate from POS receipt printers.
USB barcode scanners work directly as keyboard-style input devices. On New Sale and the Products list, scanning works without clicking the search box; an exact barcode followed by Enter adds or finds the product. In Add/Edit Product, use the scanner button beside Barcode so the form knows where to place the scanned value. Duplicate product barcodes are rejected.
Per-shop loyalty rules define how spending earns points and how points convert to a checkout discount. Each sale records points earned, redeemed, reversed, and the resulting balance. The receipt designer includes an optional Loyalty points block. Sales History supports item-level refunds and replacements; these create new linked transactions, preserve the original receipt, update stock, and reverse applicable points.
Explore the product, printer options, label designer, and latest Windows download at reciept-studio.ytosko.dev.
- Windows 10 or 11, 64-bit
- Node.js 22 and npm for development
- For network printing, the computer and printer must normally be on the same local network
- For USB/system printing, install the printer's Windows driver so the device appears in Windows
npm install
npm run dev
npm run lint
npm run typecheck
npm run test
npm run test:e2e
npm run build
npm run distnpm run dist creates an NSIS installer and portable executable under release/. Production renderer, Electron main-process, and preload files are generated under dist/.
- Run every validation command above.
- Update the version in
package.json. - Run
npm run dist. - Create a tag such as
v1.0.0and push it to GitHub. - Create a GitHub Release for that tag.
- Attach the Setup and Portable executables from
release/. - Add release notes covering features, fixes, data compatibility, and known printer limitations.
For public distribution, Authenticode-sign the executables so Windows can identify the publisher and SmartScreen warnings are reduced.
Data is stored as readable, validated JSON under Electron's userData/data directory (normally %APPDATA%\Receipt Studio\data). Writes use a temporary file and atomic rename. Malformed files are copied to backups before a valid default replaces them. Automatic backups rotate to the latest ten.
Use Settings → Export backup to copy a complete backup folder. Import backup validates every collection before replacement and creates a safety backup. To reset safely, close the application, export or copy the entire user-data folder, then rename the original folder; do not delete it until the replacement starts correctly.
Receipt Studio supports common USB barcode scanners without scanner middleware. At checkout, an exact barcode followed by Enter adds the product and repeated scans increase its quantity. Completed sales deduct product stock. Product-backed sale quantities must be whole numbers and cannot exceed available stock.
Configure loyalty under Settings → Loyalty points. Points are awarded in complete spending groups after discounts and point redemption. Refunds reverse the applicable points, and a complete return reverses any remaining points originally earned by that sale.
New Sale uses a two-column workspace: the editable cart table stays on the left, while customer, receipt, payment, totals, and loyalty controls stay in Checkout on the right. Product search opens an autocomplete overlay with the 15 best name, SKU, barcode, or category matches, so large catalogs do not render as a product grid. Enter a valid number of available points and choose Redeem to apply the discount; Remove cancels it before checkout.
Open a normal sale in Sales and choose Refund or Replace. Select the returned quantities, provide a reason, and decide whether usable items return to stock. A replacement also selects the outgoing product and calculates the price difference. Every return receives a new unique receipt number linked to the original transaction.
New installations start without a printer profile because printer models, connection methods, IP addresses, encodings, and paper sizes differ. Open Printers, add a receipt printer, choose Network (raw TCP), and enter the address reported by your printer or router. For a Rongta RP336UE/RP336UV, port 9100, 80 mm paper, 72 mm printable width, and 48 characters per line are common starting values, but verify them against your hardware.
Verify the printer's IP from its self-test/configuration page or router, then test Windows connectivity:
Test-NetConnection 192.168.68.68 -Port 9100If it fails, confirm both devices are on the same LAN, the address has not changed, port 9100/raw printing is enabled, client isolation is off, and Windows Firewall or endpoint security is not blocking outbound TCP. Avoid broad network scans; set the known address explicitly.
Use Print test on the printer profile, choose a saved receipt template, and print it with sample customer and sale data. The test uses the same rendering and printer-delivery path as a real sale but does not create a sale record. A successful raw TCP write means the computer delivered bytes to the socket; it does not prove paper physically printed. Paper, cover, firmware, queue state, encoding, and printer command compatibility still require real-hardware verification.
Install the manufacturer's Windows driver, add or edit a printer profile, and select Windows / USB system printer. Use Refresh printers to discover installed devices and select the exact printer from the dropdown. System mode uses Electron's Windows printing path. Missing or renamed devices are reported; raw USB VID/PID access is intentionally not required.
Create a printer profile with type Label printer, then choose either a Windows/USB system printer or a raw network connection. Network label profiles support ZPL and TSPL/TSPL2. Configure resolution, orientation, label gap, darkness, and media size.
Open Label Templates to create a fixed-size price-tag design. Product name, price, SKU, stock, barcode, and QR fields are filled automatically from the selected product; custom text, boxes, and dividers are also available. Elements can be dragged, resized, rotated, and positioned using exact millimeter values. Once a template exists, use Print label beside any product and choose both the label template and label printer. Printer tests use the same templates with sample product data. A custom sheet is created by entering any positive width and height in millimeters.
POS checkout lists receipt printers only. Label printers cannot be selected for sales or receipt-template tests.
Encoding presets for ESC/POS receipts include common CP437/CP850-family pages, Windows-1252, ISO-8859-1, GB18030, Big5, and Shift-JIS. Actual character availability still depends on printer firmware.
src/main: Electron lifecycle, typed IPC, JSON repository, backup/diagnostics, PDF, ESC/POS and printer servicessrc/preload: narrow context-isolated renderer APIsrc/renderer: React/Tailwind UI, Zustand state, POS, history, management screens and dnd-kit designershared: Zod schemas, defaults, integer-money utilitiestests: Vitest unit coverage and Playwright Electron workflow
The canonical receipt line model powers preview-oriented rendering, HTML/PDF, system printing, and ESC/POS generation. Renderer code has no Node, filesystem, or socket access.
- Actual print mechanics, raster logo fidelity, barcode/QR firmware compatibility, label calibration, and character encoding require verification on the physical printer.
- USB uses the Windows-installed printer path, not direct USB device access.
- Network socket success cannot confirm physical paper output.
- Receipt PDF height is derived from content and may vary slightly by Chromium version.