Integrations and source ownership

• Procurement system. Keep purchase approval, supplier master data and order lines in the purchasing system. Map the accepted delivery identity to the vendor delivery record. Keep the expected quantity in purchasing, and record the inspected quantity on the stock request before returning receiving evidence. Agree the purchasing handoff before enabling connected writes.
• Supplier scheduling. If appointment messages are required, configure the provider and its authentication separately. Map them to delivery appointments’ delivery, location and appointment time, and reconcile changed or cancelled slots with the receiving team. Test an appointment update with the receiving team before enabling routine messages.
• Kitchen planning system. Let menus, recipes and catering jobs remain the planning authority. Map demand into stock requests with an agreed item, base unit, required date and owner. A planning message cannot approve the request or prove stock consumption.
• Document storage. Arrange the provider and access rules for record attachments’ document link. Preserve title, attachment type, parent request and upload date so the evidence remains explainable when an external link changes.
• Accounting system. Decide any external reporting or journal handoff separately. Agree the cost basis and the external acknowledgement that accounting needs before accepting a handoff.

Record the source owner, field mapping and retry identity for each connection before enabling writes. Preserve native workflow authority: an incoming message may prepare context, but the supervisor’s decision and the guarded stock action must remain explicit. Compare each message with its receiving result; use the operation receipt and failure reason when a stock action runs. Test provider authorization, duplicate delivery and failure recovery during connection setup, with the native operation result available for reconciliation.