Optimizely Configured Commerce offers two ways to manage pricing: the Price Matrix or Real-Time. The Price Matrix is a list of customizable rules that can be used to set up and apply different pricing based on a set of rules. Where as Real-Time pricing makes calls to the customer's ERP to update the product's basic list price. A third, but unconventional way to manage pricing would be to manually set the pricing at the product level.
In a typical Configured Commerce environment, Real-Time pricing is the default pricing model and is set up using integration jobs tied to the WIS. However, if the Price Matrix is enabled, and a matrix exists for a particular record type, then the Real-Time pricing is overridden by the Price Matrix. For more information on the Price Matrix, review the related documentation listed below.
Real-Time pricing, when chosen, has two configuration options: make direct calls to the the customer's ERP API or use the Windows Integration Service (WIS) to make calls to customer's ERP API. Typically, the rationale for using the WIS is to address security concerns, where the customer does not want the ERP API exposed to the public. Making the calls directly to the customer's ERP API is generally faster and therefore provides potentially more accurate pricing. Using WIS introduces a small amount of lag time, as there is a "data layover" on the WIS. The amount of lag time is fairly insignificant, something to effect of ?
Where do we set up the integration job to be a real time thread vs. a batch thread.