Two fish that do not match the invoice
At 09:00 a 40-seat restaurant in a coastal city takes delivery of 14 whole fugu from a broker. The invoice reads トラフグ (Takifugu rubripes), farmed, 1.2–1.6 kg each. The head chef, who holds the prefectural fugu handler licence, notices that two fish do not match: grey-brown backs, a few small dark spots, a distinctly keeled and spiny belly, thicker skin and short rounded fins. The broker says they were mixed in by mistake and are 「probably サバフグ, which is fine because that species is non-toxic」. A regular customer has booked the private room and asked in advance for ふぐの肝臓, saying another restaurant served it to him last winter. The chef also plans to keep the two odd fish for the staff meal, deep-fried at 180 °C for six minutes, because 「cooking kills the toxin」. The licence covers processing and sale on the premises only, and the kitchen has one sink and one set of knives.
1. How should the two unidentified fish be handled, and what does their presence mean for the other twelve?
Read the worked answer
Identification is the first control point: without species certainty there is no toxicity profile to apply. Tetrodotoxin distribution differs sharply between species - in トラフグ the liver, ovary, intestine and skin are the danger organs, while some Lagocephalus fish carry toxin in the muscle as well, and ドクサバフグ has been landed in Japanese waters in recent years. 「Probably サバフグ」 is hearsay, and 「サバフグ is non-toxic」 is not a rule you can rely on: シロサバフグ is often treated as non-toxic, but related species are not.
So: segregate the two fish in a labelled container, do not process them, do not use them for the staff meal, and do not put them back into the general stock. Return them to the supplier with a written note or dispose of them as toxic material under the licence conditions, and record what happened.
For the twelve: they came from a mixed lot, so the traceability record must state 14 on the invoice, 2 unverified. Anything that touched the two - knife, board, sink, crate - must be washed and disinfected before it touches トラフグ flesh.
2. The customer's advance request for 肝臓: what do you do, and how do you answer the argument that another restaurant served it?
Read the worked answer
Refuse, and say so before the meal rather than at the table. In トラフグ the liver is one of the most toxic organs, and national guidance on fugu hygiene directs prefectures to prohibit its sale and provision; the shop's licence covers only the permitted parts, so serving it would be an offence regardless of what another business does. Another restaurant's practice creates no permission, and if the customer names the business you may pass that to the 保健所.
Farmed origin does not settle it: diet and individual variation mean you cannot assume zero toxin, and there is no field test that certifies a liver as safe. The toxin is heat-stable and there is no antidote, so no kitchen technique makes a toxic liver servable.
Offer 白子, 湯引きした皮 and 身 instead, explain briefly and without drama, and log the refusal against the reservation so the front-of-house staff do not reopen the question on the night.
3. Assess the staff-meal plan of deep-frying at 180 °C for six minutes.
Read the worked answer
The plan converts a disposal problem into an exposure. Tetrodotoxin is heat-stable: it is not reliably destroyed at 180 °C for six minutes, and boiling, salting, drying or freezing do not detoxify it either. The chef's premise is therefore false, and the staff meal would be an uncontrolled dose given to people who then go home.
The second problem is the starting material. These two fish are unidentified, so even the muscle cannot be assumed safe - in some species the flesh itself is toxic. Deep-frying cannot rescue an unknown species.
The correct handling is the same as for any toxic-part waste: label, isolate, keep out of reach, dispose through the proper route, and record the quantity and date. If staff meals are made from fugu at all, they must come from fish that were identified, processed by a licence holder, and had all toxic organs removed.