Shopify customer total spent is read-only (on purpose)

Finance wants a sheet where test accounts show $0 spend. You open the spreadsheet, find Total spent, type 0, and nothing sticks. It feels like the save failed. The column is not writable.

Shopify customer total spent read only is documented for OO - Bulk Customer Data Editor: total spent, order count, and created date are display-only. You can filter and sort. You cannot overwrite Shopify’s order rollups.

Listing: Free. Spreadsheet in admin. The pitch fields Shopify’s standard editor handles poorly in bulk are Customer Locale and tax-exemption status. 0 reviews, launched 15 September 2026. Do not invent ratings. UI in English.

Yesterday: saves run in batches. Keep the tab open. Today: columns that never join that payload.

Spend is a sum. Staff do not type sums.

Total spent adds orders. Order count counts them. Created date is when the customer record appeared. Reporting, not a merchandising field.

Edit customers in the spreadsheet calls those columns display-only. The FAQ / limitations repeats the list.

Writable: name, email, phone, tags, note, locale, tax exempt, default address, marketing consent (Shopify opt-in rules), metafields the shop defines. Save sends changed fields only. A read-only cell is not in the request.

Shopify’s own customer CSV shows total spent too. Importing a “corrected” spend column hits the same wall. Empty CSV cells do not clear values on update — useful for tags, useless as a way to zero a rollup.

What people try anyway

Zeroing QA accounts in the grid. Fix orders (refund/cancel in Shopify) or use a development store. The sum follows orders.

Rewriting created date after a store move. New shop, new customer ids, new created dates. Migrate locale, tax exempt, tags, address — the fields the editor allows. Leave created date on the new record.

Using order count as a VIP flag. Filter order count ≥ 10, bulk apply tag `vip`. Allowed: you edit the tag. The count stays a filter.

Select-all matching (up to 50,000) to force spend. The cap is how many rows a bulk apply can grab. It does not unlock a column.

Use the column as a lens

Show Total spent. Sort descending. Filter above a threshold. Then change something writable:

• tag `wholesale` / `vip`

• tax exempt for B2B-like accounts (listing USP)

• locale after a CSV import left it empty or wrong (the other listing USP)

Saved views store columns + filters + sort for the whole shop. A view “high spend, empty locale” is the point of a read-only spend column sitting next to a writable locale column.

Segments: build from filters, then Edit in bulk. Segment permissions follow the shop and the staff account. If Shopify blocks protected customer data, editing stays limited until access is approved.

Consent columns have their own Shopify rules (subscribed needs a valid opt-in). Different wall, same lesson: the grid does not outrank Shopify.

Tag high spenders without forging the total

Retailer, 12,000 customers. Marketing wants `vip-spend` above $250. Finance does not want anyone “rounding” spend in a sheet.

1. Customers → More actions → Edit in bulk, or the app dashboard → Start editing.

2. Turn on Total spent (and Order count if you like).

3. Filter total spent ≥ 250. Do not select the whole store.

4. Select matching (under 50k).

5. Bulk apply the tag. Save. Leave the tab open on a large batch.

6. Do not edit Total spent. It moves when an order moves.

QA accounts with weird spend: tag `test`, or delete/archive via the normal customer profile if that is policy. The editor is not a ledger.

Locale and tax exempt are the fields native bulk tools underserve. Total spent is the field native already computes. The app opens the first pair and leaves the rollup closed.

CSV will not write spend either

Export to Excel or Google Sheets (UTF-8 BOM for Excel is in the docs) is fine for *reading* spend. Re-importing a cooked spend column does not write it back. Import matching: Customer ID → email → new record. Locale and tax exempt in that CSV *will* apply — those are the listing USPs.

Customer metafields defined on the shop can appear as columns. Unsupported types may not be editable. Total spent is not a metafield. Do not confuse a custom “lifetime value” metafield (writable if the type allows) with Shopify’s rollup.

Dashboard: support chat and docs. If Shopify blocks protected customer data, editing stays limited until access is approved. That limits writable fields; it does not suddenly make total spent editable.

Works with Excel / Google Sheets via CSV. Same read-only rule for fields Shopify will not let staff type. If a save fails for other columns, Shopify’s error shows per customer — fix those rows and retry remaining. That path never includes total spent, because it never left the client as a change.

Start here

1. OO - Bulk Customer Data Editor — Free.

2. Open the grid. Add the three display-only columns if you need filters.

3. Do not expect Save to send them.

4. Do expect tags, locale, tax exempt, notes, consent, address, supported metafields.

5. Large shops: segment or search first. 50k cap. Batches, tab open, retry listed errors.

Docs: spreadsheet editing, FAQ. Excel / Google Sheets via CSV; Shopify still owns spend.

Wrap-up

Shopify customer total spent read only is Shopify’s sum, count, and created date. Filter on them. Edit tags and the listing USPs (locale, tax exempt). Leave the cell. App: OO - Bulk Customer Data Editor.