Known limitations - Appeasements

Known limitations - Appeasements

Known Limitations & Out-of-Scope

Providing a clear view of the current functional boundaries to ensure proper usage of the feature.

Core Functional Limits

  • Order-Linked appeasements Only: Every appeasement must be tied to a specific existing order. The system does not support "standalone" credits or payments created outside of a purchasing context.

  • Refund Cap: The total amount of all appeasements cannot exceed the original total amount paid for the order.

 

Technical & Item-Level Constraints

  • Tax Management: Taxes are currently not recalculated within this module.

    • The appeasement calculation is strictly based on the price field. The system’s behavior depends on your tax configuration:

      • Tax-Inclusive Pricing: If your system is configured with “Taxes Included in Price”, taxes are automatically covered by the appeasement, as they are part of the base amount.

      • Tax-Exclusive Pricing: If taxes are not included in the price:

        • The system ignores the tax layer entirely.

        • It does not communicate with the tax provider to recalculate or adjust the remaining "appeasable" tax balance.

        • The user is responsible for determining if the tax portion needs to be handled externally.

  • Canceled Items : As the total price is currently not recalculted after a refund. We are not managing the refunded price of cancelled items in the appeasement calculation.

  • Line-Level Appeasements: While general appeasements are supported, specific "appeasements" at the individual line-item level are currently out of scope.

Operations & Reporting

  • No Bulk Actions: Each appeasement must be processed individually. A mass-appeasement tool or batch processing is not available in this MVP version.

  • Basic Reporting: No advanced financial dashboards or automated accounting exports are included. Data must be retrieved via logs or manual exports for the time being.