POS lanes, self-checkouts, electronic shelf labels, refrigerated cases and in-store screens all produce events your head office rarely sees in time. Publish them to one private MQTT broker and let store ops, facilities and your order apps subscribe to what they need.
No card required
POS, self-checkout, ESL base stations, scales, kiosks and refrigeration controllers each come with their own portal. Store ops logs into five tools to find out why a lane is down.
A frozen self-checkout, an offline payment terminal or a freezer drifting warm overnight is usually found when a customer complains or stock is written off — not when it starts.
Click-and-collect, ship-from-store and delivery apps depend on order status and stock moving in seconds. Polling the OMS from every app and store tablet is slow and costly at peak.
ConnectMQ gives you a private MQTT broker that store gateways, devices and apps reach with standard MQTT — so IT can add a store, a device type or a new app without another integration project.
A managed, private broker instance reachable over TLS. Store gateways and devices connect outbound — no inbound ports on the store network and no broker cluster for your team to patch.
A username and password for every store gateway or vendor integration, with per-topic ACLs, so a refrigeration contractor sees its own cases and nothing of your POS lanes.
Region, store, department and device in one namespace. Retained status gives a new dashboard every lane and case at once, and web and mobile apps subscribe over secure WebSockets.
Threshold rules on case temperatures, terminal heartbeats and device status raise alerts and notifications, and Last Will flags a device the moment it drops off the network.
Retailers usually start with one painful blind spot — offline payment terminals or warm freezers — then add store devices and live customer updates on the same broker.
Refrigeration, HVAC, ESL, digital signage, people counters and self-checkouts from every store on one live feed
Explore the use caseDevice health, cash and paper levels, tamper events and remote config for ATM and POS terminal fleets
Explore the use caseLive order status, delivery tracking, alerts and in-app updates pushed to web and mobile apps over secure WebSockets
Explore the use caseTemperature, door and location data from reefers, cold rooms and pharma shipments, with alerts on every excursion
Explore the use caseretail/eu/store-0412/pos/lane-03/status (retained)
retail/eu/store-0412/cold/case-07/temp
retail/eu/store-0412/esl/base-02/status (retained)
orders/ord-58213/statusHave each terminal or the store gateway publish a retained status to a topic such as retail/{region}/{store}/pos/{lane}/status, with a Last Will that marks it offline. Your store ops dashboard subscribes to retail/+/+/pos/+/status and sees every lane at once, and ConnectMQ rules can alert when a terminal goes silent.
MQTT over TLS with per-store or per-device credentials and per-topic ACLs is a solid foundation, and ConnectMQ provides all three. Keep cardholder data off the broker: publish device health, events and status, while payment processing stays in your payment stack and its compliance scope.
Yes. Browsers and mobile apps connect to ConnectMQ over secure WebSockets and subscribe to the order or store topics they are allowed to read, so “ready for pickup” or a picking update arrives in seconds. Your OMS publishes each update once, instead of every app polling it.
Both. REST suits request-response work such as placing an order or looking up a price. MQTT suits events from many devices and live updates to many screens: devices publish on change, connections survive flaky store WAN links, and any number of systems can subscribe without the device knowing.
Start on the Free plan — no card required. Connect one store’s devices and dashboards, then move to Basic or Scale when you go live. No overage charges, cancel anytime.
