After-Sale Change

What It Models

After-sale documents record cancellation, purchase amendment and goods return. Each preserves the request, authority and evaluated outcome while coordinating product work and financial settlement. Later promotion application uses an amendment document, and return-policy configuration belongs to this concept.

Identity and Attributes

The document kinds share party attribution, affected lines, approval information and settlement plans. Amendments add replacement-order and effective-date details; returns add policy snapshots and authorizations. Cancellation and amendment execution rechecks an aged plan rather than relying indefinitely on its first evaluation.

Relationships

Orders persistence changes purchased quantities and successor links. Applications perform product-specific reversal or modification; entitlement revocation and stock-cost restoration use their owning modules. Accounting records the financial documents produced by settlement.

Invariants

A partial unique index protects each document kind's live occupancy of a line. Override reasons and scoped policies have database checks. Eligibility differs by operation: ordinary cancellation and amendment require acceptance, returns also admit closed orders, and later promotions can target placed orders. Settlement checks credit caps and the configured domain-before-money policy.

How It Is Stored and Shared

Orders owns change documents and return terms. Fulfilment owns the obligations, adjustments and intervention logs they create. Local history and intervention rows preserve committed actions; Platform audit delivery remains incomplete. Export is provided without custom fields.

Open Design Questions

Scheduled amendments and overdue authorizations lack automated progression. Acceptance can leave an amendment awaiting payment when its follow-up fails. Cancellation preview leaves a real request, and the order-fee refund policy still needs a product answer.