Owner / operator side / Operator-side prototype

Scan a paper menu

The restaurant can scan a paper menu into draft catalog rows before a human review.

For a pizzeria

Useful when a shop starts from a printed takeaway card instead of rebuilding the whole menu by hand.

Where it fits

What the shop uses behind the counter

These are the restaurant-side tools for menu control, kitchen flow, stock, printing, and fallback alerts.

This page is the readable P4P explanation for one module. It is meant to be understandable before you open the raw manifest.

What it touches

Draft OCR item names, prices, categories, and source lines before catalog save.

What it does not own

It does not become catalog truth by itself and it is not a customer-facing menu.

Current state

Operator-side prototype

available in the pilot-node operator dashboard when enabled alongside the catalog editor

Current declared data-access summary: Draft item ids, names, prices, categories, and OCR source lines. Operator-only; does not write catalog truth by itself.

Read next

Do not stop at one module page.

See the catalog truth surface next

The OCR helper only creates drafts. The real local source of truth still lives in the catalog editor.

Then see the public result

After the operator reviews and saves imported items, the simplest customer-facing result is the plain online menu.

See who currently provides this stack

The provider page explains the shared reference layer behind the current public tools.

Technical identity

p4p.catalog.import.ocr

If you need the developer-facing version, open the GitHub module reference or the raw manifest. The public P4P page stays focused on what the module means operationally.

Contact

This module page is still part of the same narrow proof story.

Questions about this module, the provider layer, or the live-pilot boundary: hedegreen.research@gmail.com.

Public proof front door: https://pizza4people.com/.

Broader protocol-family direction: https://protocols4people.com/.