What this operation supports in QuickBooks
Updates an existing customer record. Because QuickBooks requires optimistic concurrency control, the update must include the customer's current SyncToken (obtained from a prior read) along with the fields being changed.
Implementation details
If the SyncToken sent doesn't match the customer's current version -- meaning someone or something else updated it since it was last fetched -- the update is rejected rather than silently overwriting those other changes.
Operational considerations
This means an update workflow generally needs to fetch the customer first to get its current SyncToken, then send the update immediately after, rather than reusing a SyncToken value cached from much earlier.
Use cases
Automate customer profile maintenance.
- Propagate changes to CRM systems.
- Update billing terms and preferences.
- Notify customers of profile updates.
- Audit customer history for compliance.