QR & Barcode Label Generator for ERPNext

ECOSIRE builds a proper Frappe app — its own module, DocTypes, and hooks.py doc events — installed onto your ERPNext bench so labeling becomes a first-class part of your operation. At the center is a Label Template DocType where you define symbology (Code128, EAN-13, UPC-A, QR, DataMatrix, GS1-128, GS1 DataMatrix), physical dimensions, DPI, and the field bindings for whatever you're labeling. Generation runs server-side through whitelisted methods using proven libraries (python-barcode, qrcode, and treepoem/Zint for GS1 symbologies), so barcodes carry correct quiet zones and check digits rather than being drawn by a browser. A Label Print Job DocType captures bulk requests: select any set of Item, Batch, Serial No, Stock Entry, Delivery Note, or Warehouse records, choose a template, and the app fans out one label per unit — respecting qty on stock documents so a receipt of 50 units yields 50 serialized labels.

Output is where this stops being a print-format toy. The app generates native ZPL (and optionally EPL/TSPL) streamed straight to networked thermal printers, so a Zebra prints at its rated speed with crisp, scanner-grade bars — no PDF rasterization in between. For desktop and office printers we still produce pixel-accurate PDF label sheets via a Frappe Print Format. GS1-compliant encoding is handled properly: GTIN-14 with computed check digit, AI (01), (10) batch, (21) serial, (17) expiry pulled from the Batch expiry date, all assembled with the correct FNC1 separators so your labels pass a verifier and read on WMS and retail scanners. Client Scripts add "Print Label" buttons directly on the Item, Batch, Serial No, and Stock Entry forms; a hooks.py on_submit doc event can auto-queue labels when a Purchase Receipt or Stock Entry is submitted; and a scheduler event can batch-generate reprints overnight. Everything is permission-aware — access to templates, print jobs, and printer definitions is governed by dedicated Roles and standard ERPNext role profiles — and every label endpoint is exposed on the Frappe REST API so a scan gun app or MES can request a label programmatically.

Because this is build-to-order, we do not hand you a generic download. After a short scoping call we confirm exactly which documents you label, your symbology and GS1 requirements, your printer models and label stock, and your ERPNext version (we support Frappe/ERPNext v15 and v16). We then build the app against your target version, test it on a staging bench with your own item and batch data, run UAT with your warehouse team, and install it on production with a rollback plan. Typical delivery is 2 to 4 weeks from confirmed scope. You receive the full source code and git repository so you are never locked in.