For small seafood processors, from the water to the customer
The operations and food safety system for small seafood processors.
Built on a Tasmanian processing floor. Set up today for sea urchin and oysters.
Why it is different
Every check, weight and reading is recorded once, by the person who did it, as the work happens. That one record comes out three ways.
For your auditor
Limits carry the clause they come from. Corrective actions open on their own. A second person verifies. Nothing is edited after the fact. The auditor signs in, read only, and reads it the way they already read a plan.
For your customers
The buyer, the chef and the diner scan it and see the lease or dive site, the harvest day and the pack day. In your colours, with your story, from your own records.
For you
No evening re-typing. The dashboard shows what is due today, what was missed and what breached, before the auditor does. Yield by source, week on week.
Today
Each tool does its one job. None of them knows about the lot. So the lot is written down again at every handover, and the audit is the day you find out which copy was wrong.
The clipboard
Temperatures and checks on wet paper, read by nobody until something goes wrong.
With BlueBatch. Recorded on the floor, by the person who did it, judged against the limit as it is entered.
The whiteboard
Today's lots and orders, wiped tomorrow morning.
With BlueBatch. Stock by lot and place, kept, with what is due today at the top.
The phone
Orders by text, email and messaging apps, in three inboxes.
With BlueBatch. Orders in one list, packed from the oldest stock first, with lot and use-by on every carton.
The logger's own app
A warm cool room found the next morning, in an app nobody opens.
With BlueBatch. A reading out of range opens a corrective action on its own and lands on the manager's dashboard.
How it works
Log the landing on the phone: species, weights, who caught or grew it, where, and the checks your plan requires. The area's status is checked before the landing is accepted.
Batches, units and cartons carry the lot. Labels print with species, lot, area, dates, net weight and the QR code. The use-by comes from the lot, not a guess.
Customers order from today's availability on their own phone, or you enter it for them. Every order sits in one list against the stock you actually have.
One carton's journey
Tap a step to see the record it leaves behind. Then run the recall.
The record it leaves
Who caught or grew it, which area, whether the area was open, and how cold it was when it landed. Checked against your limit as it is entered, by the person who did it.
Sample records from a demo tenant. People and businesses are invented.
Your customers
Each customer has a page: orders, addresses, contacts and notes. They order from today's availability on their own phone, or you enter it for them. Packing takes the oldest stock first, so every carton leaves with the right lot and use-by on it. They can follow the order and confirm receipt.
Next: invoices sent to Xero as drafts, and price lists per customer.
What your customer sees
The records you keep for the auditor are the provenance your customers are asking for. A QR code on every pack opens a page in your colours, with your logo and your story: which lease or dive site, who harvested it, and the day it was packed. Wholesale buyers see the lot. Chefs put it on the menu. Diners scan it at the table.
Your crew
Each person has their own sign-in with the access their role allows, or the shed shares one iPad and each person enters their personal PIN before they record. Either way, the record carries who did it, because they were the one signed in. Big buttons, wet hands, photos from the camera, and sign-out when the phone is left idle.
Your food safety plan
Most findings are not bad practice. They are a check that was forgotten, a limit nobody wrote down, or a fail that was never followed up. BlueBatch is built so those three cannot quietly happen. We sit with auditors to learn where small processors get caught, and build the check that catches it first.
Every limit carries the clause and plan version it comes from. A reading is judged as it is entered: monitored, or refused.
A breach, a failed check or a logger out of range opens a corrective action on its own, with photos on raise and close.
The checks your plan says are verified go to a queue for someone other than the person who recorded them.
Swabs, calibration, cleaning, the monthly review and expiring licences sit on the manager's dashboard as due, overdue or breached.
Know your business
Because every weight, price and reading is already captured, the reports are a by-product too. Seven pages, each number opening the rows behind it, with highlights when something moves.
By source and by harvest. You see which lease or dive site is paying.
The audit, every day, before the auditor.
Illustrative figures from a demo tenant.
Who it's for
Set up today for sea urchin and oysters, farmed or wild. Abalone, rock lobster and finfish are next, and we are talking to processors in those fisheries now.
Available now
Area status checked before the harvest is accepted, the harvest record inside 24 hours, the tag with the lease on it, from the phone on the lease.
Available now
Closure status checked at receival, receival temperatures and yield by source, in one place.
Next, with a design partner
Dockets, live holding and the export records kept the way the DAFF assessor reads them.
Next, with a design partner
Receival temperatures, standard fish names on every document, and yield by species without a spreadsheet.
Who builds it
Aquatrace is built by Simon de Moor, based in Tasmania, from a working system in a Tasmanian processing shed. We start with how your business works, not with the software. Your data is yours, and exports as spreadsheets any day you ask.
Free traceability check
We sit with you for 30 minutes, walk one lot from receival to dispatch, and you keep the gap list whether or not you buy.
Or download the seafood rules on one page (four printable sheets)The 9pm spreadsheet
The day typed up twice: once for the pack list, once for the invoice.
With BlueBatch. The pack list and the invoice come from the consignment. Nothing is typed twice.
The audit binder
A mock recall that takes an afternoon, and hoping the auditor does not ask for that lot.
With BlueBatch. Any carton traced back to the landing and forward to the customer in a minute, then printed.
Pack from the oldest stock first, build the run, record the temperature and the checks, print the pack list. The invoice is drafted from the consignment with the lot on the line.
Your auditor signs in, read only, and sees the trace, the records behind it and who signed what. A mock recall is a button, not an afternoon.
Every pack carries a QR code. Your customers scan it and see the same record, in plain words, in your colours.
Your forms, limits, schedules, labels and even the words on the screen are settings, not code. You change them yourself, every change is kept with a note, and any version can be restored.
Records cannot be edited after the fact. A correction is a new record that points at the original, with who and when. The integrity page states exactly what the database enforces, checked when it opens.