Since 20 March 2026 Kronixon PI reprices the store by rules you define once. The rules work by category, brand and price range, protect your margin, round the way you want, and record every change in a history that cannot be erased.

Suppliers change their prices every day. One raises processors by four percent, another runs a promotion on drives, a third says nothing but the dollar has moved.
With a catalogue of several thousand products the only workable approach is repricing in batches — once a week, once a month. Between two batches the margin leaks. Sometimes you sell below cost without noticing.
Each rule describes one case: for this category, in this price range, from this supplier — this markup, rounded this way.
Tiers. A single rule can have several tiers, each with a different markup depending on value. A twenty-euro accessory and a two-thousand-euro laptop do not tolerate the same percentage.
Guards. A minimum and maximum price, and a minimum margin over cost. The rule cannot go below them, even when the supplier has made a mistake in their list.
Trusted matches. Once you have confirmed that item X at supplier A is the same product as Y in the store, the system remembers. Next time it does not ask.
Exclusions. Products the rules never touch at all.
Fixed prices. Since April 2026 an individual product can be given a locked price — for a set period or open-ended. Useful for prices agreed with a customer, or for a product you do not want moving while a campaign runs.
Pricing is where a single error costs money immediately. So three things stand between a rule and the store.
A dry run. You see what would change before anything has changed — a list of products, old price, new price, reason.
A review queue. Changes that look unusual wait for a human.
History. Every change is recorded — when, by which rule, from what value to what value. It can be traced back per product.
Since August 2026 the Omnibus registry sits underneath: a full record of every price change, with the lowest price over the last thirty days calculated for you. That is not a convenience but a legal requirement when advertising a reduction — and it is kept automatically.
The pricing module is linked to promotions, so the two never overwrite each other, and to ordering, so the per-item cost stays correct.
How do I guard against a wrong price? Three things at once: guards inside the rule itself (a minimum price and a minimum margin), a dry run that shows the changes before they happen, and a review queue where unusual changes wait for a human.
Can a specific product be left alone? Yes, in two ways. An exclusion — the rules never touch it. Or a fixed price — a locked value for a set period or open-ended.
Do automatic prices clash with promotions? No. While a promotion runs, the pricing module leaves the participating products alone. The two systems know about each other.
How far back is price history kept? Indefinitely. Every change is recorded with its date, source, and old and new value, and can be traced per product. Separately, the Omnibus registry calculates the reference price for the last thirty days.
Read more: Pricing in detail
Tell us what eats your team’s day. We will show you — on our own live system — how much of it can simply disappear.