Fulfillment Service Module
What This Service Is For
Coordinate delivery conditions, authorizations and application outcomes so staff can see outstanding sale obligations.
Boundary
This service owns the register, policies, enforcements, exceptions and adjustments. Operations exposes some staff routes over those records; delivering applications own their resulting records.
Operations in Words
Staff read obligations, administer policies and use separately authorized interventions. Applications use system callbacks to report outcomes and readiness.
Events and Jobs
Receivable events trigger evaluation and reversal work. A scheduled dispatcher publishes authorization pointers, the queue worker invokes applications, and the Orders sweep revisits bounded pending and overdue records. Register history and audit attempts are internal records or calls, not published change events.
Consistency Guarantees
Gate opening and outcome application each have local transaction guarantees. Event processing and subsequent history, enforcement, dependency and document work can span commits. Known retries use stable authorization or step keys, while recorded gaps require explicit recovery design.