> For the complete documentation index, see [llms.txt](https://docs.tracr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tracr.com/tracr-user-guide/whats-new.md).

# Whats New?

Here's what's new in Tracr.

### Shipments Improvements (1.34.0)

We've made some improvements to the Shipments interfaces, both inbound and outbound.

On the inbound shipments you can now select multiple rough shipments and accept any that are awaiting acceptance in bulk. This process uses the same slide out drawer control used in other places such as transfer, share and unlock.

We've also begun to split the shipments into multiple views to separate the active shipments and the archived shipments. Over time we will continue to separate out the views and make further improvements to the shipments flows.

### Update box/shipment information (1.28.0)

You can now edit the details of the container (box, shipment) that a rough diamond is registered against in Tracr.

If you accidentally register a diamond against the incorrect box or shipment, you can now correct this without having to contact support. These values can be edited using the Tracr API.

If you change the box or shipment details then Tracr will automatically invalidate any Rough Check matches against the updated diamond and will perform a new match using the updated details.

***

### Transfer from Inventory (1.27.0)

The Transfer from Inventory feature provides a fast and structured way to move diamonds from your available inventory to recipients. This process eliminates the need for manual CSV exports and imports by allowing you to handle transfers directly within the platform.

More details [here](/tracr-help-pages/shipments/shipments-outbound-transfer-from-inventory.md)

### Lab Eligibility (1.27.0)

Tracr has been working on integrations with trusted grading labs which will allow you to submit a diamond to a grading lab with a Tracr ID to link your grading report to the Tracr digital record.

> There is also the option with some labs (GIA, IoD) to add your Tracr provenance to the grading report. This requires a diamond to be unlocked.

A diamond needs to have a few requirements met to be eligible for grading through one of our integrations. These include: being a polished diamond and having a supported scan report that Tracr can process.

We have extended the Portal and Tracr API to provide you with the LAB ELIGIBLE status and the breakdown of the eligibility requirements.

***

### Changes to provenance information display (1.26.0)

Tracr remains dedicated to driving industry success and transparency across the diamond supply chain. To support the continued growth of our platform and secure its long-term business viability, we have introduced an important update to how provenance information is managed.

Provenance information is not available until the diamond is polished and unlocked.

### Update Participant ID / ERP ID / Stock ID

For any Tracr diamond, you can now update the Participant ID by changing the Stock ID value in your Sarine software and that update will flow through to the diamond record in Tracr.

It’s also possible to update the Participant ID against a diamond in Tracr using the API. Documentation for that is [here](https://docs.tracr.com/docs/tracr-api/202db28925f02-update-rough-diamond)

***

## Inventory

#### Rough and Split Diamonds

For rough and split diamonds, your diamond will have one of two new values for **Provenance**: single provenance or mixed provenance.

<figure><img src="/files/n1Duc0OIcwEhBDDUKE0H" alt=""><figcaption><p>New values for Provenance</p></figcaption></figure>

#### Polished Diamonds

For polished diamonds, you will need to unlock a diamond to see the provenance information.

If your diamond is locked, your diamond will have one of two new values for **Provenance**: single provenance or mixed provenance.

If your diamond is unlocked, your diamond will have a mixed provenance or the country of origin.

> Note: **DTC** is an example of a mixed provenance, and will be available on unlock.

<figure><img src="/files/eCNM0dj99wgwWofWWrgq" alt=""><figcaption><p>Example of polished inventory with differing provenance information</p></figcaption></figure>

### Participant Search and Share

#### Rough and Split Diamonds

For rough and split diamonds, your diamond will have one of two new values for **Provenance**: single provenance or mixed provenance.

<figure><img src="/files/0J60GJiEDkKJHSdsv1mX" alt=""><figcaption><p>Example of a rough diamond with single provenance.</p></figcaption></figure>

#### Polished Diamonds

If your diamond is locked, it will **not** be available in Participant Search and Share.

If your diamond is unlocked, your diamond will have a mixed provenance or the country of origin.

<figure><img src="/files/Ai4sFVeUf2P9E0EGUlPK" alt=""><figcaption><p>Example of a polished, unlocked diamond witgh a single provenance: Botswana.</p></figcaption></figure>

### Tracr API and Tracr Search API

Where provenance is returned in the Tracr API and Tracr Search API, the following changes will come into effect.

#### Mixed Provenance

{% tabs %}
{% tab title="New - Rough, Split & Polished Locked" %}

```json
{
  ...
  "provenance": 
  {
    "is_country_code_available": false,
    "is_locked": true,
    "provenance_name": "",
    "provenance_type": "Entity"
  }
}
```

{% endtab %}

{% tab title="New - Polished Unlocked" %}

```json
{
  ...
  "provenance": 
  {
    "is_country_code_available": false,
    "is_locked": false,
    "provenance_name": "DTC",
    "provenance_type": "Entity"
  }
}
```

{% endtab %}

{% tab title="Previous" %}

```json
{
  ...
  "provenance": 
  {
    "is_country_code_available": false,
    "is_locked": false,
    "provenance_name": "DTC",
    "provenance_type": "Entity"
  }
}
```

{% endtab %}
{% endtabs %}

#### Single Provenance

{% tabs %}
{% tab title="New - Rough, Split & Polished Locked" %}

```json
{
  ...
  "provenance": 
  {
    "is_country_code_available": true,
    "is_locked": true,
    "provenance_name": "",
    "provenance_type": "Country"
  }
}
```

{% endtab %}

{% tab title="New - Polished Unlocked" %}

```json
{
  ...
  "provenance": 
  {
    "is_country_code_available": true,
    "country_code": "BW",
    "is_locked": false,
    "provenance_name": "BW",
    "provenance_type": "Country"
  }
}
```

{% endtab %}

{% tab title="Previous" %}

```json
{
  ...
  "provenance": 
  {
    "is_country_code_available": true,
    "country_code": "BW",
    "is_locked": false,
    "provenance_name": "BW",
    "provenance_type": "Country"
  }
}
```

{% endtab %}
{% endtabs %}

***

## Table Improvements (version 1.24.0)

Tracr has improved our interface to enable better user experience. The first step is the inventory table.

There is an updated look and feel, as well as improvements including:

* Ability to copy fields
* Reordering columns
* Pagination
* Improved column resizing

***

## Search by Report/Inscription Number (version 1.24.0)

This version of Tracr introduces the ability to search using grading report numbers and inscription numbers across the Tracr Inventory, Participant Search, and Diamond Experience.

***

## Archive and unarchive diamonds in your inventory (version 1.23.0)

This version of Tracr introduces the ability to separate your inventory into **Active** and **Archived** sections.

<figure><img src="/files/HNQf2XsilH2dTXawbSaJ" alt=""><figcaption><p>Active and Archived sections.</p></figcaption></figure>

If you sell a diamond or remove it from the Tracr process, you can archive the diamond so that it is no longer appears in your **Active** inventory but instead appears in your **Archived** inventory. If you later withdraw a diamond for sale, or the buyer of the diamond becomes a Tracr participant and you want to transfer the digital asset to them, you can unarchive the diamond so that it moves back to your **Active** inventory.

On the **Archived** tab you can only view or unarchive a diamond. You cannot edit, share, or unlock an archived diamond.

<figure><img src="/files/nAb1r9F1oqq9s8GkR6vl" alt=""><figcaption><p>View or unarchive an archived diamond</p></figcaption></figure>

For more information, refer to [Archive and unarchive diamonds in your inventory](broken://pages/e0f620bdc4476f2acb17a66d01933cacc9fce48b#archive-and-unarchive-diamonds-in-your-inventory).

***

## Transferring status (version 1.23.0)

This version of Tracr introduces a new status, **Transferring**, to help users know which diamonds are available to archive. Diamonds in an active Transfer have the status **Transferring**.

> Note: **Transferring** status can be displayed for rough, split and polished diamonds.

***

## Shipments outbound and inbound (version 1.15.0)

This version of Tracr introduces a change to the transfer process. A non-De Beers producer can now register rough diamonds on the Tracr platform. Once registered, the producer can create a shipment of rough diamonds and send that shipment to a manufacturer using the shipment outbound workflow. Accepting the inbound shipment allows the manufacturer to load diamonds using the Integration Tool against that shipment up to the bounds of the shipment (count, total carats, carat range).

***

## Rough Check (version 1.14.0)

This version of Tracr includes the addition of Rough Check in the Portal. Rough Check is a check against a rough diamond uploaded by the producer and the rough diamond a manufacturer uploads.

This check is performed using Diamond ID, a core service in the Tracr platform ecosystem primarily tasked with validating, verifying, and identifying diamonds.

You will be able to see a Rough Check against your diamond in your Rough Inventory and on the Diamond Details page.

<figure><img src="/files/VArRzdRMNLvRb3AcUHpo" alt=""><figcaption><p>Rough Check in the Rough Inventory.</p></figcaption></figure>

## Changes to transfer in (version 1.13.0)

In this version of Tracr, the 'transfer in' workflow has been simplified and inscription numbers no longer need to be provided when accepting transfers of polished diamonds.

In the following image, the recipient has accepted five diamonds, rejected three diamonds, the sender has cancelled one diamond, and one diamond is available for transfer. The **Accept** and **Reject** buttons allow this diamond to be accepted (without the need to upload a CSV file containing Tracr IDs and inscription numbers) or rejected.

<figure><img src="/files/QXNGNuFOF3gcBTZKONLC" alt=""><figcaption><p>Accepting ownership of diamonds.</p></figcaption></figure>

For more information, refer to [Transfer In](broken://pages/49f31a6df7e725997a0807ca40c73bd77256519a).

***

## Diamond unlocking (version 1.10.0)

From 1st January 2024, all new polished diamonds added to Tracr will be automatically locked.

To share or transfer a locked diamond, the owner must first unlock the diamond. Participants can unlock one or more locked diamonds from their inventory or from the Diamond Details page.

{% hint style="warning" %}
To make sure that stones that are unlocked are accessible for future use, you will not be able to delete an unlocked stone. Please make sure you are happy with the stone you are unlocking and that it has all the necessary assets.
{% endhint %}

The following video shows you how to unlock a diamond from your inventory.

{% embed url="<https://vimeo.com/894062765/314cd85a3f>" %}

For more information, refer to [Unlock a diamond](broken://pages/e0f620bdc4476f2acb17a66d01933cacc9fce48b#unlock-a-diamond).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.tracr.com/tracr-user-guide/whats-new.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
