PlanMaker PRODUCT Function: Multiply Ranges and Understand Text

PRODUCT multiplies its numeric inputs, making it useful for multi-step conversion factors, repeated percentage adjustments, units sold by units per package, and products across multiple ranges. It is equivalent to using multiplication operators for numeric entries: =A2*A3*A4. However, PRODUCT has an important type-filtering behavior with referenced cells which can make it differ from A2*A3*A4 when a range holds text or Booleans. [S1]

Use SUM for addition; use SUMPRODUCT for multiplying corresponding elements and adding those products, not as a generic substitute for PRODUCT. A PRODUCT result does not represent revenue, profitability or statistical probability unless your inputs and units justify that interpretation.

=PRODUCT(Number1 [, Number2, Number3 ...])

There is no argument for precision, ignoring zeros or alternative operators. The 2026 reference does not specify a PlanMaker-specific upper argument cap in its PRODUCT entry; do not silently import Excel’s documented 255-argument cap into PlanMaker. Examples reproduce the manual’s English notation; the exact separator punctuation for a user’s locale must be checked in the installed editor. [S1, S2]

Enter the values:

In B2, type =PRODUCT(A2:A4). Expected: 24; this matches SoftMaker’s official equivalent sample for numeric 2, 3 and 4. In B3, type =A2*A3*A4; independent multiplication also gives 24. In B4, type =PRODUCT(A2:A4,5); independent expectation 120. The extra B4 multiplier tests mixing a referenced range and a directly entered number. [S1, C1]

SoftMaker documents a particularly useful counterexample:

=PRODUCT(2,"5",TRUE)

The expected result is 10, because the directly supplied text string "5" is read as numeric five in this example and directly supplied TRUE contributes 1. But if A2:A4 contains numeric 2, the text string "5" and the logical value TRUE, then =PRODUCT(A2:A4) has the vendor-documented result 2. Text and logical values in referenced ranges or arrays are ignored, whereas the directly supplied values in the documented counterexample are converted. [S1]

A text cell merely displaying a numeral is not the same as a number cell. To reproduce the range form, enter the second cell explicitly as text (e.g., format it as Text before entering 5) and enter TRUE as a logical formula/value rather than the quoted string "TRUE". If the cell becomes a numeric 5 during entry, the test no longer reproduces the documented comparison.

This shows why replacing PRODUCT(A2:A4) with =A2*A3*A4 is safe only after checking types and the desired coercion policy. The operator’s handling of text has not been tested in PlanMaker in this run.

A source inventory starts at 100 units and has multipliers +3%, +5%, and −2%. Enter numeric multipliers into D2:D4:

=PRODUCT(D2:D4) independently yields 1.05987; =100*PRODUCT(D2:D4) yields 105.987; =PRODUCT(D2:D4)-1 yields 0.05987, or 5.987% net compound change. The product formula is vendor-documented; these particular input values and results are independently calculated, not observed in PlanMaker. Do not instead add the percentage changes (3+5−2=6%): multiplicative compounding is not a simple sum. [S1, C1]

Place numeric 2,3,4 in A2:A4 and numeric 5,6 in C2:C3. =PRODUCT(A2:A4,C2:C3) has the independently checked expectation 720 (2×3×4×5×6). A zero entered into any included numeric cell forces the mathematical product to zero; an empty referenced cell is not the same as an entered numeric zero. Use PRODUCT on ranges that are specifically intended to represent factors rather than on mixed notes and audit labels. [S1, C1]

Boundary caveat: The inspected PlanMaker PRODUCT entry doesn’t state what result or precise error token is displayed for all-empty/all-text ranges, overflowing magnitudes, or invalid literal strings. These remain unverified engine edge cases. Excel’s handling of such boundaries must not be presented as a PlanMaker test.

SoftMaker documents PRODUCT in its 2026/NX English manual. Microsoft documents Excel’s PRODUCT(number1,[number2],...), including ignoring text and logical values in referenced ranges. Both names and basic intent align, but we did not open/save/recalculate a workbook in either app. Microsoft says Excel permits up to 255 arguments; this is an Excel-specific limit and not evidence of PlanMaker’s cap. SoftMaker’s manual covers desktop operating systems and discusses mobile; none was run for this guide. [S1, E1]

• SUM is additive, not multiplicative.
• SUMPRODUCT multiplies aligned arrays and sums resulting products.
• The official reference lists SUM as related in its PRODUCT entry.

[S1] SoftMaker Software GmbH, PlanMaker Manual, SoftMaker Office 2026 and NX, printed pp. 765–766, entry PRODUCT. https://www.softmaker.net/down/pm2026manual_en.pdf. Authoritatively supports syntax, numeric/reference handling, direct literal coercion and vendor examples 24, 10, 2.

[S2] SoftMaker, same manual, printed pp. 64 and 461. Supports regional decimal separators; does not prove that a particular locale uses semicolons for formulas.

[E1] Microsoft, PRODUCT function (Excel), https://support.microsoft.com/en-us/excel/functions/product-function. Excel-only support including Excel’s separately documented optional arguments and limit. Not a PlanMaker runtime observation.

[C1] Independent arithmetic reference values prepared 2026-10-13, UTC. The additional results 120, 1.05987, 105.987, 0.05987 and 720 were calculated without PlanMaker or Excel. Native execution: not performed.