JDOMS Guide
Fluent is the 3rd party provider behind the JDOMS integration, which provides real-time stock levels to Aurora and it's Store Locator.
This article describes how to configure the JDOMS Integration in Aurora and what doing so can achieve. It also outlines what you need too be aware of to ensure that the service works smoothly on the Aurora Front-end.
Introduction
When enabled, the JDOMS integration permits the checking of a products stock from the 3rd party JDOMS platform. When a product stock check is triggered, for example when adding a product to the basket, Aurora will send a request to the JD OMS API, and based on that response, the behaviour of Aurora will be determined.
This article explains how this third party integration can be configured.
Switching Stock Check Provider
To switch stock checks to use the JDOMS platform, visit the Store > Settings > Aurora > Products section. Here you can change the Stock Check Provider to Aurora or JDOMS, which will change the stock check provider respectively.
- Aurora will check Aurora internally for product stock.
- JDOMS will check the JDOMS (Fluent) system for stock values.
When is the JDOMS used to check the stock?
The JDOMS Stock Integration does not replace Auroras own internal stock management completely, so you will be required to provide stock feeds to Aurora (in addition to using this integration) in order to allow it to manage your Product Listings and Details Pages (more detail found below).
The JDOMS is not always used; it is only used when purchasing or shipping becomes involved in the user's journey. Please see the breakdown below that broadly describes when Aurora checks stock with the JDOMS and when it does so with it own internal database.
| Aurora's Internal Stock Levels | JDOMS' Stock Levels |
|---|---|
| Product Listing/Category Page (PLP) Product Details Page (PDP) | Product Stock Checker Store Locator (for 'collect from store' shipping options) Basket Checkout Order Placement |
As a rule of thumb, it might be said that everything up to the Product details page is driven by Aurora and thereafter it is driven by the JDOMS.
JDOMS Fall-back Procedure(s)
For more detail regarding the JDOMS's fall-back processes, please read the JDOMS Fall-back Procedure(s) Support Article.
Backend Settings
This section explains the options when configuring the JDOMS integration. Find these settings in the Aurora Back-end under Store > Settings > Feeds > JDOMS.
| Setting | Description |
|---|---|
| Enabled? | When the Enabled? tick-box is not checked, the integration will be disabled throughout Aurora. This will disable all associated CLI processes, preventing them from uploading or downloading changes of any sort. |
| Live? | If the integration is enabled, then ticking this box will have Aurora use the 'Live' settings described below. Otherwise, the 'Test' equivalent of all the below settings will be used. |
| Live/Test Endpoint | Live/Test endpoint is the url address of the service which is used for the stock check. Example : https://jduk.api.fluentretail.com |
| Live/Test Username | Live/Test Username provided by Fluent, when the JDOMS integration is Enabled. |
| Live/Test Password | Live/Test Password provided by Fluent, when the JDOMS integration is Enabled. |
| Live/Test Client Secret | Live/Test Client secret provided by Fluent, when the JDOMS integration is Enabled. |
| Live/Test Client ID | Live/Test Client ID provided by Fluent, when the JDOMS integration is Enabled. |
| Live/Test Retailer ID | Live/Test Retailer ID provided by Fluent, when the JDOMS integration is Enabled. |
| Log Requests? | When this is ticked, all requests sent to and responses received from the JDOMS API will be logged in the Aurora API Integration Log. |
| Enable API Fallback? | When this is ticked, if requests sent to the JDOMS API do not respond in full to Aurora within the timeouts defined (see bellow), then the fallback procedure will be deployed. |
| Request Timeout (Urgent) | This timeout controls how long Aurora will wait for a complete response from the JDOMS API during: The checkout process. Use of the Store Locator. When this is not set (or set to 0/Zero), this value will be defaulted to 2 seconds by Aurora. |
| Request Timeout (Non-urgent) | This timeout controls how long Aurora will wait for a complete response from the JDOMS API on the Basket and while navigating Aurora in general. When this is not set (or set to 0/Zero), this value will be defaulted to 4 seconds by Aurora. |
| Request Cache Time | This setting controls for how long Aurora will cache the responses for identical requests sent to the JDOMS API (for X seconds) to help reduce the issues caused by excess traffic to this API. Set this field to 0 to remove the caching completely. |
Updated over 2 years ago