Integrations

• Item master. Agree how SKU, base unit and active item state reach stock items if another system owns product identity.
• Purchasing or order system. If an adjacent system supplies requests, define its identifiers and how its data will be mapped into stock requests.
• Finance. Agree whether posted movement quantities and unit cost are passed to a separate accounting system.
• Reporting. Decide which authorized report consumers need request, movement and review evidence.

For each connection, name the owning team, source identifier, retry policy and reconciliation contact. For any proposed connection, test its identifiers and compare imported records with the source. A connection plan should preserve item, location, lot and parent request references so a reviewer can find the same case in both systems. Keep access to internal attachments and reviewer reasons limited to the people who need them.