Point of sale PRINTING

Print POS receipts and kitchen dockets from a cloud application

Route a completed sale or order to the receipt printer and kitchen printer selected for that site—without relying on the browser print dialog.

AppClickPrint cloud print gateway

Use the gateway that fits each customer site

Your API integration stays the same. The customer can connect Android, Windows or Linux depending on the printers and computers already available at the site.

Android
AndroidQR setup, network, paired Bluetooth and USB discovery without a dedicated PC.
Windows
WindowsDiscovers supported network printers without installing them. Existing Windows queues are optional and discovered too.
Linux
LinuxDiscovers supported network printers without CUPS setup. Existing CUPS destinations are optional and discovered too.

THE PRINTING PROBLEM

A cloud POS still needs a local printer connection

Web and mobile POS applications can process an order anywhere, but receipt printers usually live on a private network, USB cable or paired Bluetooth connection. Browser printing adds prompts and is difficult to route independently to front-counter and kitchen devices.

AppClickPrint separates the cloud transaction from the local connection. The POS backend sends each receipt or docket to a printer alias, and the site gateway delivers it locally.

Customer receipts

Print a sale receipt to a 58 mm or 80 mm thermal printer after payment is confirmed.

Kitchen and bar dockets

Route order content to a separate preparation-area printer based on venue configuration.

Collection tickets

Print order numbers, pickup details and QR codes for counter or click-and-collect workflows.

FROM APP ACTION TO PAPER

A workflow your application can own

Complete the order in your application

Only create the print request after your own payment and order rules say the receipt or docket is ready.

Choose the configured output

Use separate saved aliases for receipt, kitchen, bar or pickup printing rather than making staff choose every time.

Submit PDF or ESC/POS

Send binary ESC/POS safely as a file or padded Base64, or submit a PDF at the receipt width.

Handle outcomes honestly

HTTP 202 means queued. Use job webhooks when the POS UI needs a later completed or failed result.

WEB, MOBILE AND AI-BUILT APPS

Works with the stack you already use

Cloud POS products built in Replit, Lovable, Bubble, FlutterFlow, Base44, WeWeb, Bolt.new or a custom React/Next.js stack can keep printing behind the same authenticated backend used for orders.

Implementation checklist

Build printing as a tenant-safe backend capability, then expose simple controls in the customer-facing application.

  1. Never print a payment receipt merely because a frontend button was clicked; verify the order state on the backend.
  2. Save separate printer aliases for each operational destination at a venue.
  3. For ESC/POS, avoid applying copies twice when the command payload already repeats content.
  4. Use idempotency keys based on order, output type and print version.
  5. Make Reprint explicit and label duplicates where the business workflow requires it.
  6. Test cutting, feed distance, character encoding and logo density on the actual receipt printer.
Core integration pattern: provision the customer once, keep acm_ and acp_ keys on the trusted backend, provide permanent Add Gateway and Manage Gateways controls, let the user select an available printer, and submit jobs using its current alias.

Common questions

Can one order print to both the counter and kitchen?

Yes. Submit separate jobs to the configured receipt and kitchen aliases so each outcome can be tracked independently.

Can I send raw ESC/POS?

Yes, when the selected printer is configured with the Epson ESC/POS driver. Upload binary commands or send padded dataBase64.

Does the browser have to stay open?

No. The backend submits the job and the registered gateway receives it over its persistent connection.

More application printing ideas

From your app to their printer

Start with the included demo customer, connect a gateway and test the complete workflow before provisioning production customers.