Link to this view:
Actions related to this instance of the report
Period started | Period ended | Entity ID | Entity name | Measure |
---|---|---|---|---|
01/08/2022 | 31/08/2022 | TOP5 | Genesis Energy, Mercury, Meridian Energy, TrustPower, Mercury, Contact Energy | 471.000000000000 |
01/09/2022 | 30/09/2022 | TOP5 | Genesis Energy, Mercury, Meridian Energy, TrustPower, Mercury, Contact Energy | 356.000000000000 |
01/10/2022 | 31/10/2022 | TOP5 | Genesis Energy, Mercury, Meridian Energy, TrustPower, Mercury, Contact Energy | 396.000000000000 |
01/11/2022 | 30/11/2022 | TOP5 | Genesis Energy, Mercury, Meridian Energy, TrustPower, Mercury, Contact Energy | 373.000000000000 |
01/12/2022 | 31/12/2022 | TOP5 | Genesis Energy, Mercury, Meridian Energy, TrustPower, Mercury, Contact Energy | 319.000000000000 |
01/01/2023 | 31/01/2023 | TOP5 | Genesis Energy, Mercury, Meridian Energy, TrustPower, Mercury, Contact Energy | 281.000000000000 |
01/02/2023 | 28/02/2023 | TOP5 | Genesis Energy, Mercury, Meridian Energy, TrustPower, Mercury, Contact Energy | 304.000000000000 |
01/03/2023 | 31/03/2023 | TOP5 | Genesis Energy, Mercury, Meridian Energy, TrustPower, Mercury, Contact Energy | 371.000000000000 |
01/04/2023 | 30/04/2023 | TOP5 | Genesis Energy, Mercury, Meridian Energy, TrustPower, Mercury, Contact Energy | 386.000000000000 |
01/05/2023 | 31/05/2023 | TOP5 | Genesis Energy, Mercury, Meridian Energy, TrustPower, Mercury, Contact Energy | 496.000000000000 |
01/06/2023 | 30/06/2023 | TOP5 | Genesis Energy, Mercury, Meridian Energy, TrustPower, Mercury, Contact Energy | 518.000000000000 |
01/07/2023 | 31/07/2023 | TOP5 | Genesis Energy, Mercury, Meridian Energy, TrustPower, Mercury, Contact Energy | 559.000000000000 |
01/08/2023 | 31/08/2023 | TOP5 | Genesis Energy, Mercury, Meridian Energy, TrustPower, Mercury, Contact Energy | 644.000000000000 |
01/09/2023 | 30/09/2023 | TOP5 | Genesis Energy, Mercury, Meridian Energy, TrustPower, Mercury, Contact Energy | 483.000000000000 |
01/10/2023 | 31/10/2023 | TOP5 | Genesis Energy, Mercury, Meridian Energy, TrustPower, Mercury, Contact Energy | 427.000000000000 |
01/11/2023 | 30/11/2023 | TOP5 | Genesis Energy, Mercury, Meridian Energy, TrustPower, Mercury, Contact Energy | 395.000000000000 |
01/12/2023 | 31/12/2023 | TOP5 | Genesis Energy, Mercury, Meridian Energy, TrustPower, Mercury, Contact Energy | 263.000000000000 |
01/01/2024 | 31/01/2024 | TOP5 | Genesis Energy, Mercury, Meridian Energy, TrustPower, Mercury, Contact Energy | 318.000000000000 |
01/02/2024 | 29/02/2024 | TOP5 | Genesis Energy, Mercury, Meridian Energy, TrustPower, Mercury, Contact Energy | 320.000000000000 |
01/03/2024 | 31/03/2024 | TOP5 | Genesis Energy, Mercury, Meridian Energy, TrustPower, Mercury, Contact Energy | 385.000000000000 |
01/04/2024 | 30/04/2024 | TOP5 | Genesis Energy, Mercury, Meridian Energy, TrustPower, Mercury, Contact Energy | 404.000000000000 |
01/05/2024 | 31/05/2024 | TOP5 | Genesis Energy, Mercury, Meridian Energy, TrustPower, Mercury, Contact Energy | 546.000000000000 |
01/06/2024 | 30/06/2024 | TOP5 | Genesis Energy, Mercury, Meridian Energy, TrustPower, Mercury, Contact Energy | 503.000000000000 |
01/07/2024 | 31/07/2024 | TOP5 | Genesis Energy, Mercury, Meridian Energy, TrustPower, Mercury, Contact Energy | 547.000000000000 |
01/08/2022 | 31/08/2022 | OTHR | Small and medium retailers | 439.000000000000 |
01/09/2022 | 30/09/2022 | OTHR | Small and medium retailers | 341.000000000000 |
01/10/2022 | 31/10/2022 | OTHR | Small and medium retailers | 252.000000000000 |
01/11/2022 | 30/11/2022 | OTHR | Small and medium retailers | 289.000000000000 |
01/12/2022 | 31/12/2022 | OTHR | Small and medium retailers | 195.000000000000 |
01/01/2023 | 31/01/2023 | OTHR | Small and medium retailers | 218.000000000000 |
01/02/2023 | 28/02/2023 | OTHR | Small and medium retailers | 190.000000000000 |
01/03/2023 | 31/03/2023 | OTHR | Small and medium retailers | 250.000000000000 |
01/04/2023 | 30/04/2023 | OTHR | Small and medium retailers | 250.000000000000 |
01/05/2023 | 31/05/2023 | OTHR | Small and medium retailers | 330.000000000000 |
01/06/2023 | 30/06/2023 | OTHR | Small and medium retailers | 427.000000000000 |
01/07/2023 | 31/07/2023 | OTHR | Small and medium retailers | 460.000000000000 |
01/08/2023 | 31/08/2023 | OTHR | Small and medium retailers | 551.000000000000 |
01/09/2023 | 30/09/2023 | OTHR | Small and medium retailers | 486.000000000000 |
01/10/2023 | 31/10/2023 | OTHR | Small and medium retailers | 376.000000000000 |
01/11/2023 | 30/11/2023 | OTHR | Small and medium retailers | 302.000000000000 |
01/12/2023 | 31/12/2023 | OTHR | Small and medium retailers | 220.000000000000 |
01/01/2024 | 31/01/2024 | OTHR | Small and medium retailers | 281.000000000000 |
01/02/2024 | 29/02/2024 | OTHR | Small and medium retailers | 256.000000000000 |
01/03/2024 | 31/03/2024 | OTHR | Small and medium retailers | 314.000000000000 |
01/04/2024 | 30/04/2024 | OTHR | Small and medium retailers | 346.000000000000 |
01/05/2024 | 31/05/2024 | OTHR | Small and medium retailers | 463.000000000000 |
01/06/2024 | 30/06/2024 | OTHR | Small and medium retailers | 403.000000000000 |
01/07/2024 | 31/07/2024 | OTHR | Small and medium retailers | 516.000000000000 |
Link to this view:
Link to this view:
This trend report provides a simple indicator of potential saves and win-back activity. Retailers are banned for 180 days from contacting customers who have decided to switch to a new retailer to entice them back or to stay. Results can highlight traders or parent companies that stand out from their peers and require further investigation to understand the underlying reasons.
On 31 March 2020, Part 11 of the Code was changed to ban retailers from contacting customers with an incentive to stay after those customers had initiated a switch away. However, customers may voluntarily choose to contact their previous supplier to withdraw a switch away, or to arrange a switch back. Such customer-initiated actions will appear in this report as potential win-backs, even though they are compliant with the Code amendment on saves and win-backs. The ban on win-backs applies to customers that were supplied by the retailer (or a retailer in their parent group) during a switch protected period lasting 180 days. The win-back ban is defined by the relationship between a retailer and a customer. The registry currently holds information on traders and ICPs, so looking at this information in isolation is insufficient to tell if an ICP-trader switch withdrawal or switch back is a retailer-customer win-back. Insights can nevertheless be derived where the report highlights outliers that may require further investigation.
This report presents metrics for win-backs via a withdrawal of a switch lodged by the losing trader, or by a switch back to the losing trader. Since 25 June 2015, a withdrawn switch at the customer's request must have a reason recorded against it such as ‘customer requested (CX)’ or ‘customer error (CE)’. Prior to the introduction of these withdrawal reason codes in 2015, a single code, ‘customer request (CR)’, was used.
The ‘ICPs won by’ parameter allows users to investigate the mechanism by which a trader-ICP win-back is executed, and the reason code given if it was via a withdrawal. For this report, ICPs won via a withdrawal process count the same as ICPs won via a switch. This approach is different from other market share reports which count completed switches.
The ‘Show’ parameter allows users to put the numbers of potential win-backs within the context of the scale of the retailer's activity or market share. The withdrawn switches lodged by the losing trader can be presented as a proportion of initiated switches away from that trader, showing how many ICPs may have been incentivised to stay. The mechanism for winning back an ICP can also be represented as a count or proportion of the total ICPs won by that trader (including via withdrawals) during the same month. This measure provides context for how significant the method is to the trader.
Switch types are included as a filter on the report. Customers are obviously free to move house and thereby become associated with a different ICP at any time. We are unable to assess win-backs of customers after such a move. Most interest will be in Trader switches, where the customer has remained at an ICP and has chosen to switch suppliers. Move In switches that appear to be won-back may be the previous trader at the ICP competing to retain supply of the ICP after a new customer has moved in. This behaviour is not banned but is included for completeness.
Market segment breakdowns are available from September 2013 when ANZSIC codes were introduced into the registry in a field maintained by the trader. No breakdown is available at NSP level. Market segments are not mutually exclusive. Residential connections have no ANZSIC code. Small and Medium Enterprise (SME) connections are defined as those assigned meter categories 1 and 2 (low voltage up to 500A) with an ANZSIC code excluding those relating to central or local government and other utility services. Industrial connections have ANZSIC codes from A through E while commercial connections use ANZSIC codes F through Z. More information on ANZSIC codes is available at www.stats.govt.nz.
Retail entities are parent company or trader. A grouped option is also provided separating the largest 5 retailers from small and medium retailers. Switches between entities within a parent company are excluded from this monitoring (i.e. a retailer can't win-back from itself). However, a potential win-back is recorded for a trader if an ICP switches from another retailer, and the ICP was previously supplied by any trader within the winning traders parent group within the 180 days. Bulk ICP transfers between traders that don't involve consumers are excluded. Some care is needed in interpreting the results from retailers of different scales. Those with significant market share may have some bias given the increased likelihood they have previously supplied any given ICP. This is especially apparent when looking across time scales longer than 180 days.
Region types are either network based or derived from standard statistical boundaries. Network-based regions are network supply points (NSPs), network reporting regions, and zones. Mappings are available in the NSP table which is available as a wholesale report. Other regions are derived from ICP location data and statistical boundaries (2013 census). ICPs without location data default to the location of their NSP. Main centres use Territorial Authority boundaries (City Councils) where Wellington includes Porirua City, Upper Hutt City, Lower Hutt City, and Wellington City. Many data reports allow for the selection ‘All regions’ (where the regions are not the data series) to get data for all regions in a single file. Regions are listed in a North to South ordering, except for NSPs which are listed alphabetically.
Visit the glossary for a list of defined terms used on the website.
Visit the forum to see if the information you are looking for is already available or ask a question to see if some of our informed users or staff can help?
Clicking the blue discussion tags below the notes will take you directly to discussions on that topic.