Skip to main content

Frequently Purchased Items— Real-Time from the ERP

We list the systems already supported for real-time Recent Purchased Items from your ERP and how to integration new back-office ERP systems.

João Estima avatar
Written by João Estima
Updated over 10 months ago

Live Recent Purchased Items, provides real-time list of items previous purchased to logged users on your EvolutionX webstore. With this module, customers can find and purchase the items they may want to order again. Replaces the EvolutionX version of the Frequently Purchased Items List.

New ERP Integrations for Live Recent Purchased Items

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

Current ERP Systems with Live Recent Purchased Items Integrations

The following systems are already integrated for Live Recent Purchased Items and are easy to setup:

  • TIMS Software

  • Kore Kourier Integrator V2

  • Horizon ERP

  • Red Falcon ERP

This is an example Live Recent Purchased Items Request:

Request Header

Notes:

  • Bearer Token is preferred but oAuth2 and other authorization types can be supported too.

Example Request Header:

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

Request Body

Notes:

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

  • Page size (limit) is usually set high and only the first page is retrieved. The goal is to get all relevant data in one request.

  • Currently, there are some deprecated filters in the request that EvolutionX is providing, but those can be ignored.

Example Request Body

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

Response Body

Notes:

  • Return records in order of LastOrderedDate descending to ensure that recent orders are included in page 1 of results.

  • Not all fields are required in the response, the most critical ones are the following:

  1. customer_code

  2. sku

  3. uom

  4. total_qty_ordered (sum of quantities ordered per SKU)

  5. times_ordered (count of order lines per SKU)

  6. last_ordered_date (time is not required but we assume UTC unless specified)

  7. count (number of products possible, ignoring the per_page filter)

  • The return should have distinct SKU and UOM (group by SKU, UOM) and, if possible, exclude cancelled orders.

  • If there are no items to send, the record should be empty (without objects).

Example Response Body

{
    "customer_code": "ACME001",
    "products": [
        {
            "sku": "ABC125",
            "last_qty_ordered": 8,
            "last_ordered_date": "2022-09-29T00:00:00Z",
            "part": "125",
            "total_qty_ordered": 212,
            "supplier": "ABC",
            "times_ordered": 4,
            "uom": "CYL"
        },
        {
                ...
        }
    ],
    "count": "12"
}

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 Recent Purchased Items integration project.

Did this answer your question?