Example: connect two systems without losing ownership.

Business context

A team copies accepted customer orders from a commerce system into an operational system. The first integration should reduce that preparation work while preserving existing order validation.

Defined behavior

Identify which system owns the customer, product, price and order state. Define the triggering event, required fields and the source identifier used to recognize repeated requests. Confirm the supported interface and permissions for the actual software versions in use.

Review and recovery

Uncertain customer or product matches enter a review queue. Failed handoffs retain enough evidence for an operator to understand the cause. A retry must use the same business identity so it cannot create a second order.

Acceptance example

When the destination accepts an order but the response is interrupted, a retry must find the existing accepted record or use an equivalent duplicate-control mechanism. It must not assume the first attempt failed simply because no response arrived.

Useful evaluation

Test representative orders, missing references, permission failures and repeated events. Measure duplicate records, operator recovery effort and whether the destination preserves its normal business validations.