How It Works

The integration uses the vintrace API (Application Programming Interface) to connect the two softwares.

Two specific endpoints of the API are being used::

• Endpoint 1: Insert a fruit booking into vintrace
• Endpoint 2: Record a new fruit intake into vintrace

The transfer is done in two steps.

The fruit booking sent from AgCode to vintrace through the Insert a Fruit Booking into vintrace endpoint. This endpoint transfers the following data:

Once the weighing is done in AgCode, the booking is updated with the Record a New Fruit Intake into vintrace endpoint. The following data is added:

Once the booking has been updated with the second data transfer, the fruit intake panel displays the fruit receival information.

Alternate Methods

• You can create the booking in vintrace ahead of time and only use the Record a New Fruit Intake into vintrace endpoint to update the booking with AgCode weight data.
• You can use the Insert a Fruit Booking into vintrace endpoint to send AgCode booking data, but complete the weighing in vintrace.
• Brix, pH, TA transfer is optional as well; you decide which ones you want to send over (e.g., 1-3 or none).

Before You Begin

In order for this integration to work, be sure the data fields in AgCode match the ones in vintrace. Here are the key fields you need to check:

• Block name — the block name must be unique and match the block name in AgCode. If you want to keep some duplicates, the workaround is to create a unique external block ID code that will be the reference point between AgCode and vintrace.
• Winery name — the winery name must be unique and match the winery name in AgCode.
• Owner name — the owner name must be unique and match the owner name in AgCode. A unique external ID can be set for this field to make sure it has a unique differentiator.
• Scale name — the scale name be unique and match the scale name in AgCode.