AVERAGEIF checks a range for a criterion and averages the numeric values associated with matching rows. Its optional third argument decides which cells are averaged. If that argument is omitted, it averages the matching numeric cells from the tested range itself. This differs from SUMIF, which adds matching amounts rather than dividing by the number of eligible numeric amounts.

=AVERAGEIF(Range, Criterion [, AverageRange])

This is SoftMaker’s documented English spelling and argument order, with the optional item in square brackets for documentation only (do not type the brackets).

Source: Official PlanMaker 2026 AVERAGEIF reference. Quoted conditions and the optional last argument are expressly documented there. Keep criteria and amount rows aligned; do not assume unsupported Excel-specific resizing of a mismatched average range.

Create a worksheet with the exact headers in cells A1:D1 and the following values in rows 2–9. Amounts in C2:C9 must be numbers, not text strings with currency symbols.

1. Enter the labels and eight records in the specified cells.
2. Select a blank result cell, such as F2.
3. Type the formula below and press Enter in your own copy of PlanMaker.
4. Compare the displayed number against the independently calculated value.

=AVERAGEIF(A2:A9,"East",C2:C9)

Expected result: 92. East occurs in rows 2, 4, 6, 7 and 9; the amount sum is 120 + 90 + 35 + 155 + 60 = 460, and 460 / 5 = 92.

To compare another region:

=AVERAGEIF(A2:A9,"West",C2:C9)

Expected result: 91.666666…, because West values 75 + 115 + 85 = 275, divided by 3. Changing the display format to two decimals would show approximately 91.67, but does not change the underlying mean.

If AverageRange is omitted, PlanMaker’s documented rule is to average qualifying values in Range itself. Use the order amount column as both the test and the values to be averaged:

=AVERAGEIF(C2:C9,">=100")

Expected result: 130. Only the numeric amounts 120, 115, and 155 qualify; (120 + 115 + 155) / 3 = 130.

A further useful analysis is to average only orders marked Closed, even though the criterion is text:

=AVERAGEIF(D2:D9,"Closed",C2:C9)

Expected result: 93.333333… based on six closed orders with total amount 560; 560 / 6 = 93.333333…. Use a numeric formatting option if you want to show 93.33 rather than the repeating decimal.

Handle zero matching rows predictably

This optional display guard combines functions whose separate purpose is documented in SoftMaker’s references:

=IF(COUNTIF(A2:A9,"North")=0,"No matching orders",AVERAGEIF(A2:A9,"North",C2:C9))

Expected result: No matching orders because the table has no North region rows. The result is derived from counting the eight printed rows and the intended IF/COUNTIF logic; no PlanMaker execution took place. For production, also check whether the matching rows have actual numeric values (a matching category alone does not guarantee a meaningful average).

The English official function references for PlanMaker 2021, PlanMaker 2024, and PlanMaker 2026 all document the syntax displayed above. That establishes documented availability in these releases, not the first release in which the function ever appeared. The 2026 online guide covers the PlanMaker 2026/NX product family; it does not establish that every edition and every Android, iOS, macOS, Windows, or Linux build behaves identically. No edition-specific or device-specific execution has been performed.

SoftMaker explicitly warns that saving a workbook with this function to the older Excel 97–2003 .xls format replaces affected formulas with fixed calculated values. For editable formulas, the 2026 guide recommends a native .pmdx document or modern .xlsx export. The 2021 and 2024 guides additionally list older native .pmd options; this is a documented file-format recommendation difference, not evidence that the function’s arithmetic changed. Make an editable native backup before experimenting with export.

Locale note: The formulas here use the comma-separated English syntax shown in SoftMaker’s references, with a period as the decimal separator. If your installed locale shows a different separator or translated function name, use its formula editor/help. Commas are not guaranteed to be correct in every regional configuration. Confirm spreadsheet cell types and decimal settings when importing data.

• Incorrect argument order: Check whether the average range comes before or after criteria. The two AVERAGEIF-family functions deliberately use different orders.
• Unquoted literal criteria: For string and comparison criteria, follow SoftMaker’s double-quoted examples, such as "East" and ">=100". Without a quoted comparison, the expression may be interpreted differently or rejected.
• Numbers stored as text: Convert imported amounts to genuine numeric cells; otherwise averages can exclude or mishandle entries. This practice example uses numeric literals only.
• No matching numeric rows: A valid arithmetic mean requires at least one included number. Use a count-based guard before displaying a division-by-zero-like error. The native error outcome for this exact edge case was not executed in PlanMaker here.
• Misaligned ranges: Map categories and numeric values row by row. For AVERAGEIFS, matching range dimensions are expressly required by the official manual. Test the corresponding columns and addresses visually.
• Malformed formulas and broken references: PlanMaker’s official error-value guide for the 2024 release documents #NULL!, #VALUE!, #REF!, and #DIV/0! for applicable general error classes. An error code is not guaranteed for every specific invalid AVERAGEIF-family formula; inspect arguments first.
• Expected versus observed results: The numbers on this page were checked by independent arithmetic. They are expected values, not screenshot readings or native PlanMaker test results.

Microsoft Excel documents AVERAGEIF and AVERAGEIFS with the same broad purpose and corresponding English argument order. Nevertheless, do not assume every subtle behavior is identical: criteria coercion, treatment of blanks/text, wildcard support, range resizing, local separators, and old-format export deserve app-specific tests. In particular, Microsoft’s AVERAGEIF guidance permits an average range with different dimensions from its criterion range in certain circumstances; the SoftMaker AVERAGEIF reference reviewed here does not promise that same range-resizing rule. Use equal-height aligned columns for portable workbooks. LibreOffice Calc and Google Sheets offer similarly named functions, but their locale conventions and edge cases were not tested in this batch.

• COUNTIF: count rows matching one condition
• COUNTIFS: count rows matching multiple conditions
• SUMIFS: sum rows matching multiple conditions
• PlanMaker function directory

• SoftMaker PlanMaker — function documentation
• SoftMaker PlanMaker 2024 — AVERAGEIF
• SoftMaker PlanMaker 2021 — AVERAGEIF
• SoftMaker 2026 — Operators in formulas
• SoftMaker 2024 — Error values

Verification status: Official documentation checked; example outcomes were independently reasoned or arithmetically checked where applicable. Not executed in SoftMaker PlanMaker.

• No genuine SoftMaker PlanMaker screenshots are included; this guide does not use mock application images.