FeedbackHub
For the POS system that has no API and never will
Plenty of point of sale and back-office systems offer no webhooks, no integrations and no realistic prospect of either. If your staff complete sales in a browser, the FeedbackHub Connector extension can watch that screen and fire a feedback request at the moment a sale is finished.
If a person can see it, the extension can use it
The extension is a Chrome add-on installed on the machines your staff use. It is paired to one specific domain, which is the address of your POS or admin system, and it does nothing at all on any other website.
On that domain, it watches for the triggers you configure. Usually that is a click on the checkout, save or complete button. It can also watch for the browser landing on a particular URL, such as an order confirmation page. When a trigger fires, the extension reads the customer's details from the page and sends them to FeedbackHub, which handles the request from there.
The customer sees nothing different at the counter. The staff member does nothing extra. The request goes out on its own.
Pairing a till in five minutes
Register the extension in FeedbackHub
In your account, register an extension against the domain of your POS system. You receive a pairing key, which is what links a specific browser to your account.
Install and connect on the till
Install the extension in Chrome on the machine, click its icon, paste the pairing key and connect. The backend address is built into the extension, so there is nothing else to type.
Configure the triggers centrally
Back in your account, add the triggers: the CSS selector of the button that completes a sale, or a URL fragment that appears on the confirmation page. Optionally point at the page elements that hold the customer's email, name and order number so those travel with the request.
Roll it out to the other machines
Repeat the install on each till. Every browser keeps its own installation identity, so pairing a second machine never disconnects the first. Triggers are configured once and apply everywhere.
Do not know the CSS selector for your checkout button? Neither do most people. We work it out during setup.
Narrow by design
An extension that watches web pages deserves scrutiny, so it is worth being precise about what this one does.
It exits immediately on any host that is not the domain it was paired to. On other websites, including everything else your staff might open on that machine, the script stops before it reads anything. On the paired domain, it reads only the specific elements you nominated in the trigger configuration.
Configuration is pulled from the server every fifteen minutes, which means changing a trigger does not require touching a single till. Revoking an extension in your account invalidates its session token, and the next configuration poll disconnects that machine.
- Active only on the paired domain, inert everywhere else
- Reads only the page elements named in your trigger configuration
- Configuration polled centrally, no visits to individual machines
- Revocable per installation from your account
- Each till holds its own installation identity and token
Duplicate protection at three levels
A checkout button can be clicked twice, a page can reload, a staff member can go back and re-save. Without guards, that means a customer gets messaged repeatedly about one purchase.
The extension applies a short in-page debounce so rapid repeat clicks count once. The server applies a separate event deduplication window on top of that. And the dispatch layer itself deduplicates by customer contact details before anything is sent.
Three independent checks, because the failure mode here is annoying real customers and it is not worth risking.
Where the extension is the right answer
Browser-based POS
Cloud tills that run in Chrome, where the vendor offers no webhook and support has been vague about it for two years. The extension gives you the trigger the vendor never built.
Back-office and invoicing screens
Systems where a staff member saves an invoice or closes a job. The moment of saving is a reliable signal that the work is finished and the customer can be asked about it.
Specialist trade software
Garage, clinic, salon and workshop systems are often locally dominant, browser-based and closed. Those are exactly the cases where an integration will never exist and a screen-level trigger is the only practical route.
When not to use it
If your platform offers a webhook, use the webhook. It is more reliable, does not depend on a browser being open, survives interface changes, and needs no software on your machines. The extension exists for the cases where that option is genuinely unavailable.
What can break it
If your POS vendor redesigns the checkout screen, the CSS selector pointing at the old button may stop matching. The fix is to update the selector centrally, which takes a minute and does not involve visiting any tills. Watching your integration event counter is how you spot it quickly.
Manual sending as an alternative
Not every counter suits a fully automatic trigger. Where a staff member should decide case by case, the connector can add a button to the screen instead, so the request is sent deliberately rather than on every sale.
This suits businesses where a single sale record can cover several very different situations, or where staff know that a particular customer should not be messaged. It trades some volume for judgement, and in some settings that trade is worth making.
Both modes apply the same protections. Repeat sends for the same invoice are blocked, and a configurable gap prevents the same customer being asked again too soon, which matters in businesses where regulars come in weekly.
Rolling out across several sites
One integration can serve many machines. Create it once, select the shared feedback form, and use the same install key on each cashier PC. Every browser receives its own token, so tills can be added and removed without disturbing the others.
If a key is ever lost or a machine leaves your control, rotating the key revokes every installation paired with the previous one, and the tills are re-paired with the new key. It is deliberately blunt, because the alternative is leaving an unknown machine connected to your account.
Tell us what POS you use
Send us the name of the system, or a screenshot of the checkout screen, and we will tell you whether the extension can drive it and what setup would involve.