What it touches
Order summary, public order status, estimated ready time, payment mode, and board target.
Counter / pickup side / Operator-side prototype
Ready-for-pickup board
A simple local screen can show which direct orders are accepted or ready at the counter.
For a pizzeria
Gives the shop a cheap customer-facing pickup signal without exposing the full operator dashboard.
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 take new orders or replace the kitchen queue.
Current state
Operator-side prototype
builtin local counter surface when enabled and configured
Current declared data-access summary: Order summary, public order status, estimated ready time, payment mode, and configured pickup-board target.
Read next
Do not stop at one module page.
Start with the customer order surface
The pickup board only matters after the customer has first seen the direct menu and submitted an order.
Then see the status source behind it
The local pickup board is easier to judge when you compare it to the public order-status page.
See the kitchen queue behind the board
The board only stays truthful if the operator queue is still the thing driving state changes.
Technical identity
p4p.pickup.board.basic
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/.