Field notes · POS
Toast POS: field notes from three years of operator conversations
What survived actual service, what created new friction, and which implementation details kept returning in operator conversations.
Read →Thread · Ongoing
POS systems
The service systems connecting floor, kitchen, payments, online channels, reporting, contracts, and the first ninety days after a switch.
Editor's field notes, drawn from three years of conversations with independent restaurant operators. As the verified community grows, these notes will incorporate direct member signal — with consent, always anonymized.
Member-only activity
Pseudonymous member discussions
Email-verified members read and contribute here under a recoverable pseudonym. Submissions appear to other members after editorial approval — your own pending posts stay visible to you right here in the thread.
Filed to this thread
Latest field notes
Field notes · POS
Toast vs Square: patterns from operators who switched both ways
A neutral comparison of restaurant depth, operating simplicity, contract structure, and the switching costs that matter after the demo.
Read →Field notes · Operations
The first 90 days on a new POS: pattern report
What operators wish had been sequenced earlier: menus, modifiers, printers, training, parallel runs, and the first live services.
Read →Field notes · POS
Interchange, assessments, and markup: the three layers under every swipe
Two of the three layers in every card fee are fixed by Visa and Mastercard and cannot be negotiated. Operators who understood the split negotiated the one layer that was actually theirs to negotiate.
Read →Field notes · POS
PCI DSS 4.0.1: what independent operators actually have to do now
Every "future-dated" requirement in PCI DSS 4.0 became mandatory in 2025. Multi-factor authentication, network segmentation, and quarterly scans are no longer optional for a restaurant that takes cards.
Read →Field notes · POS
When the internet goes down: what your POS actually does next
Modern cloud POS platforms keep selling through an outage — but a stored offline payment can still be declined once the connection returns. Operators are responsible for that gap either way.
Read →
Editor-curated at launch
Open questions in this thread
These prompts organize the next round of field notes. They do not represent live member activity or consensus. Members: any of them is a fine place to start a discussion.
Which hardest service workflows must be tested before signing?
How should menus, modifiers, kitchen routes, and permissions be cleaned before migration?
When does an integrated stack remove labor, and when does it create lock-in?
Which hardware reliability problems only appear during the busiest service?
What data, contract, and processor obligations determine the real cost of leaving?
Verified operators only
Join to add yours.
Membership is free. Applications are reviewed weekly, and vendors are declined.
Request to join →