Enterprise DNA

Instead of Chomp

Stop renting Chomp. Own your kitchen records.

We build your version around your food control plan, map and check your Chomp history, and run it for you. Your checks, corrective work and verification evidence stay in a database you own.

Chomp lists NZ$959 paid annually or NZ$92 a month, excluding GST. Multiple kitchens are quoted separately.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What the subscription covers

Compare the kitchen workflow, not just the annual bill

Chomp bundles a device app, management tools, training and audit reports. The free base here gives a trusted operator the records and recurring reviews. Your custom version adds the working tools your kitchen needs.

paid

An annual or monthly plan

Chomp lists NZ$959 paid annually or NZ$92 monthly, excluding GST. This is a modest bill for one kitchen, so ownership and fit matter more than a large savings promise.

storefront

A quote for multiple kitchens

Chomp asks businesses with more than one venue to talk to its team. Compare your actual quote with the scope of your own version.

dashboard

Task and user management

Chomp includes a management dashboard for tasks, users, training and reporting.

school

Food safety training

Training is included with Chomp. The free base here records training evidence and review dates. It does not supply a training course.

description

Audit reports

Chomp includes audit reports. Here, verification preparation draws on your checks, corrective records and training evidence, with original reports kept in your archive.

sensors

Optional temperature loggers

Chomp lists logger hardware at NZ$265 each and an annual subscription of NZ$39 per logger, excluding GST. Sensor collection is a separately scoped connection in your custom version.

Your own working records

From a missed check to a documented outcome

Kitchen round

See what has not been checked

Start from the schedule and limits your operator sets from the actual food control plan.

  • check Checks due across your kitchens
  • check The last recorded check and next due time
  • check Equipment and measurement limits beside each task
  • check A question of your own that joins the round with overdue work

Corrective work

Keep the response beside the failed check

Name the owner, record containment and follow the action through to its actual outcome.

  • check Failed checks with no linked corrective action
  • check Owners and due dates for outstanding work
  • check Resolution and prevention recorded before closure
  • check Repeat failures grouped by task across the recorded history

Verification preparation

Find gaps before preparing the records

Bring the evidence together for the responsible operator to review with the verifier.

  • check Checks missing an operator or result
  • check Staff with no current training evidence
  • check Equipment with a missing or overdue calibration date
  • check Printable verification, delivery and corrective registers in your business name

Record ownership

Keep the original when a record is corrected

Your working database and original archive stay under your control.

  • check Corrections add a record and retain the original
  • check Each check retains the limits used when it was recorded
  • check A reviewed mapping brings historical checks across
  • check Open records for your own reports and future connections

Make it yours

Design your own Chomp replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Chomp. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your Chomp replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your Chomp data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Food Control Plan for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Food Control Plan for Claude Code

Connected to your own database

Which kitchen checks are overdue?

Harbour Kitchen

Task
Opening pest inspection
Overdue
true

Harbour Kitchen

Task
Sanitise prep bench
Last checked
2026-10-02 03:13 UTC
Next due
2026-10-03 03:13 UTC
Overdue
true

Harbour Kitchen

Task
Walk-in temperature
Last checked
2026-10-02 03:13 UTC
Next due
2026-10-03 03:13 UTC
Overdue
true

Hilltop Catering

Task
Prep fridge temperature
Last checked
2026-10-02 21:13 UTC
Next due
2026-10-03 21:13 UTC
Overdue
true

Ask it anything

Ten questions across your kitchen records

These answers run on the demo records today. Build the reviews your operator needs around your own history.

chat_bubble Which checks are late at each kitchen?
chat_bubble Which tasks have repeated failures?
chat_bubble Which failed checks have no corrective action?
chat_bubble Who owns overdue corrective actions?
chat_bubble Which records lack an operator or result?
chat_bubble Which people have no current training evidence?
chat_bubble Which equipment needs a calibration review?
chat_bubble Which deliveries remain held or were rejected?
chat_bubble Which verification follow-ups are overdue?
chat_bubble Which kitchens have upcoming verification and unresolved failures?

Switching

How to switch from Chomp

A move involves exporting and reviewing your records, mapping the checks you want to bring across, and testing the new process before you stop using Chomp.

  1. 1

    Export and keep your records

    Chomp documents audit reports that you can select by date range or task, but its native spreadsheet layout has not been verified. Ask Chomp what export formats your account allows, usually CSV or Excel, and keep the original reports and archive. Decide which check history to bring across. Attachments and sensor history need separate handling.

  2. 2

    Prepare a test import

    Map the checks you want to bring into the supplied CSV layout, then have a person review the mapping against the Chomp source. Only reviewed, mapped check records can be imported. Start with a dry run, which tests the prepared records without importing them. Do not assume other Chomp history will transfer automatically.

  3. 3

    Review the import findings

    Check what the dry run flags and compare its record counts with the source reports. Resolve mapping or record issues before importing. A bad row can stop the whole import, so do not proceed until the prepared checks have been reviewed and the counts make sense. Keep the source reports available for comparison.

  4. 4

    Run both systems briefly

    After importing, keep Chomp available while the operator records real work in the new system for a short period. Compare the checks and results with the Chomp source, and confirm the staff workflow and configured plan details are right. The base system is for a trusted operator, so agree who records work before making the switch.

  5. 5

    Switch off Chomp

    Stop using Chomp only after the operator has checked the new records and confirmed the day to day process works. Keep the original reports, exports and attachments in your archive, and preserve records for the required retention period. The new system does not certify compliance or replace your food control plan or verifier.

construction

Where the real effort goes

The main work is usually mapping your own fields and rules, then deciding how much Chomp history to bring across. Attachments and sensor history need separate handling, and the base import covers reviewed mapped checks only. If you have Enterprise DNA install and run your custom version, they handle the mapping and review work for your version.

Not ready for a call?

Get your Chomp switch plan by email

We will send you the step-by-step plan for moving your business off Chomp, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Choose who builds and runs your version

Open source

Do it yourself

Free, MIT licence

  1. 1 Clone food-control-plan-for-claude-code and run npm install, npm test and npm run demo.
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor and read AGENTS.md.
  3. 3 Archive your Chomp audit reports, review the CSV mapping and run import chomp with --dry-run.
  4. 4 Use your own database and set tasks, limits and dates from your actual food control plan.
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your kitchen fields, plan rules and document layouts
  • check Your Chomp records mapped, checked and brought across
  • check A web front end, tablet entry or sensor connection scoped for your kitchen
  • check A different technology stack when your operation needs one
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a monthly retainer

  • check Installed and operated through Omni by Enterprise DNA
  • check Your checked records in a database you own
  • check Access, backups and connections scoped around your operation
  • check Ongoing changes as your food control plan and kitchen routines change
Book a call

Questions

Instead of Chomp, answered

Is this an approved food control plan? expand_more

No. It is a records system for the plan your business follows. The responsible operator and verifier confirm the applicable rules and required evidence. Record checks flag gaps and configured reminders. They do not certify compliance or decide food is safe.

Can we bring our Chomp history across? expand_more

Yes, after mapping and review. Chomp describes audit reports selected by date range or task. We have not verified a native spreadsheet layout. Keep your original reports, map the checks and compare them with the source before importing. Enterprise DNA handles that work for your custom version. Attachments and sensor history need separate handling.

Will it work on the kitchen tablet and collect temperatures? expand_more

Tablet entry and automatic sensor collection are scoped additions to your custom version. We agree the actual staff workflow before switching. The free base supports a trusted operator recording work and producing read-only reports.

What does the free version cost to keep? expand_more

The software is free under the MIT licence. You handle installation, backups, access and ongoing changes. Hosting and any assistant subscription are separate costs. Enterprise DNA can build and operate your version for one setup fee and then a retainer.

Is switching worth it for one kitchen? expand_more

Chomp lists NZ$959 paid annually excluding GST. A small subscription alone is not a reason to commission a custom system. Bring the questions, record gaps and working habits your current setup does not handle. The call establishes whether owning a tailored version is worth the work.

Show Sam how your kitchen keeps its records

Spend 30 minutes with Sam looking at your current bill, food control plan records and the questions your operator needs answered. We agree what your version needs, what history to bring across and what it takes to run it.

Book a call Get the free version

Food Control Plan for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Chomp?

Get your version built