> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/administration-and-setup/workflow/cards-overview/and/compare-with-purchase-order/order-data-in-order-confirmation.md).

# Order Data in Order Confirmation

<figure><img src="/files/IPgi0N60edV0fvSMAcEq" alt="" width="563"><figcaption></figcaption></figure>

## **Purpose**

This workflow card is designed to compare specific fields—**Unit Price**, **Discount**, or **Quantity**—between an order confirmation and a purchase order. It ensures consistency and compliance with agreed terms. Based on the comparison result, the card allows users to write specified text into a chosen field when the condition evaluates as **true** or **false**, streamlining document processing and reducing manual intervention.

## **Components of the Card**

1. **Order Data**
   * **Description:** Specifies the field to be compared between the order confirmation and the purchase order.
   * **Options:**
     * **Unit Price**: Compares the unit price in both documents.
     * **Discount**: Compares the discount percentage or value.
     * **Quantity**: Compares the ordered quantity.
2. **Operator**
   * **Description:** Defines the condition applied during the comparison.
   * **Options:**
     * **Equals (=):** Checks if the value in the selected field matches between the order confirmation and the purchase order.
     * **Not Equals (≠):** Ensures the value in the selected field differs between the two documents.
3. **Text**
   * **Description:** Specifies the text to be written into the target field upon condition evaluation.
   * **Detail:** This text can include custom notes, status updates, or predefined values.
4. **Field Name**
   * **Description:** Specifies the field where the text will be written.
   * **Detail:** The target field is selected from available editable fields within the system.
5. **Condition Result**
   * **Description:** Determines when the text should be written, based on the comparison result.
   * **Options:**
     * **True:** Writes the text if the comparison condition is met.
     * **False:** Writes the text if the comparison condition is not met.

## **Functionality**

* **Comparison Evaluation:** The system compares the selected field between the order confirmation and the purchase order using the specified operator.
* **Action Execution:** If the condition evaluates as **true** or **false**, the specified text is written into the designated field.

## **Setup and Configuration**

* To set up this card, users first select the field to be compared—**Unit Price**, **Discount**, or **Quantity**. Then, they choose an operator to define the comparison condition, such as **equals** or **not equals**. Users specify the text to be written into a target field and select when this action should occur, based on the condition result (**true** or **false**).

## **Example Scenario**

* An order confirmation lists a unit price of $50 for a product, while the purchase order specifies a price of $45. Using the **Not Equals (≠)** operator, the card identifies the discrepancy and writes the text "Price Mismatch" into a designated field when the condition evaluates as **true**.

## **Conclusion**

The "\[Unit Price/Discount/Quantity] in Order Confirmation" workflow card provides a practical solution for ensuring document consistency. By automatically flagging discrepancies and writing relevant text into specified fields, it enhances efficiency and reduces errors in order management processes.


---

# 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.docbits.com/administration-and-setup/workflow/cards-overview/and/compare-with-purchase-order/order-data-in-order-confirmation.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.