What it touches
Order items, note, contact, and fulfillment type.
Owner / operator side / Planned next
Print to kitchen or POS
Accepted orders can later be printed or forwarded to a restaurant-owned printer or POS surface.
For a pizzeria
This is the bridge from a direct online order to a paper ticket or POS flow inside the shop.
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 does not own
It does not replace payment or public discovery.
Current state
Planned next
not enabled
Current declared data-access summary: Order items, note, customer contact, and fulfillment type.
Read next
Do not stop at one module page.
See the main kitchen flow first
Printing is a support surface. The main operator story still starts with the kitchen queue.
Then see the fallback alert
If a print path fails or stalls, the operator alert module is the next useful fallback.
See who currently provides the tools
The provider page explains the current shared source behind the operator-side extras.
Technical identity
p4p.order.print
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.
Open provider page / Open GitHub module reference / Open GitHub provider reference / Open raw manifest
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/.