Owner manages Order source with the person responsible for the factory-system adapter. A saved connection, a successful lookup and a delivered callback are different results. These controls do not book a carrier shipment or authorise physical label output.
Prepare and activate the intended version
Review the current source before adding another connection. Agree the exact adapter version, HTTPS lookup and callback endpoints, fact catalogue and signing arrangements. Keep secrets in the approved private handover.
For Add a version, choose the intended offered kind, enter Lookup URL, Callback URL, Adapter version and the complete Fact catalogue in its declared format. A synthetic source, where allowed, is separate from a live HTTPS adapter. Do not describe invented order facts as data returned by the real factory system.
Read the saved version and its status before Activate. Check both required signing-secret purposes and the intended endpoints. The site supports one active source. A version change can affect dependent preset/rule evidence and is not merely a displayed rename.
Where the page offers a newly generated signing secret, retain it at that time and give it only to the intended adapter operator. Use the offered rotation/retirement controls deliberately. Repeatedly generating another secret does not recover a missed original value or prove the receiver has installed the current one.
Test the correct boundary
Test a lookup contacts the configured live source for the chosen reference. It does not book or print, but it can return private order/delivery data. Use an agreed permitted reference and inspect the exact result.
Send a test event sends one signed test callback to the live configured endpoint. It is not a real order or carrier booking. Arrange that receiver-side test with its responsible operator before sending it; a sample label on the button does not make the network destination fictional.
A successful lookup does not prove callback delivery or carrier sending. Preserve the source/version and actual test result when handing over readiness.
Recover original callback events
Read Callbacks to the source, current sending status and Needs attention. Callback failure does not book or print again. The screen describes automatic delivery attempts for twenty-four hours; events still needing a person retain their original identity and history.
For eligible failed events, Send these events again, unchanged replays the original signed event. Check its despatch, sequence, type, attempts and reason first. Do not recreate the booking to repair a delivery problem.
An endpoint-change hold needs a separate decision. Confirm that those exact original outcomes belong at the current receiver/version, enter Why these events may go to the current endpoint, then choose Move held events to the current version. It is a recorded migration, not an ordinary retry of an unchanged endpoint.
Verify the handover
Inspect the resulting delivery/held state and have the receiver inspect its corresponding event. Saved or queued events are not proof of delivery. A server configured not to send callbacks retains waiting events until that configuration is addressed by the responsible administrator.
After endpoint, catalogue or carrier changes, arrange current rule/preset review and any required Automatic qualification. Keep shipment and label uncertainty on their own original records while the source delivery issue is resolved.