Documentation Portal

globale.client.js.domain = 'https://www2.bglobale.com' 
globale.client.js.path = '/scripts/merchants/globale.merchant.client.js'

globale.enabled = true
globale.enabled.initial.product.call = false

globale.cookie.name = 'GlobalE_Data'
globale.cookie.expiration = '259200'

globale.api.call.timeout = '6000'

globale.api.connect.timeout = '1000' 
globale.api.call.max.connections.host = '100'
globale.api.call.max.total.connections = '200'

globale.send.products.batch.size = '10'

globale.default.country.code = 'GB'

globale.store.multilanguage = 'true'

globale.store.english = 'en'

The following Global‑e scripts are installed.

To enable fixed prices per country and currency:

To enable fixed prices per currency (only):

10% off all products excluding Global-e operated countries

10EUR off 100EUR minimum spent on all products in Germany

Free Shipping Coupon

Care should be taken when creating a promotion where conversions are used.

Actions with fixed discounts will not be applied if neither store’s default currency - nor a promotion’s action currency matches a customer session currency.

For example, a discount is not be applied in the following cases:

The globaleaddon adds the Global‑e Country Selector and the Managed Checkout capability to the SAP Hybris Accelerator-based Storefront.

The globaleaddon includes:

globalecore places REST API calls to the Global‑e API. globalecore uses custom-built caching to speed up the retrieval of the Global‑e data sets from the database.

The Global‑e implementation uses the Spring RestTemplate to communicate with the Global‑e API.

The RestTemplate is the central Spring class for client-side HTTP access.

Conceptually, it is like the JdbcTemplate, JmsTemplate, and the various other templates found within the Spring Framework.

This means, for instance, that the RestTemplate is thread-safe once constructed, and that you can use callbacks to customize its operations.

By default, the Global‑e Add-on includes a configuration for API connection timeouts. Each timeout represents the maximum time to wait for a Global‑e API response. If there is no response by the expiration time, the call fails.

Here are some examples of key values that you can see in your local. Properties:

Fixed prices are used to define a Recommended Retail Price (RRP) per country in the local currency. Fixed prices do not change regardless of Global‑e coefficients, rounding rules, or FX rates.

The fixed price selection process can be configured:

(1) By country and currency – or –

(2) By currency and it is active for all countries that support this feature.

To enable or disable fixed prices based on country, use the Global-e API.

To activate the fallback mechanism (2),

Add the property 'globale.fixed.price.fallback.to.currency.match.enabled=true'.

The fixed price algorithm determines if a PriceRow contains a fixed price for the country and currency (1):

The Global‑e Add-on extends the ProductPriceValueProvider and alias with the Global‑e price value provider: GlobaleProductPriceValueProvider.

The price value provider sets the session parameters to ensure that the Global-e add-on has the correct session parameters for price conversion when it creates the price information.

Global‑e sends notifications to the globaleendpoint module. Currently, four notifications are sent via JSON and marshalledmarshalled by the Jackson JSON Processor. POJOs corresponding to Global‑e API classes are annotated with Jackson Core (Data-Binding) annotations to facilitate proper mapping.

The globalefacades module provides simplified interfaces to the service layers.

Overridden Facades include:

The globalepromotions extension provides support for the SAP Hybris promotion engine.

This extension adds the following conditions:

In addition, Global‑e has overridden and replaced the OOTB SAP Hybris currency conversion logic with the Global‑e conversion rates taken from the Global‑e API. This is relevant to any action applying percentage or absolute value discounts.

Example:

In this case, if we assume Global‑e API provides 1.285 as a conversion coefficient, the condition threshold will be converted as 10 GBP = 12.85 CHF, which is under the cart value of 15 CHF, and the promotion is applied.

How it works:

See Known Limitations for information about processes that may trigger an unexpected behaviour (during conversion).

globalebackoffice is for Backoffice changes which you can configure in: globalebackoffice-backoffice-config.xml.

The Global‑e add-on also overrides the CurrencyTypeRenderer with the GlobaleCurrencyTypeRenderer to support sub-types of Order Entry.

When a request is made to the integration service, the following steps take place:

Global‑e provides flow diagrams and details about which endpoints/objects to cache. A snippet of front-end activities is provided as an example below.

Example of the recommended Global‑e cache behaviour flow:

All API method calls may optionally return the following headers:

These headers indicate the recommended client-side caching interval for the data returned by the respective call unless otherwise stated in a specific class or method definition.

There is functionality to parse those headers into a usable object.

Global‑e relies on the SAP Hybris persistence for caching API data. Global‑e creates new cache types in SAP Hybris with the common ancestor GlobaleBaseCache to store the cache. Cache age is controlled by Global‑e.

During the customer checkout with Global‑e-enabled countries, the customer is redirected to the Global‑e iframe to complete their order.

Once Global‑e completes the checkout process with the customer, Global‑e creates an order and notifies SCC via the module globaleendpoint. This order includes delivery details for the local Global‑e hub, along with the customer’s billing address and payment information.

The JSON file is parsed and converted to a MerchantOrder, which is then unmarshalled again and saved as a string of JSON.

To avoid information loss, if there are missing mappings in the MerchantOrder object, the Global-e add-on makes sure to log any requests in full coming into the web module globaleendpoint using the filter: globaleRequestLogger.

The Global‑e flow shows that the custom price factory takes control of creating price information. This allows the product data object to be populated with price rows that are converted and rounded to display on the front end.

The recalculation of a cart forces the price information to go through the same process (price rows converted and rounded). Tax information is managed by Global-e.

The Global‑e cache takes precedence over making a Global‑e API call. Below is a list of the cache entities managed by the Global‑e add-on:

Rounding rules, country coefficients, and currency rates are used when converting prices.

Non-Global‑e flow is OOTB behaviour apart from one aspect, in the case SCC tries to use its currency conversion logic. This happens in the following circumstances:

In the above example, we will fall back to the standard Global‑e conversion flow over the OOTB SCC conversion logic.

Global‑e always displays:

Global‑e injects JavaScript and CSS into the website to provide functionality such as the welcome popup, country switcher, checkout form, and more.

In the backend, the GlobaleCookieToSessionFilter custom filter sets up the session based on the customer's chosen country and currency. This is taken directly from the Global‑e cookie: GlobalE_Data.

If the country and currency or currency cannot be found, Global‑e uses the customer’s location by IP and converts the IP into a country, currency, and culture.

If the Global‑e add-on cannot find the location of the IP (e.g., when testing locally), the country, currency, and culture session parameters are set to the default value:

When a customer uses the popup to change their country and currency: