Integration Requirements
On this page, the general Unosof and Komet Sales Integration requirements are explained.
Last updated
On this page, the general Unosof and Komet Sales Integration requirements are explained.
Last updated
Ask Komet Sales support to generate a token and grant access to the required APIs for the integration you wish to establish between both systems.
An API token is a unique identifier or key to authenticate a user or application to authorize access to an API. This is mainly used to protect data and resources.
Ask Unosof about the list of APIs that must be added to the token permissions.
Example: purchase.order.list
The list of APIs is listed on the Komet Knowledge Base.
To build any API integration, you must map appropriately the standard data fields that each endpoint requires so that we create seamless cooperation between the Unosof and Komet Sales apps.
Depending on the API method, mapping one or more data fields can be necessary (Species, varieties, SKUs, Billing Customers, Shipping Customers, Cargo Agencies, Carriers, Box Types, Order Types, Incoterms, etc.)
Using some of the APIs described in the Komet Knowledge Base, Unosof can access the Komet Sales tables, store that data, and map some variables in the Unosof tables.
When clicking the dropdown menu, find the View Komet data section on the Komet Bridge Menu.
Here, you can visualize different data sets, such as Products, Carriers, Boxes, etc.
If you click on the Komet Boxes option (as an example), click on the Seach Button.
The page will display all box types created in Komet Sales, a description, and the Komet Sales ID.
The KS IDs should be mapped on the Unosof tables. Each Komet system has a unique database, so you must do the mapping process for every KS and Unosof app.
The product codes from Komet should be mapped on the Unosof Manage Products / API Mappings Menu form, KS ID column.
To access this module, go to:
Production / Product Management / Manage Products Menu: API Mappings https://farm.unosof.com/index.cfm?event=Products2.List
The page will display all SKUs. Find the column Komet ID and add the corresponding ID to the SKU.
Save your edits by clicking the button Save on the right side of each line.
Notice: The example above shows that the same ID is mapped on different Unosof SKUs. This can happen because Komet Sales generally manages SKUs by variety and length. I.e., ROSE AKITO 4OCM. Other variables, such as the number of stems per bunch and package type, are independent attributes and come as an additional field in the JSON file for the integrations.
It is also possible to map every SKU entering the Manage Product form
To access this module, go to:
Production / Product Management / Manage Products
Please search for the SKU and enter its Product form by clicking on the SKU name.
Click the Mapping tab to find the SKU form's ID Komet field. Please insert the ID and click on the Save Button in the upper right corner of the page.
Automated mapping is available as well. Unosof has a script to match both systems' product tables. For this, it is mandatory that in Komet Sales, the Komet Product ID is mapped on the Legacy Code field.
This method has the following limitations:
It can be done massively at the beginning of the integration.
100% mapping is not assured.
In some of our integrations, it is possible to post solid and mixed boxes. However, it is necessary to use the mixed box module for assorted boxes (different varieties or the same variety with different lengths).
To create mixed boxes, please follow the described steps in the following link. Mix Box Management // create mix box
Once the box is created, you can map out the mixed box IDs from Komet with those created boxes in UNOSOF. Insert the KS product ID in the option Product Code.
Choose the Stock Client by selecting the corresponding billing and shipping client.
The Billing and Shipping Customers from Komet Sales should be mapped in the Unosof Manage Customer Form.
To access this module, go to:
Customers / Customer Info / Manage Customers.
Find the customer in UNOSOF, and click on the name to open the Customer Form.
Inside the client form, click on the tab API/Providers.
Depending on the type of integration, we should map Komet Group, API Provider, and Provider Token.
If integrating in Order Creation, please fill in the KS ID in the Komet Group field.
If you are integrating with a Customer Komet System like Mayesh, Kennicot, Fresca, etc, fill the API Provider, Provider Token, Komet Location ID, and Komet Group fields
Click on the dropdown menu of the API Provider field and select Komet Sales (USA).
Fill in the Provider Token:
Fill in the Komet Location ID:
Fill in the Komet Group
The KS ID should mapped on the Unosof Manage Boxes form, External Box ID field.
To access this module, go to:
Customers / Exportations / Manage Boxes https://farm.unosof.com/index.cfm?event=Box.List#
The locations from Komet Sales can be related to the Incoterm table in Unosof. These data should be mapped in the Unosof Incoterm Form.
To access this module, go to:
Customers / Exportation / Manage Incoterms
Find the Incoterm in UNOSOF, and click on the name to open the Incoterm Form.
Fill in the Komet Location ID on the Incoterm Code field and save changes.
