Generally, a commercial statement detailing a set of products and services to be purchased in a single transaction by a buyer from a supplier at a defined price. In addition to prices, the quote negotiation process (see RFQ) also considers conditions like minimum quantity, discounts, payment terms etc.

With the Intershop Commerce Management B2X edition, the Extended B2B Module of Intershop 7 and in Enfinity Suite 6 procurement and B2B models, quote is an "answer" to a request/RFQ and constitutes a mechanism for "freezing" prices (and other product attributes) for a specific customer and for a definable period.

A recommendation is a product or a service that fits a selected product. It is offered together with the selected one (e.g., cross selling, up selling). In Enfinity Suite 6/Intershop 7/Intershop Commerce Management, recommendations are known as product links.

There are different kind of recommendations possible:

• pre-defined static recommendations (product links) like
  • cross-selling or up-selling
  • follow up
  • replacements
  • accessories
• dynamically created recommendations based business reports like
  • catalog and product data
  • basket and order information
  • click streams

Dynamic recommendations can be created by a recommendation engine provided by a business partner.

A recommendation engine is a system (software) that generates recommendations based on provided information or business reports, for example, "customers who have bought this product have also bought these products".

A recommendation engine can be provided by an external business partner (3rd party) and integrated with Intershop 7/Intershop Commerce Management via the managed service framework.

Based on an action by an actor or a system (e.g., "add to basket"), a recommendation event is the piece of information sent to a recommendation engine for it to "learn" about customer behavior and preferences.

As opposed to the recommendation request, the recommendation event feeds information to the recommendation engine.

A recommendation request is a trigger for retrieving a product recommendation from a recommendation engine, usually sent upon a specific action by an actor or a system (e.g., viewing a product's details).

As opposed to the recommendation event, the recommendation request asks for information from the recommendation engine.

Generally, refers to (administrative) units such as sovereign states; subnational units such as provinces, counties, townships, territories, etc., and multinational groupings like the EU, as well as informally defined regions such as the Middle East.

For e-commerce purposes, there can be multiple regions with different granularity for different purposes, like shipping regions (inside Germany, EU-wide, non-EU) or content regions (South America, ...)

For several purposes (e.g., shipping), locations may be mapped to regions.

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

1. Sales:
   A release is a public distribution of a product, solution or extension as well as support materials intended to be delivered to customers.
2. Software Engineering:
   A release is an assembly (or, with pre-6WR software, a build) that has passed a defined approval process (including, among others, QA and PA) and that is ready for internal or public distribution.

The Release Area is the central file server for all software releases produced by Intershop with defined version in different release states (see RA help). Depending on user rights there are different views available (public view, developer view, QA view and support view) which show a subset of all artifacts filtered by their status.

Beginning with the continuous integration support, Intershop replaces the Release Area with an artifact repository.

Generally, release notes are a type of document that accompanies the public distribution (release) of a product, solution or extension, summarizing important news, changes, etc.

At Intershop, this information is published online as product datasheets.

Depending on the context, "request" may refer to different concept:

1. Extended B2B Module/Intershop Commerce Management B2X:
   With the Extended B2B Module or the B2X edition of Intershop Commerce Management, request refers to the mechanism used to query one or more merchants about specific products, which results in a quote.
   
2. Intershop Contact Center:
   In the Intershop Contact Center, the request refers to a single issue cycle within a contact session. A request has a reason, may involve an action, and has a resolution.
3. System Administrator:
   Any message sent from a client to a server, e.g., in Intershop 7, from a storefront session via the Web Adapter to the Intershop Application Server (see request log).

The request log is the log file written by the Web Adapter protocolling the incoming requests to Enfinity Suite 6/Intershop 7/Intershop Commerce Management as well as requests issued by the Web Adapter itself.

The logged information can be used for analysis by Intershop Commerce Insight.

In the B2X edition of Intershop Commerce Management, requisition refers to a submitted shopping cart, which is subject to an approval process and is not yet turned into an order.

In Enfinity Suite 6 procurement and B2B models, requisition referred to the user interface used to collect products before purchase, which could be subject to an approval.

In Enfinity Suite 6 procurement and B2B models, a definable procedure for approving requisitions (approval), i.e., the standard path requisitions pass through before being sent to suppliers as purchase orders.

With the Extended B2B Module of Intershop 7 and the B2X edition of Intershop Commerce Management, it is called order approval.

requisition model that can be stored by buyers in Enfinity Suite 6's procurement channel and used for recurring orders.

With the Extended B2B Module of Intershop 7 and the B2X edition of Intershop Commerce Management, it is called order template.

The return management includes the steps that have to be performed to handle the return of products.

The return can be triggered in different ways

• return by customer
  • return of ordered and already delivered products
• return by carrier
  • package could not be delivered since the address or the consumer could not be found
  • acceptance of delivery has been refused by the consumer

Normally the fulfillment center is responsible for handling the returns of the delivered products. This includes the handling of

• returns by customer or carrier
• check of return reason
• quality check of returned products
• creation of return note
• repacking
• calculation of credit note
• pay refund to the customer (optional)

RFQ is a standard business process whose purpose is to invite suppliers into a bidding process to bid on specific products or services. It involves more than the price per item, information like payment terms, quality level per item or contract length are possible to be requested during the bidding process.

In Enfinity Suite 6 procurement and B2B models, RFQ is a mechanism used to query one or more suppliers about specific products (with the Extended B2B Module of Intershop 7 or the B2X edition of Intershop Commerce Management, see request).

A build type in the Intershop 7 context that is a reduced version of the smoke build. It skips some expensive build steps (such as JavaDoc generation, database dump creation). This build is therefore much faster than a smoke build and can be performed on a regular base, like every 2 hours. This build type is used as a kind of automated integration build that sends error tickets whenever the overall source code does not compile any more.

Beginning with the continuous integration support, this build type has become obsolete (see build process).