> For the complete documentation index, see [llms.txt](https://kb.theloops.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.theloops.io/releasenotes/release-notes/digital-workers-release-notes/customer-order-manager.md).

# Customer Order Manager

{% updates format="full" %}
{% update date="2025-12-01" %}

## Product Overview

* **Digital Worker Name:** Customer Order Manager
* **Release Version:** Q4 2025
* **Release Date:** 1 Dec 2025

### **What's New**

This release introduces the Customer Order Manager Digital Worker, a new autonomous digital worker that processes customer purchase orders end-to-end—from ingestion through creation of a draft customer order in IFS Cloud—while preserving governance and human control for ambiguous or low-confidence scenarios. 

#### What’s new at a glance: 

* Automatic ingestion of customer POs from email with PDF attachments. 
* Intelligent extraction of customer + line-item fields (part, qty, price, dates, ship-to/bill-to). 
* Customer and product mapping against ERP master data (including customer part number → sales part number cross references).  
* Quantity conversions and unit normalization to reconcile customer ordering formats with internal sales units. 
* HITL escalation for invalid parts, ambiguity, low-quality documents, and policy-driven exceptions. 

### Changes in Product Offering

<details>

<summary>New or Enhanced Functionality</summary>

This is the initial release of Customer Order Manager Digital Worker which focuses on delivering automated customer order ingestion, validation, and PO creation in ERP while handling HITL escalation for exceptions.

</details>

<details>

<summary>Deprecated Functions</summary>

Not applicable.

</details>

<details>

<summary>Removed Functions</summary>

Not applicable.

</details>

### Release Scope & Constraints&#x20;

<details>

<summary>Supported Scenarios</summary>

* Standard customer order creation from email or PDF&#x20;
* Orders with valid part numbers and quantities&#x20;
* Orders with ambiguous or invalid parts (HITL required).&#x20;

</details>

<details>

<summary>Unsupported Scenarios</summary>

* Autonomous negotiation or pricing decisions&#x20;
* Non-PDF attachments or multi-ERP scenarios &#x20;
* Orders without required customer or product references&#x20;

</details>

<details>

<summary>Processing Constraints</summary>

* One active order per PO number; duplicates prevented.&#x20;

</details>

### Prerequisites

#### Supported Deployment Models&#x20;

Supported with Cloud & On-Prem deployment strategies of IFS Cloud.&#x20;

#### Business prerequisites:&#x20;

* Appropriate IFS Loops entitlement to provision/use the Supplier Invoicing Manager Digital Worker&#x20;
* Appropriate IFS Cloud entitlement to provision/use specific technical components required.&#x20;
* Standardized customer order formats preferred.&#x20;
* Defined approval workflows for exceptions.&#x20;

#### Technical prerequisites:&#x20;

* IFS Cloud order management enabled.&#x20;
* Email and Teams integration configured.&#x20;
* Required permissions for order creation and document attachment.&#x20;
  {% endupdate %}
  {% endupdates %}


---

# 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://kb.theloops.io/releasenotes/release-notes/digital-workers-release-notes/customer-order-manager.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.