Integrations and source ownership

• Order or ERP system. The handoff of an accepted quote needs a downstream order connection. Until it is set up, handoff receipts stay Pending and no external reference is recorded. Agree what the order system needs from the quote and its lines, and how it confirms the order back.

• Price book source. Quotes record the price book revision applied when they are priced. Agree where the price book is maintained, how revisions are named and how unit price USD values reach the quote lines.

• Exchange rate source. exchange rates holds read-only effective rates by Currency and effective from date. Agree where those rates come from and who may mark a rate as Overridden.

• Staff accounts. team members link to platform Users accounts. Agree who requests a new account and its organization scope, and make sure a person who leaves has their team membership set to Active = No.

Each connection needs an agreed source of truth, a field mapping, a stable event or operation key and a retry policy. The app’s guarded operations already record one receipt per operation key, so a repeated delivery must return the original receipt and must not request a second order. Keep credentials in the approved secret store and grant the smallest scope the connection needs.

Rejected or unconfirmed events stay visible as Failed, Pending or needs review receipts with a reason. Before enabling a schedule, rehearse a timeout, a duplicate delivery, a changed source record and a revoked credential. Availability of each connection depends on the other system’s API, commercial access and configuration.

Use the implementation plan to agree integration acceptance criteria.