A

In case a customer abandons a basket (shopping cart) with products, i.e., leaves the storefront session without completing the checkout, then this basket is called abandoned basket. The abandoned basket can be kept and restored for further sessions. Usually only the products will be restored. Services, discounts, redeemed gift certificates that have been applied during the original session are not restored.

configurable notification that can be sent to registered customer-xs in case they abandon a basket (shopping cart) with products, i.e., leave the storefront session without completing the checkout

Typically, an access privilege is a (single) permission that controls what area of a system is available to a user. In Intershop Commerce Management, access privileges combine multiple permissions like roles.

An accessory is a product link offering a complementary product that goes with the displayed product.

Accounts are used to record transactions or entity's assets for customers, individual users, departments, companies or cost centers.

Based on accounts, different transactions can be controlled, for example:

• budget
• debit
• financial transactions
• order history
• enquiries (Call Center, Support)

There are different accounts known in the context of E-Commerce:

• customer account
• user account
• cost center account
• department account
• bank account

An address is a collection of information that describe the location of a building or apartment, specifying the end points of a postal system.

Different kind of addresses are possible:

• home address
• business address
• service point

An address check is a mechanism that verifies whether an address is a correct postal address, intended to reduce undeliverable packages.

The Address Verification System (AVS) is a system used to verify the identity of the person (customer-x) claiming to own the credit card. The system will check the invoice address (billing address) of the credit card provided by the customer with the address on file at the credit card company. Basically, the AVS verifies the numeric portions of a cardholder's billing address.

Using a common word as a search term (such as “shoe” in fashion shop) normally produces a very large number of results. The “after search navigation” allows users to reduce the results with dynamic filters, such as brand, price, price ranges, size, or color.

see application programming interface

A developer tool that verifies the compliance of API changes with the API stability requirements of the software version being developed. The API checker is executed during the build process.

Depending on the context, "application" may refer to different concepts:

1. Developer:
   From an Intershop developer's perspective, "application" refers to a database table entry that combines a dedicated application type with its corresponding data repositories (sites).   
2. Shop Manager:
   From a shop manager's or user's perspective, an application is a customizable tool that provides a set of functionality via a user interface in order to access and manage the data of Intershop Commerce Management repositories (sites). With respect to Intershop Commerce Management systems, there are two basic types of applications:
   • storefront applications (browser-based web shop, mobile shop), which constitute customer touchpoints and represent management contexts
   • management tools like System Management or the Commerce Management

customization of the channel application for each channel organization

The application framework of Intershop Commerce Management is a framework used to develop applications that consist of Java classes, pipelines, queries, webforms, and other Intershop-specific code artifacts. The Application Framework distinguishes between:

• application types - defining the code base (pipelines, ISML templates, ...) and
• applications - assigning this functionality to a particular data set in the database and the file system.

An application programming interface (API) defines a contract that is intended to be used by software components to communicate with each other. An API can take different forms, like Java interfaces, command-line parameters, web service interfaces, and others. The purpose of an API is to separate the public interface, which should be stable, from the internal implementation, which may frequently change. For Intershop, the Java API is formed by the cartridge API. Changes in an API should be avoided to ensure compatibility and are subject to strict policies. New APIs may be added in minor releases, existing APIs may only be changed in major releases.

The application server provides the runtime environment for the Intershop Commerce Management application and any additional cartridges providing business logic. The application server (currently supported: Apache Tomcat) provides (at least) the JSP and servlet engine and HTTP(S) connectivity.

From an Intershop developer point of view, an application type defines a set of functionality of applications. There can be multiple applications that are based on the same application type. The application types as well as the code artifacts themselves are deployed in the application server using cartridges.

In the B2X edition of Intershop Commerce Management, business customers can use the order approval functionality to review orders before they are sent to merchants. The order approval includes two checks:

• Cost center approval - if an order is assigned to a cost center, it must first be approved by the cost center manager before being routed to the user-specific order approval.

• User-specific order approval - if there is a budget or an order spend limit defined for a user, the order must pass the user-specific order approval.

If there is neither a cost center nor a user budget/order spend limit involved, no order approval takes place.

In Enfinity Suite 6 B2B and procurement models, approval workflows refer to the path which a requisition has to pass through before being turned into a purchase order.

single stage in the approval, assigned to specific users (approvers)

instance of an approval step in the UI; requisition line items are displayed to approvers as approval tasks

an approval instance may consist of multiple threads processed in parallel, each thread contains one or multiple approval steps

In B2B scenarios, an approver represents a user role of a business customer with the permission to approve, that is, validate and make effective, orders created by buyers.

A report about the architectural quality of Intershop software. It visualizes dependencies, metrics, consistency problems and violations against programming guidelines and architecture conventions.

An article is the smallest unit that can be ordered independently and that cannot be split further into any smaller units.

Depending on the context, "assembly" may be

• the process of combining deployment components as produced by a build process into deployable products or extensions, and
• the result of doing so, i.e., the assembled deployable and executable product or extension that can be released.

Depending on the project-specific configuration, an assembly can produce

• a product or an extension, and
• a major, minor, patch or custom fix version (of a product or an extension)

UI button, technically a means to create a relation between two persistent objects, e.g., assign a product to a catalog or assign a component to a slot of a page variant.

An assortment is the whole product range that a company (merchant) can provide to their customers. It is possible that the merchant offers several assortments in different sales channels (retail stores, printed catalog, web shop).

additional content (specifications, manuals, etc.) linked to products in the catalog or specific web shop pages

grouping mechanism to impose a meta-structure on large and complex sets of attributes, used, for example, to manage attribute mapping rules or to provide localizable attribute names

(syndication) conditions that define how attributes of the original (source) product are mapped into attributes of the target product

Auditing is the feature to produce an audit log or audit trail.

An audit trail (also called audit log) is a security-relevant chronological record, set of records, and/or destination and source of records that provide documentary evidence of the sequence of activities that have affected at any time a specific operation, procedure, or event. (http://en.wikipedia.org/wiki/Audit_trail)

The basic ideas for the auditing framework of Intershop Commerce Management include:

• Consistency between the data in the system and in the audit trail
  This implies that if a business operation fails, the audit trail must not contain an entry for a success; also, if auditing fails, the business operation must be rolled back.
• Configurability of the actual target for the audit messages
  In any case, it must be possible to route messages to an external system (PA-DSS certification requirement).
• High customizability for most features
  Since auditing brings an extra overhead to the business functionality, this allows to reach the maximum performance for each project by omitting as much as possible.