Update the vendor across change event line items in Procore
Have you ever found the same wrong vendor on forty line items?
Vendors get merged, renamed, and misassigned. Procore has no bulk edit for existing line items, so here is how to reassign one across a whole project without re-keying it.
Procore’s change event CSV import adds new line items, it does not edit existing ones, so there is no native path to reassign a vendor in bulk. To do it in one pass: pull the project’s change events into Excel, filter the line item sheet by the old vendor, fill the new vendor down, sort out the contracts that no longer match, then sync.
Pull the change events and their line items into Excel
Open the Change Events tool in the Sandspit task pane and click Pull from Procore. The second sheet it writes has one row per line item on every change event in the project, with the vendor and the contract as dropdown columns.
Filter the line items to the wrong vendor
Filter the Vendor column on the line item sheet to the vendor you are replacing. Every affected line across every change event on the project is now in front of you.
Watch out: lines Procore has tied to a PCO, a commitment, or a budget change show as Locked and cannot be edited from Excel. Fix those in Procore.
Fill the replacement vendor down
Pick the replacement from the Vendor dropdown in the first row and fill it down. The vendor has to be in the project directory to appear in the dropdown. If it is not there yet, add it in Procore and refresh the picklists.
Sort out the contracts
Vendor and Contract travel together. A contract must belong to the vendor on its row, so changing the vendor means the old contract no longer fits. Clear it, or pick one of the new vendor’s contracts. The task pane offers Clear vendors and contracts as one action if you want a clean slate.
Watch out: changing the vendor on a line does not flow to a linked commitment or PCO. Those keep their own vendor.
Review and sync
Clear the filter, check the Ready to sync list, and click Sync. Lines are sent one change event at a time, so a rejected line fails its change event’s batch and the rest go through. Only the vendor and contract fields you changed are sent.
Why the vendor is the field that breaks
Vendors change for reasons that have nothing to do with the job. A subcontractor gets acquired. Accounting merges two duplicate records. Someone picks the wrong entry from a directory with three similar names in it. By the time anyone notices, the vendor is attached to line items across several change events, and the cost is reporting against the wrong party.
The fix is conceptually trivial: replace one value with another. The reason it takes an afternoon is that Procore gives you no way to edit existing line items in bulk, and each line’s contract is tied to its vendor.
Why the CSV route does not help
The instinct is to export, fix the column, and re-import. That does not work for this. Procore’s Schedule of Values CSV template is an insert path. It adds line items to a change event. Run it against records you meant to update and you get duplicates, not corrections.
So the native options are opening each line item by hand, or moving the edit into a sheet that can update existing records and send only the fields that changed.
Frequently asked
Can I bulk change the vendor on change event line items in Procore?
Not natively. Procore’s CSV import for change events adds new line items rather than editing existing ones, and the list view’s inline editing covers only a limited set of fields. Reassigning a vendor across many existing line items means opening them individually or working in a sheet that can edit and sync in bulk.
Why does the contract clear when I change the vendor?
A contract belongs to one vendor. Procore will not accept a line whose contract is owned by a different vendor than the one on the line, so Sandspit treats vendor and contract as a pair. Pick a contract from the new vendor, or leave it blank.
What happens to the budget code when I change the vendor?
Nothing. Changing the vendor does not rewrite the budget code on the line item. That is usually what you want, but it is worth confirming, because a vendor swap that should also move cost to a different code will otherwise leave the amounts sitting against the original budget line.
The replacement vendor is not in the dropdown. Now what?
The dropdown lists the project directory. Add the vendor in Procore, or create it while importing a new change event with Change Event Import, then click Refresh Picklists in the task pane. The Change Events edit tool does not create vendors itself.
Does this work across multiple projects at once?
No. A Sandspit workbook works with one Procore project. The pull brings in every change event and line item on that project, which is usually where the wrong vendor lives. For several projects, repeat in one workbook per project.
Procore Project Financials. Needs Standard or Admin on the Change Events tool. Lines tied to a PCO or commitment are locked.
Step-by-step mechanics, every column, and every error message are in the documentation.
