> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/release-notes/archive/2025/2025-07-07-oe-commerce-events.md).

# 2025-07-07: OE - Orchestrated Commerce Events

## Overview

We're introducing a full integration of Commerce Engine events into the Orchestration Engine. This enhancement allows digital processes to be triggered directly from standard commerce events—without the need for custom connectors or middleware. With event data, now natively available in the Orchestration Engine, teams can build responsive, scalable processes faster.

## New features

| Feature                                                        | Benefit                                                                     |
| -------------------------------------------------------------- | --------------------------------------------------------------------------- |
| **Direct triggering from Commerce Engine events**              | Enables real-time initiation of digital processes based on commerce events. |
| **Support for all standard Commerce events**                   | Maximizes flexibility to respond to a wide range of commerce scenarios.     |
| **Commerce events fully integrated with Orchestration Engine** | Reduces manual configuration and eliminates need for custom solutions.      |

## Fixes and improvements

None as this is a new feature.

## Known problems

No known problems at time of release.

## Documentation and links

* [Event Registry](/oe-user-guides/management-dashboard/events/event-registry.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.emporix.io/release-notes/archive/2025/2025-07-07-oe-commerce-events.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.