USDA NASS Quick Stats
Datadory delivers usda nass quick stats packaged foods meats data covering the livestock side of the American food chain - cattle, hog, broiler and turkey inventory, slaughter and production alongside prices received - as aggregated estimates from national to county, drawn from annual surveys and the five-year Census of Agriculture. Delivered daily, weekly, or hourly.
What is USDA NASS Quick Stats?
USDA NASS Quick Stats is the federal estimate bank for American agriculture, and read through a Packaged Foods & Meats lens it doubles as a raw-materials ledger: cattle on hand, hogs kept, broilers placed, turkeys raised, head slaughtered, pounds produced, dollars received per unit - every figure the National Agricultural Statistics Service publishes, organized on one What/Where/When model. Pick the subject, pick the place, pick the period, and the matching estimates come back as flat rows.
Scale first, because it reframes what a meat company can know about its own supply base. The corpus spans six subject areas - Livestock and Animals, Crops and Plants, Economic and Prices, Demographics, Environmental, Research and Science - and runs to tens of millions of records; the animals-and-products slice alone occupies hundreds of megabytes of text before anyone has asked it a single question. Get a sample of this dataset cut to your species, states and years.
What does a sample row look like?
One estimate per row, identifiers attached. Two rows exactly as they ship:
SOURCE_DESC : CENSUS
SECTOR_DESC : ANIMALS & PRODUCTS
GROUP_DESC : SPECIALTY
COMMODITY_DESC : SPECIALTY ANIMAL TOTALS
STATISTICCAT_DESC: SALES
UNIT_DESC : $
AGG_LEVEL_DESC : COUNTY
STATE_NAME : NEW MEXICO
COUNTY_NAME : SAN JUAN
YEAR : 2007
FREQ_DESC : ANNUAL
VALUE : (D)
SOURCE_DESC : SURVEY
SECTOR_DESC : ANIMALS & PRODUCTS
GROUP_DESC : DAIRY
COMMODITY_DESC : MILK
STATISTICCAT_DESC: FAT TEST
UNIT_DESC : PCT
AGG_LEVEL_DESC : STATE
STATE_NAME : OTHER STATES
YEAR : 2022
FREQ_DESC : ANNUAL
VALUE : 3.83Read together, they demonstrate the two behaviors any protein analyst needs to plan around. The census row is a county-level sales figure withheld behind (D) because a single operation would dominate it - the dataset marking where disclosure rules bite rather than inventing a number. The survey row is a decimal-precision fat test showing how far the same schema stretches past headcounts. Numeric values land as strings with thousands separators, so ingestion handles markers like (D) and (Z) deliberately instead of tripping on them.
What fields does the dataset include?
Fourteen documented columns define every estimate row, verified against the source's published file headers during the August 2026 research pass. The identifying columns compose a natural key - program, sector, group, commodity, class, statistic category, unit, geography, year, frequency - which is why a livestock series joins cleanly to your own commodity master without a crosswalk table.
Two further columns ride along only on subsets of records and therefore fold under additional fields on request: CV_%, published where an estimate carries a coefficient of variation, and LOAD_TIME, stamping when an estimate entered the database. Name them when you request a sample and they arrive switched on.
What does coverage look like across geography, time and granularity?
Geography - United States at six aggregation levels: national totals, states, counties, ZIP codes, watersheds and congressional districts. County is where protein work actually happens - feedstock concentration, processor catchment and supplier density all resolve at that grain.
Temporal - annual survey cycles plus the five-year Census of Agriculture, whose reference years reach back to the late 1990s in the historical files. Selected statistic categories publish on finer rhythms - weekly, monthly or point-in-time readings, carried in the FREQ_DESC column - so inventory and price series do not share one clock.
Granularity - one aggregated estimate per commodity x statistic x geography x period. There is no farm- or plant-level microdata anywhere; the agency publishes summaries by design, and that constraint is precisely what makes county-versus-county comparisons defensible.
How is the data delivered?
API, files, or your warehouse. Daily, weekly, or hourly.
Who uses this data, and for what?
- Raw-material availability tracking - cattle, hog, broiler and turkey inventory series flag herd expansion or liquidation quarters before they surface in processor guidance.
- Input-cost modeling - prices received for cattle, hogs, milk and eggs give the producer side of every packaged-protein bill of materials.
- County sourcing maps - county-resolved inventory shows where feedstock actually lives, feeding procurement footprints and supplier scorecards.
- Throughput context - slaughter and production categories set official baselines for how much protein moves through the system each period.
- Feed-side exposure - corn, soybean and hay acres and yields sit in the same schema, so the cost of gain never needs a second vendor.
- Disclosure-aware rural analysis - the
(D)and(Z)markers show exactly which markets are too concentrated to publish, before a model treats silence as scarcity.
Which personas get the most value?
Investors and quant researchers build input-cost and supply-cycle factors for protein processors from inventory and prices-received series; see investors quants use cases. Market researchers and consultants size meat and poultry categories against official counts instead of panel extrapolation; see market researchers use cases. Data scientists and ML engineers train supply and demand models on county-resolved features that join on the natural key; see data scientists use cases. Competitive intelligence and product teams watch structural shifts in their own supply base decade over decade; see competitive intel product teams use cases. Journalists, academics and students cite the government's own numbers, down to the county.
Which datasets pair with this one?
- USDA AMS Market News - Livestock, Poultry & Grain - daily transactional reporting where Quick Stats supplies the settled statistical estimates; the noise beside the signal.
- USDA ERS Meat Price Spreads - the margin decomposition of the same pounds, farm gate to checkout scanner.
- USDA FoodData Central API - the composition of the finished products these animals become; the head-to-head sets out where each one wins.
- World Bank - Food Production Index & Food Commodity Indicators - global supply context wrapped around the US protein complex.
See the best Packaged Foods & Meats datasets ranking or browse the full Packaged Foods & Meats catalog.
Field dictionary
Every field below is documented against real records. The full dictionary ships with the sample.
| field | type | definition | example |
|---|---|---|---|
SOURCE_DESC | enum | Program behind the record: SURVEY for annual survey-cycle estimates or CENSUS for five-year Census of Agriculture figures. | SURVEY |
SECTOR_DESC | enum | Top-level sector of the statistic: ANIMALS & PRODUCTS, CROPS, ECONOMICS, DEMOGRAPHICS, ENVIRONMENTAL. | ANIMALS & PRODUCTS |
GROUP_DESC | string | Commodity group within the sector, e.g. DAIRY, LIVESTOCK, POULTRY. | DAIRY |
COMMODITY_DESC | string | Commodity being measured - CATTLE, HOGS, BROILERS, TURKEYS, MILK and their kin. | CATTLE |
CLASS_DESC | string | Class breakdown inside a commodity where one exists. | ALL CLASSES |
STATISTICCAT_DESC | string | Category of statistic - INVENTORY, SLAUGHTER, PRODUCTION, SALES, PRICE RECEIVED among others. | SALES |
UNIT_DESC | string | Unit of measure for the value - HEAD, LB, PCT, $. | $ |
SHORT_DESC | string | Concatenated human-readable label combining commodity, statistic and unit. | SPECIALTY ANIMAL TOTALS, (EXCL EQUINE) - SALES, MEASURED IN $ |
AGG_LEVEL_DESC | enum | Geographic aggregation level of the record: NATIONAL, STATE, COUNTY, ZIP CODE, WATERSHED, or CONGRESSIONAL DISTRICT. | COUNTY |
STATE_NAME | string | State name for state- and county-level records. | NEW MEXICO |
COUNTY_NAME | string | County name for county-level records. | SAN JUAN |
YEAR | integer | Reference year of the observation. | 2022 |
FREQ_DESC | enum | Reporting frequency of the series: ANNUAL, MONTHLY, WEEKLY, or POINT IN TIME. | ANNUAL |
VALUE | string | Observation value; numeric, or a suppression/confidentiality marker such as (D) or (Z). | (D) |
Questions buyers ask
What does USDA NASS Quick Stats cover for packaged foods and meats businesses?
The animals and products sector carries inventory, slaughter, production and prices-received categories for cattle, hogs, broilers, turkeys, dairy and specialty animals - while the crops, economics and demographic sectors cover the feed grains and labor markets sitting upstream of every protein margin.
How far back do the livestock and meat series go?
Census reference years run back to the late 1990s in the historical files, and annual survey cycles continue to the present. Selected statistic categories publish weekly, monthly or point-in-time readings rather than yearly ones, so check the frequency column before assuming one clock.
What do the (D) and (Z) codes mean?
They are suppression codes, not errors. (D) marks an estimate withheld because an individual operation would be identifiable; (Z) marks withholding for other reasons. Low-count livestock counties hit them most often. Treat both as missing, never zero - a naive sum quietly understates the herd.
Does the data identify individual farms or plants?
No. Every row is an aggregated estimate published by the statistical agency; no operation-level microdata exists anywhere in the corpus. The finest published geography is typically the county, which is exactly what makes county-versus-county comparisons defensible.
Can a sample be narrowed to specific species, states and years?
Yes. Name the commodities, geographic levels and periods that matter and the sample arrives shaped to that scope, with the full field dictionary attached. Samples precede any commitment, and nothing ships until the shape matches your pipeline.
How does this differ from daily market reporting?
Quick Stats publishes statistical estimates constructed from surveys and the census of agriculture; daily market reporting records transactions as they happen. Analysts typically run both - the transactional feed for timing decisions, the estimate bank for structure, history and citation-grade provenance.
See the rows before you pay anything.
Name this dataset and we send real records from it — scoped to the fields you asked for.