Table of Contents Introduction View and Edit Interactive Prototype Responsive Design Page Notes Feedback Wireframes Introduction The wireframes described here contain interaction designs for storefront pages. Elements and functionality of the Intershop Progressive Web App are displayed and explained

Table of Contents Introduction References Approach Architecture Overview Copilot Service Copilot Client Introduction Intershop Copilot for Buyers is an AI-powered purchase and service assistantant integrated within a Progressive Web Application (PWA) allowing users to access intelligent recommendations

Table of Contents Introduction Overview Introduction The Intershop Copilot for Buyers, an AI-powered purchase and service assistant, is designed to enhance the customer experience by providing a conversational interface for product discovery and service assistance. It leverages advanced Large Language

The Order IOM Extension REST API works only with the IOM Connector enabled. This API specification is available for download as an Open API 3.0 YAML file: icm-order-iom-extension-1x0x1.yaml References The following page lists available REST APIs for ICM 11 and their version dependencies: Reference -

Table of Contents Introduction ER Diagrams Order Product Introduction This document shows how the database schema of the BI Data Hub is defined. It is intended for data analysts who plan to use the data for their own reporting. ER Diagrams Order Column Name Description order_document document_no Order

Introduction Recipe: Configure the Order Export for the BI Data Hub Recipe: Add BI Dashboard to ICM Recipe: Create Report Based on Intershop Template Recipe: Adjust Reports Recipe: Download Default Report Templates from Intershop Introduction The BI Data Hub allows you to gain insight into different

Introduction Preconditions Instructions Creating an Order Submission Service Configuring the Service Setting Up the Order Export Optional: Export "Old" Orders Introduction To collect order data from an ICM for the BI Data Hub, an order submission service must to be created in the ICM. Once the service

Description In case of a successfully exported order, status matches IOM (mostly). If the exact same order is then exported again from ICM (user error, other reasons) the result is that the order is flagged as export failed and the correct status can no longer be seen in ICM. Steps to Repeat Copied from

Description Customer noticed, that there are some issues in the Payload they are receiving from IOM for RMA: Payload looks like this, and it is missing the county field: Also there is a NULL in the Addition address field: <ns2:Addition>Principala nr 145 null</ns2:Addition> <?xml version="1.0" encodi

Description The order history (my account) gets very slow when there are more and more orders. In our case 17 orders led to a 6s load time. ICM 7.10.30.2 / IOMConnector 6.5.1/2 We use the RSS Repro Steps Have an account with roughly 20 orders and navigate to the order history. Observe long loading times