Live inventory provides real-time stock to users as they visit your EvolutionX webstore. It can be used for any combination of guest or logged in users. Live Inventory can completely eliminate the need to manage inventory in two systems or you can use a combination approach so that you get the best of both.

Current ERP Systems with Live Inventory Integrations

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

Prophet 21 by Epicor (P21 DCKAP Integrator, Cloras Integration)
ECI DDMS
Eclipse
Spruce
TIMS Software
Live Customer Account

New ERP Integrations for Live Inventory

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

Example Live Inventory Request and Response

EvolutionX can code for new live inventory 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 stock 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 information of the found products).

Examples for Live Inventory:

Request Header

Notes:

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 and can be an empty text if the customer's not logged in.

Example Request Body

{
  "customer_code": "ACME001",
  "products": [
    {
      "item_sku": "1249291"
    },
    {
      "item_sku": "5012828"
    }
  ]
}

Response Body

Notes:

Always include the item_sku in the response even if the stock is 0.
is_quantity_control is optional. Set as true if stock is managed for this item_sku at this location_code. Set as false if the item is considered always in stock and exact quantity is not tracked, also send the qty value set as 1.
is_preferred_location is optional and only used in the TIMS live inventory, the value informs which locations are preferred for the user.
units_of_measure is optional and when provided will be the only unit of measure offered for sale on the storefront. This can override the product data UOM and can offer a dropdown for alternate units of measure. Example is on the second item of the example response below. If this list is not provided in the response then the uom is used from the product data in the store.
- uom is required when units_of_measure is included and is the UOM code that is added to the order along with the SKU.
- conversion is required when units_of_measure is included and the lowest number identifies the base selling unit of measure.

{
    "status": true, 
    "data": {
        "products":
        [
            {
                "item_sku": "1249291",
                "inventory":
                [
                    {
                        "location_code": "216",
                        "qty": "4",
                        "is_quantity_control": true,
                        "is_preferred_location": true
                    }
                ]
            },
            {
                "item_sku": "5012828",
                "inventory":
                [
                    {
                        "location_code": "216",
                        "qty": "5",
                        "is_quantity_control": true,
                        "is_preferred_location": false
                    }
                ],
                "units_of_measure":
                [
                    {
                        "uom": "EA",
                        "conversion": 1
                    },
                    {
                        "uom": "DOZ",
                        "conversion": 12
                    },
                    {
                        "uom": "BX",
                        "conversion": 24
                    }
                ]
            }
        ]
    }
}

Live Customer ERP

To use this feature we provide an ERP that uses the struct of the examples above and can be used following this article.

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