|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.|
Platform as a service (PaaS) is a facet of cloud computing. It involves services that provides a platform allowing customer-xs 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 packing slip is a document (paper) shipped together with the products to the customer-x. It contains a list of content of the package indicating the products and quantities of delivered products or services.
|packing slip message||an Intershop 7/Intershop Commerce Management gifting feature to have gifting-related messages printed on the packing slip|
In the WCM of /Intershop Commerce Management, a page can be conceived of as an "entry point" to the storefront used to collect s. 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 multiples. When a page is rendered one of its s is chosen based on various conditions.
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 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.
In the WCM of /Intershop Commerce Management, a page variant constitutes a "container" object that holds the s. 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.
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).
a release that is only talked and written about, without actually being delivered
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.
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.
|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.|
|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.|
|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.
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-x.
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 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.
Personas are fictional characters created to represent the specific user types, skills, attitudes and/or behavior sets that use a product (e.g., (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.) or are involved in the
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 (customer-xs) 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.
The pick list is a list indicating:
|PIM||see product information management|
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.
Depending on the context, "pipeline" may refer to different concepts:
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.
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.|
mechanism for defining the price list to apply
Depending on the context, "pricing" may refer to different concepts:
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.