Integrations
Bring operational counts into the kitchen — with a fallback you control.
Queux supports manual entry and CSV import. Live provider connections depend on documented access, suitable permissions, credentials and any required commercial agreement.
Three practical pathways
Queux remains usable without a live connection.
Choose the most reliable authorised source available to your service. The kitchen sees where each snapshot came from.
CSV import
Provider connector
Connection process
Permission before synchronisation.
A provider name alone is not an integration. Queux treats the external boundary as a reviewed implementation.
01
Confirm access
Verify that the provider supports the required data and that the organisation is authorised to use it.
02
Map deliberately
Match external sites, rooms and service fields to Queux without assuming names are stable.
03
Test safely
Run a connection test and review a preview before accepting operational data.
04
Monitor the source
Record sync attempts, results and external event identifiers; surface failures for manual follow-up.
Minimum useful data
The kitchen needs counts, not a duplicate enrolment system.
Connector design should request and store only the operational information the service has authorised for the kitchen workflow.
- External identifiers instead of unnecessary duplicated identity data
- Aggregate dietary summaries by default
- Encrypted recoverable credentials and hashed one-way secrets
- Signed webhooks verified before persistence
- Unique event identifiers to prevent replay
Manual continuity matters
If a provider is unavailable, delayed or not contracted, authorised staff can continue with manual counts or CSV. The source is labelled clearly so the kitchen does not mistake it for a current live sync.
Planning a connection?