The Intershop Order Entry Agent turns incoming customer order requests into validated commerce transactions inside Intershop Commerce Management (ICM). It serves inside sales, customer service, and order desk teams who today retype orders that arrive as e-mail, PDF, spreadsheet, or chat message.
The agent reads the request, resolves the applicable customer and commerce context, matches the requested items to products, validates them against the commerce rules of ICM and creates a native Intershop basket. ICM remains the authoritative system for customer context, pricing, availability, basket, and order state. The agent never bypasses an ICM rule. If ICM rejects a line, the agent surfaces the rejection instead of working around it.
The list below describes the functional scope.
Feature | Description |
|---|---|
Order Intake | |
Order request in your own words or as a document | Customers send their order the way they already do, as a message in their own words or as an attached document, for example, a PDF or a spreadsheet. The agent reads the request and builds the order from it. |
Can be used in Microsoft Teams | The agent can be used in Microsoft Teams. Intershop provides the Teams apps for this, one for employees of the merchant and one for the buyers at the customer. |
Order by e-mail | The agent monitors a configured mailbox and processes the message body and supported attachments. The reply reports what happened. |
Order from a file | An order is placed from a document the merchant or an employee of the merchant received, without retyping it. PDF, Word, Excel, CSV, text, and image files are read and interpreted. Supported extensions are listed below. |
Instruction alongside a file | A sentence sent with the file can steer the interpretation, for example, "only the laptops from this list" or "please also order backpacks for the notebooks". |
Free text understanding | Casual, unstructured wording is understood, including bullet lists and mixed sentences such as "3 of those arc mice for the design team, also 2 ProBooks". |
Identity and Commerce Context | |
Identity at the touchpoint | Interactive touchpoints operate in the context of an authenticated merchant or buyer. Unattended channels such as a monitored mailbox are processed by an authorized agent identity, and the applicable customer context is resolved from the request and the configuration. |
B2B customer and buyer resolution | Identifies the company and, where applicable, the individual buyer behind the request. |
Sales channel commerce context | The configured sales channel determines catalog, assortment, pricing context, and currency for the resolved customer. |
Interpretation and Matching | |
Order line extraction | Extracts the order lines with product identifier or SKU and quantity from text and documents. |
SKU and article number recognition | Recognizes SKUs and article numbers in the request and uses them as the matching key. If a line contains no quantity, the agent assumes one piece and says so in the basket summary. |
SKU matching | Matches the requested article numbers against the products available in the applicable commerce context. |
Unmatched and ambiguous positions | Identifies positions that cannot be matched or that match more than one product, and asks instead of guessing. |
Shipping address extraction | An optional shipping address contained in the request is extracted and applied to the basket. |
Basket and Order | |
Native basket in Intershop Commerce Management | The agent creates a native basket for the resolved customer in the configured sales channel and adds the identified articles and quantities. The assortment, the prices, and the basket rules of ICM apply. An extracted shipping address is applied. A line ICM rejects, for example, because of a minimum order quantity, is named and must be corrected before the order can be placed. |
Basket summary and confirmation | When confirmation is configured or required, the agent presents the interpreted basket with articles, quantities, and prices and asks for a clear confirmation before submission. An ambiguous answer leads to a follow-up question. |
Conversational correction | The interpreted basket is corrected in natural language, for example "make it 5 mice", and rebuilt. |
Order submission | The agent submits the basket as an order in Intershop Commerce Management when all required information is available and the configured confirmation and authorization conditions have been satisfied. |
Configurable confirmation step | Whether a request needs a confirmation step is configured instead of being fixed per touchpoint. The approval rules of ICM continue to apply in either case. |
Approval | |
Cost center and budget approval | The cost center and budget rules configured for the customer are respected. If an approval is required, the prepared order is submitted as a requisition and runs through the existing approval process. |
Notification when an approval is required | If the order exceeds a budget or a limit, it is not placed. ICM creates a requisition, and the agent reports that the order is on hold, who has to approve it, and states the budget status. |
Draft order review by the merchant | Orders received through configured agent channels can require an operational review by the merchant. They are shown as draft orders in Intershop Commerce Management, where an authorized user accepts or rejects the draft before it becomes an order. This review is separate from the customer's requisition approval. |
Attribution and Operations | |
Order on behalf of a customer | An authorized sales or service employee of the merchant prepares and submits an order on behalf of one of their customers. The identity of the acting employee and the identity of the represented customer are both preserved. Both are visible to the customer in the order history of their account area and to the merchant in Intershop Commerce Management, so it is visible that a key account manager or a service representative placed the order and not the customers themselves. Within one conversation the agent can switch to another customer. |
Order channel attribution | Orders created by the agent carry an |
Feedback when a request cannot be processed | If the agent cannot use what was sent, it says so instead of failing silently or ordering something it is unsure about. |
The file types below apply to the feature Order from a file.
Type | Extensions |
|---|---|
| |
Word |
|
Excel |
|
CSV, text |
|
Image |
|
The table names the file types supported in this version. A photo taken with a phone or sent through a browser can arrive as a variant of one of these formats. Files outside the list are rejected with feedback.
Several files in one message are supported. Each file is read, anything that cannot be used is reported back, and the remaining files are processed. The limit is 10 MB per file. A scanned PDF is read as images, for the first five pages.
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.