Live Customer Lookup, provides real-time information to logged users on your EvolutionX webstore about the customer.

New ERP Integrations for Live Customer Lookup

We work either directly with the API for your ERP or through a partner integrator (who provides API support) to setup Live Endpoint 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.

Live Customer Lookup

The following requests and responses are examples for Live Customer Lookup:

Request Header

Notes:

Bearer Token is preferred but oAuth2 and other authorization types can be supported too (Contact DevOps to support oAuth2).
The Method for the endpoint should be POST.

Example Request Header:

Content-Type: application/json
Accept: application/json
Authorization: Bearer Token or username & password

Request Body

Notes:

The Customer Code attribute will use the references of the ERP for the account number. It is not required for the ERP to store EvolutionX IDs for these entities. If needed, the EvolutionX Customer Account can store a GUID or Record ID in the Seller Reference as well (ask DevOps if you need this value in this integration).
The most important field to support is:
- customer_code — the ERP customer code as stored in the EvolutionX Customer Account Number attribute.

Example Request Body

{
    "customer_code": "ACME001",
    "seller_reference": "01"
}

Response Body

Notes:

Not all fields are required in the response, the most critical ones are the following:
- customer_code
If your system doesn't have the others fields, the response can be different.
Depending on the provided fields the system adapts funcionalities.
Funcionalities:
- Customer Discount on Checkout (customer_discount is required): To apply the correct discount to an order, the system iterates through the array of discounts, which has been ordered by minimum_amount in descending order, and compares the order amount with the minimum_amount specified for each discount. The system then applies the discount associated with the first discount object where the order amount meets or exceeds the minimum_amount threshold.
- Checkout PO (po_required and po_default_value are required. You have more information about the PO here)
- Customer Address on Checkout (shipping_address and billing_address are required)

Example Request Body

{
  "customer_code": "ACME001",
  "name": "Name, INC.",
  "email": "",
  "phone": "",
  "is_enable": true, // on hold?
  "is_prepay": false,
  "po_required": true,
  "po_default_value": "PO100",
  "po_mask_value": "^([a-zA-Z0-9]+.*)$",
  "shipping_address": [
    {
      "address_code": "ACME001",
      "name": "Name, INC.",
      "address1": "E Madison St",
      "address2": "",
      "address3": "",
      "city": "GIBSONBURG",
      "state": "OH",
      "postal_code": "43431",
      "country": ""
    }
  ],
  "billing_address": [
    {
      "address_code": "ACME001",
      "name": "Name, INC.",
      "address1": "E Madison St",
      "address2": "",
      "address3": "",
      "city": "GIBSONBURG",
      "state": "OH",
      "postal_code": "43431",
      "country": ""
    }
  ],
  "customer_discount": [
    {
      "customer_discount_code": "abc1",
      "customer_discount_percent": 10,
      "minimum_amount": 10
    },
    {
      "customer_discount_code": "def2",
      "customer_discount_percent": 30,
      "minimum_amount": 30
    },
    {
      "customer_discount_code": "ghi3",
      "customer_discount_percent": 5,
      "minimum_amount": 5
    }
  ]
}

Customer A/R Balance

You can merge this endpoint with the A/R Balance one. Both have the same request and share equal fields in the response.
The system ignores all fields that are not expected making it easy for a custome response.

Learn more about the Customer A/R Balance using this article.

ERP DIY Integration

To use this feature you need the ERP DIY Integration App see the full article.

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