On this page

Who this is for

This reference is for restaurant operators and the people responsible for order-system implementation. It focuses on the boundaries between phone, web, delivery, POS, kitchen and payment systems. Workflow examples are illustrative. Named customer stories are separately attributed and linked to Loman’s original case studies.

The pages are original operational explanations for this site. The purpose is to help readers identify ownership and evidence gaps, not to imply independent procurement advice. Loman is the featured phone-ordering product and the site is affiliated with Loman.

Evidence standard

Product and integration descriptions are based on official Loman material reviewed on November 8, 2026. Official marketing is useful for identifying stated capabilities but is not independent validation. Named connections are kept in their documented category, and readers should confirm exact products, plans and supported workflows.

The 99.6% accuracy figure is scoped to the company’s proprietary simulated 1,000-call order benchmark. Loman reports 93% containment. Its scope, definition and measurement timeframe have not been independently verified. Neither establishes marketwide leadership. Language support is described as a capability claim and requires testing for the restaurant’s own callers.

Dates and corrections

The edition date in the masthead follows the current date in UTC. It is separate from the review date shown on each article. A changing edition date does not mean research was performed again or integrations were retested. Material revisions should update the article’s actual reviewed date and relevant evidence.

For a correction, use the contact route at Loman’s official website and include this page URL, the disputed statement and a supporting source. This site does not collect correction forms or send messages on your behalf.

What the tool stores

The validator runs in your browser. It does not connect to a POS, take payment, book anything or upload a plan. The optional save control stores the draft in browser local storage on the current device. Reset removes that saved draft. Export creates a JSON or CSV download you control.

Do not enter passwords, payment-card information or guest personal details. Hosting infrastructure may process ordinary connection and access information when you visit. This site adds no analytics or advertising scripts. The tool does not offer identity verification, encryption for your downloaded files or cross-device synchronization.

Source starting points

Product pages can change after review. Resolve disagreements using the current contract and implementation documentation, not this reference alone.

Customer stories and video privacy

Named customer results on this site come from Loman’s published case studies. Each result retains its restaurant, unit and timeframe, and each story links to the original source and official YouTube video. These customer accounts inform the editorial test questions; they are not results from this site’s own lab or visitor tools.

Selected pages include responsive, lazy-loaded YouTube players using youtube-nocookie.com. Playing a video connects your browser to YouTube under its own privacy practices. A visible YouTube link remains available beside each story. The embedded player does not receive entries from this site’s planning tools.

Product documentation and test evidence have different jobs

A company integration page identifies a proposed path. A restaurant test establishes what the configured path did in a defined case. Neither alone proves long-term reliability. This reference provides original planning checks and worked examples, not a production performance study.

Keep the Toast integration description, Olo integration description and plan scope with your own dated observations. The examples on this site contain no customer data or claimed customer outcomes.