Here’s what we've been working on to make ParagonERP work better for you.
In Paragon, rules can automatically create transactions for you. For example, when you issue a packing list, a rule can be set up to automatically create a shipment for the entire quantity of the packing list. Sometimes you may not want to create a shipment for the entire quantity of the pack list, so the shipment needs to be modified after it’s automatically created. This means that there are outstanding units on the pack list that have not been shipped. These units will now be kept on the packing list as left to ship until subsequent shipments are created to fully ship all the items. This is an added layer of security that stops you from over shipping a pack or forgetting to ship it in full.
With this update, we have added the ability to convert any configured ID into a bar code. All common bar code formats are available to choose from. In the example on the right, an item SKU and pick ticket number were both turned into barcodes on the pick ticket print out.
Rules can be turned on or off in Paragon based on how you run your business. Below you can find the rules that have been created over the last two weeks. Keep in mind, however, that we have many more available.
You cannot create a transaction with items that have a zero dollar sales price. This prevents you from accidentally creating an order that does not have any prices.
You cannot create transactions whose date exceeds the current month. This prevents you from entering transactions in a month far into the future.
The total number of units on any order are shown in the “Totals” field of the header. There was a bug that caused the incorrect quantity to display here if a line item was deleted on the sales order. This has been corrected.
On a shipment, there was a column called stock adjusted. This column carries the same value as the quantity column and therefore, was removed.
Whenever you create an item or company, the first field in the upper left hand section should be the record’s unique identifier. For example, a SKU or vendor ID would be entered there. It is extremely important that this field is always filled in so we made it mandatory.
When creating a payment in the receive payment module, there will be a column called already paid. This column shows the value of the invoice that remains unpaid. There was a bug that ignored voided payments when calculating this value. If you create a payment of $10 off a $50 invoice, the already paid column on the next payment you create for the same invoice will be $10. But, if you void the original payment of $10 and create a new payment, the already paid column was still displaying $10 instead of $0. This has been corrected.
Paragon can be set up to display certain company information on the transactions. For example, a phone number stored on a customer record can automatically be displayed on a quote created for that customer. There was a bug that prevented you from setting this up, which has been corrected.