Writing Back to Cin7 Core - How to Use Owlery

Cin7 Core write-back is optional. Owlery recommends which date updates match your workflow, tests them against representative records, and introduces them after inbound synchronization is validated.

Your team confirms the intended business outcome. Owlery configures, tests, and monitors the write-back behavior.

Available date updates

Owlery event	Cin7 Core update
Sales load picked up	Sale `ShipBy`
Purchase load delivered	Purchase `RequiredBy`
Transfer load picked up	Stock transfer `DepartureDate`
Transfer load delivered	Stock transfer `CompletionDate`

Owlery uses the actual stop date first and can fall back to the matching tracking-event date.

Safe writes by design

Split Owlery orders sharing one Cin7 Core source are grouped so the source updates once.
Owlery retrieves the current record before writing and preserves unrelated fields.
Requests are paced for Cin7 Core API limits.
Rate-limit responses use bounded exponential backoff.
Validation and authentication failures are not blindly retried.
Missing source identities, dates, or unsupported order types produce actionable failures.

Start with read-only synchronization, then enable one date workflow at a time after the corresponding inbound order type is validated.