Define the configuration boundary
Choose the host-platform actions first: open a product range, recover a saved design or request a quotation. For each, specify the input and returned record, including account, product and configuration references. Decide which system owns the customer and quote. Use this brief to assess the required connection rather than treating embedding, identity or API support as settled implementation choices.
Keep identity and permissions explicit
A dealer, internal salesperson and customer may need different catalogs, price visibility and actions. Agree authentication, role mapping and session handling for the intended deployment. Specify which system is authoritative when a user changes role or loses access. Test those changes with the integration owner before publishing the workflow.
Treat integrations as maintained contracts
For each proposed connection, specify an example request and response, identifiers, version rules, errors and retry handling. Test a timeout followed by a retry to check that one action creates one quote or order. Assign responsibility for changes at both ends, including when a field becomes required or a user loses access. Include the connection and its acceptance checks explicitly in the delivery scope.
Implementation checklist
- Platform versus configurator ownership
- Role mapping
- Record identifiers and revisions
- Integration maintenance owner