Use this function when one filter is not sufficient: for example, compare online orders in the East region, average completed in-store transactions, or investigate above-threshold orders within a particular territory. Each criterion has its own testing range; they are combined using logical AND, not OR. Unlike AVERAGEIF, the AverageRange comes first and is mandatory.

=AVERAGEIFS(AverageRange, Range1, Criterion1 [, Range2, Criterion2 ...])

The English name, required first three arguments and repeated optional criterion-range pairs are taken from the PlanMaker 2026 AVERAGEIFS manual. The square brackets mean optional in the documentation and are not typed in the worksheet.

Critical difference: AVERAGEIF(Range, Criterion, [AverageRange]) puts the optional values range last; AVERAGEIFS(AverageRange, Range1, Criterion1, …) puts it first. This difference is explicitly highlighted in SoftMaker’s reference. SoftMaker documents equal dimensions for criterion ranges, so do not rely on an Excel-specific resizing quirk.

Enter these exact cells in columns A–D, rows 1–9. Keep column C numeric and avoid blank rows.

1. Enter the table with headers in row 1 and data in rows 2–9.
2. Click an unused cell, such as F2.
3. Enter the formula, keeping its first argument pointed at the amounts.
4. Compare the result in your installation to the arithmetic shown here.

=AVERAGEIFS(C2:C9,A2:A9,"East",B2:B9,"Online")

Expected result: 71.666666…. East and Online both hold only in rows 2, 6 and 9, where the amounts are 120, 35, and 60. Therefore (120 + 35 + 60) / 3 = 215 / 3 = 71.666666….

Change one criterion to compare groups

=AVERAGEIFS(C2:C9,A2:A9,"East",B2:B9,"Store")

Expected result: 122.5 because the matching East/Store rows contain amounts 90 and 155, and (90 + 155) / 2 = 122.5.

Use the same numerical amount column as both the range to average and the threshold test:

=AVERAGEIFS(C2:C9,A2:A9,"East",C2:C9,">=100")

Expected result: 137.5. The qualifying East amounts are 120 and 155; the other East rows are below 100. 275 / 2 = 137.5.

Another analysis combines sales channel with completion status:

=AVERAGEIFS(C2:C9,B2:B9,"Store",D2:D9,"Closed")

Expected result: 115. Only the Store-and-Closed amounts 75 and 155 qualify; (75 + 155) / 2 = 115.

Guard a report against an empty matching group

A useful dashboard can display text when no rows match all conditions:

=IF(COUNTIFS(A2:A9,"North",B2:B9,"Online")=0,"No matching orders",AVERAGEIFS(C2:C9,A2:A9,"North",B2:B9,"Online"))

Expected result: No matching orders for this printed table. This demonstrates the intended control-flow logic with PlanMaker’s separately documented IF and COUNTIFS functions, not an executed native test. If matching category rows contain blank or nonnumeric amounts, additionally validate numeric counts rather than only the category count.

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 — AVERAGEIFS
• SoftMaker PlanMaker 2021 — AVERAGEIFS
• SoftMaker PlanMaker 2026 — 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.