The Order Entry Agent turns an incoming customer order request into a validated order in Intershop Commerce Management (ICM). The request arrives in the form that the customer uses today: a chat message, an e-mail, or an attached document. The agent reads the request, builds the basket from it, and places the order, instead of a person keying the same order a second time.
The agent is an additional entry point to the shop, not a second commerce system. Every order it creates is a native order in Intershop Commerce Management. The assortment, the prices, the basket rules, and the approval rules of ICM apply unchanged. If ICM rejects a line, the agent reports the rejection instead of working around it. This behavior distinguishes the agent from a chatbot that keeps its own state.
The underlying business process is order entry in business-to-business trade. Customers send what they need in their own words or as an existing document. Today, an employee of the merchant reads that request and keys it into the shop. The agent takes over the keying and leaves the decisions to the responsible people.
This concept addresses product managers, solution architects, and developers who integrate the agent or extend the agent in a project. It assumes that you know the business-to-business concepts of Intershop Commerce Management, in particular sales channels, business customers, baskets, cost centers, and the approval of orders.
The concept explains how the agent works and where its boundaries are. It does not describe how to install, configure, or operate the agent, and it does not replace the feature list, which names the individual capabilities.
Term | Description |
|---|---|
Order request | What the customer sends, as free text or as a document. It is not yet an order and carries no commercial commitment. |
Touchpoint | The application in which the conversation with the agent takes place, for example, a Microsoft Teams app or Copilot for Merchants. |
Microsoft Teams merchant app | The Microsoft Teams app in which an employee of the merchant orders on behalf of one of their customers. |
Microsoft Teams buyer app | The Microsoft Teams app in which a buyer at a customer company orders for themselves. |
Commerce context | The combination of the resolved customer and sales channel that determines the applicable catalog, assortment, prices, and currency. |
Basket | The native basket of Intershop Commerce Management, created and validated by ICM. |
Requisition | An order that is held for approval instead of being placed. It has its own number, which is not an order number. It becomes a regular order once the approval is cleared. |
Draft order | The name under which Intershop Commerce Management lists a requisition that has not been approved yet. A draft order is the stage before the order. It does not appear in the order list under an order number. |
Approver | The person who releases a requisition so that it becomes an order. |
Order channel | The attribute on an order that records which agent and which touchpoint created it. |
In business-to-business trade, a large share of orders does not arrive in the shop. It arrives as an e-mail, as an order document, or as a message in a chat the customer already uses. An employee at the merchant reads the request and keys it into the shop a second time. The keying costs time, delays the order, and is the step at which quantities and article numbers are lost.
The agent removes this step. The customer keeps the usual way of ordering, and the order still enters the shop under the rules that apply to that customer.
The agent is used from two sides. Both share the same processing but they differ in who talks to the agent, how that person signs in, and whose name the order carries. The following table compares the two sides:
Aspect | Merchant Side | Buyer Side |
|---|---|---|
Who uses it | An employee of the merchant, ordering for one of their customers. | A buyer at one of the merchant's customer companies, ordering for themselves. |
Touchpoints | The Microsoft Teams merchant app and the Order Entry Agent in Copilot for Merchants. | The Microsoft Teams buyer app, WhatsApp, and a monitored mailbox. |
Signs in with | The account in the Intershop Administration Portal, with access to Copilot for Merchants. | The buyer's own shop account. |
The order is placed as | The customer, on the customer's behalf. The employee is recorded as the person who placed the order. | The buyer. |
Intershop provides both Microsoft Teams apps: the merchant app and the buyer app. Copilot for Merchants is another touchpoint on the merchant side. The agent behaves there as it does in Microsoft Teams. Nothing in the shop has to be replaced to use any of them.
The agent accepts an order request as a chat message, as an e-mail to a monitored mailbox, or as one or more attached documents. Supported document types are, for example, PDF, Word, Excel, CSV, plain text, and images, up to 10 MB per file. A scanned document is read as a picture for the first five pages of it.
The wording can be free-form. Casual sentences, mixed sentences, and lists are understood. A sentence sent together with a document determines how that document is read, for example, if only part of it is meant. Unsupported file types and empty messages are rejected rather than failing silently. The agent reports that it could not use the submitted content.
The agent extracts the order lines from the message and from the attachments. Each line contains a product ID or stock keeping unit (SKU) and a quantity, and an optional shipping address is read as well. Article numbers and SKUs are the matching key. Product names are not matched, so a request has to carry an article number for the line to be recognized. If a line contains no quantity, the agent assumes one piece and states this in the basket summary.
The extracted items are matched against the products that are available in the applicable commerce context. A position that cannot be matched, or that matches more than one product, is reported, and the agent asks a follow-up question. The agent does not select one of several candidates on its own.
Before anything commercial happens, the agent resolves who the order is for. On the merchant side, the employee names the customer by e-mail address, customer number, or surname. The agent asks a follow-up question if more than one person matches. On the buyer side, the acting user is the signed-in identity.
The resolved customer and the configured sales channel together determine the catalog, the assortment, the pricing context, and the currency. Therefore, an order placed through the agent shows the same prices and the same products that the customer sees in the storefront.
The agent creates a native basket in the configured sales channel for the resolved customer and adds the identified products and quantities to it. The validation rules of Intershop Commerce Management apply while the lines are added. A rejection, for example, a minimum order quantity or a packaging increment, is attributed to the affected line and reported. A basket that ICM considers invalid cannot be submitted. The affected line has to be corrected first.
The interpreted basket is presented before anything is ordered, with the lines, the customer's own prices, and the totals. It can be corrected in natural language, and the agent rebuilds it and shows it again. A confirmation in natural language is sufficient. An ambiguous answer leads to a follow-up question.
Whether a confirmation step is required is a matter of configuration rather than a property of the touchpoint. If the configuration allows it, a request can be submitted without an additional confirmation, while the approval rules of ICM still apply.
The approval rules form the second stage. If the cost center and budget rules of the customer require it, the prepared order becomes a requisition instead of an order. The agent then reports the requisition number, the approver by name and e-mail address, and the budget against which the order was measured. A requisition is the draft order stage. Intershop Commerce Management lists it as a draft order, and it becomes a regular order only after the approval is cleared. A merchant can also require a review of orders that arrive through an order channel. This review is performed in Intershop Commerce Management by users who hold the corresponding role.
Every order the agent creates carries the order channel it came from. An order placed for a customer also carries the name of the person who placed it. Both are visible to the customer in the order history and in the order details of their account area. They are also visible to the merchant in Intershop Commerce Management. The customer can therefore see which orders the agent handled and which a person keyed.
The agent sits between the touchpoint and the Intershop Commerce Management. It holds the conversation and the interpretation. The agent holds no assortment, no prices, and no order state of its own.
The following table lists the components and their roles:
Component | Role |
|---|---|
Touchpoint | Carries the conversation and the attachments. On the merchant side, the touchpoints are the Microsoft Teams merchant app and Copilot for Merchants. On the buyer side, they are the Microsoft Teams buyer app, WhatsApp, and a monitored mailbox. |
Agent | Receives the message and keeps the state of the conversation, including the customer it is currently ordering for. Interprets the request and drives the basket and the order through ICM. |
Intershop Administration Portal | Holds the account of the merchant employee and the access to Copilot for Merchants. The sign-in on the merchant side runs against the realm of their company. |
Intershop Commerce Management | Resolves the customer, supplies the assortment and the prices, validates the basket, applies the approval rules, and stores the requisition or the order. It remains the authoritative system for all of them. |
Intershop Progressive Web App | Shows the resulting order to the customer, with the order channel it came from and the name of the person who placed it. |
The direction of the data flow matters for the boundaries. The agent reads from ICM and writes through it. It never writes an order into a store of its own and reconciles it later, and it never caches prices or assortments to answer faster.
A request passes through seven stages. Each stage has a result on which the next stage depends. A request can end at any stage.
The following table describes the stages:
Stage | Name | Result |
|---|---|---|
1 | Intake | The message and its attachments are accepted or rejected with a reason the sender can act on |
2 | Identification | The acting user is known, and the customer for whom the order is intended is resolved |
3 | Interpretation | A list of requested items with quantities and an optional shipping address |
4 | Matching | Products of the applicable commerce context, or an open question about a position that is unclear |
5 | Basket | A native basket, validated line by line by ICM |
6 | Confirmation | An explicit confirmation, or no confirmation if the configuration allows the request to pass without one |
7 | Order | An order in Intershop Commerce Management, carrying its order channel and the person who placed it. |
Nothing is processed before the acting person is known. On the merchant side, the agent answers an unsigned message only with the sign-in card. The sign-in runs against the realm of the employee's own company. The account needs access to Copilot for Merchants, which an administrator grants in the Intershop Administration Portal. Ordering for a customer also requires the role in Intershop Commerce Management that allows acting on behalf of customers. On the buyer side, the buyer signs in with their own shop account.
The agent acts with the permissions of the signed-in person. It can see and do only what that person can see and do in the storefront or in Intershop Commerce Management. Commercial rules are therefore not a matter of trust in the agent. They are enforced in ICM where they are defined.
This has two consequences:
A budget cannot be exceeded through the agent, because the agent does not place the order; ICM does and turns it into a requisition.
An assortment cannot be widened through the agent, because the agent can match only the products that the resolved customer is entitled to see.
A conversation is bound to one customer at a time. Naming another customer switches the binding, and a basket that was prepared for the previous customer is no longer valid and is rebuilt. Ending the conversation ends the binding, so a new conversation never continues the previous one.
The following table lists the responsibilities of each party:
Party | Responsibility |
|---|---|
Intershop | Provides the agent, the Microsoft Teams applications, and the integration into Intershop Commerce Management. |
Merchant | Grants access to Copilot for Merchants and the role for ordering on behalf of customers. Decides which order channels require a review. Keeps assortment, prices, and approval rules in ICM. |
Customer | Maintains their own cost centers, budgets, and approvers, which continue to apply unchanged when an order arrives through the agent. |
The information provided in the Knowledge Base may not be applicable to all systems and situations. Intershop Communications will not be liable to any party for any direct or indirect damages resulting from the use of the Customer Support section of the Intershop Corporate Website, including, without limitation, any lost profits, business interruption, loss of programs or other data on your information handling system.