Helpful reference materials

This space will provide useful advice and techniques for your role, featuring instructions on Excel formulas, guidance on using NAV, insights on the algorithm, elaborate forecasting information and more

Ordering and forecasts 

• If a SKU has a minimum order quantity (MOQ) or minimum order value (MOV), ROMA will automatically adjust the quantities. For instance, if we require a minimum of 4 toasters but require only 1 as per the forecast, ROMA will adjust the quantities to 4 to ensure the order can be received by the supplier

• Like the above with forecasts we round numbers for AOL up ( forecast of 1.2 we will order 2 ) for WA and Tasmania and Darwin orders we round down ( forecast of 1.2 units we will order 1 ) 

• Winnings do not forecast , we will only order for orders that are paid in full 

• If an order is placed from Tasmania or Darwin for items that are eligible for ausposting, ROMA will not order as auspost is the preferred shipping option. In such cases, it is necessary for someone to modify the order accordingly. By doing this we are reducing the risk of overstocking in these small warehouse locations

• All AV forecasts need to be checked for TCL , LG and Hisense to make sure the forecast is accuarte especially for SA and WA 

Useful formulas we use 

Algorithm tips 

• Our algorithm relies on the data we input into NAV to test and assess prices and determine an optimal price . As rebates can greatly impact the final advertised price on our website, we must exercise caution when making changes to the rebate system.

• Depending on the price we have advertised ROMA will consider this data, along with other factors, to determine the quantity of a purchase order.

• The algorithm takes into account our average stock-on-hand (SOH) as an important factor in determining prices. For example, if we bought a toaster three years ago for $10 and now purchase it for $50, the algorithm will not consider the new price if we do not have any units priced at $50 in stock.

• When an item is classified as a bathroom product ( item group code 33 ) , Algo will exclude it automatically, ensuring that any price you enter into PSS remains unaffected by automated adjustments

• Algo / pricing starts to rerun at 2:30am every night , so anything we update in nav eg rebates will be absorbed into the algo ( this also includes pricing for new items ) 

Google sheet tips 

• When using Google Sheets, make sure to always use plain text for numbers, as they tend to condense, leading to inaccurate uploads into NAV or any other system 

• When uploading into NAV always download your google sheet as 'csv' 

• Always name your sheets appropriately , as we look at the history of data all the time 

• If youer sharing a document make sure you select share with winnings , this alows anyone in the company to access the sheet 

NAV tips 

• To save time while analyzing multiple sets of data, utilize the "|" symbol to separate each group. For instance, when populating the "pos" field, input the data in the following format: "PO12345|PO54321|PO67890". This will prompt NAV to display each order individually in a clear and organized manner.

• Always have outlook open prior to sending any invoices to suppliers 

Pricing Service Suite 

• When uploading new SKUs into Winnings always use " WA-Online ", for RRP you must use full CAPs Eg " WA-ONLINE " 

• We never use cents on the website so always round up or down when uploading prices - the only exception to this rule is when updating Proforma prices as these are set by the agency and we must comply with their request.

SQL queries

• We use SQL to create reports that aren't easily generated from NAV, as this method simplifies the process. For access to these queries, refer to this document. If you need assistance in building a script, please reach out to someone in RnD or contact Mehrshad Bahmani who is a life long supply chain member.