Inventory first, write-back later
Modern stacks expose APIs and webhooks. Older ERPs often expose exports, files, queues or a database view. We price the job only after we know how a row can be read and how a row can be written. No API is not a stop - it is a reason to put an approval panel in the middle.
Default design: the model prepares the record, a person confirms, the ERP or CRM commits. Logs keep the input, the field and who clicked yes. Silent overwrite is a separate, narrower decision.