BipOrder connects to your POS to sync your products and automatically push orders placed via QR, kiosk or server app. No double entry, your reports stay centralised.
Positioning: BipOrder isn't a certified POS. Your POS keeps the fiscal recording role (NF525 in France); BipOrder handles the digital layer (QR, kiosk, KDS, reservations) and pushes orders to it.
Before you start
Check that you have:
- An active POS subscription allowing API access.
- Admin access to your POS (to generate the API key or authorise OAuth).
- Your menu already configured in the POS (BipOrder imports from the POS, not the other way around).
Step 1: generate the API key
- Log into your POS dashboard.
- Go to Settings > Integrations > API.
- Generate a new API key and name it "BipOrder".
- Copy the key (often shown only once).
In BipOrder: Settings > Integrations > Select your POS > Paste the key > "Test connection". You should see "Connected" in green with your venue name.
Step 2: OAuth authorisation (depending on POS)
- In BipOrder: Settings > Integrations > Select your POS > "Connect".
- You're redirected to your POS to authorise access.
- Approve the permissions (menu, orders, tables).
- You're automatically redirected back to BipOrder, connection established.
Initial menu sync
Once connected, run "Import menu". BipOrder retrieves your categories, products, options and prices. Allow 1–5 minutes depending on menu size (up to 1000 products).
- Products are matched by POS ID — no duplicates.
- Options are imported with their groups and prices.
- VAT rates are pulled from your POS.
- You can add photos and descriptions in BipOrder without touching the POS.
Automatic order push
From connection onwards, every BipOrder order is pushed to your POS:
- Dine-in (QR): sent on payment (the customer pays on the phone).
- Kiosk: sent on creation.
- Click & collect / Delivery: sent on creation.
- Floor (server app): sent on creation.
Options and extras land in the ticket's "remark" field (not every POS supports nested modifiers). Readable in the kitchen, no mapping issues.
Troubleshooting
Connection broken
The API key may have been revoked on the POS side, or your POS plan has changed. Regenerate a key and reconnect.
A product isn't syncing
Check it's active in the POS and has a price. "Draft" products are skipped by the API. Re-run "Sync menu" from BipOrder.
Order isn't reaching the POS
See Settings > Integrations > Send log. You'll see each push, its status (success/failure) and the reason. 95% of failures come from a BipOrder product that has lost its POS ID (deleted in the POS, still shown in BipOrder).
Your POS not supported yet?
Other POS integrations are under evaluation. Contact us via the chat to signal your need — we prioritise based on demand.