Bluetooth Thermal Printing in Mobile Apps: Receipts and Labels
Why Printing Is Still a Core Mobile Feature
It is tempting to assume that paper is disappearing. Walk into any restaurant, pharmacy, courier hub or wholesale market in India and you will see the opposite. Customers expect a printed bill. Kitchens run on printed order tickets. Parcels need labels. Delivery agents hand over receipts at the doorstep. Field sales staff leave a printed order confirmation with the shopkeeper.
What has changed is the device doing the printing. The billing counter with a desktop computer is giving way to a phone or tablet paired with a small Bluetooth thermal printer. These printers are inexpensive, need no ink, run on battery and fit in a pocket or on a belt clip. For a business app, that makes reliable Bluetooth printing a feature customers will judge you on every single day.
It is also a feature that looks easy and is not. This guide explains how thermal printing works, the decisions you need to make when building it into an Android or iOS app, and the practical lessons that keep support calls low.
How Thermal Printers Work in Brief
A thermal printer has no ink or toner. It heats tiny dots on a print head, and special heat-sensitive paper turns dark where it is heated. Receipt printers commonly use paper rolls that are roughly 58 mm or 80 mm wide. Label printers use die-cut sticky labels with a gap or black mark between them so the printer knows where each label begins.
Two families of printer commands dominate:
- ESC/POS. A command language originally created by Epson and now imitated by a very large number of receipt printers. The app sends bytes that mean "bold on", "centre align", "print this text", "cut paper".
- Label languages such as TSPL and ZPL. Used by label printers. Instead of flowing text line by line, the app describes a label of a fixed size and places text, barcodes and boxes at exact coordinates.
Knowing which family your target printers speak is the first technical decision, because the two are not interchangeable.
Classic Bluetooth, BLE and the iOS Question
Bluetooth printers connect in one of two ways, and the difference shapes your whole project.
Bluetooth Classic (Serial Port Profile)
Many low-cost receipt printers use Bluetooth Classic with a serial profile. Android apps can talk to these freely. On iOS, however, Classic accessories generally need to be part of Apple's MFi accessory programme before a third-party app can communicate with them, and many budget printers are not.
Bluetooth Low Energy (BLE)
BLE printers expose a service the app writes data to in small packets. Both Android and iOS support BLE without special accessory certification, which makes BLE or dual-mode printers the safer choice when the app must run on iPhones and iPads.
The practical takeaway: if your users are mostly on Android, almost any ESC/POS printer can work. If iOS matters, shortlist printers that support BLE or are MFi certified, and test with the actual hardware before promising support.
A Real-World Style Example: A Quick Service Restaurant
The scenario below is illustrative. It describes how such a system could behave, not a reported result from a specific client.
Consider a quick service restaurant with two counters and a small kitchen. Staff take orders on Android tablets. Each order needs two printouts: a customer bill at the counter and a kitchen order ticket near the stove. The owner also wants a day-end summary printed at closing.
In the first version of the app, the tablet connects to the printer only when the cashier taps Print. Connection takes a few seconds each time, and during the lunch rush the queue grows. Sometimes the printer has gone to sleep and the first attempt fails silently, so the cashier taps again and two bills come out.
A better design keeps a background connection alive while the app is open, shows a small printer status icon on screen, and places every print request in a queue. If the printer is out of range or out of paper, the job waits and the cashier sees a clear message. When the connection returns, the job prints once. Kitchen tickets use a larger font and no prices. Bills include the GST breakup and a UPI QR code so the customer can pay by scanning the receipt.
In a setup like this, the time from order confirmation to printed bill might fall from several seconds to around one second, and duplicate or missing prints typically become rare. For a counter serving a long lunch queue, that difference is visible to every customer. Restaurants and cloud kitchens are a segment we look at closely in our work on foodtech app development.
Printing is part of the checkout experience. A bill that takes ten seconds and two taps to appear feels like a broken app, even if everything else is perfect.
Step-by-Step: Building Bluetooth Printing Into Your App
- Choose and buy the target printers. Pick two or three models your customers actually use or can easily buy, covering both paper widths if needed. Emulators do not exist for this work in any useful form. You need the hardware on your desk.
- Request permissions correctly. Newer Android versions use dedicated nearby-device permissions for scanning and connecting, while older versions tie Bluetooth scanning to location permission. iOS requires a usage description for Bluetooth. Ask at the moment the user sets up a printer and explain why.
- Build a simple pairing flow. Scan, show printers by name, let the user tap one, print a test page, and save it. Store the printer's address so the app reconnects automatically next time.
- Create a print service with a queue. All print requests should go through one service that holds the connection, sends jobs one at a time, and retries on failure. Screens should never talk to the printer directly.
- Design a receipt layout model. Describe a receipt as structured data: lines, alignment, bold, columns, dividers, QR codes. A formatter then converts this model into printer commands for a given paper width. This keeps layouts testable and lets one receipt design work on 58 mm and 80 mm paper.
- Handle text and languages. Built-in printer fonts cover basic Latin characters well. Hindi, Gujarati and other Indian scripts are often not supported by the printer's own fonts. The dependable approach is to render those lines as an image in the app and send the image to the printer.
- Send data in chunks. Printers have small buffers, and BLE has a limited packet size. Split data into small pieces with brief pauses, or use write-with-response where available, so a long bill does not get cut off halfway.
- Read printer status where possible. Many printers can report paper out, cover open or low battery. Surface these as plain messages such as "Printer is out of paper" instead of a generic failure.
- Add QR codes and barcodes. Most printers can generate these natively from a command, which is faster and sharper than sending an image. This pairs naturally with the flows in our guide to QR code workflows for ordering, payments and tracking.
- Test in real conditions. Try low battery, a printer several metres away, a phone call arriving mid-print, the app going to background, and a roll running out. These are the conditions your users meet daily.
Receipts Versus Labels
Receipts and labels need different thinking. A receipt is a continuous strip: content flows down and the length varies with the number of items. A label is a fixed canvas. Text that is too long must be shrunk, wrapped or cut, because it cannot spill onto the next label.
Label printing also needs calibration so the printer detects the gap between labels, and it demands precise barcode sizing so scanners can read the result. If your app prints shelf labels or parcel labels, test scanning them with the same devices your users will use. Our article on barcode scanning apps for fast stock counts covers the scanning half of that loop.
Cross-Platform Considerations
Flutter and React Native both have community plugins for ESC/POS and BLE printing, and they are a reasonable starting point. Plugin quality varies, though, and printers from different brands interpret commands slightly differently. Plan for some native code, or at least for forking and fixing a plugin, especially around connection handling and background behaviour.
Whatever framework you use, isolate printing behind an interface: connect, disconnect, status, print job. If you later add a network or USB printer, or change the plugin, the rest of the app stays untouched. Teams offering mobile app development for retail and field operations usually treat this hardware layer as its own module with its own test checklist.
Key Benefits of Getting Printing Right
- Faster checkout and dispatch. A persistent connection and a print queue remove the pauses that slow down counters and packing tables.
- Lower hardware cost. A phone and a portable printer can often replace a desktop billing setup, which matters for small shops and for staff who work on the move.
- Fewer support tickets. Clear status messages and automatic reconnection let users solve paper and battery problems on their own.
- Professional, consistent paperwork. Logos, tax details and QR codes are laid out the same way every time.
- Works without internet. Bluetooth printing needs no network, so billing can continue during an outage if the app stores data locally and syncs later.
- Flexibility for growth. A clean printing module makes it simple to add kitchen printers, label printers or new models as the business expands.
Common Pitfalls
- Supporting "all printers". Publish a tested list instead. It protects your reputation and gives customers a clear buying guide.
- Connecting on every print. It is slow and fragile. Keep the connection and reconnect in the background.
- Hard-coded layouts. A receipt built for 80 mm paper will look broken on 58 mm unless the layout adapts to width.
- Ignoring paper cost. Long receipts with large logos and wide margins waste paper. Offer a compact mode.
- No reprint option. Users need a simple way to reprint the last bill without creating a duplicate transaction.
Conclusion
Bluetooth thermal printing sits at the meeting point of software and the physical world, and that is why it deserves more care than a typical feature. Choose your supported printers deliberately, understand the difference between Classic and BLE before committing to iOS, route every job through a queued print service, and render regional languages as images when printer fonts fall short. Do these things and printing fades into the background, which is exactly where your users want it: a bill or label that simply appears, every time, the moment they tap the button.
Frequently Asked Questions
- What is ESC/POS and why does it matter for mobile apps?
- ESC/POS is a printer command language originally created by Epson and supported by a very wide range of receipt printers. A mobile app sends ESC/POS commands to control alignment, bold text, QR codes and paper cutting, so supporting it covers many common printers.
- Can an iPhone app print to any Bluetooth thermal printer?
- Not always. Many budget printers use Bluetooth Classic, which on iOS generally requires the accessory to be MFi certified. Printers that support Bluetooth Low Energy or hold MFi certification are the safer choice when iOS support is required.
- How do I print Hindi or Gujarati text on a thermal printer?
- Built-in printer fonts often do not support Indian scripts. The dependable method is to render the text as an image inside the app, using a font that supports the script, and send that image to the printer as a bitmap.
- Why do prints sometimes fail or get cut off halfway?
- Common causes are a sleeping or out-of-range printer, sending data faster than the printer buffer can accept, and connecting only at the moment of printing. A persistent connection, chunked data transfer and a print queue with retries typically resolve these problems.
- Does Bluetooth printing work without internet?
- Yes. Bluetooth is a direct link between the phone and the printer, so no network is needed. If the app also stores transactions locally and syncs later, billing can continue during an internet outage.