Integrations and source ownership

• ERP purchasing. Exchange approved commitments and order references.
• Warehouse receiving. Send accepted quantities and times from the dock.
• Supplier portal. Share commitments and receive invoice references.
• Inventory system. Keep stock levels and turns there; bring in what you need for reports.
• Identity provider. Map staff sign-in to team members; removing a leaver’s access must also remove their access here.

Each connection needs an agreed source of truth, a field mapping, a stable identifier and a retry policy. A retried commitment must not create a second order reference, and a repeated receiving message must not accept a line twice. Keep credentials in the approved secret store and grant the smallest scope the connection needs. Queue rejected records with their source identifier and a visible reason.

Test a timeout, a duplicate message and a revoked credential before turning on schedules. Availability depends on each provider’s API, commercial access and configuration.

Use the implementation plan to agree acceptance criteria for each connection.