This online publication is intellectual property of Apptus Technologies. Its contents can be duplicated in part or whole, provided that a copyright label is visibly located on each copy and the copy is used in conjunction with the product described within this document.
All information found in these documents has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither Apptus Technologies nor the authors shall be held liable for possible errors or the consequences thereof.
Software and hardware descriptions cited in these documents might be registered trademarks. All trade names are subject to copyright restrictions and may be registered trademarks. Apptus Technologies essentially adheres to the manufacturer’s spelling. Names of products and trademarks appearing in this document, with or without specific notation, are likewise subject to trademark and trade protection laws and may thus fall under copyright restrictions.CLOSE
The Integration section provides a full overview of what an integration with Apptus eSales Fashion entails. It conceptually consists of three parts:
- Data Feed - Producing and scheduling updates of product data.
- Behavioural Data - Providing behavioural data for relevance.
- Web Integration - The web integration of different parts of a site.
Two types of developer resources are required for the eSales Fashion integration. One server-side/back-end resource for the Data Feed and Order parts, and one client-side/front-end resource for the Web Components integration.
Market identifiers and key conventions
Market identifiers and product key conventions must be consistent across all three integration points.
A retailer must think through and decide early on in the integration process of what conventions to use and communicate it clearly to both integrators and Apptus.
Note that all identifiers and keys are case sensitive.