The Story of Our Dynamics NAV Implementation in Taiwan

This is a story of our Dynamics NAV implementation in Taiwan.

One of the things that I’m most proud of is the people that choose to work with me and the company that we built.

I am proud that everyone shares the same vision on what software implementations should be. That we care about doing the right things, even if it hurts our own bottom line.

That pride is none more so apparent than our team in Taiwan. A little background, our Taiwan branch began operation in 2014. In the relative short amount of time, they developed the Chinese Language Pack for Dynamics NAV. During this time, they’re also involved in a tough implementation in Taiwan for a licensed toy distributor.

Fast-forward today, the customer in Taiwan is so happy with how their Dynamics NAV implementation went, they agreed to speak on behalf of us with Microsoft on one of the most popular IT magazines in Taiwan.

In case you can read Chinese, here’s the link:

Also in PDF version:

Dynamics NAV_麗嬰國際

Here are the highlights of the article:

– Origially had a 5 year plan to move out of the HEAVILY customized UNIX based system. We only utilized 1.5 years to implement Dynamics NAV. (According to the article, 6 months for analysis and 9 months for implementation)
– Reduce their inventory return amount up to tens of millions in local currency.
– Redesign the inventory put and pick process and increased the accuracy by at least 100%.
– Implement wireless handheld device and doubled the warehouse shipping efficiency
– Improve order process efficiency. Now it only takes one fifth of the time to proces an order (500% increase).

The Challenge

This implementation in Taiwan was indeed one of the most complicated that I’ve been involved in. Not only has their UNIX system insanely customized, but there were virtually no documentation on the operation.

Because of the type of business they’re in, they add between 10,000 to 20,000 items every month. That’s right! over 10k new items every month. You can see why order entry and communicating those new items with their large distribution network is a nightmare. In addition, think about how the warehouse will go about fulfilling these orders.

When we did our first analysis, I was personally shocked at how they were able to manage such a large volume of business with their current setup. Basically, our job was to go from no documented business process to having Dynamics NAV fully functional. The fact that our team did it in 1.5 years is nothing short of amazing.

There were countless fierce meetings and conversation both internally and with the client to better their existing business process. Even though these discussion were fierce, the client really appreciated that we did not just go with the status quo and replicate their existing business process.


Having the right people in the right place really makes all the difference in the world. This project wouldn’t be a success without their involvement. The people that works with me, quite honestly, can work anywhere else and any company; but they choose to work with me. That really gets me in the feels…

Fedex API to be Discontinued for E-Ship

In case you haven’t heard, Fedex will discontinue the use of their old API used by Lanham’s E-Ship module for Fedex Integration. The date that the old API will be discontinued will be May of 2012. While that’s still a couple of months out, it may be worthwhile to plan an upgrade of E-Ship so you can continue using the Fedex Ingration granule for Lanham without interruption when the time comes.

This is a long time coming. Fedex had already announced that they will discontinue the API a while ago. It has taken awhile for the folks at Lanham to develop the new interface to talk with Fedex.

The old Fedex API has it’s share of problems. The more notable one is that it does not support Windows 7. With new machines from Fedex shipped with Windows 7 pre-installed, I’m sure you’re IT department will be pretty happy about the update.

CORRECTION: The web service for E-Ship is NOT the NAV2009 Web services. It’s the Fedex Web Services. So this means that you can still use version 3.7A (the lowest version you have to be on) and still implement the Fedex Web Services. You WILL need to be current on the Lanham enhancement in order to use the Fedex Web Service. The version of E-Ship will need to be at least SE0.54.18.

This is yet another reason for end users to stay current on their enhancement. If you missed the “Sky’s the Limit” offer and you wish to continue shipping using Lanham’s Fedex integration, it’s time to plan for an alternative solution or get current on the enhancement by any means possible. Microsoft enhancement amnesty will end on June 30th, 2011.

You can register to see the new Fedex web services from the webinar hosted by Lanham here:
Thursday, June 23rd at 2:00 p.m. to 3:00 p.m. EST
Register Now!