Item: Blue Yonder Luminate Logistics
Rating: 1
Author: Verified User

Overall Satisfaction with RedPrairie

Use Cases and Deployment Scope

It's used across the whole organization and it's supposed to work as a warehouse management system.

Pros and Cons

Pros

Directed work.
Highly customizable

Cons

Quite user un-friendly database design; DB table names and column names don't give any clue about their purpose.
Data separation is non-effective. This is NOT a software for a 3PL (3rd party logistics company). Multiple clients sharing the same warehouse share tables - such as the Item Master table - without a clear indication of the client's name.
Several different tables for ItemMaster, way too complicated.
System would reject new Items if the Item Color sent via EDI hasn't been codified before the Item Master upload. That is a problem for fashion clients that create many new color codes every season.
Software requires SERVER reboot for every new change in order for the change to be effective. Unacceptable when many clients are on the same server and on a distributed organization.

Return on Investment

Slower implementation / conversion
Decreased productivity
Highly increased implementation costs

Alternatives Considered

ILS and SCALE

I did not select RedPrairie and I would have not selected it if I was the one making the decision.

Other Software Used

Microsoft SQL Server, Workfront, Jabber, SAP Crystal Reports

This software doesn't seem the right choice for a 3rd party logistics company with several clients sharing the same warehouses. It is not the right choice for fashion companies that create thousands of new Items and color codes every season. I don't know scenarios where this software can be well suited.

Comments

Please log in to join the conversation

Marco Sánchez
commented 6 years ago
I guess the people who implemented the system didn't have enough experience with the system. The system is very effective with 3PLs,multi-warehouses and multi-clients. There's no need to reboot the SERVER, only the instance. There's no need to create new skus if the only change is the color (attribute). There could be different ways to handle this and avoid EDI issues. I've seen implementations where they complicate things and create a mess in the system. They spend a lot of money and blame the system for all the problems, and end up spending more money to "fix" the issues.

JDA WMS (was RedPrairie): How to complicate simple things.