Title | Description |
---|---|
cache management | In Intershop Commerce Management, cache management refers to the common approach for controlling all types of caches as provided by the cache engine. This includes:
|
call center | A call center or customer care center is a centralized office used for the purpose of receiving and transmitting a large volume of requests by telephone or e-mail. A call center is operated by a company to administer incoming product support or information inquiries from consumers. Outgoing calls for telemarketing, product services and debt collection are also made. In addition to a call center, collective handling of letters, faxes, live chat and e-mails at one location is known as a contact center. See Intershop Contact Center. |
campaign | In Intershop Commerce Management, campaigns provide a means to combine multiple promotions. In addition, shop managers can assign dedicated content assets to campaigns as well as define specific target groups and validity periods for campaigns. |
CAPTCHA framework | In Intershop Commerce Management, the CAPTCHA framework provides the ability to connect to any CAPTCHA validation service/provider or implementation. The implementation is based on the managed service framework for easy activation and configuration both globally and based on individual features. |
capture | Conversion of an authorized transaction into an invoiceable transaction when the goods are delivered or services are rendered to the consumer. legal requirment: Only the invoiced amount of the delivered products can be captured. |
card authorization | A card authorization (also authorization hold, preauthorization) is the practice within the banking industry of authorizing electronic transactions done with a debit card or credit card and holding this balance as unavailable either until the merchant clears the transaction (also called settlement), or the hold "falls off." |
card security code | The Card Security Code (CSC), sometimes called
There are actually several types of security codes:
Card Security Code should not be confused with 3-D Secure . |
carrier | A carrier is a company (e.g., DHL, Hermes) that transports products or services for example from:
Normally the carrier and the fulfillment center are under contract. |
cartridge | Depending on the context, "cartridge" may refer to different concepts:
|
cartridge API | The cartridge API (CAPI) is the API for implementing, enhancing or customizing functionality within an Intershop Commerce Management application server. The CAPI consists of Java interfaces and classes which are contained in cartridges. |
cash in advance | Cash in advance is a financial transaction / payment method used e.g. in online shop. The purchase price will be transferred to the clients bank account in advance, that means before the products will be delivered. The transfer is triggered and done by the consumer himself. The products will be delivered when the payment has been received on the clients bank account. |
cash on delivery | Cash on delivery (also known as collect on delivery) is a financial transaction / payment method where the payment of products or services received is done at the time of actual delivery. The products will be handed over only if the consumer pays at time of delivery. The payment is made to the carrier directly. From the consumer's point of view this payment method is a secure payment method since he/she pays when the products have been delivered. From the client's point of view it is a secure payment method as well, since the products will be handed over only if the consumer pays at time of delivery. |
catalog | A catalog is a view on the product repository that groups products along a specific context. Catalogs are usually structured (see category) to reflect
Products become part of a catalog via product assignment. |
catalog filter | mechanism to define catalog views, i.e., to include or exclude categories, depending on department roles |
catalog sharing | mechanism to make catalogs available across multiple channels and thus centralized management and reduction of administrative efforts |
catalog view | filter mechanism to control the visibility of catalog content on an organization-specific level |
category | A category is a structuring element for catalogs. It provides a structured view on the products associated to a catalog, which may serve the following purposes:
Via explicit product binding or implicit product binding, products are bound to categories and thus become part of a catalog. |
category link | Category links are static connections between categories and other categories or products in Intershop Commerce Management. Depending on the business semantics, there are
Intershop Commerce Management supports outbound links and inbound links. |
change tracking | mechanism to bring up locally any product or other content changes made by other actors; changes can be completely or partially accepted or rejected |
channel | Technically, a channel in Intershop Commerce Management is a data repository combined with applications (at least a back office plugin and a storefront application) that allow for viewing and manipulating this data. Channel data can be created and held locally, or it can be shared or syndicated from the parent sales organization's master repository. Channels represent a management context. From a business perspective, channels are used to structure the sales organization, for example, along dimensions like countries, brands or business models. |
channel browser | visual representation of the channels set up for an organization and the channel organizations created within each channel |
channel catalog | catalog defined from a channel repository, only available within the channel and cannot be shared across channels |
channel organization | organizations created within the channel: partners and customers |
channel page | In content sharing scenarios, content page (deprecated)s that are created, maintained and used in the context of an individual channel |
channel product | product stored in the channel repository, can be created locally or derived from master products to inherit attributes |
channel repository | Set of all products available to customers or partners within a channel. |
channel slot | In content sharing scenarios, slots that are created, maintained and used in the context of an individual channel |
channel user | users with channel-specific access privileges |
chargeback | Withdrawal by the credit card issuer of the amount credited to the merchant's (client's) account (plus a chargeback fee) when a card-holder (consumer) disputes a transaction charged on his or her card. The merchant usually has 10 days to submit proof of purchase and proof of delivery to reclaim the charged back amount. |
checkbox | A checkbox is a square interactive box customers can use to select one or more items from a list. Checking a box enables the option, unchecking disables it. |
checkout | In e-commerce the checkout process reflects the steps that have to be performed to place an order. All data needed to fulfill the order have to be provided by the customer. The main steps are:
|
CIC | |
classification attribute | definable property used to assign products to custom classification catalogs |
classification catalog | Classification catalogs pre-define a set of categories to which products can be assigned. |
CLC | see command line client |
client | Client (computing), software that accesses a remote service on another computer. |
cloud computing | Cloud computing is a type of Internet-based computing that provides shared computer processing resources and data to computers and other devices on demand. It is a model for enabling ubiquitous, on-demand access to a shared pool of configurable computing resources (e.g., computer networks, servers, storage, applications and services), which can be rapidly provisioned and released with minimal management effort. The common definition of cloud computing defines three service models:
These models offer increasing abstraction, and hence, are often portrayed as a layers in a stack. |
cluster | From Intershop's perspective, a cluster is a "complete" Intershop Commerce Management system, made up of all cluster nodes acting together. That is, a cluster consists of one or more Intershop Web Server instances and one or more Intershop Application Server instances, which use the same Intershop Shared Files instance and database instance. The components that make up the cluster may be installed all on one physical machine or distributed over several physical machines. |
Cluster Management | In Intershop Commerce Management, a management tool for the system administrator to control the Intershop Application Server instances, as well as the applications on top of them, running in the cluster. |
cluster node | In the software deployment concept of Intershop Commerce Management, a cluster node is one of the three main building blocks of a cluster, which may be deployed individually for distributed installations via host types. |
CMS | see web content management |
command line client | The command line client (CLC) is a tool to trigger pre-configured jobs or run import processes in the context of Intershop Commerce Management. The CLC is self-contained, that is, it does not require any other parts of the Intershop instance. The CLC can be copied to and run from any other machine with a JRE installed. |
Commerce Management | The Commerce Management (or Commerce management application) is the main business application of the Intershop Commerce Management. As the primary business management tool it allows for business-relevant tasks, like product and catalog management, content management, shop application management, promotion and campaign management, etc. |
commodity group | a means to establish an alternative, catalog independent grouping for products |
communication type | The communication type refers to the way of communication between the Intershop Contact Center and a customer, like phone, e-mail, chat, etc. |
community | refers to the members of an organization within Enfinity Suite 6 with respect to their ability to exchange messages in discussion forums |
component | Generally, a component is one of several parts that make up a whole. From a development process point of view, a component is a container for feature or feature set intended to be release. Technically, a component is a container for all kinds of implementation artifacts (see system component) that are to be assembled to form a product, solution or extension. In the context of Intershop Commerce Management, component may refer to: |
component file | In the context of the component framework of Intershop Commerce Management, the term component file refers to the XML file that actually declares the contracts, implementations and instances of the corresponding code artifacts. |
component framework | In Intershop Commerce Management the component framework is introduced to declare dependencies between code artifacts. It allows to initialize a graph of Java objects ("run-time component") that represent the running application types. So-called component files are XML files that define which Java classes must be instantiated and how the members of the instances must be initialized/connected with each other (contracts, implementations and instances). Instances that are created by the component framework can be application-specific, i.e., different wirings can be achieved per application type. As opposed to the dependency injection framework, which is based on Guice, the component framework provides more flexibility and supports Intershop-specific development artifacts. |
component template | In the WCM of Intershop Commerce Management, a component template is a blueprint for content components or other component templates, which specifies the structure (the slots, etc.) and defines any required rendering parameters. As opposed to a component type, a component template is created in the back office. |