What a pricing engine is
A pricing engine is the part of a pricing system that computes the price. It takes an input (customer, part number, quantity, date) and returns a number, every time, in the same way. In a spreadsheet the engine is a formula. In an ERP it is a price level lookup. In Elastly it is a model that reads the customer's history, the part's cost and stock, recent wins and losses at similar prices and any competitor prices you track, then returns one price with its factors and a confidence score.
The difference between the three is not speed. It is what the engine knows. A lookup knows the list. A model knows what this customer paid last time, what similar customers accepted, and what the market looks like today.
What moves a price
Every Elastly price shows the factors that moved it from list, each with its size. A rep sees them in the quote screen they already use, so the answer to "why is it this price" is on the line.
Where the engine runs
On a quote: each quote line in your ERP gets a price and its reasons in about a second, written back to the quote. On the catalog: the whole price book is repriced on a schedule or when cost changes, into price levels and store price lists. On a store or custom system: one API call with a customer, part and quantity returns the price and the reasons.
The same engine runs in all three places, with the same policy, so a web price and a rep's quote never disagree.
How your team controls it
The pricing policy sets floors, ceilings, rounding and how confident the engine must be before it moves a price. The strategy builder adds rules with scope and priority, for example "OEM accounts price on contract, volume breaks only". The simulator runs a strategy on last year's quotes before it goes live. Approvals catch anything the engine would like to do outside the limits.
Every decision is logged with its inputs. If a price looks wrong a month later, open the decision inspector and see what the engine knew at the time.