Use this checklist for shipping-label printers, desktop barcode printers, portable units, embedded thermal modules, printer mechanisms, controller boards, cutters, labels and OEM or private-label projects. Workflow compatibility must be specified; a printer that produces the right label can still fail the intended system.
1 · PRINT METHOD AND APPLICATION
State whether the project requires direct thermal or thermal transfer printing. Describe the actual use: shipping labels, warehouse barcodes, mobile field labels, instrumentation, kiosks, measurement equipment or an embedded OEM device. Include the expected daily print volume and operating environment.
2 · PRINT WIDTH, RESOLUTION AND SPEED
Specify the maximum media width, printable width, required resolution and target print speed. Common values such as 203 dpi, 300 dpi or 600 dpi should be chosen around barcode density, font size, graphics and application needs rather than marketing preference.
3 · MEDIA HANDLING
Provide label width and length, liner type, maximum roll diameter, core size and sensing method. Confirm gap sensing, black-mark sensing, continuous media, fan-fold feeding, tear bar, peeler or cutter requirements. Test with the intended labels before approving the complete solution.
4 · CONNECTIVITY
List every required interface: USB, Bluetooth, Wi-Fi, Ethernet, serial or another connection. Define the target device and workflow for each interface. A Bluetooth connection alone does not establish compatibility with the buyer’s application.
5 · COMMAND LANGUAGE, DRIVERS AND SDK
State whether ZPL, TSPL, EPL, ESC/POS or another command set is required. Identify Windows, macOS, Linux, Android or iOS support; driver versions; SDK languages; sample applications; API documentation and update responsibility. Ask for a demonstration using the intended software environment.
6 · FORM FACTOR AND POWER
Define desktop, portable or embedded format; enclosure dimensions; mounting points; power adapter; voltage; battery capacity; charging method; display and key requirements. For an embedded module, include mechanism, board, sensor, cutter and space-envelope requirements.
7 · OEM, BRANDING AND PACKAGING
Clarify logo method, enclosure color, firmware identity, startup screen, label, box, manual, accessories and barcode. Ask whether firmware and board revisions will remain compatible across repeat orders.
8 · ORDER AND SUPPORT PLAN
Provide sample quantity, pilot order, annual estimate, destination and launch timing. Confirm production lead time, warranty handling, spare parts, cutter and mechanism life, component availability and engineering support.
EVIDENCE TO REQUEST
• Demonstration print using the intended label
• Driver, SDK and command-language list
• Connectivity demonstration
• Mechanism and cutter life-cycle information
• Compatible media specification
• Certification scope where applicable
• Component and firmware revision policy
• Warranty and spare-parts plan
• Packaging contents and dimensions
COMMON RISKS
A device can print a sample successfully but fail because the driver, command language, sensing method or SDK does not match the buyer’s workflow. Media claims may exclude the intended roll diameter or liner. OEM projects also face board, firmware and mechanism changes after the first order, so revision control must be discussed early.
COPY-READY RFQ EXAMPLE
Product: 4-inch desktop shipping-label printer.
Resolution: 203 dpi.
Connectivity: USB and Bluetooth.
Compatibility: Windows driver plus Android SDK.
Media: 100 × 150 mm shipping labels, gap sensing.
Program: 300-unit private-label trial order for a European fulfillment equipment distributor.
Evidence requested: demo print, driver and SDK list, Bluetooth demonstration, life-cycle information, certification scope and packaging proposal.
NEXT STEP
Review the full Sourcefield industry guide at www.yaiopc.com/industries/thermal-printing or submit a sourcing brief at www.yaiopc.com.
Last reviewed: 30 September 2026