You define the pricing rules — by category, price range, cost (KK) price — and Kronixon PI applies them: it proposes new prices, guards against pricing mistakes and keeps the full history of every change.
Open full size ↗
Kronixon PI detects products with identical SKUs or models but different brands or suppliers — and requires confirmation before a pricing rule is applied.
With guards inside the rule itself, a dry run that shows changes before they happen, and a review queue where unusual changes wait for a human.
Yes, in two ways: an exclusion, where the rules never touch it, or a fixed price for a set period or open-ended.
No. While a promotion runs, the pricing module leaves its products alone. The two systems know about each other.
Indefinitely. Every change is recorded with its date, source, and old and new value. Separately, the Omnibus registry calculates the thirty-day reference price.
Every module works together with the rest: products feed prices, calls become offers, offers become orders. Start with the module that removes the most routine — the platform grows with you.
Tell us what eats your team’s day. We will show you — on our own live system — how much of it can simply disappear.