Home > Knowledge > Details

Broad Bean Nutrition Facts: Choose the Correct Data Basis

Sep 20, 2023

Allen
Allen
I am Allen, General Manager of XMSD, specializing in IQF frozen fruits and vegetables. I focus on delivering safe, stable, and reliable supply solutions for global food buyers and partners.
Broad Bean Nutrition Facts: Choose the Correct Data Basis

    A broad bean nutrition facts table is useful only when its food description matches the beans you are evaluating. USDA lists 62 kcal, 4.8 g protein and 3.6 g fiber per 100 g for cooked, drained immature seeds without added salt. Its cooked mature-seed entry gives 110 kcal, 7.6 g protein and 5.4 g fiber per 100 g. Those are two different reference foods, not competing answers for one identical product.

    For a frozen broad bean specification, begin with maturity, skin condition, processing state and the weight basis. A table for cooked young beans can help with early comparison, but it is not automatically the nutrition declaration for a bag of uncooked frozen beans. Equally, a mature dry-seed figure should not be assigned to tender green beans simply because both carry the name fava bean.

    The practical task is to connect each figure to a named food and a defined use. Keep the source entry, units and preparation details with the numbers. Then distinguish a general reference from supplier data and from the declaration approved for your particular product. This makes differences easier to resolve before they reach a specification sheet, recipe file or printed pack.

Green broad beans, several showing dark seed markings.

A compact table with two clearly named reference foods

    The following comparison uses USDA FoodData Central records 170378 and 173753. Both describe edible seeds after boiling, without added salt; the immature entry explicitly specifies draining. Values are per 100 g of the described edible food. Neither record describes fresh beans still inside their pods, and neither is a laboratory report for an XMSD frozen lot.

Nutrient per 100 g Cooked immature seeds Cooked mature seeds
Energy 62 kcal 110 kcal
Protein 4.8 g 7.6 g
Carbohydrate, by difference 10.1 g 19.65 g
Total dietary fiber 3.6 g 5.4 g
Total fat 0.5 g 0.4 g
Water 83.7 g 71.54 g
Sodium 41 mg 5 mg
Folate 58 µg DFE 104 µg DFE

    Read the column headings before comparing individual rows. The table makes a useful point: even after cooking, young and mature beans have different reported composition. A product called broad beans may appear in a vegetable application or as a mature pulse ingredient. Match the maturity as well as the familiar crop name.

    Water is included because it helps interpret the figures. These entries report 83.7 g and 71.54 g water per 100 g respectively. A difference in water content changes how much other material is present in the same weighed portion. Read these as separate food records with different moisture contents, rather than a before-and-after experiment on the same beans.

    Folate is shown as dietary folate equivalents, or DFE. Preserve that description rather than silently changing the heading to folic acid. The NIH explains that folate is needed for making DNA and other genetic material and for cell division. A composition figure can describe a food's contribution, while a person's dietary requirements and medical situation remain separate questions.

    For a separate raw comparison, USDA SR28 record 11088 describes raw immature broad bean seeds. It lists 72 calories, 5.6 g protein and 4.2 g fiber per 100 g of edible seeds. The cooked immature record is a different food description. Use the one that matches the weight in your recipe or label calculation.

Broad bean pods and loose beans on a woven basket.

Name the bean before choosing a database entry

    Use a complete ingredient description: broad bean or fava bean, maturity, skin-on or peeled, whole or split, and processing state. This is a short description with a large effect on data selection. The words raw, frozen, blanched and cooked identify different stages. They should stay attached to the ingredient even when a spreadsheet column is narrow.

    A fresh-looking green photograph gives you an appearance reference. For the preparation behind a nutrition figure, read the sample description. In a purchase discussion, describe the visible seed coat and the supplied form directly, including which material has been removed. Where terminology differs between suppliers, an agreed sample and a precise written description help prevent two people approving different products.

    We would start an XMSD comparison with the actual bean form, then review the nutrition basis. If the request is for peeled green beans for a smooth filling, the specification must identify the peeled ingredient. Starting with whichever table has the most attractive protein figure would reverse the decision and leave the calculation disconnected from the product.

    The frozen fava bean range provides a product-form starting point. Use it to identify the intended presentation, then request the corresponding current specification. Broad category descriptions are useful for discovery; the exact supplied item is what connects a nutrient record, a preparation trial and a purchasing decision.

    For screening, reject a proposed match when the record is plainly for a different maturity or preparation state. If the match is close but incomplete, record the gap explicitly. For example, "cooked immature seeds; peeling status not established" is a useful limitation. Hiding that uncertainty behind the shorter name "broad beans" makes later review harder.

    USDA SR28 also describes raw mature fava seeds. That reference lists 341 calories and 26.12 g protein per 100 g of the low-moisture mature seed. Use it only for a comparable food state. If the ingredient is a tender frozen bean, ask for the product-specific basis or state which difference prevents a direct match.

Peeled green broad beans gathered in a shallow pile.

    If your recipe uses the seed without its skin, start by comparing a sample of frozen peeled broad beans.

Keep edible weight separate from purchase weight

    The denominator of a nutrition table is part of the data. A per-100-g edible-food value describes 100 g of the food named in the record.

    Fresh pods, a carton including packaging and a frozen sample with loose ice each have a different gross-weight basis. Keep those weights on separate lines when calculating yield.

    For an ingredient review, write down what was weighed and when. Was the sample frozen, prepared, drained, peeled or blended into a recipe? Was the measurement taken before or after removing a discarded part? These details are more helpful than adding decimal places to a number whose food basis is unclear.

    An edible yield tells you how much usable food remains from an input quantity. A nutrient retention factor addresses what remains of a nutrient through processing. Use the yield to plan usable quantities, and use nutrient-specific information for a retention calculation. Removing water, discarding skins and changing the recipe affect the calculation in different ways.

    This distinction matters for a business buying one form and selling another. The purchase specification may describe frozen skin-on beans, while the final product uses a peeled puree. Both records can be correct if they name their own state. Trouble starts when the supplier's per-100-g table is copied into the finished product file without recording the transformation.

    We prefer one short preparation record attached to the sample comparison: input weight, supplied form, required preparation, discarded material and final edible weight. That record allows a second person to reproduce the basis. It also reveals whether two samples are being compared fairly, especially when one is weighed immediately after draining and another after additional holding.

    Take out the carton and liner before calculating the net pack weight. For a pod sample, weigh the edible seeds separately. The table uses prepared edible weight. Record separately how much is discarded during preparation and how much is used in a finished portion.

Broad beans with visible frost on a dark surface.

Read the nutrient name, unit and missing values together

    A complete-looking table is not necessarily a better table. Blank fields, unavailable values, reported zeros and rounded zeros mean different things. Keep a missing nutrient as missing until an appropriate source resolves it. Filling every empty cell with zero creates new claims that the source did not make.

    Use the nutrient name exactly enough to preserve its meaning. USDA's carbohydrate by difference is not the same heading as sugars. Total dietary fiber is not interchangeable with insoluble fiber alone. Folate, food folate, folic acid and DFE should not be combined simply because the values are all expressed in micrograms. When a sheet changes terminology, ask what changed in the underlying measurement or calculation.

    Units deserve the same attention. One milligram is 1,000 micrograms, so a misplaced prefix creates a much larger error than ordinary product variation. Energy may be expressed in kilocalories or kilojoules. Preserve the original unit beside the original value and perform any conversion in a separate calculation field rather than overwriting the source.

    The sodium values in the comparison are a useful reading test. Both entries say without salt, yet each reports sodium. "Without added salt" describes preparation, while the sodium row describes the reported amount in the food. Keep the listed sodium value when using either reference, including when the ingredient is plain.

    FoodData Central contains different data types and sources. Its documentation explains those distinctions. In a working record, save the food identifier and source type along with the access date.

    A number copied from an anonymous web table has less traceable context than a number linked to a specific database food. The useful improvement is traceability, not the appearance of a more formal spreadsheet.

Worked example: identify a reference mismatch before approval

    Suppose a private-label project is reviewing a preliminary sheet for cooked young broad beans. The planned comparison sample is 120 g of edible cooked beans. A draft calculation uses the mature-seed protein value, 7.6 g per 100 g, because the database search returned "fava beans" first. This is an illustrative document-review scenario, not an XMSD test result.

    With that mature reference, the calculation is 7.6 × 120 ÷ 100 = 9.12 g protein. The immature reference gives 4.8 × 120 ÷ 100 = 5.76 g protein. The difference is 3.36 g for the same stated sample weight. Arithmetic can be flawless while the selected food is wrong.

    The reviewer should replace the mismatched reference in the preliminary comparison and record why. Mark the revised figure as a database estimate, retain the calculation and request the nutrition information for the intended retail item. This leaves the next reviewer with a clear record of what was corrected and which product-specific information is still needed.

    The 120 g quantity is an illustrative review input. Establish the appropriate serving basis separately for the intended market before carrying a development calculation into consumer artwork.

    The same review should check the rest of the rows. Correcting protein while retaining mature-seed carbohydrate or folate would create a hybrid table. Replace the reference consistently or explain any separately supported source used for an individual field. Save the superseded version so the reason for the change remains visible.

    For everyday portion arithmetic and mixed meals, the separate broad bean carbohydrate and calorie guide develops that use case. Here, the approval question is narrower: can every figure in the sheet be traced to a food description that fits the intended ingredient? Resolve that first, then scale the quantity.

    The two 120 g protein calculations compare separate USDA foods at the same edible weight. The difference reflects the values for those named foods in the database. For an order-specific declaration, keep the recipe and the approved basis for the exact product.

Pale green broad bean pieces on a light surface.

Frozen processing needs its own nutrition basis

    A frozen ingredient has a process history. Blanching, cooling, draining, freezing and later preparation may all be relevant to the final food description. Obtain that sequence from the product documentation and place it beside the nutrition information. The two records together describe the supplied ingredient more clearly than either one alone.

    Avoid a blanket adjustment called "freezing loss." If a supplier provides values for a prepared frozen product, review the named product and basis. If only a raw or cooked reference is available, identify the mismatch before using it for development. A universal percentage applied to every nutrient would conceal the separate effects of preparation, changes in water and product variation.

    At XMSD, we would connect the specification review to the preparation trial. A bean that performs well in a soup may need a different texture assessment from one used as a visible inclusion in a chilled meal. Record the endpoint that works in the intended dish, then match the nutrition information to that prepared ingredient state.

    The equipment overview helps frame questions about process stages. It is not a substitute for a product-specific process record or a nutrition analysis. Ask which steps apply to the proposed broad bean item and which are completed by the receiving kitchen or manufacturer. That division of responsibility belongs in the ingredient file.

    Keep cooking instructions separate and visible as well. Establish ready-to-eat or cook-before-use status from the product instructions and follow the required preparation. If your operation changes the final method, review the resulting food and its nutrition calculation. The supplier's figures remain attached to the original supplied state until an appropriate prepared-food basis is established.

Stainless steel equipment inside a food-processing room.

    For a dish with visible pieces, compare the size and breakage of whole and split frozen broad beans after preparation.

Practical example: approve a peeled filling ingredient

    Imagine a food manufacturer comparing two broad bean samples for a smooth filling. Sample A is skin-on; sample B is supplied peeled. Each trial starts with 2 kg of frozen ingredient and follows the documented preparation required for that sample. The trials then record the usable bean component before oil, seasoning or other ingredients are added.

    For illustration, suppose the usable weights are 1.6 kg from A after skin removal and 1.8 kg from B after preparation. Those assumed results give yields of 80% and 90%. They do not establish standard yields for either product form. The decision is whether the more convenient supplied form improves usable output and the required texture in this particular process.

    The manufacturer would compare the two fillings at the same final recipe composition and texture target. A smoothness difference, visible skin fragments or a different water demand can change which sample fits the application. The useful result is an approved form and repeatable preparation record, not a claim that a higher yield proves higher nutritional value.

    For nutrition work, the team keeps the supplier data for each supplied form and asks whether it covers the prepared peeled component. The 0.8 and 0.9 factors belong in the usable-mass calculation. For the finished formulation, use matching ingredient values and record every added ingredient. This connects the chosen product form to both the manufacturing trial and the nutrition worksheet.

    This is where a foodservice and catering application discussion can help connect pack format, preparation and the expected dish. The operation must know which work happens before delivery and which happens in the kitchen. Keeping that boundary clear prevents a convenience decision from quietly changing the food described in the approved specification.

Closed cardboard cartons on a handling platform.

    For additional context, see the guide to broad bean suitability and G6PD precautions.

Carry the data into the specification and artwork

    Use one product identity across the specification, sample record, nutrition worksheet and proposed label. If the item code changes, check whether the ingredient or process also changes.

    Similar product photographs and nearly identical trade names are not enough to establish that two sets of figures describe the same item. Compare the item codes and specifications directly.

    For a supplier nutrition sheet, look for the food state, reporting basis, units, source method and document version. Was the information obtained from a database calculation, formulation calculation or analysis? An analytical result should identify the sample and the test basis. A calculated value should identify the inputs and method sufficiently for its intended use. These are different types of support, so keep their descriptions accurate.

    Review unexplained differences before choosing a number. If one sheet reports values as supplied and another reports them after cooking, resolve that basis first. If both claim to describe the same product state but differ materially, ask for the source and calculation detail. Averaging two inconsistent tables can hide the cause without improving accuracy.

    The FDA's consumer guidance makes another relevant distinction: the amount of food represented by a serving determines how the displayed nutrition information is read. Scale a per-100-g reference to the stated food quantity before comparing it with a pack or serving declaration. For commercial artwork, use the requirements and approved calculation method for the destination market. Keep that label review separate from the preliminary data-selection work described here.

    Coordinate the final data with frozen packaging and label preparation before artwork release. A packaging change may be purely visual, but a new declared serving, added sauce or different bean form can affect the supporting information. Keep the approved nutrition version attached to the artwork so later revisions start from the correct file.

What the table can settle, and what needs another answer

    The table establishes a clear comparison between two named reference foods. Use it for transparent calculations and for spotting a mismatched data source. Exact crop-lot composition calls for product-specific information. Health outcomes and individual suitability are separate questions requiring their own scientific and clinical support.

    Fava beans can trigger the breakdown of red blood cells in people with G6PD deficiency. If you have G6PD deficiency, follow medical guidance about avoiding fava beans. Peeling, cooking or freezing does not make these beans suitable for someone who has been advised to avoid them. Seek prompt medical care if possible symptoms occur after exposure.

    For a product review, finish with a short, usable record: the exact ingredient, the state in which it is measured, the source of the figures, any unresolved mismatch and the next decision those figures support. If the intended use is only an early comparison, say so. If the figures are being prepared for a product declaration, complete the product-specific documentation and destination review before approval.

    The strongest broad bean nutrition sheet is the one another person can follow without guessing. Preserve the food description beside the numbers, show any calculation openly and revisit the basis whenever the ingredient changes. This gives a buyer, developer or reviewer a reliable starting point for the next step without making the table claim more than it contains.

    For a frozen broad bean project, send XMSD the required bean form, preparation state, application and nutrition-document needs through our inquiry form. We will review the product information relevant to that request.

References