pH vs Titratable Acidity in Fruit Ingredients: What Each Test Tells a Formulator

Read pH as a condition, not a quantity of acid

A pH result is not a percentage of acid. It relates to hydrogen-ion activity in the sample, commonly explained as the effective hydrogen-ion concentration. Lower pH indicates a more acidic condition. The USGS explanation of pH emphasises its logarithmic scale: a one-unit difference represents a tenfold change on that scale. It does not mean ten times the mass of fruit acid or ten times the perceived sourness.

Frozen apple wedges retain visible skin and surface frost. Name the supplied form and the fraction tested when requesting an acidity result.

Imagine two fictional apple-ingredient reports that both state pH 3.5. That is a useful point of comparison only after checking how the samples were prepared and measured. It does not establish that the two ingredients contain the same neutralisable acidity, behave identically in a recipe or taste equally sharp. Do not fill an empty TA field by copying the pH result into another column.

Equally, avoid treating a small pH difference as a purchasing conclusion by itself. Ask whether the values were obtained at comparable temperatures, from the same defined sample fraction and with an appropriate calibrated instrument. Then compare them with a justified specification and the intended use. A report with more decimal places does not automatically have better accuracy or provide stronger evidence of suitability.

The apple photograph shows identifiable wedges with green skin and surface frost. It helps describe the incoming form. A laboratory still needs to know whether the requested result represents those wedges as a whole, a prepared homogenate or an extracted liquid fraction. “Apple pH” without that connection leaves the reviewer to guess what was actually in the test vessel.

Keep ingredient and finished-product results separate. The pH measured on an incoming fruit sample belongs to that sample and method. When the fruit is combined with other ingredients, the resulting recipe has its own composition and needs its own relevant assessment. An ingredient COA cannot stand in for the finished-product record merely because fruit is a prominent component.

For a routine comparison, write down the question first: are you checking incoming conformity, investigating a recipe difference or reviewing a process-sensitive attribute? That question determines which sample and decision limit are relevant. It also helps prevent a supplier from sending a technically valid result that answers a different question from the one your development team intended.

Use titratable acidity to measure neutralisation to an endpoint

In a TA test, the analyst adds a base of known concentration to a defined amount of sample until the method’s endpoint is reached. The volume consumed, concentration of the base and sample amount support the calculation. A pH electrode may be used to identify that endpoint, but the reported TA comes from the titration calculation, not from converting the starting pH.

Conceptual comparison: pH reads the prepared sample; TA measures base used to an agreed endpoint. The simplified apparatus shows no actual reading or validated laboratory procedure.

The distinction matters because fruit systems contain acids and buffering components. As base is added, the acid–base balance changes and additional hydrogen ions can become available for neutralisation. CFIA’s processed-product procedure explains this buffering behaviour in its apple-juice titration section. That provides a reason why equal starting pH values need not lead to equal titrant consumption.

TA is an operational measurement: its meaning depends on how the test is defined. Avoid interpreting “total acidity” as a chemical inventory of every acid molecule in the fruit. The result is conventionally expressed using a selected acid, even where several acids contribute. A TA result reported as citric acid does not establish that all the acidity in that sample came from citric acid.

Hach’s wine and fruit-juice application procedure shows this reporting choice explicitly: neutralisation can be expressed in equivalents or converted to a mass concentration of a chosen acid using its molecular mass and reaction stoichiometry. The chosen basis is therefore part of the result, not an optional note that can be dropped when transferring data into a purchasing spreadsheet.

For formulation work, this adds information that a starting pH alone cannot provide. Suppose a fictional fruit preparation meets the agreed pH requirement but gives a different TA from the approved baseline under the same method. The team has a reason to investigate acid balance in the application. It has not yet proved the ingredient is defective, that the recipe will fail or that extra sugar is the appropriate correction.

The analytical result should narrow the next question. It may lead you to review sample identity, check the declared method or run a controlled recipe comparison. It should not be used to infer unmeasured cultivar identity, nutritional composition or authenticity. If the question concerns a particular acid rather than the overall titration response, discuss an appropriate compound-specific analysis with the laboratory.

Compare the method, acid basis and units first

Two reports can both say “acidity 0.60%” and still describe different measurements. One may be mass-based and another volume-based. They may use different endpoints, different sample fractions or different acid equivalents. Before deciding whether one lot is more acidic than another, obtain enough information to understand both numbers.

Frozen mandarin segments show the supplied citrus form. The report should separately identify the preparation, endpoint and acid basis.

Published methods illustrate why the endpoint must be named. The UC Agriculture and Natural Resources fruit protocol uses an endpoint of pH 8.2. The publicly accessible extract of AOAC 942.15 describes interpolation to pH 8.1 for its glass-electrode method. These references do not justify silently changing a supplier’s agreed endpoint. Record the method and version actually used.

The acid name also needs sufficient detail. The AOAC extract lists a factor of 0.070 for citric acid monohydrate, whereas the UC fruit protocol lists 0.064 for citric acid. The latter is consistent with the approximately 192.1 molecular mass and three-equivalent calculation shown in the manufacturer procedures for anhydrous citric acid. Do not treat these factors as interchangeable or interpret their difference as a change in the physical fruit.

The following table is an authored report-comparison aid. It does not select the laboratory method or impose acceptance limits.

A short fictional calculation makes the denominator visible. Assume a 10.00 g original sample, a method-approved endpoint and 10.00 mL consumption of 0.1000 N sodium hydroxide, with no blank correction or prior dilution factor required. Using the rounded anhydrous citric factor 0.064 g per milliequivalent, the result is 10.00 × 0.1000 × 0.064 × 100 ÷ 10.00 = 0.640 g per 100 g. These are invented teaching values, not a fruit specification or a tested lot.

With those same assumed titration inputs, using the monohydrate factor 0.070 would report 0.700 g per 100 g on that different basis. The titrant consumption has not changed. This is why a spreadsheet should preserve the stated acid convention instead of normalising the column heading to an unexplained “acid %”. Have the laboratory confirm any conversion needed for an actual result.

Do not relabel g/100 g as g/100 mL. Converting a mass-based concentration to a volume-based one requires appropriate density information and consistent units. By contrast, converting g/100 mL to g/L changes the scale by a factor of ten while retaining the volume basis. Distinguish a legitimate unit conversion from a change in what the sample or method represents.

Water added inside the analytical procedure needs similar care. Thermo Fisher’s orange-juice application note weighs the original juice aliquot, adds water for titration and retains the original sample weight in the calculation. That is different from preparing a diluted extract and titrating only part of it, where the calculation must account for the portion represented. Ask the analyst to explain the preparation; do not apply a second dilution factor automatically.

Prepare a representative frozen-fruit sample

A reliable comparison begins before the electrode enters the beaker. Define the material that the result should represent and how the laboratory portion is selected. A few convenient pieces from the top of a bag may not answer the same question as a sample prepared under the agreed lot-sampling plan. Record the package and lot identity so that a later discussion can return to the actual material tested.

Illustrative whole-product preparation: retain the specified material, prepare it consistently and identify the portions tested. The laboratory method determines the actual preparation conditions.

Frozen fruit adds a practical complication: solids and released liquid can separate during preparation. If the requested test represents the whole supplied product, do not discard liquid casually and then describe the remaining material as the original sample. If the method intentionally tests expressed juice or a drained fraction, state that explicitly. The right choice depends on the defined method and the question, rather than a universal rule to blend every fruit sample.

For the fictional apple-wedge example, the team might agree a whole-product preparation that retains the released liquid and mixes the identified material before taking analytical portions. The illustration shows that concept. It specifies no thawing time, temperature or validated preparation method. The laboratory must use a suitable documented procedure and handle the sample so the preparation itself does not create an unexplained difference.

The UC fruit protocol offers different routes to clear juice, including pressing and filtering or homogenising and separating the liquid. That is useful evidence that “prepare the fruit” can conceal several distinct operations. When comparing frozen puree, pieces and juice, ask whether the reports refer to comparable material before comparing their acid numbers.

Instrument and reagent checks are separate tasks. A calibrated electrode does not establish the actual concentration of the sodium hydroxide used in the calculation. Hanna’s fruit-juice application dataset, for example, records electrode calibration and titrant standardisation separately. Ask for the method’s quality-control arrangements rather than assuming that “automatic titration” resolves every source of variation.

Where laboratories disagree, exchange the complete preparation and method details first. Check whether one measured a separated liquid, used a different endpoint or selected another acid basis. Then arrange any necessary comparison using identified portions and agreed conditions. Averaging two incompatible results can produce a tidy number while leaving the original disagreement unanswered.

Check both measurements in the intended recipe

Incoming pH and TA can help development understand a fruit ingredient, but the purchasing decision still needs an application context. State how much fruit enters the recipe, what other ingredients are present, where it is added and which finished-product observations matter. Without that context, a laboratory value can become an arbitrary target detached from the food being made.

Conceptual formulation sequence. The finished sauce has its own pH and TA records; the illustration supplies no result, process setting or safety conclusion.

Consider a fictional mandarin sauce trial comparing an approved ingredient with a proposed alternative. Use identified materials and keep the recipe and preparation conditions consistent for the initial comparison. Review the incoming analytical information, then assess the resulting sauce at the agreed observation point. Record the finished sample separately so an ingredient result is not accidentally presented as a measurement of the sauce.

If the team adjusts water, sweetener or another ingredient to accommodate the alternative, document the revision. That may be a useful development route, but it now evaluates a changed recipe. Retain enough information to distinguish the original matched comparison from the later adjustment. Otherwise, the next buyer may order the alternative for the old recipe without understanding why the trial had appeared acceptable.

Soluble-solids information can add context. A Brix-to-TA comparison can be useful when both measurements follow a consistent convention, but the ratio is not a universal sensory acceptance score. State the TA units and basis used in the denominator; changing from a percentage to g/L without adjusting the convention changes the numerical ratio. Our guide to comparing Brix in IQF fruit explains the separate soluble-solids measurement.

Keep actual sensory observations in the record. Ask whether the sauce has the intended flavour balance and whether the agreed texture and appearance are acceptable. A matching ratio or pH can support the discussion, but neither replaces evaluation of the complete product. Avoid correcting a recipe from a single analytical value before establishing what difference needs to be corrected.

Safety and shelf life require their own appropriate assessment. CFIA’s procedure treats titratable-acidity work and pH verification for specified processed products as separate activities. For your product, use the applicable food-safety plan and qualified process review. A low incoming fruit pH or an acceptable TA result alone does not establish that a finished recipe is safe, shelf-stable or suitable for a proposed storage period.

Write separate, usable specification rows

Once the team knows which measurements matter, specify pH and TA separately. Each row should connect its acceptance requirement to a defined material and method. The pH row needs the relevant preparation and measurement conditions. The TA row additionally needs the endpoint, acid basis and explicit units. Use limits justified for the ingredient and application; the fictional values in this guide are not recommended purchasing ranges.

Keep the full method available even if the commercial specification uses a short reference. A concise row can point to a controlled method and version rather than reproduce the entire laboratory procedure. Agree how revisions will be handled. A supplier should not change a method, endpoint or reporting basis while leaving an apparently unchanged specification value that the buyer interprets as directly comparable.

Describe how actual lot results will be reported. Where a COA is required, connect the result to the lot, test date, method reference and agreed units. Clarify how results near a decision limit, rounding and any relevant measurement uncertainty are handled through the agreed acceptance process. Do not add an improvised tolerance after a disputed shipment arrives.

If an acidity result changes, review the evidence in a useful order: confirm the sample and lot, confirm preparation and calculation, compare the agreed limit, then investigate the ingredient or recipe where the difference remains. This sequence does not assume that every difference is analytical error. It makes sure the supplier and buyer are discussing the same measurement before deciding the next action.

The final record should allow another colleague to reconstruct the decision without interpreting a bare percentage. They should be able to identify what was measured, how the result was expressed, which application was assessed and why the ingredient was accepted. That is what makes pH and TA useful procurement information across repeat orders.

References

1. USGS: pH and water, logarithmic measurement.
2. UC ANR: measurement of pH and titratable acidity.
3. AOAC 942.15: publicly accessible method extract.
4. Hach: pH and acidity in wine and fruit juice, Edition 4.
5. Thermo Fisher: titratable acidity in orange juice.
6. Hanna Instruments: fruit-juice titration dataset, calibration and standardisation procedure.
7. CFIA: processed-product grade verification, acidity sections.

More guides and related supply information