Overview: Integrating your ERP with ChemCloud

ChemCloud centralises much of your procurement data in one place, saving time and helping businesses reduce their cost of goods sold with better access to their procurement data.

ChemCloud does not replace your ERP system, but it is important that it interacts with it to ensure your data is synchronised across systems.

How does ChemCloud integrate with your ERP system?

Most ERP systems have an external facing API which allows ChemCloud to send (POST) information to your ERP and receive (GET) information back.

Typically, an ERP system will have a public facing list of fields that can be accessed via API. These fields are relatively standard across different systems.

Each ERP system has a different way to authorise access to your own system by API. Typically this involves setting up an API within the ERP and then giving ChemCloud an API Key (or password) to give it access to your system.

How do you set up the integration?

We have instructions for a number of ERPs to set up your API integration: MYOB Account Right, Unleashed, Ostendo and Cin7 Core.

If you would like a detailed instruction page for your ERP, please get in touch with your account manager.

If your ERP is on premise, we also recommend creating this secure way to access the ERP at this page here.

What information does ChemCloud send to and receive from ERPs?

ChemCloud synchronises with your ERP system in two ways:

Onboarding and setup (one time)
1. Get Product data | Synchronise product data with a GET/list call to a Products endpoint
2. Get Supplier data | Synchronise supplier data with a GET/list call to a Suppliers endpoint
3. Get Purchasing data | Synchronise purchasing data with a GET/list call to a Purchase Orders endpoint
  (Note, the exact endpoints will differ from system to system)
Automations and actions (ongoing)
1. Create draft PO | Create a draft purchase order based on a quote product data with a POST call to a Purchase Orders endpoint
2. Update delivery as delivered | Mark a delivery as delivered based on a daily sync with receipted goods in your ERP a daily GET call to a Purchase Orders endpoint
  (Again, the exact endpoints will differ from system to system)

More information on synchronisation

Onboarding and setup - One time data synchronisation

Data type	Why we synchronise	What we synchronise
Products	We set up your product data in ChemCloud to match the codes and names used in your ERP. This product data is then used when creating sourcing requests for quotes and when we generate draft purchase orders in your ERP.	`GET/list` call to a `Products` endpoint to retrieve: Product code Product name Other generic product identifying data Product unique ID
Suppliers	We set up your supplier data in ChemCloud to match the codes and names used in your ERP. This supplier data is used to generate sourcing requests to the correct account manager.	`GET/list` call to a `Suppliers` endpoint to retrieve: Supplier code Supplier name Other generic supplier identifying data Supplier unique ID
Purchase Orders	One of they key value propositions of ChemCloud is uploading your approved materials for each product. We do that based on your purchasing history.	`GET/list` call to a `Purchase Orders` endpoint to retrieve: Supplier code Product code

2. Actions and automations - Ongoing data synchronisation

Action	Why we synchronise	What we synchronise
Generate draft Purchase Order	Quotes are automatically generated in ChemCloud. From ChemCloud you can generate a draft PO in your ERP based on the quote	`POST` call to a `Purchase Orders` endpoint to create a PO with following details: Supplier code Product code Volume Price ETA Status (Draft)
Update delivery to delivered	Deliveries in ChemCloud can be updated to 'Delivered' based on receipted status of a Purchase Order in your ERP	Daily `GET` call to a `Purchase Orders` endpoint to get delivery status: Purchase Order ID Delivery status

Example POST call to create a purchase order

This is a typical POST call to create a draft purchase order in an ERP. the information in the POST call has to be tailored depending on the exact configuration of the ERP.

Example call

{
  Request name: Send POST to create Purchase Order on ERP_NAME,
  Request: 
{
    Method: POST,
    Request content type: application/json,
    Request URL: PurchaseOrders,
    Request body:             
  [
    {"SupplierId":123,
     "CurrencyCode":"AUD",
     "Reference":"PO-MKE932",
     "InternalComments":"Created by ChemCloud by Hector Williamson on 30 October 2024 8:49am",
     "DeliveryInstructions":"To be delivered ASAP",
     "DeliveryCompany":"Hector's Humectants",
     "DeliveryAddress1":"74 Burwood Road",
     "DeliveryCity":"Hawthorn",
     "DeliveryState":"VIC",
     "DeliveryPostalCode":"3172",
     "DeliveryCountry":"Australia",
     "LineItems":
       [
        {
          "Code":"LA8",
          "UnitPrice":3.20,
          "Qty":1000
        }
       ]
    }
  ],

},
}