A.M. Leonard Grows Its Business With Sage ERP X3
Customer Company Size
Mid-size Company
Region
- America
Country
- United States
Product
- Sage ERP X3
Tech Stack
- Visual Basic
Implementation Scale
- Enterprise-wide Deployment
Impact Metrics
- Productivity Improvements
- Customer Satisfaction
Technology Category
- Functional Applications - Enterprise Resource Planning Systems (ERP)
Applicable Industries
- Retail
Applicable Functions
- Sales & Marketing
- Warehouse & Inventory Management
Use Cases
- Supply Chain Visibility
- Inventory Management
Services
- System Integration
About The Customer
A.M. Leonard is a company that has been delivering tools and supplies to professionals in the horticulture industry and to home gardening enthusiasts for more than 130 years. The company differentiates itself by selling quality products and backing them with the best customer service possible. A.M. Leonard has a multifaceted sales channel that includes a busy call center handling phone and mail orders, two websites, and channel sales through Amazon.com, Search.com, and Newegg.com. The company is located in Piqua, Ohio and operates from one location.
The Challenge
A.M. Leonard, a company with a multifaceted sales channel that includes a busy call center handling phone and mail orders, two websites, and channel sales through Amazon.com, Search.com, and Newegg.com, was seeking to replace its older, inflexible application with a customizable and scalable ERP solution. The company needed a system that could handle its complex pricing structure, streamline order entry, and improve inventory handling. The company also wanted to enhance its team’s ability to access information across the enterprise, which would lead to better decision making.
The Solution
A.M. Leonard chose Sage ERP X3 for its ability to be tailored to meet unique business requirements, its powerful architecture, and robust inventory management tools. The implementation of Sage ERP X3 was completed quickly, in just four months. The inherent flexibility of Sage ERP X3 saved the company time and money while delivering a higher level of customer service. The software was able to adapt easily to A.M. Leonard's business model, while streamlining and simplifying order entry in the process. The software also improved inventory handling, cutting the process to complete physical counts in half.
Operational Impact
Quantitative Benefit
Case Study missing?
Start adding your own!
Register with your work email and create a new case study profile for your business.
Related Case Studies.
Case Study
Improving Production Line Efficiency with Ethernet Micro RTU Controller
Moxa was asked to provide a connectivity solution for one of the world's leading cosmetics companies. This multinational corporation, with retail presence in 130 countries, 23 global braches, and over 66,000 employees, sought to improve the efficiency of their production process by migrating from manual monitoring to an automatic productivity monitoring system. The production line was being monitored by ABB Real-TPI, a factory information system that offers data collection and analysis to improve plant efficiency. Due to software limitations, the customer needed an OPC server and a corresponding I/O solution to collect data from additional sensor devices for the Real-TPI system. The goal is to enable the factory information system to more thoroughly collect data from every corner of the production line. This will improve its ability to measure Overall Equipment Effectiveness (OEE) and translate into increased production efficiencies. System Requirements • Instant status updates while still consuming minimal bandwidth to relieve strain on limited factory networks • Interoperable with ABB Real-TPI • Small form factor appropriate for deployment where space is scarce • Remote software management and configuration to simplify operations
Case Study
Digital Retail Security Solutions
Sennco wanted to help its retail customers increase sales and profits by developing an innovative alarm system as opposed to conventional connected alarms that are permanently tethered to display products. These traditional security systems were cumbersome and intrusive to the customer shopping experience. Additionally, they provided no useful data or analytics.
Case Study
How Sirqul’s IoT Platform is Crafting Carrefour’s New In-Store Experiences
Carrefour Taiwan’s goal is to be completely digital by end of 2018. Out-dated manual methods for analysis and assumptions limited Carrefour’s ability to change the customer experience and were void of real-time decision-making capabilities. Rather than relying solely on sales data, assumptions, and disparate systems, Carrefour Taiwan’s CEO led an initiative to find a connected IoT solution that could give the team the ability to make real-time changes and more informed decisions. Prior to implementing, Carrefour struggled to address their conversion rates and did not have the proper insights into the customer decision-making process nor how to make an immediate impact without losing customer confidence.
Case Study
Ensures Cold Milk in Your Supermarket
As of 2014, AK-Centralen has over 1,500 Danish supermarkets equipped, and utilizes 16 operators, and is open 24 hours a day, 365 days a year. AK-Centralen needed the ability to monitor the cooling alarms from around the country, 24 hours a day, 365 days a year. Each and every time the door to a milk cooler or a freezer does not close properly, an alarm goes off on a computer screen in a control building in southwestern Odense. This type of alarm will go off approximately 140,000 times per year, equating to roughly 400 alarms in a 24-hour period. Should an alarm go off, then there is only a limited amount of time to act before dairy products or frozen pizza must be disposed of, and this type of waste can quickly start to cost a supermarket a great deal of money.
Case Study
Supermarket Energy Savings
The client had previously deployed a one-meter-per-store monitoring program. Given the manner in which energy consumption changes with external temperature, hour of the day, day of week and month of year, a single meter solution lacked the ability to detect the difference between a true problem and a changing store environment. Most importantly, a single meter solution could never identify root cause of energy consumption changes. This approach never reduced the number of truck-rolls or man-hours required to find and resolve issues.
