All Collections
Getting Started
Pricing
Live Pricing — Real-Time Price from the ERP
Live Pricing — Real-Time Price from the ERP
We list the systems we already support for real-time pricing from your ERP and how to integration new back-office ERP systems.
Séamus Diamond avatar
Written by Séamus Diamond
Updated over a week ago

Live pricing provides real-time pricing to users as they visit your EvolutionX webstore. It can be used for any combination of guest or logged in users. You have the ability to turn it on and off by account or across the store. Live Pricing can completely eliminate the need to manage pricing in two systems or you can use a combination approach so that you get the best of both.

Use Cases for Live Pricing

  • Guest user pricing — this uses a designated guest account code to request pricing from your ERP

  • Customer Account contract pricing — each customer can be specifically turned on or off to use Live Pricing from your ERP

  • Multiple Quantity Pricing — when items are added to the cart we recheck the pricing based on the quantity added so that multi-buy price policies are supported. Note: this is not available for all integrations (see below).

Current ERP Systems with Live Pricing Integrations

The following systems are already integrated for Live Pricing and are easy to setup:

  • ECI Progress

  • Prima Software

  • Office Team

  • Eclipse — Multiple Quantity Pricing supported

  • Calidor

  • Intact

  • Navevolink

  • Oasis

  • ECI DDMSPlus (CA only)

  • Prophet 21 by Epicor (P21 DCKAP Integrator, Cloras Integration)

  • Dynamics (CKAP Integrator, Cloras Integration)

  • Spruce

New ERP Integrations for Live Pricing

We work either directly with the API for your ERP or through a partner integrator (who provides API support) to setup Live Pricing for new systems. This typically is a fast-tracked development to ensure you are up and running quickly. Contact our team today to discuss your options and questions.

Important Notes

  • Sorting search results by price is not available with Live Pricing.

  • Some ERP systems require additional database pooling licenses or API licenses.

  • Show Cheapest Price is not supported with Live Pricing.

Alternatives to Live Pricing

EvolutionX has deep pricing features built in along with the support to import pricing. Here are some of the alternatives to using Live Pricing from your ERP:

Example Live Pricing Request and Response

EvolutionX can code for new live pricing integrations. EvolutionX includes an account code and one or many products in a single request. If, for example, we send 12 products in the list and you are unable to find one of them in the ERP, we would ask that your response includes the item and pricing that you did find (you can either not include the missing item or include it with an error message in your response, along with the item prices of the found products).

This is an example Live Pricing Request:

Request Header

Notes:

  • Authorization types supported:

    • Bearer Token is preferred

    • Username & Password can be supported

    • oAuth2 support is possible but requires a custom app in EvolutionX

  • The Method for the endpoint should be POST.

Example Request Header:

Content-Type: application/json
Accept: application/json
Authorization: [token]

Request Body

Notes:

  • The Customer Code and Item SKU will use the references of the ERP. It is not required for the ERP to store EvolutionX IDs for these entities.

  • customer_code — EvolutionX uses the Customer record account_number field value

  • shipto_id — This is optional, EvolutionX uses the Customer record seller_reference field value if set

{
"customer_code": "ACME001",
"shipto_id": "2",
"products": [
{
"item_sku": "ABC-100",
"uom": "ea",
"qty": 1
},
{
"item_sku": "AAA-200",
"uom": "ea",
"qty": 1
}
]
}

Response Body

Notes:

  • HTTP Response Status

    • Return HTTP response status 2xx for success if the request is correctly sent, even if SKUs did not exist in the ERP.

    • Return HTTP response status 4xx for malformed requests

    • Return HTTP response status 5xx for internal errors

  • Not all SKU items in the request must be returned, if an item is not found it can be excluded from the response list. Do not fail a request if SKU items are not found, instead return what is found or an empty list.

  • not all fields are required in the response, the most critical ones are the SKU and the Price for each item returned

{
"status": "success",
"data": [
{
"customer_code": "ACME001",
"shipto_id": "2",
"item_sku": "ABC-100",
"uom": "EA",
"qty": 1,
"unit_price": "56.02"
},
{
"customer_code": "ACME001",
"shipto_id": "2",
"item_sku": "AAA-200",
"uom": "EA",
"qty": 1,
"unit_price": "150.22"
}
]
}

Contact the customer success team to discuss a new Live Pricing integration project.

Did this answer your question?