T Tekin Works
Live system · nothing here is a mockup

The FDA asks on a Tuesday.
You have until Wednesday.

21 CFR 1.1455(b)(3) gives you 24 hours to hand over your traceability records as one sortable electronic sheet. This is a five-minute walk through a real producer — Copper Kettle Foods, a hot sauce and salsa maker in Asheville, with fourteen months of receipts, production runs and shipments already in it. Open each screen yourself. There is nobody to talk to.

Log in first

One shared demo account. Nothing you do here affects anything real — the data resets every night.

demo@lotpath.app  ·  demo1234
Open the demo →

  1. Start with the score that is deliberately not 100%

    The dashboard opens on recall readiness, and it is 89%. A demo that scored 100% would prove nothing. The number matters far less than what sits under it: the gaps are listed per Key Data Element, per lot, with the specific lots to go fix. A score with no work list is a vanity metric. Gaps that break the chain outright count triple the ones that only make a record untidy, because those are the two different problems. Open the dashboard →

  2. Find the receipt with no supplier lot code

    Almost everyone keeps records. The failure mode is a hole exactly where the trace has to cross. Two receipts in here came in without the supplier’s lot code, which means you know you bought peppers from Carolina Pepper Farms and you cannot tell an investigator which peppers. That is a dead end, not an untidy field, and the readiness score says so in those words. Open the lots →

  3. Open a production run — the part spreadsheets get wrong

    A run here is N inputs to M outputs, not a parent-child column. Jalapeños, tomatoes and vinegar go in; a batch of base sauce comes out; that base later becomes filled jars, and the jars become cases. Modelling it as a run rather than a parent lot is the thing that makes multi-level tracing possible at all — and partial consumption, where half a tote goes into Tuesday’s batch and the rest into Thursday’s, is handled rather than rounded away. Open production →

  4. Trace a case of finished sauce back to the farm

    Pick a lot of Chipotle Hot Sauce and walk backwards: case → filled jars → base sauce → the pepper lot and the day it was received. Then turn around and walk forward from that pepper lot to every case it ever touched. It is one graph walked in both directions, and it terminates cleanly on a diamond or a loop — two lots that share an ancestor, or a rework that goes back into an earlier batch — which is where a hand-built query usually hangs or silently drops a branch. Open the trace →

  5. Run the recall and see what is still out there

    A recall does not ask “what did we make”, it asks “where is it now and who has it”. This screen takes one suspect lot and returns every downstream lot, every shipment, every customer and the quantity that went to each — with the shipments separated from the stock still on your own floor, because those are two different phone calls. Open recalls →

  6. Export the thing the rule actually asks for

    Not three pretty reports — one flat sortable sheet with a CTE column, so an investigator sorts by lot code and the receiving, transformation and shipping rows for that lot line up together. Columns follow the Key Data Elements of Subpart S. Fields that do not apply to an event are left blank rather than filled with “N/A”, because a blank is a truthful “not applicable” and “N/A” is a string somebody has to ring you about. Open the records →

What it does not do

It is not a food safety plan. There is no HACCP builder, no CCP monitoring, no supplier approval programme and no audit preparation — this covers Subpart S traceability and nothing else. It does not talk to your ERP or your scales, it does not print GS1-128 labels or generate SSCCs, and it is not a substitute for your own legal reading of which of your foods are on the Food Traceability List. If you are shopping for a whole food safety system, this is not it, and I would rather you learned that from a web page than from a call.

If you want it on your own domain

$3,600 one time. No subscription. First working version in five working days.

For comparison: the enterprise traceability platforms do not quote small producers at all, and the ones that do start in the thousands per year and keep going. This is paid once and runs on your own instance. The compliance date is 20 July 2028 — the FDA extended it by 30 months in 2025 and Congress then directed FDA not to enforce before that date, so the deadline is real but it is not next week. That is the good time to build this, not the bad one.

You get a perpetual licence to use and modify your instance, and a dedicated one — your data is never pooled with another customer’s. Hosting and nightly backups are included for the first 30 days; after that either I keep it running for $99 a month, or I hand you the database, the source and the setup notes to run it anywhere. No lock-in either way. Reply with one question about your own records and you will get a straight answer the same day, including if this is not the right fit for you.

Email me a question

If you advise food companies rather than run one

Food safety consultants are buying something different: not one instance, but the tool you hand to every client who asks what their traceability programme is supposed to look like. Same system, your branding, your domain, my name nowhere in it, and you keep the code. Exclusive against other food safety consultancies in the regions you name.

$5,000 one time, white label. Not per seat, not per client, no revenue share.

The install above is a perpetual licence for your own facility; putting it in front of your clients under your own name is this offer, not that one. How the white-label arrangement works →