Warehouse Extension for Dynamics GP: Barcoding, Allocation, Replenishment

First approach is to implement brand name standalone WMS and then establish integration in the form of connectors to send scanned documents to your ERP Sales, Purchasing and Inventory modules.  Typically such brand name products have connectors to numerous mid-market and high end ERP and Accounting packages, including Great Plains.  Second approach is to implement something that extends existing functionality in GP to enable barcoding in Sales, Inventory and Purchasing directly.  We would like to compare the two and give you additional details on the second option, where direct enabling is recommended:

1. External WMS versus GP extensions.  External system might have hidden cost, as it typically produces the logic, already available in Great Plains: Order Allocation in Sales Order Processing document, Restocking in POP Purchase Receipt, Inventory Transfers and Counts in Inventory control.  When you purchased parallel functionality in WMS and GP – there is the question about paying for software licenses twice.  Second point to think about is where do you want to keep primary record for such document as Fulfilled Order – in your Corporate ERP or Warehouse System?  And it might be a bit personal opinion level question, but we heard some complaints from the customers who tried implement standalone WMS with integration to SOP, POP and Inventory and they got the feeling down the road, that connectors are not really ready for going into production (some custom programming, and testing was required, and this fact triggered additional unexpected initially budget).  There are certain pluses in external application, such as high number of implemented cases, compatibility with major Barcode Scanners and RFID readers.  High volume of installations typically means that you are not exposed to software bugs and known issues are already reported by other customers and resolved.  WMS extensions are preserving your investments into GP licenses, plus they are naturally integrated.  But due to the fact, that extensions have to be native to only one Corporate ERP platform Dynamics GP – the number of installations is lower.  Let’s now take a look at Warehouse Management logic and how it is implemented in Extensions

2. Allocation or Fulfillment.  Such SOP documents as Order or Invoice could have either automatic item line allocation or manual.  When you plan to scan Barcode label on the warehouse floor, you typically expect that Sales Order is already created, items are entered, but they are waiting for being fulfilled.  This is why you select manual allocation for SOP type.  You scan the label or RFID tag and send the information about the scanned merchandise to the SOP Order Line to be allocated (this process could include such important features as lot or serial numbers, warehouse ID, bins, if substitute items were taken, user category, etc.)

3. Restocking often also referred as Replenishment.  There are powerful methods in GP to reorder items based on their existing quantities, ABC codes, economy order size and other mathematically accurate calculations, defined in Purchasing Configurator.  If you created Purchase Order either manually or via Configurator (or in Manufacturing Suite of modules), then Purchase Receipts could be done in WMS extensions.  When you receive items by barcode scanning you transmit to GP Item number, quantity, in which warehouse it is going, serial and lot number, and additional features

4. Merchandise move from one Warehouse to Another, Stock Count.  These processes should be done in inventory transactions by enabling them for Barcoding

5. Budget, Version Upgrade Considerations.  Warehouse Management software licenses and implementation hours costs could be comparable to Great Plains modules owned pricelist.  With this observation we strongly recommend you to be on the current version of GP.  As we are writing these lines in May 2011 current version is 2010, also referred as 11.0 (in Microsoft Dexterity).  The price for you to upgrade to 2010 or maybe version 10.0 is a fraction of Price List, but the hidden cost to find programmer or consultants who are still familiar and comfortable to customize or code integration to the older version is a risk factor.  Historically Great Plains came to us through the following versions: 9.0, 8.0, 7.5, 7.0, 6.0, 5.5, 5.0, 4.0, 3.2 – all these versions could be updated to the current release of 2010/11.0

6. Possible customization requirements.  Each business has unique features, allowing it to compete on the market.  Uniqueness might be associated with modification requirements.  In the case of direct WMS extensions, customizing your accounting application is not a problem and you can deploy such tools, as Microsoft Dexterity, Modifier with VBA, Extender, eConnect, SQL Stored Procedures and scripts

7. Implementation and Support options.  Specialized modules are typically implemented with Nationwide and even International travel and short term local implementation phase with following remote support via web sessions and phone conferences.  As we analyze customers geography – it is scattered proportionally across the business metros in USA, Canada and internationally.  There is cluster of customers in Latin America, Arabic peninsula

8. For additional information, please feel free to call us 1-866-528-0577 or 1-630-961-5918 (this number works for international customers) or email us help@albaspectrum.com We serve you USA/Canada nationwide via remote support (web sessions and phone/Skype conferences). Local service is available in Western Michigan, Chicagoland, Southern California (LA, Orange County, San Diego), Houston area of the state of Texas