Easily sync customers & orders from WooCommerce to Sage ERP 100 (or MAS 90/200) via the eBusiness Web Services API.

This plugin pushes customers and orders from WooCommerce into Sage ERP 100 via the eBusiness Web Services API. After initial setup & configuration, you can select orders in bulk to export to Sage. Customers will be created if they do not exist and a sales order will be created for each order. The Sales Order number will be returned and used as the order number with WooCommerce. There are filters available to customize the customer and order data sent to Sage.

• WordPress 4.0 (tested up to 4.2.2)
• Sage ERP 100 or MAS 90/200 (including SQL)
• Sage eBusiness Web Services API module (ERP 100 2014 includes this, if you are using an older version you must purchase it from Sage)
• (optional) Sage eBusiness Web Services Extended API if you're using a SQL version of Sage ERP and would like automatic postal code creation (see FAQ)

• Download the ZIP and upload to your /wp-content/plugins directory
• Activate the plugin through the 'Plugins' menu in WordPress

• Configure the Sage eBusiness Web Services API and expose a public endpoint. This is beyond the scope of this readme, but you can follow the excellent walk-through provided by Sage here. You'll need to also create a specific Sage user to use with the API as part of this configuration.

• In WooCommerce, browse to WooCommerce > Integrations > Sage ERP Connector and enter your API endpoint, along with the username/password for the user you created.

• Enter the company code of the company you want to create customers/orders in. You'll also need to enter a division number and Salesperson number that customers & orders will be created under. Price level is required.

• Place a test order and click on the Sage icon in the Orders list to test the import. You'll likely see an error message or two that will need to be resolved first.

• Q: Is it possible to sync product stock levels from Sage? No, the Sage API does not provide any methods for retrieving item stock.

• Q: How do I customize the data that's used for creating customers and sales orders? Use the wc_sage_erp_customer, wc_sage_erp_connector_sales_order_line_item, and wc_sage_erp_connector_sales_order filters. These are best used in a custom plugin -- checkout the sample plugin for more examples.

• Q: How can I learn more about the Sage eBusiness Web Services API? You're in luck! Check out the out-of-print API guide!

Support is only provided via GitHub, please add an issue if you're experiencing an issue or bug.

Copyright (c) 2012-2015, SkyVerge, Inc. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Fork this repository and send a pull request :)

Please adhere to the WordPress Coding Standards in your contributions.