Enterprise DNA

Instead of FoodLogiQ

Stop renting FoodLogiQ. Own your recall records system.

We build your version around your batches, recipients and recall plan, bring the agreed FoodLogiQ records across and run it for you. Keep the evidence behind every follow-up and quantity.

FoodLogiQ pricing is supplied by enquiry. Compare your annual contract with the cost of a records system built around your recall process.

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

A recall needs clear records at every step

FoodLogiQ combines several supply-chain services. Decide which work you need to own, then price that scope against your actual agreement. A records desk is the starting point for your own version.

package

Product and batch history

FoodLogiQ Traceability records product movement. Your own desk starts with finished batches, their source references and the direct deliveries you have verified.

users

Recipient coordination

FoodLogiQ Recall supports targeted notifications and response tracking. Keep each recipient, the actual communication evidence and the person responsible together.

clipboard-check

Withdrawal progress

FoodLogiQ Recall helps teams manage withdrawal events. Your version records the selected batches and shows which recipients still have unresolved stock.

file-text

Investigation exports

FoodLogiQ Traceability documents spreadsheet exports of event, location and product information. We map the selected records and reconcile them with your production and stock evidence.

smartphone

Capture and connections

Trustwell offers mobile recall capabilities. We build the capture screens and source connections your operation needs, with the access and response process agreed first.

database

Your operating history

Keep your plan references, coordinator notes, contact corrections and reviewed report references in a database your business owns. The free base provides the records and review work.

Your records, your recall plan

Move from a batch code to the next action

Trace

Know who received the batch

Start with the finished product and follow its recorded direct deliveries.

  • check Keep the product, batch identifier and date mark together
  • check Separate each delivery line and its source reference
  • check Snapshot the direct recipients when an event starts
  • check Find every recorded batch supplied to a particular destination

Respond

Keep follow-up attached to evidence

A completed call and a recipient acknowledgement are different records. Both matter during the round.

  • check Record actual notifications without sending from the free base
  • check Record the recipient reply and its evidence reference
  • check Append verified contact details while keeping the original snapshot
  • check Find overdue follow-ups beside the responsible coordinator

Reconcile

See what is still unaccounted for

Keep stock quantities tied to their batch, recipient and unit so the review has a clear starting point.

  • check Separate returns, destruction and consumption
  • check Reject quantities that exceed the recorded distribution
  • check Show on-site held stock, samples and undistributed stock
  • check Require reconciled recipients and decision evidence before closing the record

Practise

Make the exercise useful for the next event

Combine missing acknowledgements, stale plan references and report dates in the same weekly review.

  • check Keep exercises clearly labelled beside live events
  • check Find gaps by coordinator and batch
  • check Prepare a working distribution list and reconciliation report
  • check Change local review rules as your process changes

Make it yours

Design your own FoodLogiQ replacement

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

2. What it runs

3. Make it fit

4. Your colour

Your business · your FoodLogiQ 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 FoodLogiQ 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 Recall for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Food Recall for Claude Code

Connected to your own database

Who has not acknowledged the practice recall?

DEMO-EXERCISE

Lot
DEMO-BATCH-A
Destination
DEMO-SOUTH
Owner
Mara
Response due
2026-10-23

Ask it anything

Ten questions your recall desk can answer

These use your records and local review rules. They do not claim that FoodLogiQ cannot provide similar reports.

chat_bubble Which recipients still have no acknowledgement evidence?
chat_bubble How much stock remains unaccounted for at each destination?
chat_bubble Which overdue follow-ups belong to the same coordinator?
chat_bubble Which current recall contacts still need verification?
chat_bubble Where did this finished batch go?
chat_bubble Which batches went to one destination?
chat_bubble How much of each batch was held, sampled or left undistributed?
chat_bubble Which Australian exercise reports are due or missing?
chat_bubble Which plan references are past their own review date?
chat_bubble Which coordinator has the most unresolved record checks?

Switching

How to switch from FoodLogiQ

A move involves exporting and mapping your records, checking the imported results, then running both processes together before you switch off FoodLogiQ.

  1. 1

    Export the records

    Use FoodLogiQ’s documented spreadsheet exports for the event, location and product records you need. Export what your account allows, usually CSV or Excel, and check with FoodLogiQ if you are unsure which records or formats are available. Keep the original export unchanged so you can compare it with the imported records.

  2. 2

    Map and load records

    Map the export columns to products, direct recipients and deliveries. Add reviewed batch balances from your stock records, since those balances may not be in the export. Check the actual column headings and decide which history to bring, including whether historic messages, attachments and recall responses need separate mapping. Have the import tested first, review its proposed result, then load the records.

  3. 3

    Check the import findings

    Compare the imported products, recipients, deliveries and batch balances with the original records. Review anything the import flags, such as unmapped columns or conflicting identifiers, and resolve it before relying on the new records. Check a batch against its original delivery records and stock balance. An export cannot reveal records that were never included, so confirm the coverage you need.

  4. 4

    Run both processes together

    Keep FoodLogiQ and the new records process running side by side for a short period. Use a recall exercise to check that you can trace a batch, find its direct recipients, record acknowledgements and reconcile stock. Compare the results with your original records, and keep your established emergency communication process in place. Your food safety lead remains responsible for recall decisions.

  5. 5

    Switch off FoodLogiQ

    When the records and working process have been reviewed, switch off FoodLogiQ according to your account arrangements. Keep the original exports and any evidence you need under your records policy. Confirm that staff know where to record recall activity and how to use your established emergency communication process. The replacement is a database and Claude Code, not a web front end.

construction

Where the real effort goes

The main work is usually mapping your own fields, stock units and review rules, then deciding how much history to bring. Event, location and product exports need checking against their actual headings. Historic messages, attachments, supplier connections and recall responses need separate mapping. You also need reviewed batch balances from stock records. Enterprise DNA does this mapping and setup when you have them run it.

Not ready for a call?

Get your FoodLogiQ switch plan by email

We will send you the step-by-step plan for moving your business off FoodLogiQ, 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

Do it yourself, have it customised, or have it run for you

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo and run npm install
  2. 2 Run npm run demo and open the folder in Claude Code, Codex, OpenCode or Cursor
  3. 3 Map your FoodLogiQ CSV or XLSX export and reviewed lot balances, then run the import test
  4. 4 Compare source totals and complete an exercise before switching the records desk
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your batches, stock units, contact rules and recall plan
  • check Your agreed FoodLogiQ records mapped across and reconciled
  • check A web front end or different technology where your team needs it
  • check Capture and communication connections built around your existing response process
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed with access, backups and evidence storage agreed
  • check Your review reports prepared for the responsible operator
  • check Kept working as your records and reporting needs change
  • check Run through Omni by Enterprise DNA, beside the rest of your business
Get your version built

Questions

Instead of FoodLogiQ, answered

Can we bring our FoodLogiQ history with us? expand_more

FoodLogiQ documents spreadsheet exports containing event, location and product information. The free version takes explicitly mapped files for products, direct recipients, reviewed batch balances and deliveries. We check your actual export headings and coverage. Historic messages, attachments, supplier connections and recall responses need separate mapping.

Does the free version replace every FoodLogiQ service? expand_more

It covers the finished-batch distribution and recall records desk. Your version can include the capture screens, source connections and reporting work you need. We agree those requirements before switching, and keep your established emergency communication process in place throughout.

Who decides whether a product must be recalled? expand_more

Your food safety lead works with the relevant authority and owns that decision. The system records their selected scope, actual communications and stock reconciliation. Clear record checks or a closed record do not declare food safe or close an authority case.

How do we know the stock numbers are right? expand_more

Compare the imported deliveries and reviewed batch balances with the original records. The free base rejects excess distribution and excess recovery, and keeps consumed stock separate from recovered stock. It cannot detect records missing from an export. Complete a reviewed exercise before relying on the new process.

What does Enterprise DNA charge, and what is the first step? expand_more

One setup fee, then a retainer, agreed around the records, connections and work you want us to run. Bring your FoodLogiQ agreement, one investigation export and the matching stock records. Sam will scope the version your coordinator can use and the checks needed before you switch.

Bring one batch and the records behind it

In a 30-minute call, Sam will look at your current agreement, recall process and source records. See what your own version needs to trace a batch, follow up recipients and reconcile the stock.

Book Sam's 30-minute call Get the free version

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

Done paying for FoodLogiQ?

Get your version built