Path 01
Manual entry
Available without a provider.
Enter aggregate room, meal, dietary and texture counts with an actor and timestamp.
Integrations
Connect the data your kitchen needs.
Use manual entry, CSV import or an authorised provider connection, with a reliable fallback available at every site.
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.
Count intake / choose one
Source register
Path 02
CSV import
Available without live API access.
Upload a validated file, preview mappings and resolve errors before accepting the snapshot.
Path 03
Provider connector
Conditional on provider access.
Enable only after suitable documentation, permission, credentials and agreements are in place.
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
Planning a connection?