To check the version of commercebuild Payments that your system is running, click the Start button, type “Add or remove programs” and then click the match that appears: Once the window ope...

commercebuild’s Sync Agent, which replicates data from the SQL Server used by Sage 300, relies on change tracking being enabled on the database, as well as on the tables. For more information ab...

Note: credit card fee is not the same as pre-auth increase. Pre-auth increase is a buffer (or a floating amount) that is added to the pre-authorization on the card via the payment gateway settings whe...

For your commercebuild web store to integrate seamlessly with Sage 300, our web store user should have full access to the following modules: OE (Order Entry) AR (Accounts Receivable) AP (Accounts Paya...

If there is a price discrepancy on a Sage 300 web store, our team will request that you show the price for the item(s) in question through Order Entry in Sage 300. To provide us this information, open...

commercebuild Payments simplifies capturing preauthorizations in Sage 300 web stores. To learn how to capture a preauthorization, please watch the video below.

If you are seeing errors under /admin/Msystem_notifications regarding Paya Connect Desktop (Sage Exchange Desktop) Client Not Running, here are the steps to get that running again. Open Symphony Clien...

If your webstore is unable to connect to the server (for example, you are seeing “No SSH Connection” errors) follow these steps to restart the service. Start or Restart Symphony Client Ser...

When adding new items to your commercebuild store, there are a few steps that must be taken to make them active and accessible online. Navigate to Catalog > Products and search for a product to che...

In the web store, you or your customers may see the following error messages when attempting to check out: CUSTOMER DISABLED This account has been disabled, please contact the site administrator to ac...