Sodium Reduction in Sauces and Soups: Balancing Saltiness, Umami and Mouthfeel
A sodium-reduction brief should begin with two questions: what nutritional target must the finished product meet, and what eating experience must it retain? For a sauce or soup, the aim is not simply to make a lower-salt sample taste stronger. It is to preserve the product’s identity while meeting a defined formulation target.
This guide proposes a practical approach for development teams: establish the reference, identify the sensory gap, select a targeted intervention and compare the results under controlled conditions. Publicly described T. Hasegawa technologies provide useful context; the decision should still be made in the actual product.
1. Define the target using total sodium
Salt and sodium are not interchangeable terms. Sodium chloride is one source of sodium; ingredients such as monosodium glutamate and sodium bicarbonate can also contribute. A reduction in added table salt does not, by itself, quantify the reduction in total sodium. [1]
Start with a sodium inventory for the complete recipe, using current supplier specifications. Record the baseline and target on the same basis, such as milligrams per 100 grams of ready-to-eat product. For powders or concentrates, document the intended dilution instead of comparing the dry product with a prepared serving.
Write down what must remain unchanged: the characteristic flavor, preparation instructions, portion size, processing route and target cost. This creates a clear brief before ingredients are screened and prevents a sodium-reduction project from quietly becoming an entirely different product.
2. Diagnose the gap before choosing a solution
Human taste research has demonstrated that salts can suppress bitterness in tested mixtures. That finding gives formulators a reason to investigate changes beyond saltiness, without assuming that every sauce or soup will respond in the same way. [2]
For the first comparison, ask the panel to describe the difference rather than immediately propose an ingredient. Is the first taste insufficiently salty? Has the savory middle become weaker? Is the finish bitter or unbalanced? Does the product feel less rounded, or has its physical consistency actually changed?
Use product-specific questions. In a tomato sauce, examine the perceived balance of tomato, acidity and seasoning. In a mushroom soup, check whether mushroom character remains distinct rather than being replaced by a generic savory note. For a creamy soup, assess perceived richness separately from the measured flow behavior. These are diagnostic prompts, not predictions of what a sodium reduction will necessarily cause.
3. Separate saltiness, umami and kokumi
Use distinct terms on the sensory scorecard. Record saltiness as its own attribute and umami as the savory taste dimension. Kokumi should not be used as another word for either one: research has associated kokumi-active substances with perceived flavor thickness, continuity and mouthfulness in the systems tested. [3]
Keep the sensory and physical measurements separate. A panel’s description of a fuller taste is not a viscosity measurement. Conversely, increasing the thickness of a soup is not, by itself, evidence that its savory taste has improved. Set acceptance criteria for each attribute that matters to the product.
4. Where T. Hasegawa’s technologies fit
T. Hasegawa describes its Flavor Modulation portfolio as including salt-reduction support, umami enhancement, mouthfeel improvement, bitterness blocking and off-note masking, with solutions tailored to the customer’s formulation. [4]
For a development brief, translate that broad capability into a specific task: improve the finish, restore savory balance or investigate perceived fullness. Avoid asking one modifier to solve every difference at once. Request the relevant technical specification and a starting evaluation range for the particular application rather than selecting a dose from an unrelated example.
BOOSTRACT®: a candidate for flavor depth and fullness
According to T. Hasegawa, BOOSTRACT® is a technology for adding or enhancing kokumi in food and beverages; the company describes kokumi as amplification in mouthfeel, taste and texture that enhances existing profiles. [5]
This makes it a candidate to discuss when those attributes are part of the brief—not a one-for-one replacement for sodium chloride. Its public description does not establish a guaranteed sodium-reduction percentage in a particular soup. Confirm the specific grade, sodium contribution, labeling documentation and suitability for the target market before evaluation.
5. Build a three-sample comparison
Begin with a small, interpretable experiment. The following design is a proposed screening framework, not a set of tested commercial recipes.
Sample | Formulation | Question it answers |
A — Reference | Current approved recipe | What eating experience are we trying to preserve? |
B — Reduced sodium | Lower-sodium recipe without the proposed flavor correction | What changed when sodium was reduced? |
C — Targeted correction | Lower-sodium recipe with the candidate flavor solution | Does the intervention address the identified gap? |
Match B and C for total sodium. Count any sodium introduced by the candidate solution and adjust the comparison accordingly. Otherwise, an apparent flavor improvement could be confounded by a higher final sodium level. Document any accompanying changes to solids, fat, water or processing rather than treating those samples as equivalent.
Use blind sample codes, balance the serving order and keep preparation, serving temperature and portion size consistent. Agree on a short scorecard covering saltiness, savory depth, characteristic aroma, unwanted finish, mouthfeel and overall acceptance. Repeat the comparison, and assess more than the first spoonful.
For promising candidates, repeat the assessment after the intended industrial process and at relevant points during the proposed shelf life. Separate descriptive panel findings from consumer acceptance: the decision to advance should match the project’s predefined criteria, not a single favorable comment.
6. Keep technical approval separate from taste approval
Before commercial release, plan verification of the final sodium content and review the revised formulation with the responsible quality and food-safety specialists. Include the product-specific controls they identify, such as pH, water activity, physical stability, processing adequacy and microbiological shelf-life validation where relevant.
Do not treat a successful tasting as approval of safety, shelf life or a nutrition claim. The terminology used on packaging and the supporting evidence should receive a separate regulatory review for each intended market. No universal reduction target, ingredient dose or label claim is proposed here.
7. Turn the project into an actionable brief
Share the product category, current and target sodium values, calculation basis, process conditions, target market, ingredient restrictions and cost-in-use target. Add a reference sample or a precise description of the flavor to preserve. Where available, include the observations from the reference and reduced-sodium comparison.
Send that brief to Galbora to discuss the next steps for flavor selection and sample evaluation. The objective is a solution that addresses the product’s documented sensory gap—not simply a stronger flavor or an impressive technology name.
The practical sequence is straightforward: measure the starting point, diagnose the difference, test a targeted correction and validate the finished product.
Related reading
Sources
Sources checked on 16 September 2026. The trial framework is a proposed development approach, not a report of Galbora laboratory results. Manufacturer descriptions do not establish performance in an untested formulation. Product suitability, availability and documentation require project-specific confirmation. BOOSTRACT® is a T. Hasegawa trademark.
Comments