> 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/vsm-guides/readme.md). # Value Stream Modeller Get to know the goals of VSM. Value Streams are structured visual representations of the end-to-end processes involved in delivering a product or service to a customer. They provide a comprehensive view of operational steps, helping organizations identify bottlenecks, improve workflows, and optimize value delivery.


Value Streams	View a list of all your tenant value streams.	Value Streams
Value Stream Examples	Check example value stream templates available to use right away.	Value Stream Examples
Extensions	Monitor how your value streams are running.	Extensions

Value Stream Modeller is the visual interface within Commerce Orchestration for designing, operating, and managing automated business processes. Powered by the Orchestration Engine and integrated with the Commerce Engine and Agentic layer, it enables teams to model end-to-end value streams that coordinate the sales lifecycle, from order capture through fulfillment, by responding to real-time events across the commerce and Agentic stack. By decoupling business logic from hardcoded application layers, Emporix enables composable commerce with greater flexibility, scalability, and adaptability. AI capabilities embedded throughout the solution further enhance automation, decision-making, and customer experiences. Built on a low-code/no-code foundation, the solution allows both technical and non-technical users to configure integrations, automate business processes, and deploy changes quickly. This AI-augmented environment is designed to support enterprise agility, operational efficiency, and continuous innovation. Value Stream Modeller enables you to define and monitor value streams that react to business events in real time. Each process starts with a trigger that initiates the flow, followed by a sequence of steps executed to achieve a specific business outcome. These processes run independently and follow a top-down execution model, helping ensure that outcomes such as order fulfillment and customer onboarding are delivered consistently, efficiently, and traceably. --- # 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/vsm-guides/readme.md?ask=&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.