FIRST STEP: Decide what’s in and complete Training Manual (Functional Design)

This documentation explains a lot of possibilities for integrating your ePos/ERP with your AB Commerce website.  However, not all of this will be possible due to limitations that each ePos/ERP has.

The Ideal – Fully managed from ePos/ERP

In an ideal situation, all product information would be managed through the ePos/ERP – with only the product imagery being uploaded outside the ePos/ERP.

What are the important parts

However, if this is not possible, the following are the important functionality to achieve:

• New products are automatically uploaded to the website.
• All price changes are automatically updated on the website.
• All stock changes are automatically updated on the website.

Remember, for any fields that you cant send to AB Commerce, AB Commerce will still have optional manual edit screens to allow the website admin maintain these fields outside the ePos/ERP.

First Step – Complete the technical spec and functional spec / training manual

So before any development begins, you should complete the functional specification – i.e. what functionality in the ePos/ERP will we enable to allow management of the website content?

And if this functional spec is done in the form of a training manual called “How to Update the website through the ePos/ERP”, this could then be used by the people responsible for maintaining the website going forward.

Once this is complete, then the developer knows what parts he/she needs to use to implement it.

The section “TEMPLATES – Technical Spec Checklist & Training Manual” contains a template for a technical spec in the form of a checklist, which you should fill in before completing the training manual – and a template for the training manual.