Checkout Service Module
What This Service Is For
Checkout holds purchases in progress and exposes their selection, assessment and placement operations. The composer uses those operations for staff purchases; portal calls are restricted to the buyer's authority. This module also hosts the shared background schedule.
Boundary
The module owns carts, selections and their trail. Catalog supplies policies, stores, prices and offers; CRM supplies purchasing parties; Platform supplies eligibility. Placement is hosted here but writes through the owners of sale, resource, redemption and delivery records in one shared transaction.
Operations in Words
Cart operations create, edit, reserve, assess and abandon selections. Staff can switch policy; callers can choose shipping and offered deposit plans. Code changes recalculate the preview, while placement requires its own permission and request key. No operation declares a Submissions publication.
Events and Jobs
Cart events are local history rather than externally published messages. The minute schedule runs expiry, reservation, payment-window, register, financial and grant work in order, followed by ledger purge during its daily window.
Consistency Guarantees
Mutation and history writes share a commit, including releases through application database functions. Preview is a saved assessment rather than a lasting price guarantee. Scheduled expiry depends on the pass reaching the record without a propagated earlier failure.