Whenever a product gets updated in Sage 300, you probably want to make sure that the inventory, pricing, and maybe other information that's critical to the business goes into Magento. But you most likely wouldn’t want to override the overall
product information in Magento, because your marketing team members may have carefully enriched or enhanced the product metadata. What you really need is an advanced queue-based persistent task engine that allows for systematic business logic
and data transformation capabilities, with respect to each task or area of integration. One of the other core entities that we usually recommend integrating between systems is to have customers and accounts go two ways. This can typically
include pulling core records from Sage 300 into Magento and whenever new customers or accounts are created, they go from Magento into Sage 300.
The fundamental need for certain business logic is apparent, to ensure that information isn’t needlessly duplicated and replicated. In this manner, it's also critical to handle user associations properly, so that when a new user gets created
in Magento but already exists inside of Sage 300, the correct user association occurs. With a customer and account integration, we're inevitably looking at core customer data, address information (billing, shipping, and primary), as well as
contacts. There might be a single contact or hundreds -even thousands- of contacts that have relevant pricing information that is specific to the account.
Other information that can be integrated among systems includes tax levels and different locations. Regarding locations, the associated business logic per each distinct location may also be incorporated, namely: pricing, credit limits by
location, a tax exemption status, and past order history (which could drive available replacement parts). The higher idea essentially involves a general two-way integration and syncing for customers and accounts. In practice, whenever a new
Magento user is created the information gets pumped into Sage 300, where it searches for an associated account. This process is possibly based on the domain name, address information, phone number, or other verification rules, to perform the
association and link back to the Sage 300 account.