You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Architecture: Central pricing/adjustment service & financial ledger boundary #369
Architecture: Central pricing/adjustment service & financial ledger boundary
Summary
Pricing logic is currently spread across POS, orders and bills. Manual discounts (#359-adjacent), promotions/coupons (#359), combos (#366), tips (#364), gift cards (#363), split checks and refunds (#278) will all interact — a small central pricing/adjustment service and a proper financial transaction/ledger boundary will pay for themselves.
Goals
Order
↓
Bill
↓
Payments (Cash | Card | Gift card | Loyalty)
Bill adjustments (Manual discount | Promotion | Coupon)
Refunds → reference original payment/bill
Shift → cash in − cash refunds = expected drawer
A single place that computes prices/adjustments, taking an order snapshot so historical bills are immutable.
A ledger boundary so promotions/gift cards/tips/refunds don't become four unrelated piles of accounting.
Incremental: introduce with these features, not a giant "rewrite pricing engine" project.
Activity