When deciding upon a new integrated eCommerce solution, implementing the integration with your ERP is as important as the front-end software itself. Based on our experiences in past projects, we wanted to present a few “key learnings” that should make the process go a little smoother.
Learning #1: Efficiently Exposing Key Data
When working with the latest generation of cloud ERP’s, we consume data with web services instead of SQL or local XML interfaces. Typically, your team will be responsible for exposing web services with our team during the installation. Any data stored and maintained in the ERP is essential to the new site. Pricing, items, customer data, etc., might need to be included in the particular web service you will expose.
Learning #2: Access to the Database Server
Our connections team can troubleshoot issues quicker if they have access to your ERP SQL Database Server for the On-Prem ERP’s that we support. With proper permissions and access, we can go into your client-server, look at the database, and change things quickly.
Learning # 3: Know your Data
One of the most significant benefits of Nomad is the ability to leverage ERP data for use on your site with flexibility and extensible business logic. It is beneficial to have your technical resource available to assist us with your data, pointing us in the right direction with where the data is and where it should live on the website. Having someone that can assist us in navigating where specific information is in your ERP is crucial.
Learning #4: Have a Plan for Pricing
When users come to your site, they expect to see their pricing. On a typical B2C site, pricing tends to be configured to match your list pricing or MSRP. On a B2B site, your customers usually have to log in to see their pricing. Complex customer pricing on the backend may require some extensions of our connector logic after discussion with your technical resources and subject matter experts. Nomad can get pricing rules from the ERP, but the pricing needs to be set up and available in the ERP to get implemented. Having a plan on how your pricing gets synced to the website and where that information is stored is key. Also, knowing how to maintain your pricing going forward is a great way to save time, money, and employee resources. We have different options on how to get access to pricing data, even if it’s not in the ERP. We recommend discussing complex customer pricing upfront and early in the project.
Although these 4 Learnings, as we call them, might not seem that impactful, each can save a crucial amount of time. By incorporating these into your execution plan, we can ensure that we get you running on Nomad as efficiently as possible.