Connections

• Stock source. Map item identifiers, base units and organization codes from the system that owns your product records.
• Warehouse execution. Plan how physical confirmations from a separate floor system will be matched to the request and signed movement evidence.
• Documents. Establish how teams attach and share supporting files on a request.
• Upstream planning. Decide whether and how request outcomes and transfer results should be shared with an upstream planning team.

For any connection you set up, use the parent request and operation key as stable references. Agree how a repeated message is recognized, how an uncertain response is reconciled, and who owns a failed receipt. Check the expected revision before applying an outcome to a changed request. Review effect references with an Inventory Reviewer before treating a retry as a new operation.