Price entry checklist

Run this before publishing a new menu, after any bulk price change, and as part of the periodic menu review. It is deliberately mechanical — pricing errors are found by comparison, not by reading.

1. Completeness

• [ ] Every published item has at least one price.
• [ ] No item shows a format the house does not serve.
• [ ] Every item sold by the piece has a unit price.
• [ ] Every wine poured by the glass has a glass price, and every wine has a bottle price.
• [ ] Every large-format wine price corresponds to stock that exists.
• [ ] Each tasting menu has a menu price, and a pairing price only where a pairing is offered.
• [ ] Each set menu has a menu price.

2. Empty versus zero

• [ ] Formats that are not offered are empty, not 0.
• [ ] Any 0 present is genuinely a price of zero.
• [ ] No price field contains placeholder text left over from setup.

3. Formatting

• [ ] Currency symbol position is identical across every menu type.
• [ ] Decimal separator is identical everywhere.
• [ ] Trailing zeros follow one rule.
• [ ] Counts in portion prices — (6 unidades) — follow one rule.
• [ ] No price carries formatting that arrived from a spreadsheet by accident.

4. Accuracy

• [ ] Every price was compared line by line against the current printed card or the POS.
• [ ] The half portion / full portion relationship is deliberate on every dish that has both.
• [ ] Unit prices and portion counts are consistent with each other.
• [ ] Large-format wine prices are sensible against the standard bottle.
• [ ] Supplements inside set menus are stated where the choice is made.

5. Conditions

• [ ] VAT treatment is stated where guests need it.
• [ ] Minimum orders are stated on the items they apply to.
• [ ] Tasting and set menus state minimum diners and availability in the footer note.
• [ ] Measures — glass sizes, shot sizes, bottle volumes — are stated consistently, or not at all.

6. After a bulk change

• [ ] An Excel export was taken before the change and kept.
• [ ] A fresh export was taken after and compared against it.
• [ ] Only the intended rows changed.
• [ ] No duplicate items were created by titles that did not match exactly.
• [ ] The menu order was re-checked, since imports move matched items to the end.

7. Published result

• [ ] The public menu was read signed out, on a phone.
• [ ] Prices are legible without zooming.
• [ ] The same values appear in every published language.
• [ ] The site's page cache or CDN was purged if an old price persisted.
• [ ] Every circulating PDF was regenerated and replaced.
• [ ] Printed cards, if any, match the digital menu.

8. Ownership

• [ ] One person owns prices on this site.
• [ ] They know that an empty field and a zero are different.
• [ ] They know that a change is only live once it has been checked signed out.
• [ ] They know where the last verified export is stored.

A menu passes when a guest, the floor and the POS would all quote the same number for the same thing.