July 18, 2024

First of all we would like to share with you our believes that ecommerce shopping carts, such as Magento/PHP (especially when you are on Linux), ASP.Net Storefront, Nop Commerce and others, are pretty robust and there is no real need to program shopping cart from scratch internally (until you are really huge ecommerce wholesaler or retailer, where you prefer to have complete control over program proprietary business logic and source code, and have the budget to afford that kind of luxury approach). In our case, we tried to give you ecommerce add-on for Microsoft Dynamics GP (often referred by its historical name Great Plains Dynamics and eEnterprise, in case if you have some confusion with the application name) where you simply follow setup wizard, selecting your ecommerce shopping cart name from drop down list on one of the initial steps. Other steps are specific to Dynamics GP typical integration with ecommerce: settings in Inventory Control, Sales order Processing modules:
1. Ecommerce Shopping Cart Image in Great Plains. It is typically Sales Order Processing Invoice or Sales Order with Customer Deposit in the form of Credit Card payment (especially in B2C scenario, while in B2B scenario you may sell on account, and prepayment is optional). If you plan to allocate Invoice or Order lines automatically directly from the Shopping Cart, you need to specify default ecommerce SOP Document ID as the one with automatic allocation (in this case item line fulfillment happens instantly as ecommerce document is transferred to GP). If you would rather prefer to fulfill the lines via Warehouse Management System/Barcoding on the warehouse floor, then pick document ID where allocation is set to manual. Second important concept is default ecommerce Inventory Site ID – in Great Plains it is important to have default settings to minimize data entry per document. In the case of Sales Order Processing document each one may have default site ID, and if it is specified – each line will be automatically allocated (or assigned for manual fulfillment) from the specified site. Inventory control hosted Site object is participating in the logic is such distribution modules as Sales Order Processing, Purchase Order Processing, Bill of Materials, Manufacturing Suite of Modules, Invoicing (this module however is rather legacy, we do not recommend it for serious consideration in eCommerce implementation)
2. eCommerce and Non-inventory items. For eCommerce development agency smaller ecommerce retailers, especially specializing in very volatile (changing every week or month) reselling catalogues of items, you may decide to completely abandon such Inventory Control features as Quantity on-hand, returned, damaged, in-service and only track items sold through Sales Reports (based on SOP30200 and SOP30300 tables – document header and line history). If you transform your ecommerce shopping cart document lines into non-inventory items in Dynamics GP SOP – item id is simply capitalized text (or flow of the characters), then description is the combination of Capital/Small letters, digits and delimiting characters, plus there is no pricelist (you must specify QTY sold, price and cost if known)
3. eCommerce integration technology. Our Add-on ecommerce module is based on Alba Spectrum proprietary technology Order Connector. According to our performance tests, Order Connector is more efficient, comparing to Dynamics GP SDK eConnect (both technologies as based on SQL stored procedures, however Order Connector is geared toward light weight Sales Order Processing transaction logic, where eConnect validates 100% of the Dynamics GP SOP business logic, which might contribute to longer stored procedures execution time and in our opinion and taking into consideration the set of processes in ecommerce add-on module – only some of the business logic must be validated, the rest of the logic realm is really optional)