News

Readysell “Isaac” May 2021 update

We’re pleased to announce that Readysell 8.59 (codename “Isaac”) is rolling out progressively to all of our Readysell 8 customers. This release is focused on implementing some important service enhancements, improvements to the framework of the whole application, and actioning bugs that have been reported over the last period.

New feature Development

16038 – Users can now generate, print and scan barcodes from cards to be used in sale transactions. This label can be downloaded from Readysell Store. “Card Label”

15570 – Added the ability to use variables in email batch template subject line.

16053 – Readysell Import/Export now allows users to import service call activities into an existing service call.

15838 – oData v3 is now importing new fields (Details, Specification, UNSPSC) to the price book and product details.

15970 – If a card’s default site is changed, Readysell now sends the previous site as ‘Inactive’ and the new site as ‘Active’ to external core systems (where implemented) through the ‘Business Intelligence’ task.

16044 – Email batch for Sale Quotes, now includes a URL link to web for customer to modify product quantity in quote

15562 – Added new fields ‘Price Import Adjustment Factor’ on Product, and ‘Cost Import Adjustment Factor’ on Product Supplier, for multiply or divide Sell Price/Cost when doing an import from Group or Suppliers.

Bug Fixed:

15923 – Barcodes are now being added to products when importing from a DDO or DD2 file.

16035 – We have fixed an issue where some product images were not getting fetched from the web.

16058 – While creating a service order – if a machine and technician were assigned – an issue resulted where the event would appear on the schedule without the machine’s location. This has been resolved, and the machine location now appears on the schedule.

16074 – We have Increased the maximum allowed character length for the following fields in ‘Bank Reconciliation’: ‘Payment reference’; ‘Matched reference’, and ‘Search reference’. We have also increased the maximum allowed length for the column named ’Default Order Unit Code’ for product suppliers in the price book

16060 – An issue was identified where POS was missing the Customer on an Order after it was converted from a Sale. This issue now has been fixed.

16014 – A one-cent discrepancy was identified between a web order and a Readysell order after it was imported. This issue now has been fixed. Readysell will create another sale order line called ‘Rounding’.

KeyPay – Important changes to the definition of ‘Active Employee’ for billing purposes – please read

Attention all KeyPay users: Important changes to the definition of ‘Active Employee’ for billing purposes – please read

This alert is to inform you of some planned changes that may affect how you are charged for use of the KeyPay platform in the near future.  

KeyPay’s current billing model defines an ‘active employee’ as an employee who has been included in a finalised pay run at least once within our billing cycle. Unfortunately, this has led to a small number of users significantly exploiting a loophole to avoid paying for use of the payroll platform.

This problem has prompted KeyPay to change their definition of an ‘active employee’:

Please note that the previous KeyPay correspondence was missing the action regarding ‘approved timesheet’; we apologise for any confusion this may have caused

An employee will be considered ‘active’ when at least one of the following actions have been completed for that employee during the billing cycle:

  • Included in a finalised pay run
  • Has had an approved leave request                        
  • Has had an approved expense request
  • Has had a published roster shift  
  • Has had an approved timesheet

Please note that if a user unlocks the pay run in any given month, any of the actions above are still counted towards an ‘active employee’.

This change will come into effect from the 1st of July 2021. You will see the change (if there is one) on the invoice you receive on the 1st of August 2021.

Please notify the other areas of your business that need to be made aware of this change. Feel free to reach out to me if you have any questions or concerns about this.

Readysell “Hastings” April 2021 update

We’re pleased to announce that Readysell 8.59 (codename “Hastings”) is rolling out progressively to all of our Readysell 8 customers. This release is focused on implementing some important service enhancements, improvements to the framework of the whole application, and actioning bugs that have been reported over the last period.

New feature Development

15997 – We’ve added a new field “Number of students” Student in Sales Quotes. Once a sales quote is converted into a sales order, the Product Sale Quantity field will be multiplied by the Number of Students.

15995 – Education project: New executable form report: F-147 Sale Quote EDU Report (By Supplier)

15994 – Education project: New Standard note button on sale order and quote

15987 (applicable to particular customers) – POS Gift voucher: when a user opens a completed order, POS will pop up warning if any gift voucher sales without voucher number and user can click the warning to send the voucher number to Readysell support team.

16046 – Users can now generate, print, and scan barcodes from a product’s Oid – to be used in the same way as existing product labels

Bug Fixed:

15759 – We fixed an issue where the product feed from Ingram Micro was too large and needed to be broken into smaller feeds.

15760 –  RS3 Product Import was not updating the quantity on hand or cost price for product suppliers in the Pricebook and product file. This issue has been fixed.

16072 – RS3 Product Import was overriding the cost price for primary suppliers in the Pricebook. This has been fixed.

16047 – Clicking the Extract banking button multiple times on the Bank Reconciliation will result in duplicate bank reconciliation lines to appear. This issue has been fixed

15988 (applicable to particular customers) – An issue was identified where not every web order from POS was being synced with the orders at head office.

*Note: the referenced POS is a standalone POS, only relevant for a particular set of customers. These features are not relevant to the Readysell POS functionality.

KeyPay – Important changes to the definition of ‘Active Employee’ for billing purposes – Please read

Attention all KeyPay users: Important changes to the definition of ‘Active Employee’ for billing purposes – please read

This alert is to inform you of some planned changes that may affect how you are charged for use of the KeyPay platform in the near future.  

KeyPay’s current billing model defines an ‘active employee’ as an employee who has been included in a finalised pay run at least once within our billing cycle. Unfortunately, this has led to a small number of users significantly exploiting a loophole to avoid paying for use of the payroll platform.

This problem has prompted KeyPay to change their definition of an ‘active employee’:

An employee will be considered ‘active’ when at least one of the following actions have been completed for that employee during the billing cycle:

  • Included in a finalised pay run
  • Has had an approved leave request                        
  • Has had an approved expense request
  • Has had a published roster shift  

Please note that if a user unlocks the pay run in any given month, any of the actions above are still counted towards an ‘active employee’. This change will come into effect from the 1st of July 2021. You will see the change (if there is one) on the invoice you receive on the 1st of August 2021.

Please notify the other areas of your business that need to be made aware of this change.

The Readysell Team.

Readysell “Daintree” update – Now rolling out!

We’re pleased to announce that Readysell 8.59 (codename “Daintree”) is rolling out progressively to all of our Readysell 8 customers. This release is focused on implementing some important service enhancements, improvements to the framework of the whole application, and actioning bugs that have been reported over the last period.

Readysell framework improvements:

We’ve added some small improvements to some of our commonly used Readysell features, by updating the development framework. This includes new security options like ‘security over users accessing buttons’. These enhancements also include improvements to the filter editor. There are a lot of small changes in this framework update that will make filtering, colouring and accessing your Readysell data a little easier.

Service module enhancements:

  • Service orders. We’ve listened to our service module users and added a lot of enhancements around service orders. These include linking service orders and sale orders; copying sale orders to/from service orders, and quite a few more. The enhancements were covered in our recent service training session. Please let us know if you would like a link to the training video (or an invitation to any of our future training sessions)
  • Staff schedule. We have improved the staff schedule, making it easier to drag service calls between staff members and to reschedule service team members with the staff schedule.
  • Numerical sorting of Machines. You can now sort your machines in numerical order. We have added a read-only field that shows the MachineID as a number, meaning you don’t have to pad the MachineID with zero’s just to get machines to sort in numerical order by MachineID.

WebX website integration improvements

  • We now always try to grab images live for WebX users. Preventing older images on your hard drive, such as old diary images from displaying
  • Removed rounding issues when importing from the booklist or Paypal prepayments from your website
  • Improved the product sync functionality

But wait, there’s more…

We’ve also made a number of other improvements and under-the-hood changes. Here’s a full list. If you’d like more details about any of the below items, please don’t hesitate to get in touch with us through the Readysell Helpdesk.

  15587 Added an Action Button ‘Show Related’ from the service order that has a linked Schedule
15589 When changing or moving the tech, date and/or time on the staff schedule for a service order, update the service order
15590 Create a new staff schedule for a service order, once the first service order call is finalised if a further service call is created for that service order for a technician.
15591 Staff Schedule customisation to show a date from a specific start and end time instead of from 12am to 11.59pm
15592 Staff Schedule report to reflect the date and time of the staff schedule if it has been customised
15615 Action button ‘Accept Quote’ in Service Order Quote should behave the same way as Accept Quote in Sales Order Quote
15716 Update Readysell to DevExpress framework 20.1
15748 Add a button to allow a machine to be added to a contract
15779 Service Order to reflect the manual non stock product costing method like Sales Orders
15785 Fail “AppEndSaleShipmentPicking” has no reference of the error in Messages
15810 Service orders converted from Quotes do not copy manual prices
15811 Provide API access to modify service orders
15812 Add the ability to copy a Sale Quote to a Service Quote and vice versa
15813 Add two-way links between sale orders and service orders
15816 Tidy up staff schedule
15823 Machine average meter count incorrect when resold
15828 WB POS sale of Gift vouchers with no transaction gift voucher number
15830 Last Run product Sync – OB
15832 Create a Description field in Delivery Module
15846 Create a persisted field re-sorting machineID, allowing you to sort lists of machines in numerical order.
15847 Bug Fixes re Styles
15848 Increase the name of web categories from 40 to 80 characters
15849 Increase the length of the txt field and customer reference on bank statement line
15850 Change the API for importing web orders to trim customer order data where it is longer than 40 characters
15853 web order issues occurring where customer order and cost centre fields are longer on the web but only 40 characters in Readysell
15860 Add a read-only date field “BIDateLastUploaded” to sale invoices
15867 Improved Office Choice product import for promotions
15870 booklist order is not dropping in with eway payment on it.  It drops into Sales orders module without payment
15874 Auto Sale Runs error rectified
15877 Web order is importing with the wrong site on it. The store has 2 sites
15885 Paypal Order Payment Values incorrect in Readysell due to one cent differences in some cases
15889 Web Orders – If there is a balance on the Salweb do not allow HO to send it to the POS Site.
15892 Voucher number does not attached to sale order from web order
15901 OB Product get Image from web is now live all the time
15917 Change the colour and size selections in Styles to filter out archived colours and sizes in Styles
15922 Office Choice Task product Import check file exists before download
15928 Sale shipment line site must sync with sale shipment header site
15936 Purchase Receipt validation window popping up after hitting action button
15945 Error when starting Readysell from recent update with a Sales Dashboard screen

2021 is looking up!

We are well on the way into the year, and there’s plenty in store from Readysell:

  • The next Readysell update “Daintree” is rolling out starting today – which brings quite a few tweaks and fixes, as well as some, requested new features such as Service orders, Staff scheduling, and Numerical sorting of Machines. (plus quite a few more)
  • We have another update coming in a couple of weeks, and a ‘speed’ update coming around mid-March.
  • User Group and Training Sessions have kicked off for the new year, and the feedback has been great! If you – or your team – aren’t already enrolled for these, reach out to Mat Unwin (mathewu@readysell.com.au) and get on the invite list. These sessions are free, and provide you with an opportunity to not only up-skill on Readysell functionality but also have a say in our development and priority roadmap.
  • We have a lot more in the plan for the next 12 months, so stay tuned, and we will update you ASAP.

The Readysell Team.

Readysell operating arrangements for Labour Day Public holiday

Dear Readysell customers,

On the 5th of October, Queensland, the Australian Capital Territory, New South Wales, and South Australia will be observing the Labour Day public holiday. As the Readysell head office is located in New South Wales, the office will be closed, but our normal ‘after-hours’ support is available for critical issues. We will have a staff member on call to respond to any critical issues that arise.

Update on GNS integration with Readysell

Good afternoon everyone,

Over the weekend it became apparent that there was an issue with the integration between GNS and Readysell – because of a change that GNS affected to their systems on Friday. 

Readysell has worked with GNS and we are pleased to announce we now have a solution get GNS EDI integration from Readysell working again! The solution must be setup at each business individually. Shannon, on our support team, has already started rolling out the change to some businesses today – starting with those businesses that have put in support tickets. Shannon will continue to roll out the change (including to your business) over the next few working days.

In the meantime, until the change is rolled out to your business, the workaround to this issue is still to send purchase orders to GNS via email. Use the “Send” button on purchase orders or email batches to send your purchase orders to GNS via email.

If you have any questions or if you need any further assistance. Please contact Readysell support.

Update on GNS integration with Readysell

Good afternoon everyone,

Over the weekend it became apparent that there was an issue with the integration between GNS and Readysell – because of a change that GNS affected to their systems on Friday. At the current moment, this latest change is not allowing our customers to send their purchase orders via EDI to GNS.

GNS informed us late on Friday of the change they had made to their system and gave our team instructions on the minimal changes required to Readysell in order to ensure that the systems continued to operate together. While our team made the requested changes immediately, unfortunately these did not work as we were told, and issues arose with this functionality over the weekend.

GNS are currently working on a resolution, and our team will be communicating with them constantly, to ensure the duration of this issue is as short as possible. We will update you all as the fix progresses.

In the meantime, the workaround to this issue is to send purchase orders to GNS via email. Use the “Send” button on purchase orders or email batches to send your purchase orders to GNS via email.