Food-Allergy Intelligence at the Point of Sale.
STRAIN is an allergy-management technology designed to bring menu, allergen, and modification guidance into the restaurant ordering workflow.
Actual screens from the STRAIN prototype environment. Shown for demonstration; not connected to a commercial POS.
Allergy information shouldn't be separated from the moment an order is taken.
When a guest reports a food allergy, employees often have to step outside the ordering workflow to find answers. Today that can mean relying on:
- Memorized allergen information
- Printed allergen guides and binders
- Leaving the POS to ask a chef or manager
- Manually interpreting ingredient lists
- Unclear modification options
- Inconsistent communication between front-of-house and back-of-house
STRAIN is designed to bring relevant allergy information closer to the ordering decision.
One allergy, followed from the ordering screen to the kitchen.
A guest reports a milk allergy. These are the actual screens from the STRAIN prototype, step by step.
-
Step 1
Select the guest's allergen
The employee identifies the guest's reported allergen during the ordering workflow.
Milk tagged for the seat in the prototype.
-
Step 2
STRAIN evaluates the menu
STRAIN evaluates operator-defined menu information against the selected allergen: menu items, ingredients, allergens, modifiers and preparation information.
-
Step 3
The menu responds
Each item shows one of three states, based only on the operator-provided item data.
Contains selected allergen. Dimmed, struck through, and cannot be added.Modification possible. Shows operator-defined guidance, such as "Ask for no feta cheese."Potentially suitable. No selected allergen is listed in the operator-provided item data.Soup & salads with Milk selected.
-
Step 4
Guidance follows the order
Operator-defined modification guidance can remain connected to the item during ordering. In the prototype, the note is added to the item automatically and stays editable by the employee.
-
Step 5
Allergy context reaches the kitchen workflow
STRAIN is designed to help maintain allergy context as the order moves from front-of-house toward kitchen operations.
STRAIN supports employee decision-making and communication. Restaurant and kitchen verification remains required. STRAIN does not independently guarantee that a menu item is safe for a guest with a food allergy.
See STRAIN in Action
A recreation of the prototype's milk-allergy example. Follow the six steps below; each one lights up as you complete it.
- 1Select an allergen
- 2STRAIN evaluates menu information
- 3Menu items respond
- 4Modification guidance appears
- 5Allergy context follows the order
- 6Kitchen-facing allergy communication
Soup and salads
Recreated from the STRAIN prototype using its sample menu data. The prototype supports other allergens; this demonstration is limited to the milk example. All allergen and modification data is operator-defined. Restaurant and kitchen verification remains required.
A More Consistent Allergy Workflow
Allergy handling shouldn't depend on which employee is on shift. STRAIN is designed to give every employee the same starting point.
Employees
Quick access to relevant allergen information during ordering.
- Less reliance on memorizing the menu
- A more structured way to handle allergy orders
- Support for training new employees
Operators
A more standardized workflow based on operator-defined menu and allergen information.
- Clearer front-of-house to back-of-house communication
- More consistent processes across shifts
- Allergen and modification data stays under operator control
Guest experience
A clearer and more consistent process for communicating food-allergy information.
- Clearer allergen conversations at the table
- Better visibility into potential menu options
- More informed ordering conversations
Designed to Complement the POS — Not Replace It.
STRAIN is designed to complement existing restaurant POS platforms — not replace them. It is being developed as a specialized food-allergy intelligence layer for restaurant technology ecosystems.
The POS stays the POS.
The POS remains responsible for its existing ordering, payment, routing, and kitchen workflows.
STRAIN adds a focused layer.
STRAIN's intended role is to provide focused allergy-management intelligence using relevant menu, modifier, ingredient, allergen, and operator-defined information.
Integration is defined together.
Data access, integration points, and where guidance appears would be determined with each platform's product and integration teams.
- Existing POSCore POS environment, unchangedPOS
- Menu + modifier dataAccess method determined in discoveryPOS
- STRAIN allergy intelligenceEvaluates items against the guest's selected allergensSTRAIN
- Employee guidanceItem status and operator-defined modification guidanceSTRAIN
- Existing order / kitchen workflowHow allergy context reaches the kitchen is determined with the POSPOS
What technical discovery would determine
STRAIN is seeking technical discovery with POS companies. STRAIN does not currently have access to any POS company's API, SDK, KDS, or internal systems. Each of these would be established together with the partner.
Discuss a POS Integration- Available API capabilities
- Menu and modifier data access
- Order-level or item-level metadata capabilities
- Potential UI integration options
- Kitchen and KDS communication possibilities
- Authentication and security requirements
- Partner certification requirements
- Sandbox and developer environment availability
Building the Allergy Layer for Restaurant Technology
We're exploring partnerships with restaurant technology platforms and operators interested in improving how food-allergy information is handled during the ordering workflow.
We welcome technical discovery conversations regarding APIs, menu and modifier data, order workflows, and potential pilot programs.
- 01, start hereTechnical discovery
- 02API and data feasibility
- 03Prototype integration
- 04Pilot location
- 05Operator feedback
- 06Broader deployment
Steps 02 through 06 are contingent on technical and commercial feasibility.
Built Beyond the Idea Stage.
Here is exactly what exists today, and what would require partnership and API development.
Working prototype Exists today
- Working: Allergen selection
- Working: Menu-level allergen response
- Working: Modification guidance
- Working: Order-level allergy context
- Working: Kitchen-facing allergy communication
Commercial integrations Requires partnership
Technical discovery required with POS partners.
The current POS-style interface is a prototype environment used to demonstrate the STRAIN workflow. The commercial vision is for STRAIN's allergy-management capabilities to integrate with established restaurant technology platforms.
Why STRAIN
STRAIN was created around a simple operational problem: restaurant employees should not have to rely entirely on memory, printed guides, or disconnected information when helping communicate a guest's food allergy.
The ordering screen is where that conversation turns into an order. STRAIN's approach is to bring operator-defined allergen and modification information to that moment, and to keep the allergy context attached as the order moves toward the kitchen.