Do not begin with write access
Start by reading the product catalog, customer context and approved commercial data needed for a quotation. Validate matching and review behavior before allowing a new tool to create or update ERP records.
Define system ownership
The ERP should remain the source of truth for master data and posted transactions. The quotation workspace can own evidence, intermediate analysis, supplier comparisons and approval context.
Map identifiers and exceptions
Customer item descriptions rarely match ERP item codes directly. Store the mapping evidence and route uncertain matches to a reviewer. Avoid creating duplicate products simply to complete a quote.
Write only approved outputs
After approval, transfer structured quote data through controlled APIs with validation, idempotency and logs. Failed writes should be visible and recoverable without duplicating records.