Docs
Search
Search
Help & Feedback
Get Started
Functionality
Learning
Extension
Dev Tooling
APIs
Releases
Extend Fluent Store
Some how-to guides for extending Fluent Store
Image capture of Returned Goods during Return
How-to Guide
Step-by-step guides to achieve a specific scenario or setup.
This article gives System Integrator (SI) Partners and Businesses a high-level idea of where new features can be built on top of the OMS reference solution to support the customer's requirement within Fluent OMS.
This idea/solution will provide a new feature where the Store User can take a photo of the returning item and attach it as part of the returnOrder entity.
The source code will not be provided in this article.
Build a Webhooks Monitoring Dashboard
How-to Guide
Step-by-step guides to achieve a specific scenario or setup.
For Frontend Configurators (JSON) of the
Fluent OMX UX Framework
with access to a
small custom component
Enable a
visual Webhooks Monitoring Dashboard
in the Fluent OMS (or any other Fluent web app)
How to add a new page to the Insights section
How to query the Event API for Webhook Audit Events
How to use the
`devrel.provider.rest`
component to display information from the Fluent REST APIs using standard the standard UX Component Library
Access specific attributes by name (even when they contain spaces!)
How to conditionally color code a specific table column
How to display a details drawer from a list
How to display contextual Webhook information on the Order Details screen
Validate Customer ID at Pickup
How-to Guide
Step-by-step guides to achieve a specific scenario or setup.
This article gives System Integrator (SI) Partners and Businesses a high-level idea of where new features can be built on top of the OMS reference solution to support the customer's requirement within Fluent OMS.
This idea/solution will provide an extended new feature where the Store User can validate the Customer ID during the Customer Collection Process.
New custom UI components and rules are needed to capture the user input and confirm the selected articles in the UI user Action screen. Then, the store/business can track and trace the proof of the shopper's collection.
Due to security reasons, the shopper's sensitive personal information should not be stored within Fluent OMS. Therefore, the proof of collection should be stored at a third-party storage.
Enable entering of Rejection Reason Code during pick confirm in Fluent Store
How-to Guide
Step-by-step guides to achieve a specific scenario or setup.
This article gives System Integrator (SI) Partners and Businesses a high-level idea of where new features can be built on top of the OMS reference solution to support the customer's requirement within Fluent OMS.
This idea/solution will provide a new feature where the Store User can enter the rejection reason code during the Pick Confirm Process.
This feature allows specifying the rejection reason for fulfillment on the picking step of wave processing. The user can select the rejection reason code when the picked item list is confirmed as the first step of wave processing.
Fluent Store Dashboard: new dashboard tile based on fulfilment expiry time
How-to Guide
Step-by-step guides to achieve a specific scenario or setup.
A guide to extend Fluent STORE UI capabilities to allow the store users to have a better visibility on the fulfilments by expiry time.
The use case where the store staff would like to see number of fulfilments for the next 2 hours so that they can plan their pick and pack process accordingly.
One of the solutions is by using OOTB component and manifest to display the fulfilments number based on the expiry time. Hence, there are no custom rules nor custom component is required for this solution.
Here are the steps to archive the outcome:
Create a new screen in fluent Store
Create dashboard tiles
Enable Home Delivery shipping label in Dispatch stage of Fluent STORE
How-to Guide
Step-by-step guides to achieve a specific scenario or setup.
Typically, the HD shipping label is generated by the nominated carrier company or carrier aggregator. The label URL is then stored in OMS for printing.
This guide will take you through the setup to allow the store users to print the shipping label from Fluent STORE.
Enable location store users to update store hours
How-to Guide
Step-by-step guides to achieve a specific scenario or setup.
Each location has an opening hours setup that can be used for store activities. One activity could be during the fulfillment allocation phase, where the fulfillment expiry time for a store is calculated, giving store staff sufficient time to process the order before it expires.
Since opening hours can change week by week, we have created this guide to showcase how you can enable Store Managers to make these changes directly in the Fluent Store Web App.