# Post-processing

{% hint style="info" %}
You can use Liquid formulas in all fields described in this section.
{% endhint %}

### Tag order

Check the option *Tag exported orders with* and provide a tag to be added. Previous tags will not be overwritten.

<figure><img src="/files/7NQpflMwnnb0IEdKytUq" alt=""><figcaption><p>Tag an order after a successful export</p></figcaption></figure>

To add more tags, separate them with commas:

<figure><img src="/files/dXs6jGbL1jgGhdmaQH7N" alt=""><figcaption><p>Add multiple order tags</p></figcaption></figure>

You can use Liquid with variables related to an order to add tags conditionally:

<figure><img src="/files/UGoJqNyewhTc99SVWEIf" alt=""><figcaption><p>Tag orders conditionally</p></figcaption></figure>

### Order note

Unlike tags, Exporteo overwrites the content of the order note field. To keep its previous content and add new information, use the variable `{{ order.note }}`

<figure><img src="/files/2J22ZfodoxX6NX0fP5fZ" alt=""><figcaption><p>Update order notes</p></figcaption></figure>

### Order metafield

Exporteo allows updating the order metafield after a successful export. This can be particularly useful when an order is transmitted via API, and there is a need to save the order ID created in the supplier's system.

<figure><img src="/files/pAt7Q6fkyBO9Mljn9wkf" alt=""><figcaption><p>Update order metafield</p></figcaption></figure>

Available only for the HTTP destination channel.

### Customer metafield

Exporteo enables you to update the order metafield after a successful export. You can use this option when you need to save the customer's ID from the supplier's system.

<figure><img src="/files/DnbnP9RsGZrMYyhaTKzI" alt=""><figcaption><p>Update customer metafield</p></figcaption></figure>

Available only for the HTTP destination channel. Requires adding `write_customers` scope to Exporteo.

### Save the value of a field from the API response

You can save the value of a specific field from the API response as a tag, order note, order metafield, or customer metafield. To do that use a Liquid formula. The entire response is stored in the `response` object. To fetch the value from a specific field use a dot notation, e.g.: `{{ response.customer.customer_id }}`

{% code title="API sample response" %}

```json
{
  "supplier_id": "12345",
  "order_id": "67890",
  "customer": {
    "customer_id": "09876"
  },
  "status": "Confirmed",
  "items": [
    {
      "product_id": "ABC123",
      "name": "Wireless Mouse",
      "quantity": 2,
      "price_per_unit": 25.99,
      "total_price": 51.98
    },
    {
      "product_id": "XYZ456",
      "name": "Keyboard",
      "quantity": 1,
      "price_per_unit": 45.99,
      "total_price": 45.99
    }
  ],
  "shipping": {
    "method": "Standard",
    "estimated_delivery_date": "2024-12-30"
  },
  "total_order_price": 97.97,
  "currency": "USD"
}
```

{% endcode %}


---

# Agent Instructions: 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:

```
GET https://help.exporteo.solvenium.com/post-processing.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.