OMS architectural longevity
Tuesday, June 26, 2018

OMS Architectural Longevity – What is it?

The other day a consultant asked us about the OMS architectural longevity of OrderDynamics DOM. For medium to enterprise level retail technologies, this is a concern. You don’t want a system that takes many months to deploy. Much less one that then needs resources to update as soon as you have it deployed. Frankly, retailers need systems designed for ease of use. You need a system that is flexible, and highly configurable. You also need a technology designed for scalability, flexibility, no coding, and yes – longevity.

Snake Oil, Anyone?

On many projects, we hear about a POS vendor, retail generalist, or inexpert SI (systems integrator) pitching an entirely new OMS development. They don’t really have the background in the specific technology. But it seems easy enough. At least at the beginning. It’s just some order routing setup around a few business rules, right?  For this, you don’t even need any serious testing or quality assurance. That’s just overhead, right?

This is a great example of vendor hubris and taking a wild risk with your brand, sales, profit margins, and future!

Seriously, What is OMS Architectural Longevity?OMS architectural longevity speaks to a system in which minor improvements and fixes take place in the background

OMS architectural longevity speaks to a system in which improvements and fixes take place in the background. This is away from the awareness of the merchant customer. In most cases, if the system appears to auto-update without retailer intervention – great news!

It also speaks to the same idea about new features, enhancements, and architecture changes. All these need to be on a continual improvement cycle, keeping the product updated and relevant. Major new features and architectural adjustments also need to be completed behind the scenes. Yes occasionally (and rarely) there may be the need for a migration to an entirely new platform or architecture. These are often fraught with risk. We all know of a certain vendor that release their 2.0 platform giving customers a disastrously hard time in their migration. However, to the earlier point, a well thought out system at the start, means these shifts are rare.

Furthermore, OMS architectural longevity also means you don’t have to recode your system for tweaks and features. Again, the ideal state means all this happens in the background. Being faithful to the SaaS philosophy, the service is uninterrupted. Changes, updates, and technical adjustments are all done behind the scenes without customers intervention. Also, the technology vendor needs to handle these without affecting the performance. That means no down-time, and no going offline.

What I Told the Consultant

Whitepaper: Will the Real Retail OMS Please Stand Up?Without a doubt, the OrderDynamics solution is a system designed with OMS architectural longevity in mind. It is a native SaaS product. No ‘legacy dinosaur system patched to look like a SaaS solution’ – here. It has been architected as an Out-of-the-Box solution. There is NO CODING at all, once the system is implemented and live. Any re-configuration is done by the system administrator, within minutes. No extra fees, or wasted time to book a consultant’s time. The system is thoroughly and continually tested by quality assurance teams. There are several releases per year, to keep customers on the latest and greatest version – continually. Best of all, any and all changes are all done in the background. When there is a new feature release, you can use it IMMEDIATELY!

Ultimately, that’s our definition of OMS architectural longevity. We deliver it to our customers, every day.

Ask Your OMS & Retail Technology Vendor…

OMS architectural longevity means you don't have to recode your system for tweaks and features.Thinking about your OMS architectural longevity is a smart move. It means you are planning for the future. You are making sure your company has room to grow. It also means one less thing to worry about. Here are a few questions to ponder, and about which you want to ask your retail vendors:

  • Is Coding needed for new features?
  • How many releases do you get per year?
  • Is the system a NATIVE SaaS application?
  • Is it on a multi-tenant cloud platform?
  • How high can it scale? Can they show you the test results?
  • Is the OMS recognized by Gartner, Forrester, IDC, RSR, IHL, and/or EIQ? Get them to send you the report.
  • Can a systems administrator make adjustments (or do you need a coder every time)?
  • Is there a licensing fee?  (Immediate give-away that it is NOT Native SaaS application)

Want to discuss any of these items, or just get a second opinion? If yes, then please Contact Us, for an easy-going discussion about your challenges, and needs. If we can’t help you, we will suggest someone who can.

Author:

Charles Dimov - Director Marketing OrderDynamicsCharles Dimov is Vice President of Marketing at OrderDynamics. Charles has 21+ years experience in Marketing, Sales and Management across various IT and Technology businesses. Previous roles include Chief of Staff, Director Product Marketing, and Director Sales. Charles has held roles in brand name firms like IBM, Ericsson, HP, ADP, and OrderDynamics.

 

 

 

Related: 

3 Keys to choosing a retail order management solution

Do You Need Global Inventory Visibility?

Omnichannel Retail ROI - Does it Exist?