All ideas

Sometimes a small change of SKU in an ERP system is required due to product update / revision. Changing the SKU rather than creating a new one ensure that you do not lose the historical data of that item such as sales and purchasing however if we ...

Specific example - customer would like to create a report showing what products are missing weights.

Stock Messages show the name of the SKU by default but can show Stock Codes instead via a setting. Introduce another setting to show Name and Stock Code

Bundle are posted to the accounts system in two different ways but both make reporting on how often customers order bundles very difficult. Produce a report showing how often Bundles are ordered.

Features have the option of adding a description. When used in a list on a product page have a mouse over event on the name bring up the Description as an info box

To be able to define minimum quantity product purchasing per customer account, not across all accounts as now, also so can be for trade or retail or both

For example, we offer a discount off all online orders for customers but as this has no discount code applies even to Agent orders.

When an order is placed on the web site it is pushed through to Opera as a "document". This means that multiple times during the day someone has to either go into each individual account and progress the "document" to an "order" or use the batch s...

Currently if Sage description gets updated, only the matrix options descriptions get updated but the "Front" product page does not, so it means a record has to be kept and manually updated, very inefficient.

Sqaureup has proved to be much better value for us since changing over in the shop and a lot simpler around compliance.