Retail Archives - Page 8 of 14 - Sunrise Technologies

Post go-live support

Mike Pereira is Sunrise’s Vice President of Global Customer Support and one of Sunrise’s longest-serving employees. Mike has over twenty years of experience and a deep background in apparel and textile management as well as manufacturing supply chain management.

You did it! Breathe a sigh of relief — you made it through go-live, and your new ERP system is up and running. Now it’s time to tackle what to do after go-live. Even though you may want to call this project “done” and move on, the work isn’t over. The first few weeks after going live, it’s critical that you stay vigilant and nip any issues in the bud. Let’s walk through the hyper care process and document some things you should expect…

Data migration: the first wave

Special cases

Helping new users

Avoid the Valley of Despair

Frequently asked questions

Data migration issues — the first wave

People are surprised at how quiet the first week after go-live can be. If you did all your testing and gave yourself plenty of time and CRPs, transactions should be flowing through your system without a hitch. The first thing you might encounter are data migration errors. These usually happen because business users have only interacted with the old, migrated data before, and any issues that existed could throw errors in the new system. It’s important to clear out these data migration errors first, before too many pile up.

Special cases

It’s impossible to test every possible scenario prior to go-live. The second wave of issues you might encounter are the outliers — one-off scenarios you didn’t have time to test. These are to be expected (after all, you have to go-live at some point, right?) As users start adding new master and transactional data, these corner cases become obvious. The intersection of data and business processes can create unique, unexpected situations. If your project team handles these cases as they appear, you should be fine.

Helping new users

You’ve conquered any migration problems and taken care of the corner cases. The last thing to look out for are user errors. We consider these issues the most dangerous because if they aren’t dealt with swiftly, user errors can snowball into an avalanche of problems that affect the whole organization. For example, an employee from merchandising might forget to associate the cost for a new product. The warehouse then receives the product at zero cost, and now the fix requires several financial transactions and lots of time. During this time, speed of resolution is key. If errors are being created faster than resolutions, that’s a problem. Your project team and your organization’s power users should work on clearing out these errors and reinforcing best practices among the rest of the organization.

Avoid the “Valley of Despair”

The Valley of Despair is when your ERP’s performance drops dramatically, shortly after going live. Users might get frustrated, disappointed, and wonder if the project was even worth it. Guiding users around this metaphorical valley of despair is why your project team should stick around a little longer. The real benchmark people should focus on is closing the first financial period in the new system.

Frequently asked questions

What are the most common problems users might experience after go-live?

Data migration errors, followed by special cases regarding business processes, and user errors are most common.

What’s a good benchmark for measuring success post go-live?

Closing the first financial period in your new ERP system is a common benchmark to use.

We don’t have time to test every scenario in time for our scheduled go-live, is this bad?

Assessing go-live readiness is an art and a science. Businesses are complex—and it’s impossible to test every single scenario and stay on schedule. It’s to be expected that some special cases will reveal themselves in the first few weeks after go-live.

Start Your Journey with Sunrise Today!

Whether you’re exploring your options for new business platforms, or ready to get started, we are trusted business partners for some of the world’s most well-known brands. With over 25 years of experience with the Microsoft stack, we can help you understand all the capabilities Microsoft has to offer.

To customize, or not to customize?

Implementing a cloud-based ERP system like Microsoft Dynamics 365 is essential for organizations seeking to stay competitive. However, one topic that often causes hesitation during ERP projects is customizations. While ERP customizations have historically been a source of frustration, particularly when they lead to long-term maintenance issues or system instability, a “no customization” policy isn’t always the best approach. The key is knowing when customizations add value versus when they create unnecessary complexity.

Understanding When to Customize Your ERP System

Not all customizations are created equal. The decision to customize should never be taken lightly, but avoiding all customizations across the board can leave your organization struggling to maintain a competitive edge. A better approach is to evaluate whether a customization serves a clear business purpose. Customizations should align with your company’s goals and long-term strategy, enabling your teams to perform at their best while enhancing overall efficiency.

Gap-Fit Analysis: Identifying When Customizations Are Necessary

During the early stages of an ERP project, your team will engage in a gap-fit analysis to document current business processes and compare them with the new system’s out-of-the-box functionality. This is where the decision to customize or change your processes often comes into play. Should the software be customized to fit your current business processes, or should your processes adapt to fit the software?

There are pros and cons to each approach. Customizing the software may seem like a faster, easier option in the short term, especially when users resist change. But using customizations as a shortcut can result in significant long-term costs, from ongoing maintenance to system updates that break existing custom code. On the other hand, asking your team to change ingrained business processes can be time-consuming and may lead to friction during implementation.

The trick is finding the right balance. Customizations should be reserved for areas that truly impact your company’s uniqueness or provide a competitive advantage.

Strategic Factors to Consider Before Customizing

Adding Value to the Organization

Customizations should deliver measurable value. Will the customization improve efficiency, enhance the customer experience, or contribute to higher revenue streams? If the answer is yes, it may be worth considering. However, any customization should align with your organization’s broader strategic goals and business objectives.

One good rule of thumb is to ask: Will this customization make my business more competitive in the marketplace? If the answer is no, it might be better to explore standard functionality or process changes.

Streamlining Processes

A well-planned customization can help streamline workflows by automating repetitive tasks, simplifying processes, or integrating disparate systems. For instance, if your business relies heavily on manual processes, a customization could significantly reduce time and labor costs.

However, remember that customizing software to match inefficient processes isn’t the answer. Consider whether changing your business processes could deliver similar efficiency gains without the need for custom code.

Exploring Low-Code Alternatives

Before diving into full-blown customizations, consider low-code solutions, such as Microsoft’s Power Platform. Low-code platforms allow you to build custom applications with minimal development effort, providing needed functionality without heavy investments in development or future maintenance.

The Power Platform integrates seamlessly with Dynamics 365, giving users the flexibility to extend the ERP system without feeling like they’re interacting with a completely different solution. This approach can reduce complexity and help you avoid the maintenance issues that customizations can introduce, all while enhancing user satisfaction.

Evaluating the Long-Term Feasibility of Customizations

It’s easy to overlook the long-term implications of customizations, but it’s critical to assess their feasibility over time. Customizations require ongoing updates, especially as cloud platforms evolve. You’ll need to ensure that your customizations remain compatible with future upgrades and don’t become a burden on your IT team.

When evaluating whether a customization is sustainable, consider:

The resources required to maintain and update the customization over time.
The potential impact on future upgrades or new system features.
Whether the customization aligns with the long-term goals of your business.

By thinking ahead, you can ensure that customizations don’t become obstacles but rather sustainable enhancements that support your growth.

Everything You Need For A

SUCCESSFUL IMPLEMENTATION

Cloud-based ERPs have changed implementation best practices and methodologies. Based on over 30 years of experience, we’ve identified seven critical factors that influence whether a project succeeds or fails.

Ready for your tailored ERP solution?

Schedule a call with one of our ERP experts today to implement Dynamics 365 with less cost and fewer customizations.

Supply chain rebound—back on track, but better: 3 ways to improve visibility and agility

Start Your Journey with Sunrise Today!

Don’t underestimate data migration

As a Director of Consulting for Sunrise Technologies, Jason Wolf has over 15 years of experience implementing Dynamics ERP solutions for apparel, footwear, retail, and consumer goods companies.

ERP implementations are tough

Over the years, implementation partners have created methodologies, project management and planning tools to account for every aspect of an ERP implementation. Yet it’s still common to see data migration get left behind during project planning. We believe this is backwards, since without the data, your new ERP system can’t go live. Data migration should be considered at the beginning of an ERP project, while other important design decisions are being made. By taking the time upfront to plan your migration strategy, you can avoid unexpected delays during your project.

Why migration planning is so important
Data migration strategies
Data cleansing
Validation and testing
Frequently asked questions

Data migration can make or break your implementation

Migration planning should happen early in the project. Getting a jumpstart on the challenges for each data structure can save tons of time, and safeguard against unexpected hiccups during the project. It also gives the project team a better idea on timelines and resources needed to get from the old system to the new one. The bigger the change to a data structure (especially master data structures like product, customer, vendor, etc.,) the more challenging it will be to move to the new system. Without a plan in place, budgets can run over, timelines run long, or an issue stalls the process late in the project.

Selecting a strategy for data migration

The key to a smooth migration is picking the right strategy. One size does NOT fit all, which is why it’s important to spend time early in the project deciding on the best method. Some examples are:

Bill of Materials data might be complex, with significant changes to the data structure. However, the volume might be small enough that it’s easier to enter it manually. For very complex data structures, it doesn’t make sense to write a migration script that you’ll only use once, when in the same amount of time you could just enter the data.
Sales orders (or other types of transactional data), might be thousands or even hundreds of thousands of lines long. In that case, it might be better to create an automated script to move and map the data.

Cleaning the data

One of the unsung benefits of an implementation is getting a fresh start with clean, well-organized data. You can’t realize all the benefits of a new ERP system if your data is riddled with errors. Take this opportunity to remove redundancies, append missing information, fix typos and errors, and archive what you won’t need going forward. The key is to clean the data before migrating to the new system. Source data should be audited, issues resolved quickly, and controls set up for maintaining data quality and governance in the new ERP system. Much of this data cleansing work is manual, but it’s worth it to get the full value out of your implementation.

Data validation

The only way to know for sure that the data migrated successfully is to check. The basic process is to start with a small amount of data, load it into the new ERP system, test, add more, and repeat. Once the migration is complete, you can validate it by checking against the source system. For example, say you want to check your open sales orders. You could check the line counts, quantity, and amount against the original source and if the numbers match, you’re good to go.

Frequently asked questions

When should we start thinking about data migration strategy?

As early as possible! A data migration strategy should be considered early in the project, while other key design decisions are being made.

How do we decide which strategy to use for data migration?

There isn’t a one-size-fits-all approach for data migration. Your implementation partner should offer guidance based on their experience. In general, for lower volumes, it might be more efficient to manually enter the data rather than spend time creating an automated script. For very large sets of data that contain complex mapping and business logic, automation may be the way to go.

How should we handle data cleansing?

Clean your data in the source system prior to the migration.

How do we validate that the migration was successful?

Create a checklist to test what’s in your new system against the legacy data source.

Start Your Journey with Sunrise Today!

What kills an ERP project?

As a Project Manager for Sunrise Technologies, Kristin Pehilj brings over 20 years of industry experience to the table and serves as a trusted advisor for apparel, footwear, and consumer goods companies that are in the midst of an ERP replacement.

No one wants to think about it, but your ERP project might fail. And while there’s a wealth of analysis on why ERP implementations fail, we consider one factor to be the difference between an implementation’s success or failure. Executive involvement is key — without it, an ERP project will struggle from the beginning and may not recover.

Change management

The executive’s role

Steering committee meetings

Frequently asked questions

More than just an ERP project

An ERP implementation is really a change management initiative. Just with more software involved. Asking people to change is never easy. It’s up to your company’s leaders to champion the project and guide your employees throughout the process.

Once a project is underway (and starts to get tough), the new system should be the catalyst for business transformation, something people can reference as the driving force behind positive change. You can have the best consultants, but even skilled, friendly, hard-working people face resistance when they’re the outsiders. Members of groups follow their leaders. And this is a good thing! Huge projects only get accomplished when people work together as a team, which is why executives should be prepared make tough decisions, foster consensus, and drive the project forward.

How executives can play a crucial role

Of the thousands of decisions that need to be made during a project, many are going to be controversial. An ERP system touches almost every department in a company. Each department has its own set of processes and distinct personalities. Something like sales order management — which crosses paths with sales, credit, customer service, planning, logistics, accounts receivable — could require days or weeks of meetings. And when people can’t come to an agreement? The process stalls. This is the death knell of your project. This type of deadlock is why executive support is crucial. They can smooth the path and make the tough decisions needed to drive the project forward.

Why meetings are so important

We recommend you form a project steering committee and meet at least once a month. The meetings don’t have to be long, but they should focus on specific asks for executives, rather than just listing project updates. It’s amazing what you can accomplish in a one-hour meeting. The key is to keep requests concise, limit needless updates, and be clear on who is responsible for what. By bringing a list of short, actionable items to the executive team, you can respect everyone’s time and keep them engaged and involved.

Frequently asked questions

Why is this more important than budgets, applications, platforms, or other resources?

Certainly those factors are important, but we consider executive involvement the backbone of a successful ERP implementation. These projects involve change management, which is never easy and relies on a company’s leaders to see it through.

How can I ensure my executive team’s involvement?

The most basic thing you can do is establish a steering committee and ask key members of the executive team to participate. Getting executives to attend regular meetings might be tough, but a well thought out meeting with an agenda, decisions and next steps will go a long way to keeping them involved. And it will be worth it in the end.

Ultimately, who is responsible for what?

It’s the implementation team’s job to decide who is responsible for what activities, which problems need an executive decision, and which can be solved on their own.

Fitting in another monthly meeting is hard, how do we use the time effectively?

The key to a successful steering committee meeting isn’t just project updates (people can get that information on their own time), it’s bringing up the issues that need executive input. Get in, follow the agenda, assign next steps, and move on.

Start Your Journey with Sunrise Today!

Inventory Allocation

As the SVP of Global Business Development for Sunrise Technologies, Cem Item serves as a trusted advisor to C-level executives running large global enterprises. He conducts corporate business strategy engagements and digital transformation workshops around the world. With over 20 years of consulting experience, Cem specializes in the textile, apparel, footwear, home furnishings, consumer goods manufacturing, and retail industries.

If hard allocation is the hammer and nails of supply chain, soft allocation is like magnets and a whiteboard.

Defining soft and hard allocation

Allocation (the point where supply meets demand) is one of the most important pieces of the supply chain. So many critical business processes— customer service, inventory, sales — start hinge on smart allocation. Among supply chain professionals, software vendors, and other stakeholders, different words and terms get thrown around and people get confused. Here’s our point of view on hard and soft allocation, and challenges within each.

Very simply, hard allocation means the commitment between supply and demand cannot be changed. It’s been finalized, agreed upon, and now items are ready to go. Soft allocation, on the other hand, has a little wiggle room. Supply can shift as needed. Both practices play an important role in the supply chain, but typically we expect allocation to start out soft. Over time, as conditions change, allocation should get harder. During the planning process, hard and soft allocation can even be tied together.

Key differences between hard and soft allocation

Soft allocation

Supply is flexible, depending on changes to demand. It’s possible to shift quantities and orders as needed.
Usually, in the early stages of planning, soft allocation is the name of the game. Delivery is a long way off.
Deals with planned and firm entities alike.
More planning-oriented.

Hard allocation

Supply is committed to the demand, with no changes.
Delivery date is very soon…think days or weeks.
Only interested in firm entities.
More execution-oriented.

Challenges in the planning process

Planning usually starts with a forecast. Over time, orders are placed and users compare them to the forecast and adjust. The type of business can dictate how planning is handled. For example, wholesale businesses that gradually firm up demand over time may have semi-firm demand like a bulk or blanket sales order. For retail or eCommerce businesses, demand is never locked in until a customer places an order. Things get really complex for companies with multiple channels – retail, ecommerce, and wholesale, for example. Every channel requires different demand planning, from forecasting to bulk orders to placing actual orders.

Meanwhile, you also have planned purchase orders or production orders. Over time, these planned orders are scheduled, or goods are produced and delivered, and placed in inventory. All along the way, a company is juggling many types of supply (planned orders, in-progress orders, inventory, etc.) alongside many types of demand (the forecast, sales orders, standing bulk sales orders, etc.) And it’s the supply chain’s job to strike the delicate balance between the two.

How soft allocation helps you manage your supply chain

Let’s say you’ve just begun a new season, or otherwise in the beginning of the planning cycle. At this point, few orders are confirmed. You have a forecast, but products are still on order or in production, or something in between. This is the worst possible time to start hard allocating supply against the demand. You’ll encounter both inventory headaches from all the effort to re-organize and re-plan when orders are canceled or rescheduled, and you’ll have a bunch of customer service problems, too. This is the time when you should go with the flow. This is where soft allocation is your superstar.

If hard allocation is the hammer and nails of supply chain, soft allocation is like magnets and a whiteboard. While orders are being placed, you should be able to shift supply to demand as priorities change. Seeing the big picture — whether that’s by channel, customer, product, vendor, or other entities — is key to understanding and managing your supply chain for the best results.

Hard allocation comes into play when you’re ready to execute. At this point, you’re dealing with the firmest supply and demand (inventory and sales orders). Releasing the orders might be constrained by fulfillment rules, like no partial shipments, or at least fifty percent of line level is satisfied, or similar. Challenges at this stage are implementing these fulfillment rules while maximizing the amount of inventory that ships. The right allocation solution lets you set up and edit these constraints quickly and easily.

Start Your Journey with Sunrise Today!

Continuous updates: stay current and avoid issues

Scott Hambright is Sunrise’s Director of Global Customer Support. Prior to joining the Global Support Team, Scott was a Senior Technical Architect for Sunrise, assisting clients on ERP implementations in the apparel, retail, consumer goods, and manufacturing industries.

The new ERP update model

The continuous update model has been one of the biggest shifts in modern ERP over the past few years. In the past, companies would spend millions of dollars and go through intensive upgrade projects to migrate to the newer version of whatever ERP they were using.

ERP upgrades used to be expensive and time-consuming, but no more. Instead, companies have replaced one anxiety for another – continuous updates. Dynamics 365, and cloud-based infrastructure, means software updates can be pushed automatically. But this makes people nervous. Since an ERP system handles so many functions within a business, users are wary to just accept the latest updates. But they’re essential for keeping your business humming along. So, you need a strategy for handling continuous updates in a way that maximizes their value and minimizes impact on your business.

Prioritize the most essential business functions

When it comes to updates to your ERP system, focus on maintaining business continuity. Before you start testing, define the most important processes — the ones that you have to get right to keep the lights on. Being able to get orders out the door is far more important than posting a fixed asset depreciation journal. Get your team together and make a list. Plus, it’s easier to define success when you have criteria to refer to.

Focus on testing customizations and extensions

There are generic ERP software functions, and then there are your functions — the customizations and extensions that make your business unique. Get your software vendor to handle testing the basics, like creating sales orders, receiving a purchase order, etc. And if your software vendor can’t or won’t do this for you, find a vendor who will. This testing phase is your opportunity to make up scenarios to ensure your customizations are good to go.

How to handle integration testing

Integrations are the most fragile part of your system, so spend the most time making sure those connections are solid. Luckily, you only have one aspect to test – your connection, not the external system. Here’s one way to do it:

For inbound messages: have a set of sample data prepped before you start
In your test environment: push the sample data through the system (with the new updates) and see what happens.
For outbound messages: export your data in XML format and use file comparison tools to see if anything changed from the new updates.

Use automation to keep up with updates

Most cloud solutions will come with tools to help you test updates. This is where automation comes in handy. You can save significant amounts of time by setting up automated functional and integration testing. There are a lot of options – you can build functional scripts to run through your customizations. You can take data snapshots for use in inbound and outbound integration testing. Obviously, you’ll need a separate software environment to test everything, and a human to oversee this testing process.

We recommend that you aim to make testing your software updates as fast and automated as possible (so if there is a problem, you can devote time to fixing problems, not boring rote work).

Checklist for testing ERP updates

Define the most important business processes and prioritize testing those first.
Create test scenarios for your system’s customizations and extensions. Leave the standard functionality testing to your vendor
Spend the most time on testing integrations – these are the areas that are most unique to your system footprint.
Consider automated testing for functional and integration updates.

See how Dynamics 365 handles inventory management

Are you interested in learning more inventory best practices? Would you like to a see a modern, streamlined allocation solution that gives you both flexibility and accuracy? Contact Sunrise today!

Season codes: what are you really tracking?

The importance of seasonal products for brands

Some brands live or die by seasons. We work with a lot of apparel and fashion brands, and seasonal inventory is very common for these companies. Winter coats, summer dresses, that sort of thing. While other types of businesses certainly have a seasonal element, there is tremendous pressure for brands to stay on top of the latest trends (or create trends themselves).

Optimize inventory with season codes

Season codes give you the ability to report on a product’s sales performance by season. This is a good thing. Especially for apparel and fashion brands, the styles of products change from year to year. A style may have one season to prove itself, and if it doesn’t sell well, it’s gone next year. Often, we find companies add the season code to a product’s style number — for example, say you make a dress and call it DressF20.

Embedded season codes in style numbers cause problems

At first glance, combining season codes and style numbers seems fine. It makes logical sense. But over time, keeping these two attributes together causes problems. Let’s examine a few:

Problem 1: If you decide to sell across seasons, you need to create new style numbers for the same product

The dress from Fall 2020 was a big hit. You want to carry it next year. Great! However, you’ll now have to make a DressF21 style and move the 2020 inventory to the new 2021 style number.

Problem 2: Carried-over styles need new color and size product variants

The original dress you sold that was so popular — you also have to make new color and size variants for the carried-over style.

Problem 3: You must complete inventory transfers for the new SKUs.

You’ve got your new style number, your new variants — now it’s time to transfer the leftover inventory from the old SKU to the new SKU. Now imagine doing all this work for 10, 20, 30 styles every season. Think about all the time and effort wasted — all because you’re tracking styles and the season code together.

Last season doesn’t really mean last season (for styles)

Ask yourself: what data are you really trying to capture with the season code? Are you trying to document:

When the product was designed?

When the product was manufactured?

The selling season for the product?

A better way to manage seasonal inventory

You may find a more logical attribute than season, or that there are actually multiple “seasons” that have nothing to do with whether it’s snowing outside or not. Maybe design seasons are the way to go. Another way to think about it is in terms of color. Colors lend themselves to seasonality more than style, so you could link a season code with a color rather than a product. The best way to generate season codes will differ for your business, but being thoughtful about what you really need that data for, and setting it up right the first time, can save time and money down the road (no more frantically keying in new product numbers and inventory transfers).

Start Your Journey with Sunrise Today!

What should your product numbers mean?

As a Senior Supply Chain Consultant for Sunrise Technologies, Melissa Welhelmi brings over 20 years of industry experience to the table and serves as a trusted advisor for apparel, footwear, and consumer goods companies that are in the midst of an ERP replacement.

Intelligent product numbers

Like we’ve discussed before, product is the heart of your brand. And since product structure is such an integral part of your business, how you number (or don’t number) those products matter. A lot.

Intelligent numbering is very common in the industries we work with. This is when a product’s number or ID contains meaningful information. For example, a fashion brand might have a jacket label WJF20S123-BLK-S. In the style name, “W” means Women, “J” means Jacket, F20 means Fall 2020 season, S123 means the sequential style number. “BLK” is the color black and “S” stands for small size. The style numbers can get really detailed.

At first, intelligent numbering makes a lot of sense, especially for quick analysis. At a glance, users can see the most important attributes. Especially with companies using legacy inventory management systems, users may rely on those product numbers packed with meaning for reporting and analytics.

Why smart numbering is no longer a best practice

Businesses change. Employees leave and take their institutional knowledge with them. New staff members have to learn and maintain the product numbering schema. Because humans maintain these numbers, mistakes happen. Eventually, you may find that no one understands what your company’s product numbers mean anymore, but you have to maintain it for the sake of not having a better alternative.

In many ways, intelligent numbering is an outdated practice that should be left behind with legacy systems. There are many downsides:

Someone needs to be well-trained and well-versed in the product numbering schema so they can correctly configure products. Mistakes cost time and money to fix.
Heavy reliance on insider knowledge — new staff members don’t know the meaning behind the intelligent numbers.
Hard to maintain — adding new product categories means you might have to rethink the whole data structure and add new, complicated logic.
Adding new products can be time-consuming, with a higher likelihood of manual entry and errors.

Intelligent numbering isn’t just a human problem, it’s a systems problem. Especially for consumer brands, once they start adding new product categories, additional information must be added to the product master data setup. The extra business logic that comes with this work adds another layer of complexity to something as simple as numbering products.

Trade smart numbers for a smarter system

We’ve discussed this in detail in some of our other blogs — there’s a better way!

Business applications today are built to handle multidimensional products without complex naming schemes. Data entities like dimensions, hierarchies, attributes, categories, and assortments can be used to create a new master data model for a company that is easy to maintain, without intelligent number schemes.

Legacy systems often lack this capability, so we understand why organizations struggle with intelligent product numbering.

Why you should ditch smart numbering in your product data management

Easier than intelligent numbering

Adding new products is quick and easy.

Users don’t have to remember extra information about meaning behind product numbers

They can use other dimensions in the ERP system for search and reporting.

No single point of failure (or bottlenecks)

Multiple users can work with products in the system, and they don’t have to ask someone what the numbers mean.

Easy to maintain

Has your brand expanded into dog beds, home furnishings, or hair products? No problem. Configuring new dimensions is easier and faster than rethinking your numbering schema for your entire product catalog.

Improve part or product lifecycle management

If product information changes, the number doesn’t have to.

Easier to merge new product catalogs

Product catalogs from different companies or acquisitions can be merged without losing information.

Ease of reporting

Advanced reporting like data mining, automated queries, and business analytics is easier to do with simple product IDs.

Other considerations for intelligent numbering and ERP systems

A new systems implementation is a complete paradigm shift for your business. Like we discuss in product attributes, an ERP project is an opportunity for you to cleanse your data and setup a new master data structure that works for you. Changing these data entities is a big deal and requires a solid change management strategy.

Analyst Reports: Read what industry experts say about Microsoft cloud solutions

Nucleus Research ERP Technology Value Matrix

The ERP Value Matrix reflects the continued shift to the cloud, with vendors seeing accelerated adoption rates. Microsoft continues in its Leader position with Microsoft Dynamics 365 for Finance and Supply Chain, Enterprise Edition. All the enterprise capabilities in Microsoft Dynamics for Finance and Supply Chain, Enterprise edition are underpinned by Microsoft’s global delivery strategy that includes 36 geographies and over 60 language localizations. Additionally, the Microsoft business application platform delivers capabilities such as Power Apps, Power BI, Power Automate, and the Microsoft Dataverse (formerly Common Data Service), helping customers better collect and analyze their data as well as build applications to automate manual tasks.

Microsoft, A Leader in the Magic Quadrant for Cloud ERP

Product-centric organizations are increasingly adopting cloud ERP platforms to standardize operations and drive intelligent automation. The 2025 Gartner® Magic Quadrant™ recognizes Microsoft as a Leader for its ongoing innovation and proven ability to support scalable, composable transformation across finance and operations.

The Total Economic Impact™ of Microsoft Dynamics Supply Chain

Microsoft Dynamics 365 Supply Chain Management addresses key supply chain challenges. These include limited visibility, adapting to changing customer demands, outdated systems, and disruptions. The solution enhances visibility across the supply chain network, enabling better planning, agility, and asset uptime optimization, ensuring smooth operations even during disruptions. Forrester Consulting conducted a Total Economic Impact™ (TEI) study to assess the potential ROI of deploying Dynamics 365 Supply Chain Management. The investment led to significant benefits, including:

Increased production volume capacity by 10% to 15% due to faster time-to-market.
Enhanced operational efficiency with a 2% to 3% reduction in unplanned machine downtime, worth over $1.5 million over three years and 500 manufacturing machines.
Increased developer productivity by 10% to 50%, reallocating developer time for higher-value tasks.
A 5% boost in revenue attributed to improved product quality, translating to more than $6.8 million in three years.
Infrastructure footprint consolidation of 35% to 65% by shifting from on-premises to cloud solutions, saving close to $11 million over three years.

The Total Economic Impact™ of Microsoft Dynamics Finance

Microsoft commissioned Forrester Consulting to conduct a Total Economic Impact™ (TEI) study and examine the potential return on investment (ROI) enterprises may realize by deploying Microsoft Dynamics 365 Finance. The purpose of this study is to provide readers with a framework to evaluate the potential financial impact of Dynamics 365 Finance on their organizations.

To better understand the benefits, costs, and risks associated with this investment, Forrester interviewed four representatives with experience using Dynamics 365 Finance. For the purposes of this study, Forrester aggregated the interviewees’ experiences and combined the results into a single composite organization that is a retail and wholesale organization with 120 finance personnel and revenue of $750 million per year.

Above Average ROI from Dynamics 365

In analyzing the results of Microsoft Dynamics 365 deployments, Nucleus found that for every dollar spent, companies realized an average of $16.97 in returns. This is significantly higher than the average for both enterprise resource planning (ERP) and customer relationship management (CRM), which deliver, on average, $7.23 and $8.71 respectively. Nucleus found that companies taking advantage of Microsoft’s investments in cloud and usability, as well as integration and analytics, were able to achieve significant returns by increasing productivity and revenues and reducing costs. Microsoft’s integration of business capabilities such as ERP, CRM, and HCM with Office 365, Power BI, Power Platform, and Azure offer even greater value than the industry averages and as Microsoft makes further investments in integration and innovation, customers will benefit from the additional value provided by the cloud platform.

The Total Economic Impact™ of Power Apps

Adopting Power Apps can transform a company’s IT function from a blocker to an enabler. One interviewee in the Forrester Total Economic Impact Study said: “We can now build once and deploy to different places….We can now make changes on the fly and support a very dynamic business.” Benefits included:

74 percent less cost to develop an application
188 percent ROI over 3 years, with a net present value of $6.1 million
Average payback period is less than 6 months

The Digital Commerce Imperative

A staggering seventy-six percent of retail and CPG decision-makers agree that improving digital commerce capabilities is their most urgent business priority. And yet for many organizations running on legacy or disparate systems, this goal is far out of reach. Microsoft commissioned Forrester to evaluate how retail and CPG companies are approaching digital commerce improvements today. In this thought leadership report, read key insights about the state of the retail and CPG industries in a post-pandemic world, and how technology leaders plan to invest to make true unified commerce a reality.

The Total Economic Impact™ Of Microsoft Dynamics 365 For Finance And Operations

Cloud simplicity, gained agility, improved user adoption, and enhanced security were a few of the benefits of Microsoft Dynamics 365 Finance and Operations. The quantitative benefits over a three year period included:

Increased wholesale revenue by 3 percent, retail revenue by 4 percent and decreased excess inventory and shrinkage by 10 percent
Operational efficiencies reduced cost of goods sold by 10 percent and improved gross margin by 2.4 percent
Employee productivity gains reduced shop floor staffing by 6 percent, increased finance productive by 20 percent, and increased sales productivity by 4 percent
Total benefits resulted in a 60 percent ROI and a 20 month payback period, including legacy license, maintenance, hardware, and admin cost avoidance

The Total Economic Impact™ of Microsoft Dynamics Commerce

Dynamics 365 Commerce provides a seamless shopping experience across physical and digital channels. Customers using a network of disparate and inflexible legacy solutions stand to save significant time and money by moving to an integrated omni-channel solution like Commerce. Forrester’s Total Economic Impact study of Dynamics 365 Commerce found:

Improved inventory management to the tune of $3.7 million
Saved $1.9 million through decreased training time
Increased brick and mortar sales by $1.5 million
25 percent eCommerce sales uplift
Payback period of only 17 months

Microsoft Security a Leader in 5 Magic Quadrants

Gartner has named Microsoft Security a Leader in five Magic Quadrants. This is exciting news that we believe speaks to the breadth and depth of our security offerings. Microsoft was identified as a Leader in the following five security areas:

Cloud Access Security Broker (CASB) solutions
Access Management
Enterprise Information Archiving
Unified Endpoint Management (UEM) tools
Endpoint Protection Platforms

The Total Economic Impact™ Of Microsoft Azure IaaS

Microsoft commissioned Forrester Consulting to conduct a study to examine the potential return on investment (ROI) enterprises may realize by shifting some or all their management and operations from on-premises, hosted, and outsourced implementations to Azure’s infrastructure-as-a-service (IaaS) offering. Benefits included:

Improved production efficiency
Reduced datacenter, IT resource, and outsourcing costs
Easier and faster software and hardware management (such as patching and support)

A Platform for Today, Tomorrow, and Decades from Now

Microsoft offers a complete platform at a tremendous value. When you consider the billions of dollars invested in research and development, cloud growth, and long term viability, an investment in Microsoft makes long term sense.

You Just Went Live...Now What?

Data migration issues — the first wave

Special cases

Helping new users

Avoid the “Valley of Despair”

Frequently asked questions

Further Reading

Start Your Journey with Sunrise Today!

To Customize, or Not to Customize?

Table of Contents

Understanding When to Customize Your ERP System

Gap-Fit Analysis: Identifying When Customizations Are Necessary

Strategic Factors to Consider Before Customizing

Adding Value to the Organization

Streamlining Processes

Exploring Low-Code Alternatives

Evaluating the Long-Term Feasibility of Customizations

Everything You Need For A

SUCCESSFUL IMPLEMENTATION

Ready for your tailored ERP solution?

Supply Chain Rebound—Back On Track, But Better: 3 Ways To Improve Visibility And Agility

Start Your Journey with Sunrise Today!

Don't underestimate data migration

ERP implementations are tough

Data migration can make or break your implementation

Selecting a strategy for data migration

Cleaning the data

Data validation

Frequently asked questions

Further Reading

Start Your Journey with Sunrise Today!

What kills an ERP project?

More than just an ERP project

How executives can play a crucial role

Why meetings are so important

Frequently asked questions

Further Reading

Start Your Journey with Sunrise Today!

Soft and hard allocation: understanding the difference

If hard allocation is the hammer and nails of supply chain, soft allocation is like magnets and a whiteboard.

Defining soft and hard allocation

Key differences between hard and soft allocation

Soft allocation

Hard allocation

Challenges in the planning process

How soft allocation helps you manage your supply chain

Further Reading

Start Your Journey with Sunrise Today!

Don't be afraid of continuous updates

The new ERP update model

Prioritize the most essential business functions

Focus on testing customizations and extensions

How to handle integration testing

For inbound messages: have a set of sample data prepped before you start

In your test environment: push the sample data through the system (with the new updates) and see what happens.

For outbound messages: export your data in XML format and use file comparison tools to see if anything changed from the new updates.

Use automation to keep up with updates

Checklist for testing ERP updates

Further Reading

See how Dynamics 365 handles inventory management

Remove season codes from style numbers for better inventory management

The importance of seasonal products for brands

Optimize inventory with season codes

Embedded season codes in style numbers cause problems

Problem 1: If you decide to sell across seasons, you need to create new style numbers for the same product

Problem 2: Carried-over styles need new color and size product variants

Problem 3: You must complete inventory transfers for the new SKUs.

Last season doesn’t really mean last season (for styles)

When the product was designed?

When the product was manufactured?

The selling season for the product?

A better way to manage seasonal inventory

Further Reading

Start Your Journey with Sunrise Today!

What should your product numbers mean?

Intelligent product numbers

Why smart numbering is no longer a best practice

Trade smart numbers for a smarter system

Why you should ditch smart numbering in your product data management

Other considerations for intelligent numbering and ERP systems

What should
your product numbers mean?