POS connection
The POS owns the official menu, prices and check. 4u Check reads from it before every payment and writes back to it after.
| 4u Check needs to | Why |
|---|---|
| Read the menu | Dishes, prices and options shown to guests match the till |
| Read tables and sections | Each QR code is linked to one POS table |
| Read a table’s open check | The bill a guest pays is compared with it line by line before payment |
| Send an order | QR orders reach the kitchen through the POS |
| Record a payment on the check | The till knows the bill is paid |
| Record a refund | Refunds show on the POS too |
| Get notified of changes | Webhooks or polling, so edits at the till are seen quickly |
When the POS cannot do something
Section titled “When the POS cannot do something”Not every POS lets a partner do everything. 4u Check reads what each POS can do and adapts, rather than pretending:
| If the POS cannot | 4u Check instead |
|---|---|
| Add a partner’s payment to an open check | Staff close the check at the till with a “4u Check” payment method, and 4u Check reads the check back to confirm it was closed for the amount paid by QR |
| Accept orders from a partner | Ordering is off; guests use 4u Check to pay only |
| Notify changes | 4u Check polls the open check |
Bill matching
Section titled “Bill matching”Before any payment, the POS check and the 4u Check bill must have the same items, the same totals and the same amount left. Rounding, charges and VAT are compared to the fils. If anything differs, payment is held and staff see why. See bill check.
Supported POS
Section titled “Supported POS”| POS | Status |
|---|---|
| Foodics | Sandbox adapter, connection and table links built and in review. See Foodics |
| Oracle Simphony, Lightspeed, Revel | Candidates with open APIs. Not started |

