Term | Description | Documentation |
---|---|---|
quantity advice | When using Intershop Commerce Advisor in B2B scenarios, the quantity advice tells how many units (per size, if applicable) of an individual product are 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. | |
query | In Enfinity Suite 6, Intershop 7 and Intershop Commerce Management, the term query refers to a specific type of XML files that allow to dynamically construct SQL queries and to execute them in the database. The database response can be mapped to various Java objects, like primitives or persistent objects. | Overview - Query |
questionnaire | in RFQ templates, a form to be filled by buyers and suppliers to discuss details of the requested product or contract | |
quick access button | navigation element in the Enfinity Suite 6 back office that provide immediate access to certain functionality | |
quick access link | Links in the management tools of Intershop 7/Intershop Commerce Management that provide immediate access to certain functionality | |
quote | 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. | |
ranking | A ranking is a relationship between a set of items such that, for any two items, the first is either "ranked higher than", "ranked lower than" or "ranked equal to" the second. With rankings, the order of items is determined by a (computational) process like product ratings or the selling statistics. | |
RAPI | The remote API (RAPI) is the old API for providing access to an Intershop Commerce Management/Intershop 7/Enfinity Suite 6 application from a remote system. The RAPI consists of Java interfaces and classes, which can be generated from EDL models. | |
recommendation | 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:
Dynamic recommendations can be created by a recommendation engine provided by a business partner. | Overview - Recommendation |
recommendation engine | 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. | Overview - Recommendation |
recommendation event | 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. | |
recommendation request | 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. | |
recurring budget | recurring budgets are valid for an unlimited time period and can be calculated on a weekly, monthly, or yearly basis | |
recurring requisition | In Enfinity Suite 6 procurement and B2B models, a mechanism for re-submitting requisitions manually, automatically at regular intervals, or automatically at pre-defined dates and times | |
recycle bin | A container that temporarily keeps products after they have been deleted from a repository. Products kept in the recycle bin can be completely restored. | |
refund | A refund is a compensation paid to a customer for over-invoicing or for returned goods. It belongs to a credit note but not every credit note ends up in a refund. | |
region | 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. | |
regression test | Testing of a previously tested program following modification to ensure that defects have not been introduced or uncovered in unchanged areas of the software, as a result of the changes made. It is performed when the software or its environment is changed. | |
release | Depending on the context, "release" may refer to different concepts:
| |
release area | 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. | |
release build | In the context of continuous integration, a release build refers to a build process that compiles all system components that belong to an assembly. The produced output is supposed to be released after the corresponding nightly build has passed successfully all integration and test stages in the artifact repository. | |
release note | In Intershop's software engineering process, a release note is a document type that informs about completing the development of a single feature. | |
release notes | 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. | |
remove | to move something away from access or from a given context, but keep it in existence | |
replacement | a product link offering a similar product, used when the requested product is currently out of stock | |
replication | Short for data replication. | Overview - Data Replication |
replication group | in data replication, a means to identify the data to be replicated, with each replication group referring to a certain content domain | Overview - Data Replication |
replication task | In data replication, a means to manage the data to be replicated. | Overview - Data Replication |
reply | reaction to a post in a discussion forum | |
reporting | a data exploration module in Enfinity Suite 6 for monitoring sales activities inside channels, can produce reports on products and orders (not part of Enfinity Suite 6 but can be included using the reporting framework) | |
repository | (virtual) container for storing business objects | |
request | Depending on the context, "request" may refer to different concept:
| |
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. | |
requirement | A requirement is a documented need, want or expectation of the stakeholders of what a particular product or service should be or perform. | |
requirement specification | A document that specifies the requirements for a system or component. Typically included are functional requirements and non-functional requirements, interface requirements, design requirements and development standards. | |
requisition | 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. | |
requisition 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 template | 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. | |
requisition workflow | definable procedure for creating requisitions | |
reseller | A reseller is a trader or dealer, who sales products in the retail sector, and provides the products with additives. | |
resolution | The resolution is the documented result of whether and how a customer's request is completed/fulfilled via the Intershop Contact Center. | |
responsive design | Responsive design, or responsive web design (RWD), is an approach to web design in which a site is crafted to provide an optimal viewing experience - easy reading and navigation with a minimum of resizing and scrolling - across a wide range of devices (from desktop computer monitors to mobile phones). Usually Cascading Style Sheets (CSS) are used to realize this technique. | |
Responsive Starter Store | Intershop Commerce Management includes blueprint web shops for B2C and B2B business models ("Responsive Starter Store"), which enable the fast and cost-effective creation of customer-oriented shopping environments. These demo stores use responsive web design for optimum display on all devices as well as established web technologies, such as the Bootstrap front-end framework. | Overview - Responsive Starter Store |
REST framework | In Intershop 7/Intershop Commerce Management, the REST framework serves as the foundation for RESTful web services APIs. The REST framework acts as an additional access layer on top of the application layer. Specific APIs (back office, storefront, integration services, customer-specific applications, etc.) can be defined on top of this REST layer. | Overview - REST Web Service Framework |
retail set | a group of products offered together with an own product ID but without an overall price, constituents are sold only separately | |
retailer | a business that sells products and services to customers | |
return | A return is the act of giving or sending back ordered products. | |
return management | 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
Normally the fulfillment center is responsible for handling the returns of the delivered products. This includes the handling of
| |
return note | A return note is a document that contains the list of products that are eligible for return by the customer. | |
return sticker | A return sticker is a sticker with the merchant's return address. It can be used by customers for returns to avoid that a wrong address is used and to reduce the shipping costs for the merchant. | |
reverse auction | A buyer-initiated auction in which a buyer invites bids from multiple suppliers. Generally, the price decreases as suppliers compete for the buyer's business with the lowest bid considered the winner. | |
review | in online shops based on Enfinity Suite 6/Intershop 7/Intershop Commerce Management, a written comment on products as part of product ratings submitted by customers | |
RFQ | 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). | |
RFQ template | in sourcing, RFQ model that defines product and contract questionnaires | |
roadmap | In the software engineering context, a roadmap displays the planned milestones and versions of a product, solution or extension. It is a compilation of the feature wishes that Intershop will address in the future. It is derived from the prioritized and sorted feature requests and is always preliminary and subject to change. | |
role | A specific set of access privileges assigned to users that control the tasks they are allowed to perform in the system. | |
rolling build | 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). | |
root category | top-level category, usually referred to as catalog | |
root edition | in Enfinity Suite 6's CMC, an edition that serves as a master for new editions | |
rule engine | The Intershop 7/Intershop Commerce Management rule engine, which is based on Drools, provides an abstract way of executing rules on business objects (like promotions, shipping conditions, etc.). Users or developers can create, load, store, and remove rules, as well as manage rules and execute them without the need to know any specific rule engine language as long as they use the interfaces provided by the rule engine implementation. In addition, the rule engine serves a framework that allows for integrating another rule engine. | Overview - Rule Engine |
run-time component | Run-time component refers to the graph of (interrelated) Java objects instantiated based on the component framework of Intershop 7/Intershop Commerce Management. |
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.