The Commerce Modeler

The Orckestra Commerce Cloud Commerce Modeler is a hierarchical structure representing the desired commerce landscape of your business. This landscape can span many targeted markets each with their own unique offering. Some examples of a market might include brand, a geographical region, a virtual marketplace or a physical location. A market is represented in the Commerce Modeler using a scope.

Scopes are entities that you can use to organize and search data and settings for a given market. They may contain data such as a product catalog, product prices or a marketing campaign, as well as links to customers and orders that are related to that scope. This scoped data can be organized and configured differently from scope to scope depending on the needs of the market. For example, each scope can select which languages it supports.

There are four types of scopes: the Global scope, Sales scopes, Dependent scopes, and Virtual scopes. The Global scope is always at the root of the Commerce Modeler and there’s always only one such scope. The Global scope contains main configurations such as the languages and currency used by your business. Below the Global scope reside one or more Sales scopes. Sales scope can have one level of dependent scopes. Virtual scopes may be used to group together related sales or dependent scopes.

•

The Global Scope sits at the root of the hierarchy. The Global scope contains the complete product catalog for a Commerce Cloud client. The scope also provides an aggregated view of the system including customer and order-related information.

•

A Sales scope represents one of many possible markets targeted within the platform. Different sales scopes can be used to model brands, geographical regions, a physical location or any other unique selling market. Sales scopes can be differentiated by varying product offerings, prices and currencies, supported languages, marketing promotions and other related settings such as payment and shipping options.

•

A Dependent scope represents a more customized offering for a very specific market. Different dependent scopes can be used to model sub-divisions of a geographical region or a physical store. A dependent scope shares most of its offering with that of its parent’ sales scope with the exception of product pricing and merchandising relationships. These exceptions can be modified specifically for this targeted market. Settings such as payment and shipping options may optionally be configured for a dependent scope.

•

A Virtual scope is used to group and organize related sales or dependent scopes. Virtual scopes are primarily used to facilitate navigation between scopes when abundant. Virtual scopes are not operational and don’t have an associated product catalog or order data, for example.

REFERENCES

•

Using the Commerce Modeler