Skip to content
Queux

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.

Manual, CSV and authorised provider pathways connecting to Queux

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.

Manual entry

Available without a provider. Enter aggregate room, meal, dietary and texture counts with an actor and timestamp.

CSV import

Available without live API access. Upload a validated file, preview mappings and resolve errors before accepting the snapshot.

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.

  1. 01

    Confirm access

    Verify that the provider supports the required data and that the organisation is authorised to use it.

  2. 02

    Map deliberately

    Match external sites, rooms and service fields to Queux without assuming names are stable.

  3. 03

    Test safely

    Run a connection test and review a preview before accepting operational data.

  4. 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?

Tell us the provider, data pathway and sites involved.

Contact Queux