|PA-DSS||The Payment Application Data Security Standard (PA-DSS) is the global security standard created by the Payment Card Industry Security Standards Council (PCI SSC). The standard aims to prevent developed payment applications, incl. e-commerce systems, for third parties from storing prohibited secure data including magnetic stripe, CVV2, or PIN.||Intershop 7 PA-DSS Implementation Guide|
Platform as a service (PaaS) is a facet of cloud computing. It involves services that provides a platform allowing customers to develop, run, and manage applications without the complexity of building and maintaining the infrastructure typically associated with developing and launching an application.
The capability provided to the customer is to deploy onto the cloud infrastructure customer-created or acquired applications created using programming languages, libraries, services, and tools supported by the provider. The customer does not manage or control the underlying cloud infrastructure (network, servers, operating systems, or storage), but has control over the deployed applications and possibly configuration settings for the application-hosting environment.
Intershop offers Intershop Commerce Management and Intershop Order Management as PaaS solutions to their partners and customers, including the option to modify and extend the standard offering as well as to re-distribute the offered services.
A pack slip is a document (paper) shipped together with the products to the customer. It contains a list of content of the package indicating the products and quantities of delivered products or services.
Intershop 7 and Intershop Commerce Management provide an option to have gifting-related messages printed on the pack slips, "pack slip messages".
|pack slip message||an Intershop 7/Intershop Commerce Management gifting feature to have gifting-related messages printed on the pack slip|
|packet||A packet is a packaging unit for physical products that have to be shipped to the customer.|
|page||In the WCM of/Intershop Commerce Management, a page can be conceived of as an "entry point" to the storefront used to collect page variants. Pages are instances of a specific page type (defined by a pagelet) which specifies any parameters required for rendering the web page. Pages can have assigned multiple page variants. When a page is rendered one of its page variants is chosen based on various conditions.|
|page cache||In Enfinity Suite 6, Intershop 7 and Intershop Commerce Management, page cache means a temporary memory (managed by the Web Adapter) that keeps compiled front end pages (i.e., application responses) in order to speed up retrieval.|
|page component (deprecated)||in Enfinity Suite 6's storefront editing, the "container" providing the content to be displayed in the slots/content page (deprecated)s|
|page template||In the WCM of/Intershop Commerce Management, a page template is a blueprint for page variants or other page templates that specifies the structure (the slots, etc.) of the final web page shown in the storefront and defines any parameters required for rendering the web page. In contrast to page variant types, page templates are created in the back office.|
|page variant||In the WCM of/Intershop Commerce Management, a page variant constitutes a "container" object that holds the content components. Page variants are based on a page variant type or a page template that specifies the structure and defines any required parameters. Page variants are assigned to pages. Individual page variants can be subject to personalization, time control, etc.|
|page variant type||In the WCM of/Intershop Commerce Management, a page variant type is a blueprint for page variants or page templates that specifies the structure (the slots, etc.) of the final web page shown in the storefront and defines any parameters required for rendering the web page. A page variant type is the direct back office representation of a corresponding pagelet definition developed in Intershop Studio.|
|pagelet||In the WCM of/Intershop Commerce Management, pagelets are the development artifacts that constitute the meta model for the pages, page variants, content components, page templates, component templates, includes and view contexts that are managed via the back office to compose storefronts (or other front ends).||Concept - CMS - Introduction|
|paperware||a release that is only talked and written about, without actually being delivered|
|parent channel||in the demand chain, the channel of the parent (superior) organization|
|parent organization||In the demand chain, the organization that is superior to another|
|partial replication||Deprecated: use object replication instead|
Depending on the context, "partner" may refer to different concepts.
|partner back office||In Enfinity Suite 6, the channel application of the partner channel, used by administrators of partner organizations for all administrative tasks, including organization management, channel management (via channel management plug-in), catalog management, or content management.|
|partner channel||A pre-defined channel type in Enfinity Suite 6/Intershop 7/Intershop Commerce Management that enables sales organizations and partners to offer goods and services through partners, to interact with partners and to fulfill their orders.|
|partner channel management plug-in||In Enfinity Suite 6, the partner channel module within the sales organization back office, used by administrators of the parent organization that hosts the partner channel. This plug-in allows for managing partners, channel catalogs, content and orders.|
|partner organization||Selling organizations working within a partner channel, see partner|
|password reminder||mechanism to remind customers of their storefront password|
A release of a software product (Intershop Commerce Management, Intershop Order Management, Payment Connectors, PWA, Microservices) that is intended to fix a number of issues of a previous version.
|payment costs||definable surcharge to be added onto the order total depending on the selected payment method|
|Payment Forecast||Payment Forecast is a SIMCOMMERCE-based predictive analytics application that forecasts the influence of a web shop's set of payment methods on the average order value, average return rate, average conversion rate, and the revenue after returns. That is, using Payment Forecast merchants can define the optimum set of payment methods for their web shops.|
|payment framework||In Intershop 7/Intershop Commerce Management, the payment framework facilitates the integration of external payment services. This framework provides an API for plugging in new payment service implementations and works as an abstraction layer between the actual payment service implementations and Intershop 7/Intershop Commerce Management. The standard implementation of the payment framework is based on the managed service framework.||Overview - Payment|
|payment instrument||A payment instrument is the actual physical or virtual object that facilitates a purchase or a transaction via a specific payment method, such as one of possibly more physical credit cards or one of possibly more individual bank accounts.|
A payment method is a method that reflects the kind of money transfer from one party to another (customer to merchant). There are different payment methods that can be offered in online shops, e.g.
|payment service provider|
A payment service provider (PSP) is a company that offers merchants online services for accepting electronic payments by a variety of payment methods including credit card, bank-based payments such as direct debit, bank transfer, and real-time bank transfer based on online banking.
Typically, a PSP can connect to multiple acquiring banks, card and payment networks. In many cases the PSP will fully manage these technical connections, relationships with the external network, and bank accounts. This makes the merchant less dependent on financial institutions and free from the task of establishing these connections directly - especially when operating internationally.
A payment service provider is the business partner who handles the financial transactions in case, for example, a credit card will be offered as payment method. The partner is involved in the process of card authorization and capture.
A payment solution is a software for accepting electronic payments by a variety of payment methods including, for example, credit card, bank-based payments such as direct debit bank transfer or real-time bank transfer based on online banking.
Payment solutions are provided by a payment service provider (PSP).
Generally, the performance of an e-commerce software is one of the major criteria for its market acceptance. Customers expect quick response times when visiting a web shop, and the owner of the e-commerce software wants to optimize the operational efforts and costs.
With respect to Intershop 7/Intershop Commerce Management, performance and scalability measures apply to the following areas on different levels:
|Overview - Performance|
The performance report is a document, available for different builds (generally, builds that reach the QA entry criteria for testing) and give a detailed overview about the following NFR test measurements:
Permission marketing is a marketing technique that requires the approval of the customer.
For example, the merchant sends e-mail newsletters only to those customers who have specifically requested it. Different kind of procedures are possible:
Permission marketing comes into force during the newsletter subscription. The kind of procedure that has to be implemented depends on the legal requirement of the country where the consumer are coming from. In Germany, for example, the double opt-in procedure is preferred from the legal point of view but not specially requested.
Persistent objects (POs) are Java objects used to write and read data to/from the database ("ORM beans"). They are persistent implementations of business objects.
See persistent object layer.
|Overview - Persistent Object Layer|
|persistent object layer||In the layered software architecture, the persistent object layer groups the persistent objects, which are used to write and read data to/from the database (see ORM). In Intershop 7/Intershop Commerce Management, the persistent object layer is implemented in the ORM engine.||Overview - Persistent Object Layer|
|persona||Personas are fictional characters created to represent the specific user types, skills, attitudes and/or behavior sets that use a product (e.g.,) or are involved in the (e-)commerce process in a typical way. Personas are useful in considering the goals, desires and limitations of users in order to guide decisions in the software engineering process about services, products and related interactions. They have a personality, including a name and an image, and complement use scenarios. Personas are different from system user roles but are typically mapped onto them.|
Generally, online shop personalization summarizes all means for creating different experiences that are unique to individual customers or customer segments.
Personalization can be based both on
Mainly, personalization aims at the content to be presented, like catalog views, individual product recommendations, promotions etc. Additionally, personalization can impact formal presentation criteria like display language, colors, etc.
A personalization group is a temporary group of users (customers) for which the storefront must be personalized in the same way. The personalization is done for groups of users rather than for single users for efficiency reasons. This reduces the number of possible page variations and allows for better page caching and reuse of personalized pages.
The personalization group membership for a user can be determined using various criteria, like authentication state (anonymous, logged in), registration state, customer segment, address etc. The personalization group membership may change with the users interaction in the storefront, like after authentication (login, logout), registration at the store or other actions.
Personalization groups are expressed by a PGID, which is contained in the URL. The PGID is important to distinct between personalized pages with otherwise equal URLs. For example, the same product page can have multiple instances with different prices, one for each personalization group.
A pick list is a document used in a fulfillment center that enables a person to pack the packet that will be delivered to the customer.
The pick list is a list indicating:
|PIM||see product information management|
|pipelet||In Enfinity Suite 6/Intershop 7/Intershop Commerce Management development, pipelets are small, re-usable units of Java code (one type of pipeline building blocks) that perform discrete business functions.||Overview - Pipelets and Pipelines|
Depending on the context, "pipeline" may refer to different concepts:
|Overview - Pipelets and Pipelines|
|placeholder||In the WCM of/Intershop Commerce Management, placeholders define editable areas in page variants or content components that are derived from page templates or, respectively, component templates. If provided for by their corresponding types, page templates or component templates can propagate their slots to their derived page variants or components via placeholders.|
|point of sale||A point of sale or point of service is one type of a touchpoint. It can be a retail shop, a checkout counter in a shop, or the location where a transaction occurs. Point of sale often refers to a terminal or more generally to the hardware and software used for the checkout process -- the equivalent of an electronic cash register.|
|post||an individual message in a discussion forum|
|predefined product filter||Predefined product filters are a search engine-based means to provide flexible product filtering options for Intershop 7/Intershop Commerce Management. They are used, for example, to dynamically assign products to catalog categories, or to automatically populate content components with products.|
|price list||mechanism for administrating multiple prices for products, used to enable customer segment-specific pricing, special prices for certain periods or discount visualization ("strike-through prices")|
|price lookup||mechanism for defining the price list to apply|
|price step||in auctions (Enfinity Suite 6), minimum increment or, in reverse auctions, decrement between bidding steps|
Depending on the context, "pricing" may refer to different concepts:
|Overview - Pricing|
Priority represents the importance of items, where more important items are listed or dealt with before less important items.
The top priority is 1. A higher value indicates a lower priority.
Priority defines when items need to be ordered by importance, but the absolute value of the priority does not have an influence on the results of the calculation, only the fact that the priority is higher or lower.
In Intershop 7 and Intershop Commerce Management, process chains are a mechanism for automating the sequential execution of interdependent scheduled jobs or pipelines.
Defining a process chain involves, basically, the following tasks:
|Overview - Process Chains|
|procurement channel||In Enfinity Suite 6, a pre-defined channel type that enables buying organizations to collaborate with their suppliers. The procurement channel is used by buying organizations to browse catalogs and products, create requisitions and orders to be fulfilled by suppliers. The procurement channel also provides sophisticated sourcing features, enabling - for example - RFQs and reverse auctions.|
Depending on the context, "product" may refer to different concepts:
|Overview - Product Information Management|
|product advice||When using Intershop Commerce Advisor in B2B scenarios, the product advice is an individual product, which is suggested to be included in the merchant's assortment. This recommendation is based on the merchant's business profile, the order history and additional details.|
In Intershop 7/Intershop Commerce Management, product assignment refers to the (logical) allocation of a product to a category. Via product assignment, products become part of a catalog. Product assignment can be done either manually or dynamically:
|product attribute group||attribute group for products for technical processes (e.g., syndication) or front end visualization purposes|
|product binding||In Enfinity Suite 6, product binding is the assignment of a product to a catalog category. Via explicit product binding or implicit product binding, products become part of a catalog.|
|product bundle||in Enfinity Suite 6/Intershop 7/Intershop Commerce Management, a group of products offered with an own product ID and an overall price|
|product calendar||a list of all Intershop product releases maintained on the Intershop Support web site|
|product classification||Product classification is a category system used to group products based on shared characteristics. Enfinity Suite 6, Intershop 7 and Intershop Commerce Management support standard classification catalogs like UN/SPSC and eCl@ss and allow for custom classifications.|
|product data feed|
In Intershop 7/Intershop Commerce Management, product data feeds are a mechanism to transfer the content of the product repository on a regular base to different targets:
A product datasheet is an online document that contains all relevant information about a release of Intershop products, including
A product datasheet is a single entry of Intershop's product calendar and is updated during the product lifecycle.
|product filter||In Intershop 7/Intershop Commerce Management, a mechanism to predefine subsets of products based on configurable product searches.|
|product history||a special container that allows for viewing all changes within a product repository, i.e., provides information about added products, updated products, and deleted products|
|product information management|
Generally, product information management refers to features that support integration, centralized maintenance, and flexible distribution of product data across all touchpoints. To this end, the product information management included with Intershop 7/Intershop Commerce Management provides, among others
|Overview - Product Information Management|
Depending on the context, "product lifecycle" may refer to different concepts:
Product lifecycle definitions can also be used as advanced search parameters.
Product links are static connections between products and other products or categories in Enfinity Suite 6/Intershop 7/Intershop Commerce Management. Depending on the business semantics, there are
|product lock||mechanism in Enfinity Suite 6, Intershop 7 and Intershop Commerce Management to prevent a product from being edited by multiple back office users simultaneously, based on the locking framework|
|product maintenance||in Enfinity Suite 6, a mechanism to detect product ID conflicts|
|product management||deals with all aspects of product strategy and roadmap as well as release planning and requirement definition|
|product mapping||in Enfinity Suite 6, a mechanism to automatically assign products to a catalog category based on specific rules|
|product mapping rule||in Enfinity Suite 6, conditions that define how to classify products into catalog categories|
|product notification||in Enfinity Suite 6, Intershop 7 and Intershop Commerce Management, a mechanism for e-mailing registered customers about product availability or price changes|
|product rating||in online shops based on Enfinity Suite 6/Intershop 7/Intershop Commerce Management, the evaluation of products submitted by customers|
|product recommendation feed||files that contain product recommendation data, used to select and present product-specific recommendations in the storefront, intended to increase clickthrough and conversion rate|
|product report||account showing either revenue or quantity sales per product during a given time period|
|product sharing||A mechanism in Intershop 7 and Intershop Commerce Management to distribute large amounts of master products to sales channels without copying them||Overview - Product Sharing|
Product sorting refers to the mechanisms used to control the order in which catalog categories and products are displayed in the storefront. Generally, there are three options:
|product syndication||a mechanism to make master products available to multiple sales channels simultaneously copying them to the channel repositories|
|product type||container for classification attributes|
|product variation||a product that is offered in multiple variants that share most of their attribute values, but differ at some of them|
|profanity check||Intershop 7/Intershop Commerce Management feature aimed at keeping storefronts clean from profane language. Channel administrators can define words, relative to a locale, that are not allowed in the channel's storefront applications. As a consequence, any use of these words in product reviews, gift card messages or other content that customers can edit is then blocked.||Overview - Profanity Check|
|progression test||Testing of new functionality in a specific product version after implementation.|
Depending on the context, "project" may refer to different concepts:
A promotion is a marketing instrument with the intention to push the sales and to increase the customer satisfaction. A promotion applies to predefined customer segments, products and time periods. Specific discounts like reduced prices, bonus products, free shipping etc. can be offered via a promotion.
Different kinds of promotions are possible:
|Overview - Promotions|
A promotion code is an alphanumeric string or a number that entitles the owner (customer) to get the benefit of a promotion if the conditions are met.
The promotion code can be distributed to the customers via coupons.
|Overview - Promotions|
|promotion code group||A promotion code group is a set of promotion codes which can be assigned at once to any number of promotions. Promotion code groups help the shop manager to reduce the administrative effort.||Overview - Promotions|
|property group||Property groups are annotated Java interfaces that define a minimum set of properties that belong together to control a feature. For example, an account property group would consist of a login and a password.||Overview - Property Groups|
|provider||A provider is an implementation pattern in Enfinity Suite/Intershop 7/Intershop Commerce Management for retrieving information or for offering services. A provider consists of an abstract interface and one or more different implementations of that interface. The purpose of providers is to decouple the concrete implementation from the abstract interface in order to make it exchangeable or customizable. There are different approaches to select the provider which should be used, like dependency injection or the strategy pattern.|
|publication||in Enfinity Suite 6 content management, output format-specific (and versioned) sets of pages (based on rendering templates that are assigned to publication folders) that are published as part of an edition|
Deprecated: use "apply" instead
Enfinity Suite 6 UI action to bring into effect the conditions and rules defined by a filter, view, rule, etc.
|publishing||From a shop manager's perspective, publishing describes the mechanism for transferring individual business objects from a source cluster (or "editing system") to a target cluster (typically, a "live system" or "production system"). As opposed to the data replication, which transfers large amounts of data usually at regular intervals, publishing is intended to transfer individual (or a limited number of) objects in an ad-hoc fashion.|
|purchase commitment||In Enfinity Suite 6, purchase agreements used to track the purchasing volume of a contract. Transactions can be credited or debited to this agreement (and its corresponding contract), and a weekly, monthly, quarterly, or yearly budget can be assigned to the commitment.|
|purchase order||Generally, a purchase order is an order (a commercial document) issued by a customer to a merchant, indicating types, quantities, and agreed prices for products or services the merchant will provide to the customer. The customer's purchase order is the originating document that triggers the creation of the sales order.|
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 Web site, including, without limitation, any lost profits, business interruption, loss of programs or other data on your information handling system.