Deleting a storage location removes it from your account permanently — the location record, its name and details, and the CSV key that referenced it. Items previously held there aren't deleted; the app insists you move them somewhere else first. That's the only real guard around the action.
This article covers deleting a location that's empty, the short detour required when items are still attached, and what changes elsewhere in the app the moment a location goes away.
Opening the delete control
In the left nav, open Settings → Storage. Each row in the Storage Locations list has a trash icon to the right of the pencil. Click it. The app asks you to confirm, since deletion is permanent and there's no restore command for storage locations.
If the location has zero items assigned to it, confirming deletes it right away, and it drops off the list.
Locations with items can't be deleted directly
If items are still attached when you click the trash icon, the confirm step won't let you finish — the location has to be empty first. The item count on the row tells you how many are in the way.
The fix is to move those items somewhere else:
Move from Holdings: Open the Holdings page, filter by the location you're emptying, select the items, and use Move to Location in the bulk action bar. Pick the destination and confirm.
Move via Bulk Import: If you're reorganizing on a larger scale, a CSV with the destination location's CSV key in the storage column can reassign many items in one pass.
Once the count on the row reads zero, the trash icon behaves the same as it does for any empty location. See [Moving items between locations] for the full step-by-step.
What deletion removes
Three things go away when you confirm:
The location record: Type, name, institution, reference, and notes are erased from your account.
The CSV key: The stable key that bulk imports used to reference this location stops resolving. Any future CSV that names the old key will fail validation on the storage column.
The location's presence in the UI: The Holdings filter drops the option, the Dashboard's Custody Breakdown and Holdings by Location widgets recompute without it, and the Custody Statement no longer lists it as a section.
Items that used to live in the deleted location are unaffected by the deletion itself — they were moved elsewhere before deletion could happen, and they keep all their data: purchase price, locked-in spot, labels, status, everything.
When to delete versus rename
Deletion is the right move when the location itself no longer exists or no longer represents anything you want to track — you closed the IRA, the depository account was wound down, you gave up the safe deposit box. In those cases the cleanest record is an account that doesn't carry a defunct row.
If the location still represents the same physical place but the details have changed, for example, a new account number, a new custodian name after a rebrand, or a renamed depository, editing is the better tool.
Edits preserve the CSV key and the historical link between the location and the items that have ever lived in it.
After deletion: your records
Two effects to keep in mind once a location is gone:
Custody Statement: The deleted location no longer appears as its own section. Items roll up under wherever you moved them.
Tax Report: If the deleted location was IRA-typed, the items you moved are taxable from the move forward — unless their new location is also typed IRA Account. Same rule as a retype: an item's current location is what counts.
If you want a snapshot of how custody looked before deletion, export the Custody Statement to CSV first.
Where to go next
[Moving items between locations]: The step required before a populated location can be deleted.
Editing a storage location: Often the right action when you were reaching for delete.
[The five storage location types]: Reference for the Tax Report implication mentioned above.
[What the Custody Statement is]: The report that reflects the post-deletion view of where everything lives.