Progressive Pricing - version 8.0(NZ)

Size: px
Start display at page:

Download "Progressive Pricing - version 8.0(NZ)"

Transcription

1 Progressive Pricing - version 8.0(NZ) SETTING UP A PRICE RELATIONSHIP FOR PROGRESSIVE... 2 PRICING ELEMENTS FOR PROGRESSIVE... 2 STEPS TO ADDING NEW PRICES FOR PROGRESSIVE... 3 BASIC PROGRESSIVE PRICE... 5 STATE BASED PRICES NATIONAL DC AND DSD PRICING STEPS TO MAKING A PRICE CHANGE Page 1

2 Setting up a Price Relationship for Progressive Before entering prices for Progressive, you would need to set up a price relationship. The price relationship consists of your Retailer Vendor ID (8 digits) Subrange (4 digits). Example: , etc. This information will be provided to you by Progressive at your initial kick-off meeting with them. The GS1 Implementation Team can set up your price relationship for you. Pricing Elements for Progressive Progressive require a LIST_PRICE and a TRANSACTION (Invoice) price for all products. Progressive support a deferred deal allowance (DEFERRED_DEAL_1), Off invoice allowance (OFF_INVOICE_DEAL_1) or a miscellaneous allowance (MISCELLANEOUS). These are known as Article level allowances because they apply at the article level. Progressive support a FREIGHT charge or MISCELLANEOUS charge. These are also at the article level. List Price Warehouse Allowance Ullage Allowance Differed Deal ($ or %) Off Invoice ($ or %) V V A A You do not need to show a Warehouse and Ullage allowance against the trade item as these are vendor level allowances for Progressive and do not need to be shown on the NPC. However, they may factor in the calculations of your transaction cost (invoice cost) Miscellaneous (allowance $ or %) Freight (Charge $ or %) Miscellaneous (Charge $ or %) Invoice Cost A A A All promotional deals should be submitted separately to Progressive and not via the National Product Catalogue (NPC) Page 2

3 Steps to Adding New Prices for Progressive All commercial agreements about product & pricing between you (the vendor) and buying team (Category manager) must occur outside of the National Product Catalogue (NPC). Once you have their approval to add your new prices onto the NPC you must do so at least 12 weeks prior to when they become effective (as advised by Progressive). 1. It is recommended that all prices must start with a Monday start date. This is mandatory when the product has a deferred deal allowance. Your product s parent prices (List & Transaction) and child prices (Deferred deal, Off Invoice etc) must have the same start dates. 2. Determine how your product is ordered by Progressive. If your product is ordered by carton then you must enter pricing against the CASE GTIN on the NPC. If your product is ordered by each, then you must enter your pricing against the BASE GTIN on the NPC. 3. Determine how your product is invoiced. If your product is invoiced by carton then you must enter the price value and price basis quantity which reflects the case value. If your product is invoiced by each then you must enter the price value and price basis quantity which reflects the each value. 4. Determine the agreed allowances and charges which apply to the product. Some agreed article level allowances/charges which are paid post Transaction (invoice) cost in settlement and do not impact the value of your transaction costs. These still need to be shown in the NPC as an allowance/charge. 5. Check if your pricing is a National or State based price. If your product is distributed nationally you would only need to enter a single National List & transaction cost for your product on the NPC. If you supply your products to specific states then you Page 3

4 would be required to enter a List & Transaction cost for those specific states as well as a national cost. This would only be the case if the cost was different between states. If only supplied to 3 out of the 7 states and the cost is the same you would apply National only. 6. Check the agreed distribution channel for your product. In some cases, you may supply the same article nationally via a Distribution Centre (DC) and Direct to Store (DSD). Where the price values are the same for DC and DSD a single national price must be supplied for DC against that product. Where the two are different - the national DSD price types must be captured by state (List & Transaction with applicable allowances) and you must also provide a national List and transaction cost for your DC prices. 7. Once you have determined which elements need to be applied to your prices, the next step is to enter the prices on the National Product Catalogue (NPC). You must always release all price elements (List, Transaction, Allowances/Charges) together otherwise these will fail once they arrive in Progressive systems. 8. There are three different pricing scenarios that you may encounter for your products. Once you have completed steps 1-7 above you should have a clear idea of which sample applies to you. Use these samples to guide you when adding your pricing elements together. A) Basic Progressive Price B) State Based Pricing C) National DC & DSD Pricing 9. Check your prices before releasing/sending them to Progressive. Important Note: You cannot change a released/sent price other than to end date it. For example, if you have forgotten to add an allowance which should be shown on the NPC but you have released/sent your prices already you cannot amend the existing prices to add the allowance in later. You will need to end date all those prices and add them in again with the changes. You can however make changes to the price while it is still in Working or draft state. Important Note: If you make a mistake with prices and you have released them already: please do not end date the incorrect price with the same day as your start date. The end date must be in the future. Page 4

5 10. When your buyer accepts the new price you should see a confirmation message saying SYNCHRONISE. If you receive a REVIEW confirmation, it means that the prices have been rejected and you need to contact the buying team. Confirmations occur when the buyer responds to the workflow they have received in Progressive System. If you do not see a confirmation within 48 hours you can follow up with the buying team. Basic Progressive Price Your product is ordered by carton and invoiced by carton Your product is supplied nationally via Distribution Centres. You have a standard deferred deal allowance of $5 calculated in the transaction cost (invoice cost) GTIN Hierarchy Level Number of Base Units $ values Ordered by Invoiced by CASE 24EA $48.00 Y Y INNER 6EA $ BASE 1EA $2.00 NPC Price Attributes List Price Transaction Price GTIN Price Type LIST_PRICE TRANSACTION_PRICE Price Type OTHER Reason for Price Action NI - New Item NI - New Item Basis Quantity Your product is ordered by carton therefore prices must be entered at th e CASE GTIN. The product is invoiced by the carton therefore the Basis Quantity UOM equals 24 each. Page 5

6 Basis Quantity UOM Price Value State/Region Alternate Location Distribution Method Effective Start Effective End Reference Document ID Reference Document Allowance/Charge Allowance/Charge Allowance/Charge Value Allowance/Charge Type Sequence Each Each $ $ DC ALLOWANCE DEFERED_DEAL_1 $ VALUE 2 DC In this sample, the value of the transaction price considers the $5 deferred deal and a $5.50 warehouse allowance (which is not shown on the NPC). (($48 - $5.50) - $5) = $37.50 Your product is ordered by carton and invoiced by each Your product is supplied nationally via Distribution Centres. You have a standard deferred deal allowance of $0.20 calculated in the transaction cost (invoice cost) GTIN Hierarchy Level Number of Base Units $ values Ordered by Invoiced by CASE 24EA $48.00 Y INNER 6EA $ BASE 1EA $2.00 Y Page 6

7 NPC Price Attributes List Price Transaction Price GTIN Your product is ordered by carton therefore prices must be entered at the CASE GTIN. Price Type LIST_PRICE TRANSACTION_PRICE Price Type OTHER Reason for Price Action NI - New Item NI - New Item Basis Quantity 1 1 The product is invoiced by each therefore the Basis Quantity & UOM equals 1 each. Basis Quantity UOM Each Each Price Value $ $ The product is invoiced by each therefore the price value should reflect this. Please also note, the value of the transaction price is less by $0.20 deferred deal and a $0.23 warehouse allowance (which is not shown on the NPC). (($2 - $0.23) - $0.20) = $1.57 State/Region Alternate Location Distribution Method DC DC Effective Start Effective End Reference Document ID Reference Document Allowance/Charge Allowance/Charge ALLOWANCE Allowance/Charge Value $ Allowance/Charge Type Sequence 2 DEFERED_DEAL_1 VALUE Page 7

8 Your product is ordered by carton and invoiced by carton Your product is supplied nationally via Distribution Centres. You have a standard deferred deal allowance of $5 calculated post transaction cost (invoice cost) GTIN Hierarchy Level Number of Base Units $ values Ordered by Invoiced by CASE 24EA $48.00 Y Y INNER 6EA $ BASE 1EA $2.00 NPC Price Attributes List Price Transaction Price GTIN Your product is ordered by carton therefore prices must be entered at the CASE GTIN. Price Type LIST_PRICE TRANSACTION_PRICE Price Type OTHER Reason for Price Action NI - New Item NI - New Item Basis Quantity The product is invoiced by the carton therefore the Basis Quantity UOM equals 24 each. Basis Quantity UOM Each Each Price Value $ $ In this sample, the value of the transaction price does not consider the $5 deferred deal which is settled after the invoice is paid (post invoice cost). There is however a $5.50 warehouse allowance deducted (which is not shown on the NPC). ($48 - $5.50) = $42.50 State/Region Alternate Location Distribution Method DC DC Effective Start Effective End Reference Document ID Page 8

9 Reference Document Allowance/Charge Allowance/Charge Allowance/Charge Value Allowance/Charge Type Sequence ALLOWANCE DEFERED_DEAL_1 $ VALUE 2 The deferred deal (this applies to any allowance of charge) must still be shown on the NPC even if it doesn t get calculated into the final transaction cost. Page 9

10 State Based Prices Your product is ordered by carton and invoiced by carton Your product is sold in Victoria and New South Wales via DC You have a standard deferred deal allowance for VIC and NSW of $5.00 calculated in the transaction cost (invoice cost) Note: warehouse allowance $5.50 has been included in the calculation of the transaction prices but not shown. GTIN Hierarchy Level Number of Base Units $ values $ value Ordered by Invoiced by (National) (VIC & NSW) CASE 24EA $ Y Y INNER 6EA $ BASE 1EA $ NPC Price Attributes List Price National Price Price Victoria Price - NSW Transaction List Price Transaction Price List Price Transaction Price Price GTIN Price Type LIST_PRICE TRANSACTION_PRICE LIST_PRICE TRANSACTION_PRICE LIST_PRICE TRANSACTION_PRICE Price Type OTHER OTHER OTHER Reason for Price NI - New Item NI - New Item NI - New Item NI - New Item NI - New Item NI - New Item Action Basis Quantity Basis Quantity Each Each Each Each Each Each UOM Price Value $ $ State/Region VIC VIC NSW NSW Alternate Location Distribution Method DC DC DC DC DC DC Page 10

11 Effective Start Effective End Reference - - EXCEPTION EXCEPTION EXCEPTION EXCEPTION Document ID (3) Reference - - EXCEPTION_PRICE EXCEPTION_PRICE EXCEPTION_PRICE EXCEPTION_PRICE Document (3) Allowance/Charge ALLOWANCE ALLOWANCE ALLOWANCE Allowance/Charge DEFERED_DEAL_1 DEFERED_DEAL_1 DEFERED_DEAL_1 Allowance/Charge $ $ $ Value Allowance/Charge VALUE VALUE VALUE Type Sequence Notes: 1) Whenever you have a state price, you must always have an accompanying National price with it. 2) List and Transaction prices must be entered for each state individually. Even if the dollar values for those states are the same. 3) For Publisher UI users, National pricing must have the Reference Document ID = - and Reference Document = - 4) State prices must have the Reference Document ID = EXCEPTION and Reference Document = EXCEPTION_PRICE. 5) Where the state price has an allowance/charge but the national price doesn t. You must enter a zero value for the corresponding allowance/ charge for the national price and vice versa. 6) In some cases, you may have regional prices (e.g. Far North Queensland) in this instance you would use the Alternate Location Grouping attribute to specify the region. Please clarify the code list for your region with the Progressive team before entering prices. You do not need to enter a state if entering the alternate location group. Page 11

12 National DC and DSD Pricing Your product is ordered by carton and invoiced by carton Your product is sold nationally through DC as well as DSD (direct to store) You have a standard off invoice allowance for of $5.00 calculated in the transaction cost (invoice cost) for your products. Note: warehouse allowance $5.50 has been included in the calculation of the transaction price for DC GTIN Hierarchy Level Number of Base Units $ values $ value Ordered by Invoiced by (DC) (DSD) CASE 24EA $ Y Y INNER 6EA $ BASE 1EA $ NPC Price Attributes National DC Price List Price Transaction Price GTIN Price Type LIST_PRICE TRANSACTION_PRICE Price Type OTHER Reason for Price NI - New Item NI - New Item Action Basis Quantity Basis Quantity UOM Each Each National DSD Price List Price Transaction Price LIST_PRICE OTHER NI - New Item Each TRANSACTION_P RICE NI - New Item Each If the DC and DSD prices are the same, you should provide only one List & Transaction with distribution method marked as DC. Page 12

13 Price Value $ $ State/Region Transaction Cost = List cost - Warehouse allowance - off invoice deal ($120 - $ $5) Transaction Cost = List cost - off invoice deal ($120 - $5) Alternate Location Distribution Method Effective Start Effective End DC DC DSD DSD Reference Document ID Reference Document Allowance/Charge ALLOWANCE ALLOWANCE Allowance/Charge OFF_INVOICE Allowance/Charge $ Value Allowance/Charge VALUE Type Sequence 2 OFF_INVOICE $ VALUE 2 Page 13

14 Steps to Making a Price Change 1. Ensure that the price has been agreed with your trading partner before updating the NPC. Price changes must be made typically 12 weeks before they are due (as per Progressive requirements) 2. Edit your old prices (List + Transaction) and populate the end date. It must be the same for the whole price hierarchy. Important Note: End dates cannot be the same as the start date of the product. DO NOT RELEASE or send the end dated prices ahead of your new price changes. If old and new prices arrive separately in Progressive systems they will fail. 3. Add the new List and Transaction cost. Important Note: The new prices must have a start date after the end date of the old prices. For example, if you end date the old prices for Sunday, 18 th June the start date of your new prices must be Monday, 19 th June. Please ensure all elements of Progressive pricing that apply to your product have been applied. If you need to remove an allowance from the existing product price after end dating the old prices, you must add the new price (List and Transaction) and show a zero-value deferred deal. This cancels out the old deferred deal. Simply loading an end date against an existing Deferred Deal will not discontinue the Deferred Deal, it must be loaded with a $0 value. 4. Check your prices prior to releasing/sending to your recipient. Once a price is released, it cannot be changed other than end dated. You must release all prices together (old and new) to avoid a split message from occurring in Progressive System and failing. 5. When your buyer accepts the price change you should see a confirmation message against the old and new price saying SYNCHRONISE. If you receive a REVIEW confirmation, it means that the prices have been rejected and you need to contact your buyer. Confirmations occur because of the buyer responding to the workflow they have received in Progressive Systems. If you do not see a confirmation within 48 hours you can follow up with the buying team. Page 14

15 Document Version Control Version Release Nature of Change / Comments Author v1.0 November 2012 Initial Release D.Prince v2.0 July 2014 Deferred Deal notes added under Basic Principles S.Timoshanko RETAIL_PRICE - SRP (Suggested Retail Price) removed as no longer required by Progressive/Progressive v3.0 April 2015 Updated the Basic Principles S.Timoshanko Added section on removing allowances and charges against Progressive Pricing Updated FAQ s V4.0 August 2015 Minor updates to terminology S.Timoshanko V5.0 November 2015 Minor updates to terminology S.Timoshanko V6.0 March 2016 Minor updates to terminology S.Timoshanko V7.0 October 2016 Updated Exception Pricing section S.Timoshanko V8.0 June 2017 Refresh document format and examples D.Prince V8.0 NZ August 2017 Replaced Woolworths reference to Progressive for clarity in NZ market C.Frith Page 15