Create and Refresh a Pivot Table in Apple Numbers

Quick answer: Select the pivot table, then use Organize sidebar → Pivot Options → Refresh. Numbers requires a refresh after its source data changes. If the new rows are still missing, check whether they belong to the source table and whether the pivot was created for only selected cells. A refresh does not mean “summarize every cell anywhere on the sheet.” Apple documents the refresh control.

Requirements and scope

These are Numbers for Mac instructions based on Apple’s 15.4 user guide, checked October 15, 2026. Check the app version with Numbers → About Numbers. The creation commands below are Mac menu-bar commands. On iPhone, Apple instead documents the table/cell action menu and separate Create Pivot Table and Create Pivot Table for Selected Cells choices. This walkthrough does not claim the Mac controls exist in Numbers for iCloud. See the Mac guide and iPhone creation guide.

Use a flat source table with one record per row, clear column headers, and numeric amounts. Apple requires at least one nonheader data cell and excludes cells merged across adjacent rows from a pivot source. Do not mix a manual grand-total row into the body of the source: that would summarize the total alongside the transactions.

Reproducible sales example

Download the feature-practice sales CSV, or enter the following into a three-column table named Sales. Use one header row, so the data occupies A1:C9. CSV supplies the source records, not a ready-made pivot table.

Region	Channel	Amount
North	Online	120
North	Retail	80
South	Online	90
South	Retail	140
North	Online	60
South	Online	30
North	Retail	40
South	Retail	20

Before creating the pivot, check there are eight records and the amounts sum to 580. A separate check table can use =SUM(Sales::C2:C9). See SUM.

Build the summary from the entire table

1. Select Sales.
2. In the menu bar, choose Organize → Create Pivot Table → On New Sheet. This is the whole-table choice. The alternatives beginning For Selected Cells deliberately use a selected range.
3. Select the new pivot. In Organize → Pivot Options, drag Region to Rows, Channel to Columns, and Amount to Values.
4. Open the details control beside the Amount value field. Under Summarize by, choose Sum. Use an ordinary value display rather than a percentage or running total.
5. Compare the result with the benchmark below.

Apple documents whole-table versus selected-cell creation, field placement, and value calculations separately. A newly created pivot is blank until fields are added.

Region	Online	Retail	Total
North	180	120	300
South	120	160	280
Grand total	300	280	580

You can audit one intersection independently with =SUMIFS(Sales::C2:C9,Sales::A2:A9,"North",Sales::B2:B9,"Online"), which should return 180. See SUMIFS. If your locale uses semicolons as argument separators, enter the formula using your app’s local syntax.

Add a row, then refresh

Add a ninth body row inside Sales, containing:

Region	Channel	Amount
North	Online	50

The source now occupies A1:C10. A row in another table, or a text box placed underneath Sales, is not a new record in Sales.

Select the pivot, open Pivot Options, and click Refresh. The same area reports when it was last refreshed. Check these three numbers rather than judging the update by appearance:

• North / Online becomes 230: 180 + 50.
• North total becomes 350: 300 + 50.
• Grand total becomes 630: 580 + 50.

South should remain 280. If South changes too, look for a second source edit, a moved field, or a different aggregation. As an additional control, =SUM(Sales::C2:C10) should now return 630.

The numbers above are independently calculated targets, not a claim that this example was run in the native app.

Refresh and source coverage are separate checks

Think of the pivot as answering two questions: which records belong in the calculation? and when were those records last read? Refresh addresses the second question.

For a growing transaction list, the whole-table creation option is usually the simplest choice because the source is defined as the table. Still verify each import adds records to that same table and refresh before using the report. Do not assume a pivot made for selected cells has included an appended row merely because that row looks adjacent to its original selection. Whether inserting or appending changed a boundary needs checking in the actual file.

Try this deliberate coverage test on a separate practice pivot:

1. In Sales, select A1:C8: the header and first seven original records.
2. Choose Organize → Create Pivot Table → For Selected Cells on New Sheet.
3. Arrange the same three fields with Amount summarized by Sum.
4. Expect 560, not 580 or 630. This selection excludes the original South/Retail 20 and the appended North/Online 50.
5. Refresh it. If its source still excludes those rows, refreshing alone cannot add their amounts.

Apple says selected-cell source ranges can be edited later, but its retrieved text does not spell out the range-edit dialog. Rather than rely on an unverified button sequence, the following recovery uses documented creation commands.

Recover a report with uncertain source boundaries

Keep the old pivot until the replacement is verified. Create a new pivot from the entire Sales table, place the same fields, and choose the same Sum calculation. The expected current grand total is 630.

If the new whole-table pivot is correct while the old one is not, compare the old source selection and filter settings. If both are wrong, investigate the underlying records and value field. Do not delete a production pivot until charts, formulas, and people using it have been accounted for; a replacement is a diagnostic step, not an instruction to discard a report blindly.

Troubleshooting in a useful order

Symptom	Check next
An existing amount changed but the pivot did not	Refresh the selected pivot and inspect its refresh time.
Old edits appear, new records do not	Confirm the appended rows are in the source table; compare whole-table and selected-cell scope.
Amount shows 8 or 9	The field may be counting records. Set Summarize by → Sum and verify amounts are numeric.
The total is correct but a region seems missing	Check pivot filters, field placement, and whether totals are hidden.
North appears as multiple groups	Inspect the original labels, including spaces. Use TRIM in a helper to investigate.
The source sum is also wrong	Fix the source first. A pivot cannot repair missing transactions or amounts stored incorrectly.
The pivot is blank	Add fields to Rows, Columns, and Values; creation alone does not choose them.

After every monthly import, retain a small reconciliation: source record count, source amount total, pivot total, and the refresh time. A total that agrees is useful; agreement at a few region/channel intersections is stronger evidence that the grouping is also right.

Verification and sources

The totals 580, 630, and 560, plus the grouped results, were independently calculated. This tutorial was not tested in Apple Numbers, and no application screenshots were captured. Exact selected-range editing controls have not been verified. Documentation was retrieved on October 15–16, 2026.

• Create a pivot table
• Refresh a pivot table
• Add and arrange pivot table data
• Change calculations, grouping, and totals
• SUMIFS function reference