Fluent Order Management Reviews

Fluent Order Management's main use case is that the omnichannel capabilities are exceptionally good, and the technological aspect of it, using GraphQL and mutations, makes it an ideal solution.

A specific example of how I use those omnichannel capabilities or the GraphQL features in my day-to-day work is that it makes it very seamless when we are trying to build integrations with other third-party systems. I don't have to be worried about changing anything from an API aspect internally. The API provides attributes in the system itself, and we can seamlessly integrate with your e-commerce channel, whether it's Shopify, SFCC, or marketplaces such as Amazon or Mirakl. All of these capabilities are very great, and we can integrate with multiple systems seamlessly. Fluent provides the flexibility of using sourcing engines, and integrating with WM systems downstream also becomes easier. Having the ability to integrate with all of these systems is what makes Fluent Order Management prominent. I believe that the future of the order management system from a technology aspect has to be GraphQL; it's much simpler, the schema is well-defined, and if we want to use additional attributes, we can use them. It's not the old traditional Java where the columns have to be created and a data type has to be declared and stored and all of that, so I think that's very flexible and seamless. The entire webhook concept is great as well; it does not cause performance issues.

In terms of how Fluent Order Management fits into my workflow, when you compare all the order management systems out there in the market today, whether it's Manhattan, Sterling, or any of the upcoming systems that are available, some of the points that we are looking at or trying to be mindful of are the capabilities that it has. Can we easily update the UI? Can we add buttons? Can we introduce more integrations? The omnichannel capabilities, the UI accessibility, all of these are things that should be considered, and I do think that Fluent Order Management provides them all, which is why it makes it a leading platform.

Regarding the best features Fluent Order Management offers, I think it's all of these options because some platforms are very difficult to customize, but Fluent Order Management allows the user to build the customer's roadmap. The capabilities that I've mentioned—the UI, the GraphQL, the integrations, the technology—are commendable. The out-of-the-box product features that are provided in the modules are also great for a medium retailer or for a small use case retailer to start up with, and you can also make this more enterprise-driven as needed. I think the ability to provide solutions for small retailers as well as medium and large-scale retailers, having all of these capabilities, is brilliant.

I do want to commend the Fluent Order Management engineering team regarding the features and the improvements that the system has been making since they have launched. Having the ability to retain just one order with different types—home delivery, click and collect, and same-day delivery as part of the same order—is very rare, but Fluent Order Management is working towards a mission where they want to make it seamless and easy and accessible to have all the types of use cases within the platform itself. I think it's very important for organizations to understand and realize the capabilities that the system can do out of the box, and if your business case requires you to add things or enhance them, you can add those too. They're already doing a great job, and they just have to be completely transparent with what the goals are, share the proper use cases they're seeing on a day-to-day basis, and make things seamless.

Fluent Order Management has impacted my organization positively because being a cloud-based SaaS application, it is able to support high-volume orders. For example, L'Oréal has 36 to 38 brands that it is able to consume data from such high volume. It's ensuring that the application doesn't go down and maintaining zero downtime abilities. Having multiple retailers is part of what adds value. We are now implementing the store modules where the warehouse operations are using it for picking and packing as well. All of these capabilities are a win and a plus, and I think this is improving the operational abilities in the system and in the organization itself. Fluent Order Management having the ability to not just provide order management solutions but also provide store-related solutions for picking, packing, and making those points seamless is a win as well. The ability to easily update the UI per the user's requirement is what is key.

Unfortunately, data regarding the positive impact on orders processed per day, time saved, or reduced downtime cannot be shared as it is internal information.

I do not know of any areas Fluent Order Management can improve. As and when we are facing issues, the team is accessible to help us, and they are always available to understand our pain points and how it impacts the business. When we face issues or the platform is not working to its best potential, having the Fluent Order Management support team and the expert services is a great thing that we look to. They're very approachable, and we always have these engagements with them where they guide us or take these use cases back to the engineering team to refine modules.

Fluent Order Management is pretty easy, and it is something that people can easily get onboarded onto, and there's nothing as an improvement to be shared at the moment.

The reason why I'm saying 8 is because given that Fluent Order Management is an order management system that is still growing and still making improvements vastly, I would like to see how we can introduce AI into the order management system. Do we have capabilities of introducing a chatbot or AI on Fluent Order Management? I think that part of leveraging AI is a bit pending, and I'm deducting one from a technical aspect regarding some of the modules that I'm not aware of, just being skeptical on that front.

Regarding Fluent Order Management's AI capabilities, I have personally not had any experience with the AI capabilities that Fluent Order Management has, and maybe that is something for me to explore. I do know that Fluent Order Management has introduced some AI capabilities from a development aspect, but because I'm not a developer, I do not have those insights.

I have been using Fluent Order Management for four and a half years now.

In terms of how stable Fluent Order Management is, the application is up 98% to 99% of the time, but there are some edge use cases where, for example, during Black Fridays when you're getting thousands of orders into the system, it is possible that sometimes the orders are stuck or they do not even get into the orchestration because there are some technical Fluent Order Management issues that happen. The API was not triggered, or for some reason something went down, or while scaling up, something happens in the back end. At least 98% or 99% of the system is all the time up and available. We have those 1% edge use cases when the workflow is not triggered or the API does not work as expected or the tokens expire, and during re-authentication, the API could fail. These are not big issues.

I think the scalability of Fluent Order Management is very dynamic in nature because during peak times, Fluent Order Management ensures that the cloud capabilities are at their maximum. When there is an increase in volume and demands, the load balancer actually expands and has multiple instances or servers running in the back end so that there are no delays or issues in the system. I do not doubt the scalability in Fluent Order Management. Depending on the volumes and the size, the system proactively scales up and has more servers running in the back end even before the customer can reach out. We usually get a notification from Fluent Order Management notifying all the partners how they plan on expanding the servers and the load balancers that they have to ensure things such as Black Friday sales or any of these other sales that happen become seamless. This is a very positive response.

Regarding customer support for Fluent Order Management, the customer support is very responsive. They have a dedicated team who is proactive in nature, and depending on the severity of the case that is raised with them, they ensure that we get the alerts and the questions prompted. I would rate them around 8.

My advice to others looking into using Fluent Order Management is to share all the use cases with Fluent Order Management to see if it has all the capabilities that you are looking for. My recommendation is to go with a vision and dream big. If you're starting out as a medium retailer today and your vision is to grow into one of the large players, be transparent about this vision. Share your current use cases, irrespective of the complexities that you have today, and share your actual use cases and pain points that you are facing from an operational standpoint. Try to understand how introducing Fluent Order Management would actually ease that pain point. I think it's very important to understand the use cases you are trying to achieve. You have to have realistic timelines to ensure you actually meet those use cases. Continuously working with the product team and with your engineering team, ensuring all the use cases are captured, is what is going to lead you to success. Be vocal about your needs, think about how it is going to ease the operations for your organization, consider all the complex and the smallest use cases that can happen, and be open to ideas and suggestions that the product team has because they understand the pain points that you are going through. They are aware of the solutions because there are other customers who are already onboarded and experiencing them. I gave this product a rating of 8 out of 10.

I have experience working with Fluent Order Management for about four years with very important luxury clients. I am currently working with Fluent Order Management with a luxury client. I handle requests, development, configuration of the environment, and other responsibilities for this client.

Fluent Order Management has many important features, including the sourcing engine that is provided out of the box and can be customized. The really important point of Fluent Order Management is the customization of the framework. There are some out-of-the-box logics, but it is really easy to customize if you know Java.

There is a limitation in that you cannot customize the data model. If the entity order and entity fulfillment have certain attributes in the data model, you cannot add or remove something directly. You can customize the data model by adding a custom attribute, which is a workaround for this limitation.

If I could point to an area of improvement, it would be that Fluent Order Management lacks a native reporting tool. An OMS without a reporting tool is quite problematic. You cannot easily determine how many orders are blocked in a particular status for about thirty minutes or one hour. It is really hard to report on Fluent Order Management. You need to customize it, perhaps by creating some scripts, and reporting is not native to Fluent Order Management. There is no tool for reports included.

I have been using this solution for about four years.

I have not experienced stability issues. I worked with a big luxury customer that has many orders, and it is really rare to see a crash or downtime. The platform needs to be really stressed to have a downtime or crash.

Scalability is good. Fluent Order Management is a cloud-native platform, so it is really scalable. I do not see areas for improvement in this regard.

I have contacted customer service many times, and this is really not a good point. The support sometimes tries to not respond properly to requests. You need to follow up with them, which could be better.

I have sometimes used software such as Manhattan OMS or Miracle, but I think for efficiency and being user-friendly, Fluent Order Management is a better choice.

If you are familiar with software such as Postman or Insomnia, the initial setup is really easy because there is documentation that guides you step-by-step to set up the initial environment, the retailers, and related configurations. It is easy if you know Postman or Insomnia.

For deployment, you can have one person because it is an API-based deployment and is a really easy deployment with Fluent Order Management with zero downtime. One person is sufficient.

I do not know the pricing. With my role, I cannot see the invoice of Fluent Order Management with my company because I am an employee.

 I think this framework is really complete for an OMS. I do not think the framework needs a really big improvement because it is a new framework and is updated really frequently. About one or two months ago, they developed a native MCP server with claude. I gave this review an overall rating of eight out of ten.

My main use case for Fluent Order Management is that I am a consultant and I implement Fluent Order Management for supply chain clients who are looking to extend their operations and optimize them. It helps them source items from the correct locations, handle returns, and process refunds.

I can give you a specific example of how I have used Fluent Order Management for one of my clients. Using Fluent Order Management, we can optimize the sourcing mechanism or the sourcing logic according to the business requirements that the client needs. For instance, we can configure it to source from a particular location if certain conditions are met. We consider costing requirements or whether a location is nearest, so we can optimize it or configure it to provide them with the ideal location where an order should ideally be picked from or shipped from, depending on the requirements.

Fluent Order Management is very scalable and quick to implement, and the deployment cycles are especially short. There is no downtime, and you can implement it immediately or deploy to production without any downtime, which is a significant advantage for Fluent Order Management.

Fluent Order Management's best features are quick deployment and the ability to implement the entire design logic very quickly compared to other platforms that I have seen personally. Additionally, it is an event-driven system, so things are decoupled significantly. If something is stuck, such as an order stuck in its particular journey, we can resume it after rectifying the errors or whatever caused it to get stuck. It has all the workflows and everything, which makes it optimal to use for clients.

Fluent Order Management has positively impacted my organization significantly. We receive many projects related to Fluent, and it has been a very good product that my company has been pursuing for a long time. We are happy to implement it for our clients since it is such a good product.

Fluent Order Management can be improved, but the company is already doing a good job in improving their services. They keep introducing new features as needed, and many other enhancements are already in the pipeline. I have seen their insider webinars, and they are already working on how they can implement AI as part of their product, so they are on the right track.

Regarding Fluent Order Management's AI capabilities, governance and security are not live yet; they are still testing and it is not even in beta at this time. The company demonstrates that it is actively working on this and will have it soon. From the demos I have seen, they do not check the data or work on it directly; they are more focused on solution-oriented approaches or filtering the data that already exists with them, and they follow all globally accepted data management protocols.

I have been using Fluent Order Management for more than four years.

Fluent Order Management is very much stable.

Fluent Order Management's scalability is excellent. The company provides scalability on an as-needed basis. If sudden load increases occur, it scales automatically to handle that and ensures that anything stuck is retried and processed as soon as it is scaled.

Customer support is good. We have a platform where we can log tickets in case something goes wrong. For P1 and P2 tickets, we immediately receive a reply from the available support staff.

I would rate the customer support on a scale of one to ten based on ticket size and priority. For P1 and P2, they respond immediately and provide solutions depending on the contract type. If it is P3 or P4, it can take some time, but we definitely receive a solution by the end of the day.

I have never previously used a different solution; I have always been a fan of Fluent and have implemented it.

I am not much aware of the pricing, setup cost, and licensing, but it is industry competitive, so it is good compared to others.

We have a business relationship with Fluent other than being a customer; we are partners. We are Fluent partners, and Well-Tech implements it for multiple clients.

I have seen a return on investment in terms of time and money saved because we were able to optimize the solution to reduce the number of splits, specifically the number of shipments needed for one particular order. We were able to optimize the pick and pack process for store employees to save time and gather as much information as needed before packing an item, which definitely helped them. For certain clients, it helped them scale their business globally as well.

I am not much aware of the pricing, setup cost, and licensing, but it is industry competitive, so it is good compared to others.

Before choosing Fluent Order Management, I did not evaluate other options, as I do not have visibility into all that.

I would add that the UI is customized as well, allowing us to create certain unique scenarios for returns if needed or appeasements. Many of the entities in Fluent Order Management are orchestrable, meaning you can create a flow for them, determining how they should behave, which is a very good point.

It has helped my organization grow revenue. Recently, we completed a project that was very successful. The client was very happy, and we improved their solution significantly compared to their legacy Order Management System.

The company has already rectified most of the issues at this point, so I feel that most pain points are all gone.

My advice to others looking into using Fluent Order Management is that it is a good tool to implement, and it can be done at a cheaper and faster rate compared to other platforms that I have heard about. I rate this review eight out of ten.

My main use case for Fluent Order Management is as an enterprise order management system for retailers, brand manufacturers, and distributors, and it is used for inventory availability, order fulfillment, dynamic sourcing, connections and integrations into and through a commerce ecosystem and all omni-channel fulfillment operations.

For a retailer, I have implemented Fluent Order Management to be their global inventory. For this retailer, I set up global inventory visibility and inventory as a service for commerce and marketplace, call center, and a number of other B2B channels, and I also enabled dynamic sourcing across a number of facilities and stores and am able to track and monitor real-time velocity of demand against store inventory to broadcast demand across other stores within the region. I also have hooked in all integrations to demand planning and ERP, WMS, payment systems, fraud, and other systems, and the outcome was an 80% reduction in split shipments, a 98% inventory accuracy rate, and an increase of sales by 25%.

The best features that Fluent Order Management offers are the extensibility and configurable workflows that are easy to navigate, and additionally, they have built in some AI components that enable users to optimize and accelerate development, while Fluent Store meets the base level omni-channel criteria for most retail chains.

The extensibility and configurable workflows allow a setup so that a specific customer's requirements are able to be captured and managed without customization.

I would say that Fluent Commerce platform has been invested in heavily from a net new feature perspective where they're optimizing some of the major performance issues in the industry, such as large inventory loads processing in very little time, and the ability to optimize order volume velocities and ensure a retailer is performant regardless of size and channel demand.

I would say that Fluent Order Management system could be improved mainly through the user interface for the console, and I would say even the React components of the store, while they are able to be modified, do not necessarily have an optimized appearance and feel, so clients need to be very specific about how they want to show their branding and their workflows within those screens.

The reason I do not give it a 10 is because I believe it has some salient features that could be enabled that are just not part of the base product, so there are some fundamental use cases that are not out of the box that I believe are necessary for this solution to operate effectively.

I have been using Fluent Order Management since 2019.

Fluent Order Management is stable.

Fluent Order Management's scalability is very well supported, and depending on the time of year, the Fluent team extends and operates to ensure that its client's cloud platform is able to scale with its volume increases, whether that is holiday or other peak periods that a client will share with Fluent.

Fluent's customer support is adequate, and they define the severity of the issues, so sometimes priorities for organizations do not have the same priority as what Fluent says they are.

The main drivers to switching to Fluent typically are large historical monolithic providers such as Sterling or Manhattan or companies that were heavily reliant on ERP such as Oracle and SAP.

I think one of the biggest savings is time to value, meaning Fluent Order Management application is not a large lift for an organization to implement, or at least using Pivotalry services, it has not been a large lift, so that I can typically get to a working solution within two to four months, and the other equations and statistics are truly around a trusted inventory availability metric, meaning that I am able to establish and showcase near real-time inventory across warehouses, stores, and other channels.

As an SI, I am not in commercial negotiations for the application, and the delivery, as I have stated, is typically a four to six-month time range to get it up and operating.

As an SI, I have seen a large interest in headless cloud-based OMS applications, and Fluent Commerce has become a mainstay as one of those prolific platforms that service a multitude of use cases regardless of sector, meaning whether it is retail, manufacturing, CPG, and B2B, I am able to leverage Fluent Commerce in meeting the demands of each of those different sector use cases.

I provided examples earlier for one of my clients that received a significant reduction in split shipments, increased inventory accuracy, and an overall increase in sales based on a trusted view of reliable inventory.

I am a partner and reseller.

The other main competitors I would say to Fluent are Kibo and OneStock.

I would rate Fluent Order Management an eight out of ten, and I would say that it meets the standard OMS use cases that are required for the majority of businesses to optimize their order processing; however, it has some limitations.

I would say look for a competent SI who has historically done successful Fluent implementations and also be prepared to have Fluent supported, as it is not a traditional application that companies can support with just normal operations resources.

Governance and security of any AI is not necessarily leveraged at the AI level but at the organization level, so trying to apply governance and security around AI is not the job of AI, it is the job of the organization to ensure that it is being leveraged correctly and not using it in a cavalier manner.

I think from Fluent MCP perspective, there is a robust opportunity to accelerate delivery from a base-level perspective, and I think that you require experienced users if you want to get very proficient with it.

My main use case for Fluent Order Management is to enable retail and other B2B e-commerce businesses to set up the order management flow, which takes care of the entire orchestration of the order from when it is placed to delivery of the product, and also handles post-delivery action items like handling returns, appeasements, and refunds.

A specific example of how my team uses Fluent Order Management in a real-world scenario is that we implement Fluent Order Management for businesses, particularly those with high frequency of orders, such as a shoe brand, beauty products, or B2B mechanical gears, and we manage inventory, order flow, send notifications to downstream systems and customers regarding the status of the order, along with handling refunds and returns. The entire order life cycle is managed through Fluent Order Management.

Regarding how I use Fluent Order Management, it is modular, enabling the implementation to be modular, with each component of the OMS, such as the inventory part and availability part showing stock, along with the actual order flow and store operations being configurable and manageable. Everything is modular, allowing development and work on multiple components simultaneously without disrupting any other parts, and components have very little downtime. Additionally, it is auto-scaling and cloud-based with a lot of UI customizations allowed, thanks to a separate SDK for UI customization, making it a good order management system.

Fluent Order Management's best features include its modularity and UI customizations, along with its auto-scaling capability during peak times, a workflow concept that allows me to create a sequence of action items making orchestration simple, and visual representation of the flow for readability. The team is also integrating many AI features and has improved their DevOps with an out-of-the-box CI/CD system, making it easier and more effective to work with the application.

Fluent Order Management has positively impacted my organization because the clients we have implemented it for have seen increased sales, fewer cancellations, and better order handling, especially compared to older OMSs and competitors they used previously. It scales effectively during peak loads and takes care of infrastructure automatically, particularly during high-demand periods such as holidays, which has boosted revenue for all the clients we have implemented it for.

Regarding how Fluent Order Management can be improved, I would say that additional AI capabilities would facilitate easier implementation, and while the system is already simple and modular, enhancing AI features could help us write less code and generate templates for specific client requests more efficiently.

I have been using Fluent Order Management for a little over six years.

Fluent Order Management is stable, as it auto-scales quickly depending on request volumes, dipping when requests decrease and scaling up promptly when they increase.

Fluent Order Management scales almost seamlessly during peak seasons, such as the holiday season, meaning it manages demand very well.

Customer support for Fluent Order Management includes an expert services team and the engineering team, available for questions and calls with clients for discovery. There is a separate pricing for extended support from the expert services team, but they respond quite fast even without additional cost upon licensing.

Fluent Order Management is incorporating new AI capabilities to ease the initial setup processes, such as creating product catalogs and inventory catalogs, which were previously done manually, but now can leverage AI to assist in doing those tasks. The team is investing more in AI capabilities this year.

The workflow concept allows me and my team to work on different components of the order management system without halting development on another component. For example, if I am working on the inventory component, I do not have to stop development on the order flow or store operation flow, and this workflow helps arrange events based on actions such as requests from downstream systems or entity creation, enhancing modularity and readability and making it easier to track events through a series of steps in the workflow.

My advice for others looking into using Fluent Order Management is that it is a product that is very flexible and allows for customized UI design. Since it is an OMS, focus should be on the functionality. It can also serve as a customer care portal or CRM, and implementation can be done quickly with the right consultant or knowledgeable Fluent Order Management implementation team who understand the product and the supply chain domain well.

In conclusion, Fluent Order Management is a product I have worked on for six years, observing its significant development and improvement. The team continuously adapts to customer needs, making frequent changes, and I hope they continue to evolve positively in the future. I would rate this product and my experience with it highly.

My main use case for Fluent Order Management is to manage orders from order creation until order delivery. I use it primarily for sourcing logic; when an order comes to Fluent Order Management, I have to decide from which fulfiller, warehouse, or location that order should get fulfilled. I route the orders to all those fulfillers. If there is a split, I do that split logic to fulfill all the orders and then I send the orders back to the fulfiller to fulfill it. I also manage the returns, cancellations, and basically, I manage the entire order journey of any orders.

A specific example of how I use Fluent Order Management for order routing or splitting involves getting an order with one line item with the quantity as ten. I have a warehouse that has those items, but they do not have the complete quantity. Suppose one of the warehouses has seven line items, meaning seven quantities, and the other warehouse has eight quantities. To select from which warehouse that particular order should get fulfilled, I check the inventory; both warehouses have the items, but not the complete quantity. I then rate it based on the total quantity of that item and the proximity of that particular warehouse from the customer. In this case, if the warehouse with eight quantities is nearest to the customer's location, I assign seven quantities to that nearest warehouse and the remaining three quantities to the other warehouse. This is how I split the order into two fulfillments, and I send orders to both warehouses with their respective quantities. That is how I do the split logic.

Another use case for me in Fluent Order Management is that I also handle cancellations. For cancellation, I have provided one custom button in the Fluent Order Management screen that allows me to cancel the order. Once I cancel it, I cancel all entities involved in that order, such as the order entity, fulfillment, and any captured items. After canceling everything, I send a webhook to SAP, which is my overall business management system that manages the complete order process, from product to accounting. I send those details to SAP that the order has been canceled, and they cancel it from their end as well.

The best feature that Fluent Order Management offers, which stands out for me, is the sourcing logic. Fluent Order Management is seventy or eighty percent customizable; I can customize most of the things. Now they have increased the React component SDK where I can customize with my own React components. Therefore, the customer can have the screen as per their requirement. There is not a fixed UI screen; I can customize it with my own style and requirement. I find this fascinating because I have not seen this level of customization in any other OMS system. Fluent Order Management has positively impacted my organization by eliminating overselling. After implementing Fluent Order Management as the order management solution, I can sell only up to the inventory stock. Previously, for the client for whom I implemented this, they were overselling their product, with many mismatches in inventory. If they had ten quantities available, they accepted orders for fifteen or sixteen, resulting in overselling. Now with the implementation of Fluent Order Management, I have a kind of buffer system; if I have ten quantities, I will have available only five for sale. Once I complete that five quantities, I will not accept further orders. This approach has restricted overselling and improved the customer experience.

There are certain improvements needed in Fluent Order Management that I think could enhance the system. Recently, I faced a configuration issue where Fluent Order Management mostly uses camel case conventions, but for a particular item, they used a plain format, making it hard for me to debug. Additionally, they should enhance the logging system because sometimes it becomes difficult to obtain the correct error information.

I believe the existing documentation for Fluent Order Management is adequate, as it is available on their website, but improving it would be beneficial. It would be better to have direct chat support with an agent for quick solutions, as right now, if I need help, I have to create a FRDS ticket and then wait for some days. This process can be time-consuming, so a direct chatbot or some support agent could lead to quicker resolutions.

I have been using Fluent Order Management for around five years, as I started my career as a Fluent Order Management developer, so I am still working on that.

For integration, Fluent Order Management uses webhooks. If I want to integrate it with any other system, I have a Fluent Order Management webhook. To integrate with other systems, I surely need a middleware because with the Fluent Order Management payload, I cannot customize the payload inside the Fluent Order Management SDK. I can send only the basic details such as the orders ID and some attributes in a specific format. To integrate it with another system, I need middleware that will receive the Fluent Order Management webhook payload, transform the payload to whatever system I am integrating with, and then forward it there. That is how Fluent Order Management integration works. If an external system wants to communicate with Fluent Order Management, I can either use the connector SDK, share GraphQL mutation to the external system, or do it using event syncs, which is basically REST API calls. This is how an external system can connect with Fluent Order Management.

I measured the reduction in overselling through improved structured processing in Fluent Order Management. Although I do not remember the exact metrics, I do recall that overselling was prevalent due to their legacy OMS, but I was primarily involved in the implementation. Despite not managing all the data, I know the overselling was problematic and resulted in many order cancellations, leading to a poor customer experience. With Fluent Order Management, all processing happens more systematically, which has built my client's confidence.

For others looking into using Fluent Order Management, I would recommend it with an overall review rating of eight.

My main use case for Fluent Order Management is primarily orders, but I also utilize product locations and inventory features.

A specific example of how I use Fluent Order Management is that orders placed through the website become visible in Fluent Order Management, where I process those orders systematically.

The best feature Fluent Order Management offers is the Order Orchestration capability. I also have access to Fluent Store, where I can process orders end-to-end until the delivery stage to the end customer.

The Order Orchestration helps my team as we can divide and split fulfillments into multiple consignments and then quickly deliver them to the end customer, making operations faster.

Fluent Order Management offers features for home delivery, click and collect, and different delivery methods.

Fluent Order Management has positively impacted my organization because we now have one particular hub where we can fetch data including products, locations, inventory, and orders. We experienced fewer returns, and both the cancellation rate and refund rate decreased significantly by using Fluent Order Management.

Fluent Order Management can be improved in terms of the logging mechanism and monitoring for debugging, as those aspects can be further simplified.

While Fluent Order Management provides initial logs, I cannot drill down in-depth to those logs for identifying needed improvements. The logging mechanism particularly needs enhancement.

I have been working in my current field for more than thirteen years.

My advice to others considering Fluent Order Management is that it is a very useful tool in terms of the OMS Order Orchestration logic, by which orders can be fulfilled quickly from an end-to-end perspective until the delivery stage. I would rate this review as a nine out of ten.

My main use case for Fluent Order Management is that for my current project, I'm basically using it as an order management system to do the routing of the orders and also to provide an OMS which manages shipment, shipment updates, appeasements, refunds, and everything of that nature. It also acts as a system which provides the source of truth for different other integration systems, such as the tax management system and other few other integration systems which I cannot actually reveal. However, it acts as a source of truth for many systems.

Other than the main use case, it is most importantly useful for the order management system as a whole. In my current project, it is doing the tracking for shipment and the fulfillment, and payments are being tracked down from here. Since it is recently updated with the payment entity and the payment workflow, payment refund workflow, everything is linked from here. That is the entirety of the purposes surrounding order management and the fulfillment flow and the payment refund capture flow.

The best features Fluent Order Management offers are the workflow configuration and the custom rule part, which is very useful in my opinion since we can customize the logic as needed by ourselves. For routing, appeasement, or credit based on the payment method and the payment provider, we can customize it as needed based on our own requirement. This is the most flexible part and useful part that I would consider as the best feature.

...configurable and more easy to use according to our specific use case.

Fluent Order Management has impacted my organization positively because the projects I have worked on are currently relying on that specific order management system, and I know other projects also that are relying on this order management system. It will be a key alternative for a very good OMS solution, which does all of the OMS management. It is very easy to do an integration, and since it is more of a fire and forget way of doing integration, with Fluent Connect it is becoming much more easier to do an integration. It is very apt for our different scenarios for the project I have worked on.

Currently, Fluent Order Management is working pretty reliably, but I think there might be a few issues surrounding the multi-tenant system. That is not exactly a feature, but at times it is causing issues in the lower environment. In production, it is generally lesser, but still it has issues in my opinion. At least in my experience.

...entity, you ideally should update the out of the box rules also related to that. That ideally should come in with the same batch update. It should not delay to a next batch or the upcoming batch. Everything should come up at once. That is one of the issues I lately found out in one of the entities.

I have been using Fluent Order Management for close to one and a half years.

Fluent Order Management is mostly stable, but at times it is having issues.

Fluent Order Management's scalability is ideally scalable at least from what they are offering, but for the multi-tenant system they are offering it on, it is still having issues at times. That is the point of unreliability in my opinion.

The customer support for Fluent Order Management is pretty good from what I have gone through. I would rate the customer support on a scale of one to ten an eight.

I can tell about noticeable improvements since using Fluent Order Management. For one of my projects, I actually migrated it from a different system. It was not exactly an OMS system, but based on the way the other system was working, it is much easier to work with and more reliable and also has far better features. That is one of the few good things and easier to work on in my opinion.

I choose seven as my rating because I have heard about other OMS systems like IBM Sterling and Blue Yonder and also something else. I do not remember exactly the name, but they happened to be pretty costlier than this, but they happened to be effective too for the pricing they are offering. Their integrations with different systems also sound easier, at least from what I heard. That might be far better, but still expensive. In that math or grading, I think seven suits the value for Fluent Order Management. I am not sure though.

The advice I would give to others looking into using Fluent Order Management is that it is dependent on the requirement they have and the pricing they are willing to pay for an OMS system. It is all dependent on their call and their decision making.

...seven out of ten.