For the person who runs the shop. Setting up takes about fifteen minutes, and nothing here needs a developer — the one technical step, connecting your product data, has its own guide and can be handed to whoever looks after your POS.
Floor Lookup puts your catalog and live stock counts on your staff's handsets, so anyone standing next to a customer can answer "do you have this?" in under five seconds — by searching, scanning a barcode, or browsing.
Three things are worth knowing before anything else:
A site is a place stock can be: each shop, plus any warehouse or distribution centre you want associates to see counts for.
On Sites, add each one with a short id (main, wh-1), a name your staff
will recognise, and its kind (store or warehouse). Two things use these later:
The id cannot be changed later without re-mapping the connector, so pick something you can live with. The name can be changed any time.
On Staff, add each person with a display name and a staff code — the short
number they type to sign in on a handset (like 2214).
When you add someone, the dashboard shows a one-time setup code, valid for 7 days. Hand it to them; on the handset they enter their staff code, then the setup code, then choose their own PIN. You never know anyone's PIN, and that is deliberate — if someone forgets theirs, use Reset PIN on their row, which issues a fresh setup code the same way.
Disabling a staff member signs them out of every handset within minutes.
On Devices, press Generate enrolment QR. Any iPhone or Android phone with the Floor Lookup app scans it — camera app is fine — and the device enrols itself against your account. Each QR enrols one device; generate one per handset. The QR is valid for 7 days.
Once enrolled, a device stays signed up until you revoke it from the same page. Revoke a lost or stolen handset immediately: it loses access within minutes, and re-enrolling a found device is just a new QR.
Staff sign in on any enrolled device with their staff code and PIN — devices belong to the shop, not to a person.
Until you connect something, the app is an empty shell — the catalog and stock come from the system you already run.
On Connectors, add one. There are two kinds, and the page walks you through both:
This is the one step that may need whoever manages your POS — send them the API reference. It is written so you can also hand the same link, plus your push API key, to an AI agent and ask it to load or maintain your catalog for you.
New connectors start disabled so you can save a draft safely; enable it when the configuration is done. The Connectors page shows last run and last error per connector — if data looks stale on the handsets, look there first.
What your staff do with it, in the order they'll do it:
Billing in the sidebar shows where you stand:
| Symptom | First place to look |
|---|---|
| Counts look stale on handsets | Connectors — last run and last error on your connector |
| A product won't scan | It has no barcode in your source data — check it on Products |
| Someone forgot their PIN | Staff → their row → Reset PIN |
| A handset is lost | Devices → Revoke, immediately |
| A basket never reached the POS | Handoffs → open it — delivery attempts and errors are shown |
| Handsets suddenly signed out everywhere | Billing — the trial may have ended |
Anything else: the API reference has a troubleshooting section with the exact error messages the sync produces, or write to support.