School nutrition software resources

What is Trinity POS?

Trinity POS is a multi-program school nutrition platform that connects cafeteria point of sale, eligibility workflows, parent access, and reimbursement claim worksheets. It is built for K-12 teams operating programs such as NSLP, SFSP, CACFP, and CEP from one system.

The design goal is that a meal served at the register is the same record that a claim worksheet counts, that a parent sees in their child’s history, and that an auditor can trace back to a determination. There is no nightly reconciliation between a POS and a separate back office, because there is no separate back office.

The meal programs a K-12 platform has to cover

Most districts do not run one program. They run several at once, sometimes at the same school, and the counting rules differ for each. A district can run these side by side in one Trinity tenant, and serves are never double-counted across programs.

• ✓NSLP — the National School Lunch Program, reimbursed by category (free, reduced-price, paid) from counts taken at the point of service.
• ✓SBP — the School Breakfast Program, with its own counts, its own worksheet, and severe-need rates where a site qualifies.
• ✓CEP — the Community Eligibility Provision, where a qualifying site serves every student at no charge and claims by an identified-student percentage instead of by category.
• ✓SFSP — the Summer Food Service Program, with summer sites, their own counting, and SFA-3 worksheets.
• ✓CACFP — the Child and Adult Care Food Program, with its own site records, meal counts, and compliance rules.

How a meal becomes a reimbursement figure

This is the path most evaluations actually care about, and it is worth understanding before comparing feature lists. Four things happen in order, and a platform that is weak at any one of them creates work for your staff at the other three.

• ✓A determination is made — through a household application, categorical eligibility (SNAP/TANF/FDPIR), or a direct certification file — and it carries an effective date.
• ✓A meal is served and recorded at the point of service, with the student’s current eligibility applied on the server and never displayed at the register.
• ✓Counts accumulate by site, by program, by category, by day — including operating days and enrollment, which the claim needs alongside the meal counts.
• ✓A claim worksheet is assembled with federal edit checks applied, so a count that fails a threshold is flagged before it reaches the state rather than after.

Getting your roster in

Nothing else works until the student roster is right, and roster work is where most implementations lose their first month. Trinity takes student data as a CSV or spreadsheet upload through an import wizard that maps your file’s columns to Trinity’s fields, normalizes grade values, previews exactly what will change before anything is written, and can revert an import that turns out to be wrong.

Schools that would rather not upload a file every time can drop their export on a scheduled SFTP pickup instead, and Trinity processes it on arrival. Either way, student IDs are keyed per school so two schools using the same numbering never collide.

Privacy and compliance are structural, not settings

Two rules shape a great deal of how the platform is built. First, a student’s eligibility category is never shown at the register — USDA requires no overt identification of free and reduced students (7 CFR 245.8), so the cashier screen and the confirmation a student sees are content-free about status. Second, every record belongs to exactly one district, enforced in the database rather than in application code, and changes are written to an append-only audit log that cannot be edited after the fact.

Terms that come up in every evaluation

Vendor comparisons and state guidance use these constantly, usually without defining them. They are program vocabulary, not product features.

• ✓Point of service — the moment a student receives a reimbursable meal. USDA requires counts to be taken here, not reconstructed later from sales or attendance.
• ✓Edit check — a required sanity test on a claim, such as comparing meals claimed against enrollment times an attendance factor. Failing one does not necessarily mean an error, but it does mean the figure has to be explained.
• ✓Direct certification — matching students to SNAP, TANF, or FDPIR records so they are certified for free meals without a household application.
• ✓Categorical eligibility — free-meal eligibility that follows from a household’s participation in an assistance program, or from foster, homeless, migrant, or runaway status, rather than from income.
• ✓Carryover grace window — the period at the start of a school year during which last year’s eligibility continues to govern while a new application is pending.
• ✓Identified Student Percentage (ISP) — the share of enrolled students directly certified, which determines a CEP site’s claiming percentages.
• ✓À la carte — individually priced items sold outside the reimbursable meal. They are never reimbursable and must be accounted for separately.

Explore Trinity POS