Extend Content

• Address Validation: Ensure that the address entered by the user is valid and correctly formatted to avoid shipping issues.
• Default Address: Allow customers to set a default address for a quicker checkout process.
• Edit Capability: Provide an option for users to edit customer address details in case of errors or changes.
• User Experience: Design the add and edit address process to be user-friendly and accessible, with clear instructions and error messages.

• It’s possible to add a new state to an existing workflow by adding a new status to the

  `Statuses array`

  of the workflow JSON.
• Create a simple User Action to allow the user to change the status.

• Understanding the Market: Recognizing the importance of Cash on Delivery (CoD) in markets like India, where it is a preferred payment method.
• Global Adaptability: The workflow's design serves a global audience, providing a template that can be customised for regions where upfront payment is not the norm.
• Seamless Integration: Ensuring the CoD process is smoothly incorporated into the existing order journey to enhance customer experience.
• Operational Efficiency: Streamlining the CoD transaction to ensure quick and secure payment collection at the point of delivery.

• Extend the Order Module schema
• Modify the Rule for Return Order creation and the Order Workflow Return Order Ruleset
• Update the Order Management Manifest

• Comprehensive Data Entry: Ensure that all necessary customer information is captured accurately to create a complete profile. This includes personal details, contact information, and any specific requirements or preferences.
• Validation and Verification: Implement validation checks to prevent errors during the data entry process. Verify that mandatory fields are not left blank.
• User Experience: Design the customer creation process to be user-friendly. Provide clear instructions and feedback during the process to enhance the user's experience and minimize the likelihood of errors.

• The 'Create Order' wizard streamlines the order creation process by guiding users through each step, reducing the chances of errors, and ensuring all necessary information is captured.
• It provides a user-friendly interface that simplifies complex order configurations, making it accessible for users with varying levels of technical expertise.
• The wizard includes validation checks at each step, ensuring that all entered data is accurate and complete before proceeding to the next step.

• This component simplifies the addition of networks to locations by providing an easy to use selector of available networks
• The basic principles can be used in other scenarios where complex fields and values may be required

• Data Modification: Ensure that users can modify customer data, including the ability to correct typos in existing information.
• Error Handling: Implement error handling procedures in case the edit fails or invalid data is submitted.
• User Experience: Aim for a seamless and intuitive editing process to minimize the risk of user errors.

• 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.

• Predefined Filters: Provide a way to access commonly used search parameters with a single click, enhancing the user experience.
• User Efficiency: Predefined filters are designed to save time and streamline workflows.
• Customization: Users may have the ability to create and save their own filters for recurrent use (via manual Manifest changing).
• Consistency: Predefined filters ensure that the same criteria are used for searching, leading to consistent results.
• Learning Curve: New users can quickly become proficient in finding the information they need due to the intuitive nature of predefined filters.
• Integration: These features should seamlessly integrate with the user interface for maximum effectiveness.

• Eligibility & Conditions – Clearly define the conditions under which an item can be exchanged, such as time limits, product conditions, and receipt requirements.
• Exchange Process – Outline the step-by-step process, including how customers initiate an exchange, return shipping details, and replacement timelines.
• Inventory & Availability – Ensure the desired replacement item is in stock and provide alternatives if it's unavailable.
• Refund vs. Exchange Policy – Specify whether price differences will be refunded or charged.
• Customer Communication – Keep customers informed at every stage with order tracking, confirmation emails, and support availability.

• 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

This page covers the various Fluent CLI commands which can be used to configure / install Fulfilment Options module

• 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.

• step-by-step guide on how to install modules into your OMS sandbox

• 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 customer service to reroute an existing

  `fulfilment`

  to a specific location that can fulfill the order.

• 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 update the Store inventory through the UI to ensure the OMS has the most accurate product inventory.
• New custom UI component and rules to capture the user input in the UI user Action screen. Then, the backend will create a new Inventory Quantity entity and update the Inventory Position and the downstream workflow.

• This is the use case where users can look up OMS orders using order ID.
• Typically, the graphQL query orderById will be used to look up an order by ID. However, they can only look up one order at a time and with no wildcard search.
• This article provides an alternative approach that allows users to search for orders by ID or even with a wildcard. 
•  The approach is to utilise the recent release of the ref2 field in order entity.

• This is an enhanced feature that allows users (e.g., Customer Service Representatives) to look up customer orders by using either the customer's email address or phone number. 
• This feature can be achieved by configuration in the setting manifest without any custom components nor custom rules.
• This article will provide the following:
  • code snippet of the search Order by Customer phone/email manifest
  • Language settings
  • Display the page on the left panel menu by adding a code snippet in the setting:

    `fc.mystique.manifest.oms`

     

Following the completion of this section readers should gain an understanding of the different modules and the segregation between them. They should understand some of the key features of the modules and how they could be used to benefit both the customer and the company providing products and services.

• Availability module - provides detailed and accurate stock information & order fulfillment options
• Order Orchestration module - allows retailers to track all of the statuses of an order through its lifecycle
• Inventory module - allows retailers to get a unified version of inventory across all locations and inventory management systems
• Store module -  provides order management and fulfillment capabilities in-store by guiding store colleagues through the day-to-day processes
• Service module - provides all the capabilities to enable flexible customer support

• Quick Search Functionality: Enables users to find information rapidly by typing keywords or phrases.
• User Efficiency: Quick search is designed to save time and streamline workflows.
• Learning Curve: New users can quickly become proficient in finding the information they need due to the intuitive nature of quick search.
• Integration: These features should seamlessly integrate with the user interface for maximum effectiveness.

The Upsert Location Module contains the workflow and supporting rules to update or create (aka upsert) locations. This page covers the steps to configure and install the Upsert Location Module.

• 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.