Map every agency with authority over your product — FDA or USDA at the federal level, plus your state and your local health or agriculture department — before you fill out a single form.
Do these first
Real help from real food people
Chef Diego runs a real food plant. If this page didn't get you there, tell us — a person reads every message.
By the end of this lesson you can name every agency that has legal authority over your product, and you'll know you almost certainly answer to more than one of them — a federal food agency, your state, and your city or county — before you touch a single application. The alphabet soup you keep running into (FDA, USDA, FSIS, your state ag department, the county health office) sounds like chaos. It isn't. It's three predictable layers, and which rules land on you is decided almost entirely by one thing: what you make.
Getting legal to sell is not a matter of finding the one agency you register with. Most packaged-food manufacturers answer to three at once, and each governs a different slice of the same operation:
They stack; they don't substitute. A federal registration doesn't satisfy your state, and a state license doesn't satisfy your county. The first mistake first-timers make is assuming one form covers everything and discovering the other two at an inspection. So the job right now isn't to file anything. It's to draw the map — name all three layers — and then fill out forms in order.
At the federal level, one of two agencies owns your product, and they barely overlap. Which one is yours is set by what your product is.
The FDA regulates all foods and food ingredients offered for sale in interstate commerce, with one large exception: meat, poultry, and certain processed egg products, which belong to the USDA (FDA, How to Start a Food Business, verified July 2026). If you make sauces, baked goods, spice blends, beverages, snacks, condiments, jams — the vast majority of packaged food — you are an FDA operation.
The FDA's oversight is lighter-touch than the USDA's in one specific way: it does not station an inspector on your floor. You register your facility with the FDA, follow its rules, and it inspects your plant periodically. The federal step for most manufacturers is that registration, and a later lesson in this course walks through completing it and keeping it valid.
If your product's identity is meat, poultry, or processed egg, you fall to the USDA's . This is a different agency and a fundamentally different kind of oversight, worth understanding before you assume you're FDA or decide to add a meat product.
FSIS covers the . Its model is mandatory, in-plant inspection: an inspector is physically present in the establishment — continuously during slaughter — and by law no meat may be sold or transported in commerce until it has been inspected and passed (21 U.S.C. 610); the poultry law works the same way. Every FSIS-inspected plant also runs a system. Compared with the FDA's register-and-inspect-periodically approach, this is a heavier regime — a fact that matters the day a meat product tempts you across the line.
Here's where people guess wrong. A product with a little meat in it is not automatically the USDA's. The Federal Meat Inspection Act excludes products that contain meat "only in a relatively small proportion" (21 U.S.C. 601), and the two agencies drew that line by percentage. As the FDA lays it out on its jurisdiction page for meat products (verified July 2026), a product made with livestock meat is generally the FDA's if it contains 3% or less raw meat or less than 2% cooked meat, and the USDA's above those lines; for poultry, the FDA's below 2% cooked poultry and the USDA's at or above it. The most quoted illustration of how specific this gets: a closed-face meat sandwich is the FDA's, while an open-face one is the USDA's.
You don't need to memorize the table. The point is that the line is real, narrow, and about your recipe — so if your product contains any meat or poultry, check which side it falls on rather than assuming. A later lesson in this course works the FDA-versus-USDA question through in detail for products that sit near the line.
Confirm your own product at the source
These percentages and the amenable-species lists move, and a product near the line can surprise you. Before you build a compliance plan on being "FDA" or "USDA," confirm your specific product against the FDA's live jurisdiction page and, if it's close, contact the agency. Write down the date you checked.
Two more splits catch people. Eggs: the USDA's FSIS inspects processed egg products — liquid, frozen, and dried eggs — while shell eggs fall to the FDA. Game and wild birds: the FDA, not the USDA, regulates meat from non-amenable animals like bison, deer, elk, and rabbit and from wild birds like quail and pheasant.
Federal registration tells you almost nothing about your state's requirements, and it doesn't replace them. Your state licenses the business and, in most places, inspects the kitchen your food is made in. Depending on the state, your regulator is the department of agriculture, the department of health, or both, and the license is some form of food-manufacturer or food-processor permit tied to an inspected facility. Sales that stay inside your state are largely your state's domain to govern.
This is the same authority that ran the cottage-food exemption you may have started under — the exemption a home kitchen outgrows the day it goes commercial. As with cottage rules, there is no national version: what your state requires, what it charges, and who inspects you are its own to set. A requirement you read for another state tells you nothing about yours. Find your state's food-manufacturing licensing page, and note the date you read it.
The last layer is the one people discover latest, and it can gate your opening date. Your local health department — usually city or county — issues the permit to operate at your specific address, and many jurisdictions require before you open. That approval takes time, and finding out about it after you've signed a lease or built out a space is an expensive surprise. Whether your locality requires plan review, and what its permit process looks like, varies — so confirm it with your own city or county health office early.
Put together, the layers stack rather than compete. A hot-sauce maker is an FDA operation federally, holds a state processor license, and pulls a county health permit — often after a plan review — to operate at their address. A jerky maker carries the heavier USDA/FSIS oversight in place of the FDA layer, plus the same state and local requirements. In neither case does one approval stand in for another. The rule you actually operate under is the sum of all three, and the strictest requirement that applies is the one you meet.
Knowing who regulates you is step one; the rest of this course is the order you satisfy them. For most FDA manufacturers the federal step is , which you complete before you operate and renew on a two-year cycle (FDA, Registration of Food Facilities, verified July 2026). From there you license with your state and permit with your locality, in a sequence the next lessons lay out. But none of that starts until you've named your three layers — so name them now.
Do this in your operation