The website application requests data out of SAGE on a scheduled basis, which populates the website database. Having this one way publish of data means that the website can continue operating when the connection to SAGE is lost, and means that SAGE itself isn't facing the burden of having lots of users querying the data directly. Only the data that is required is published, so that, for instance, customer data that may be private, doesn't find its way into the public domain.
In addition to the data that comes out of SAGE, the website caters for extending that product data to support the more marketing focussed requirements of the website. For example, where a product description in SAGE may be technical for internal purposes, on the website, this needs to be friendly, readable and marketable. SAGE doesn't have somewhere to save this second description, and so the extended data is added via the Website Administration Tool just for use on the website to describe the product more effectively.
The website itself will also collect data, such as basket items and user statistics which is either transient or permanent and can be used to provide key in-depth reports .
The data used on the website is uploaded into the website database, and linked directly into SAGE to get/submit live data, which might be a customer creating a new account, an order being submitted or up to date stock information being checked and displayed. The website can make use of Business to Business functions such as getting a statement, or can be tailored to be specific to consumers, or both. The website links in with a Payment Gateway so that payments can be processed securely and in adherence of the PCI DSS guidelines, or if preferred, orders can simply be submitted 'On Account', if the business rules/customer credit allows it.
Download Orderline V200 Brochure
View Orderline V200 Feature List
For a truly integrated solution it is important that Product, Customer and Order data is held in SAGE 200. This single source of data means less maintenance (updating two separate places with the same data), less chance of human error (e.g. when re-inputting orders) and a quicker processing of orders. To allow integration with a website, SAGE must be made available to the webserver that holds the website. We achieve this using a strict Firewall setup and a VPN that allows restricted access to the SAGE database from the webserver which may be hosted remotely at an Internet Service Provider, or in some cases 'in-house'.