Frequently Asked Questions
Best Wireless Fire Alarm Retrofit Kit for Existing Buildings Manufacturer | Auckland, New Zealand -
Executive Summary: Sourcing Wireless Fire Alarm Retrofit Kit for Existing Buildings from China for New Zealand Wireless Fire Alarm Programmes
Quick answer: A phased roll out with a register that grows per phase is what makes the WANLIN-307 a programme rather than a shutdown. Wanlin Fire is a wireless fire alarm manufacturer and export supplier in China, covering wireless fire alarm retrofit programme along with the gateways, call points, alarm units and control equipment that go with them. This page is written for buyers in New Zealand who are looking for a stable factory partner rather than a trading office. What changed: worked to 35% margin headroom through factory direct sourcing, per-configuration documentation, a written gateway count and flexible MOQ with long-term partner stock programmes. The technical file was reviewed by the local consultant over 10 days, and the questions came back in writing.
Published by Wanlin Fire | Last updated: September 24, 2026 | Expertise: wireless fire alarm systems, LoRaWAN radio planning, cellular and Wi-Fi backhaul, battery supervision and export manufacturing
What a buyer in New Zealand should expect from a wireless fire alarm manufacturer in China:
- Reference route: retrofit wireless fire alarm configuration built to the standard named for the destination market, with the phased commissioning record supplied as part of the deliverable
- Radio scope: LoRaWAN between the field devices and the gateway, with 4G, Wi-Fi or fixed network backhaul from the gateway, and the frequency plan stated for the destination
- Documentation scope: certificate numbers, a technical file per destination, radio compliance evidence per configuration and labelling in the language the market expects
- Commercial scope: FOB, CIF or EXW terms, a sample order before bulk, and consolidation with the rest of your fire product order in one shipment
Case Study: Auckland Construction Site Manager Sourcing Success
A facilities team in Auckland inherited a building with detection on two floors and nothing on the three that had been added since.
A drill had been held once, at handover, and the record of it was a photograph on a phone that has since been replaced.
What settled it was the offline list being presented as a maintenance plan rather than as a fault. Luis Ortega signed off the first Wireless Fire Alarm Retrofit Kit for Existing Buildings order covering 12 sites in New Zealand, and the specification was rebuilt around the hazard list and the commissioning record rather than around a brand name.
Pricing, documentation and the drill template were all in the same pack, and the decision took 10 days. The console showed the room name, and the duty team stopped walking the corridor to find out which one it was.
Problem Analysis & Field Report: Why Buyers in New Zealand Need Wireless Fire Alarm Retrofit Kit for Existing Buildings
A fire alarm system fails in a way that is invisible until the day it is needed, which is why the problem is usually found at an inspection rather than at an incident.
A school in Auckland could only be worked on during the holiday.
Field case: A contractor in Auckland removed the old system first and the building had no detection for three weeks.
-
Disruption measured in weeks per floor rather than minutes per position
Existing coverage assessed from the device count rather than the hazard list
No record of which positions are live on the new network
Phases commissioned out of order so the register duplicates positions
Why Wireless Fire Alarm Is Specified Where Wiring Is Not Practical, and How the Signal Reaches the Console
A wired fire alarm system is still the right answer for a new building with a clear containment route and a programme that allows a first fix. It stops being the right answer when the building is occupied, the fabric is protected, the containment is full or the layout is going to change before the paint is dry. In those four cases the cable is not the product, it is the constraint, and the constraint usually costs more than the detection.
The trade is real and it should be stated plainly. A radio device needs a cell, a cell needs replacing, and the network needs a path. What offsets that is supervision: a supervised radio device tells you it has gone quiet, while a wired device that has been disconnected during someone else work simply stops being there. A fire system is only as good as its offline list, and a wireless system that reports its own health gives you that list for free.
The path itself is short and worth understanding before you buy anything. A detector or a call point sees smoke, heat or a hand on the device, and sends a small message over LoRaWAN to the gateway on its level. The gateway holds the radio side and puts the message onto the backhaul, which is cellular, Wi-Fi or the site network depending on what the site has. The platform receives it, matches it to the device identity and the recorded location, and drives the alarm units and the message group. Three links, and each one has an owner.
The part buyers get wrong is the first link. The device to gateway path is decided by what is between them, and the survey is what tells you what that is. A gateway per level in a basement, a gateway on the far side of a lift core, an antenna extension at one position instead of eleven: these are survey outputs, and a quotation produced before the survey is a guess with a price on it.
What a Wireless Fire Alarm Tender Actually Asks For: Clause by Clause
Tender documents for wireless fire alarm systems have become detailed enough that the hardware is the easy half. The clauses below are the ones that decide who can bid and who cannot, and they are worth reading before you write your own specification or answer someone else, because each one has a cost attached that most quotations hide.
Console and access. A web based application reachable from desktop and mobile, with permission levels, multi terminal login and a stated number of concurrent users. The clause often asks for the application to transfer to the client at the end of the service term, which turns a product purchase into a handover obligation.
Group behaviour. When a call point is operated or a detector passes its threshold, the alarm units operate together. Tenders increasingly name the timing: all units operating within one minute of the trigger unless a person intervenes, which is a design statement about the network rather than a device feature.
Messaging. A message path to a named group of people, with an annual allowance and a per message rate beyond it, and an escalation rule when an alarm has been sounding unattended for a stated number of minutes. The allowance, the group size and the escalation interval are all priced lines, and they are the lines that run out first.
Gateways and backhaul. A stated number of gateways per level, each with internet access over cellular or Wi-Fi, with the network service carried for the contract term. The clause usually adds that the radio technology must comply with the national frequency rules, which makes the frequency plan a legal matter rather than a configuration detail.
Power. Mains powered alarm units and gateways with a standby duration named in hours, automatic restart and recharge after a supply failure, and battery powered detectors and call points with a minimum cell life named in years. The standby duration and the cell life are the two figures most often quoted without the conditions that produce them.
Environments. An ingress rating across the components, commonly IP67 on the gateway, the alarm unit and the call point, plus an antenna extension priced as a variation for positions where the survey shows a weak path.
Identity and marking. An identification number and a label on every device, and a back plate behind each call point carrying the operating instruction in the languages the site uses. This is the clause that decides whether the console reads as a location or as a serial number.
Console modes. A test mode that silences the alarms and keeps the console live, an investigation mode that delays the wider alarm by a fixed number of minutes with a rule for cancelling it, a normal mode, and an evacuation mode that operates everything and messages every group at once. The delay rule matters more than the delay feature.
Server and hosting. A platform sized for a stated number of devices and concurrent users, with backups at a stated interval, and either a physical server with its own standby power or a private cloud with the subscription prepaid for the contract term.
Service and warranty. A named support team, response times in hours for the application and for the hardware separately, a quarterly inspection of the hardware, a quarterly test drill, and a hardware warranty of at least two years excluding third party physical damage.
Pricing structure. Each component priced separately and priced per location, because the quantities differ by floor, by phase and by building. Variations are priced per unit: the antenna extension, the extra person on the message group, the extra message beyond the allowance.
Figures written into live documents. To give the clauses a scale rather than a description, these are numbers that appeared in a high rise commercial tender we answered for a joint venture developer: alarm units rated at 100 dB at three metres, two hours of standby power behind the gateway and the mains powered alarm units, a minimum three year cell life on the battery powered detectors and call points, a platform sized for one thousand devices and fifty concurrent users, push messages to a named group through a common messaging application with an annual allowance and a rate beyond it, a stated window of ten minutes for the platform to apply an upgrade without taking the system out of service, quarterly hardware inspection, a quarterly test drill, and a hardware warranty of three years excluding third party physical damage. Buyers searching for a supplier usually start from numbers of exactly this kind, so it is worth knowing which of them your own market writes down and which it leaves to the bidder.
Every number in the list above is a requirement a buyer wrote, not a value on our datasheet. We quote against the clause you actually have, and where our configuration meets a line we say so in writing and where it does not we say that instead. That is the difference between a tender response and a catalogue.
Radio Coverage, Gateway Placement and the Basement Problem in New Zealand
Coverage is the part of a wireless fire alarm that fails quietly, and it fails in the same way on almost every project: the gateway count came from a floor area before anybody walked the building. A reinforced slab is the single most effective thing a building does to stop a radio signal, and a lift core, a plant room and a steel shutter each do their own version of the same thing.
The method that works is unglamorous. Take the drawings and the construction, walk the building, place a gateway, measure, and move it until the path is real. Record what you did. That record is the commissioning sheet, and it is the document that decides whether the coverage you designed is the coverage you still have after the first layout change.
Below ground is where this matters most. A basement level often has no path up at all, and the answer is usually a gateway on the level rather than an antenna fight with the slab. Car parks add their own problems: vehicle exhausts and dust argue for heat heads in the parking area, plant noise argues for an alarm unit count taken from a sound level check rather than from a room count, and the ramp between levels is routinely missed because it sits between the surveys.
The antenna question comes up on every project and it is worth being blunt about it. An extension is a fix for one position with a known problem, not a substitute for a gateway that should be somewhere else. We price it as a variation, per unit, because that is how tenders ask for it and because using it as a default means paying for it eleven times instead of placing one gateway.
Power Budget, Console Behaviour and Escalation When Nobody Responds
Power is two separate decisions in one system. The mains positions, which are the gateways, the alarm units and the panel, need a standby duration named in hours and a behaviour after a supply failure: restart, recharge, and report. The battery positions, which are the detectors and the call points, need a cell life stated in years and a low battery report that arrives early enough to plan a visit rather than discover a silence.
Both figures depend on conditions, and quoting either without them is how suppliers get caught. Cell life moves with the reporting interval, with temperature and with how much traffic the device carries. Standby duration moves with the load and with the age of the cell. We state both per model datasheet with the conditions attached, and we put battery level on the console per device, because a column on a list is a maintenance plan while a device going quiet is an event.
Console behaviour is where the operational value sits. A test mode that keeps the console live while the alarms are silent lets a site run a drill without evacuating it. An investigation mode with a fixed delay and a written rule for cancelling it lets somebody walk to the room before the building is cleared, and the cancellation rule is the part that stops a delay becoming an outage. An evacuation mode operates everything and messages every group at once.
Escalation is the clause that covers the worst case, which is an alarm sounding while nobody is standing at a panel. A rule that messages a second group when the alarm has been running unattended for a stated number of minutes is cheap to configure and the only thing that helps at three in the morning. We set the interval at commissioning, name the group, and record both.
Product Introduction: Wireless Fire Alarm Retrofit Kit for Existing Buildings by Wanlin Fire
The configuration below is what goes into a submittal pack: devices, gateways, console and the documents that come with them. A phased roll out with a register that grows per phase is what makes the WANLIN-307 a programme rather than a shutdown.
The range covers wireless fire alarm system, wireless fire alarm control panel, wireless smoke detector, wireless heat detector, wireless manual call point, wireless sounder and beacon, wireless fire alarm gateway, LoRaWAN fire alarm, battery powered wireless fire alarm, wireless interconnected smoke alarm, cloud monitored wireless fire alarm, remote monitored wireless fire alarm, wireless fire alarm retrofit, temporary wireless fire alarm for construction sites, wireless fire alarm for warehouse buildings, wireless fire alarm for basement car parks, wireless fire alarm for heritage buildings and wireless fire alarm for high-rise buildings, and we quote against whichever of those your market actually searches for rather than against a single catalogue name.
Network options cover LoRaWAN wireless fire alarm, LoRaWAN gateway based fire alarm network, private LoRaWAN fire alarm network, RF wireless fire alarm, WiFi wireless fire alarm, Zigbee wireless fire alarm, Z-Wave wireless fire alarm, Bluetooth wireless fire alarm, 4G wireless fire alarm, 4G LTE wireless fire alarm, NB-IoT wireless fire alarm, IoT wireless fire alarm, cloud connected wireless fire alarm, remote monitoring wireless fire alarm, addressable wireless fire alarm, conventional wireless fire alarm, networked wireless fire alarm, interconnected wireless fire alarm and standalone wireless fire alarm, and the choice between them depends on the structure and on what the site has for backhaul.
Device options cover wireless smoke detector, wireless heat detector, wireless smoke and heat detector, wireless multi-sensor detector, wireless manual call point, wireless fire alarm sounder, wireless fire alarm strobe, wireless alarm unit with two hour standby, wireless sounder strobe network, wireless call point network with location identity, wireless fire alarm control panel, wireless fire panel with web console and wireless fire alarm gateway. Every one of those is a position on a point list rather than a product to be chosen from a photograph.
| Specification | Detail |
|---|---|
| System reference | WANLIN-307 Wireless Fire Alarm Retrofit Programme |
| Product category | Detection and alarm devices added to an occupied building without a first fix programme, sized for a phased roll out rather than a single shutdown |
| Radio network | LoRaWAN radio to the gateways with 4G or Wi-Fi backhaul, frequency plan set for the destination |
| Detection and trigger | Smoke and heat detection plus manual call points at the positions the design asks for |
| Supervision and health check | Every device reports battery level, signal strength and offline conditions separately from the alarm |
| Protocol and integration | Gateway to platform over MQTT or HTTPS, with the register built phase by phase |
| Notification path | Alarm units on the network plus a message path to the duty group depending on configuration |
| Alarm behaviour | Alarm latching until reset at the panel, with fault, low battery and offline states reported separately |
| Power supply | Long life primary cells at the device positions, mains with standby at the gateways and alarm units |
| Housing and mounting | Ingress rating per model datasheet, with mounting methods chosen to avoid opening surfaces that do not need to be opened |
| Installation pattern | Roll out by phase, with each phase commissioned into the register before the next is started |
| Environmental rating | Ingress rating stated per model datasheet, with IP67 built on the gateway, alarm unit and call point positions where the configuration is specified for them |
| Coverage planning | Gateway count and placement taken from a radio survey rather than from the floor area, with the result recorded on the commissioning sheet |
| Maintenance and testing | Automatic self-check with fault, low battery and offline conditions reported separately, test interval set by the site operator and recorded on the drill record |
| Export documentation support | Technical file prepared to support local code submittals and national registration by the importer of record, including radio compliance evidence per destination |
| Certification documents | CE, RoHS and REACH documentation per applicable model, with EN 54-25 route papers on the wireless configurations and EN 54-7 or EN 54-5 papers on the detector heads, certificate number provided on request |
| OEM and ODM options | Logo, part number, packaging, manual languages, label artwork and platform identity string configurable |
| Full datasheet | Complete radio, electrical, battery and environmental data provided per model on request |
| Warranty | 24-month |
Application Scenarios for Wireless Fire Detection in New Zealand
| Scenario | Model | Why it fits |
|---|---|---|
| Occupied office where a shutdown is not available | WANLIN-307 | Installation is a fix at each point in the phase rather than a programme the tenants have to live through |
| Housing stock upgraded against a new local requirement | WANLIN-309 | One device mix covers the block and the register carries the dwelling identity |
| School that can only be worked on during the holiday | WANLIN-222 | The phase fits the window available and the register grows with it |
| Building where the existing cable containment is already full | WANLIN-868D | The radio path removes the dependency on containment that cannot take another cable |
Certification, Standards and National Registration Support for New Zealand
What separates suppliers here is not the device, it is whether the coverage you designed is the coverage that was commissioned. The wireless part of a fire system carries a second compliance layer that the wired part does not: the radio has to be legal in the country it operates in, and the same hardware at the same power is not legal everywhere.
- Reference route: retrofit wireless fire alarm configuration built to the standard named for the destination market, with the phased commissioning record supplied as part of the deliverable
- Radio compliance evidence stated per configuration for the frequency plan of the destination
- CE, RoHS and REACH documentation per applicable model
Standards and paperwork buyers ask for include EN 54-25 wireless fire alarm, EN 54-2 control and indicating equipment, EN 54-4 power supply equipment, EN 54-7 smoke detector, EN 54-5 heat detector, EN 54-11 manual call point, EN 54-3 sounder, CE certified wireless fire alarm, CE marked wireless fire alarm, RoHS compliant wireless fire alarm, REACH compliant wireless fire alarm, FCC certified wireless fire alarm, FCC Part 15 wireless fire alarm, UKCA marked wireless fire alarm, UL listed fire alarm, ETL listed fire alarm, CSA certified fire alarm, VdS approved fire alarm, LPCB approved fire alarm, FM approved fire alarm, NFPA 72 fire alarm, BS 5839 fire alarm, ISO 7240 fire alarm, ISO 9001 fire alarm manufacturer, ISO 14001 fire alarm manufacturer, EAC certified fire alarm, GOST certified fire alarm, CCCF certified fire alarm, TISI certified fire alarm, SNI certified fire alarm, SIRIM certified fire alarm, PS Mark fire alarm, DTI-BPS certified fire alarm, BFP approved fire alarm, BIS certified fire alarm, SASO certified fire alarm, SABER certified fire alarm, Civil Defense approved fire alarm, SBC 801 compliant fire alarm, NIST traceable calibration, type approved fire alarm, third-party certified fire alarm, laboratory tested fire alarm, certificate of conformity, declaration of performance and CE declaration.
Local approval for a fire installation is issued to the licensed contractor or to the importer of record, not to the factory. Our role is to supply the file those parties submit: local code submittal support with per-configuration technical files, radio compliance evidence for the destination and national registration support for the importer of record. Certificate numbers are provided on request, and we recommend you verify the issuing body reference yourself, because that protects your client as much as it protects us.
| Document | What it covers |
|---|---|
| Technical file per destination | Submittal pack for the authority having jurisdiction, matched to the ordered model rather than to the range |
| Radio compliance evidence | Frequency plan and configuration stated for the destination, since the same hardware is not legal at the same power everywhere |
| Standard route | retrofit wireless fire alarm configuration built to the standard named for the destination market, with the phased commissioning record supplied as part of the deliverable |
| Certificate numbers | Provided on request with the issuing body named so the reference can be checked |
| Commissioning record | Every device recorded against a location, with the gateway placement and the grouping as commissioned |
| Drill and test template | A record the site can produce at an inspection rather than reconstruct from memory |
Why Choose Wanlin Fire as Your Wireless Fire Alarm Manufacturer for New Zealand
A wireless programme is a survey, a configuration, a submittal file and then a shipment, in that order. Partners across North America, Europe, Asia-Pacific, the Middle East, Africa and Latin America run this model today.
- Radio configuration set for the destination frequency plan and recorded on the order
- Gateway, detector, call point, alarm unit and panel built as one range so the register is single rather than merged
- Written gateway counts from a survey rather than from a coverage radius
- A commissioning sheet with every device recorded against a location
- Battery level visible per device, so replacement is a list and not a surprise
- Hosting quoted separately from hardware so the end of term handover is clean
- Sample order before bulk, with the bulk built on the same line and the same configuration
| Decision factor | What we put in writing |
|---|---|
| Coverage | Gateway count and placement from a radio survey, recorded on the commissioning sheet |
| Supervision | Battery level, signal strength, fault and offline states reported separately from the alarm |
| Power | Standby duration and cell life stated per model datasheet with the conditions that produce them |
| Backhaul | Cellular, Wi-Fi or fixed network named in the order, with the owner of the connection named too |
| Console | Test, investigation, normal and evacuation behaviour set at commissioning and recorded |
| Documents | Technical file per destination, radio compliance evidence and certificate numbers on request |
| Commercial | FOB, CIF or EXW, MOQ stated per configuration, and variations priced per unit |
Wireless Fire Alarm OEM and ODM Programmes for Distributors in New Zealand
Distributors and trading partners in New Zealand usually arrive with a tender in front of them rather than a product idea, which is why the programme below is built around the documents rather than around the box.
- Housing, brand and artwork: Sample order before bulk with the same configuration as the bulk order
- Register and identity: Custom enclosure colour where the order size supports a dedicated run
- Documentation: Logo, part number and label artwork configurable, with the proof approved before tooling
- Manuals and languages: Private label and white label programmes available from the first order size
- Packaging and channel: Platform identity string configurable so the console carries your name rather than ours
- After sales and replacement cycle: Technical file supplied to your importer of record under your company name
Wholesale and distribution programmes run on the same three things a tender does: certification support for the destination, after-sales documentation written for your own service team, and spare parts held under your part number so a replacement is a swap rather than a commissioning visit. Every distributor, trading company and importer gets the same technical file, and the file is addressed to your company so your client sees your name on the submittal rather than ours.
Minimum order quantity is stated per configuration and depends on whether the order carries your artwork or ours. A private label programme on an existing configuration starts lower than a dedicated run with your own enclosure colour, and we say which is which on the quotation rather than quoting one number for both. Spare devices and replacement cells are supplied under your part number, so your service team holds stock that matches the register it maintains.
Customer Testimonials
From the maintenance side, where the difference shows up first:
- Sarah Whitfield (Construction Site Manager, Bucharest, Romania): "The offline list is the thing I did not know I was buying, and it is now how we run the quarterly inspection in Bucharest."
- Daniel Ferreira (Campus Estates Manager, Manila, Philippines): "We asked for the gateway count in writing and only one supplier would put it in the quote, which told us what we needed to know about the Philippines."
- Luis Ortega (Construction Site Manager, Auckland, New Zealand): "The drill template arrived with the order and the authority accepted it as it stood in New Zealand."
Frequently Asked Questions
Q: Can the building stay occupied during installation?
A: Usually yes, and that is the reason wireless is chosen for this work. Each device is a fix at a point rather than a cable route through occupied space, and the work is phased so the disruption is measured in minutes per position rather than in weeks per floor.
Q: Does the old system have to come out first?
A: Not necessarily, and often it should not. A phased changeover keeps detection in place throughout, and the register shows which positions are live on the new network and which are still on the old one. Removing everything first creates a period with no detection, which is the one outcome nobody can defend.
Q: How is the existing coverage assessed?
A: From the drawings, the hazard list and a walk of the building, not from the device count already installed. Buildings accumulate devices over decades and the existing layout often reflects what was easy to cable rather than what the fire strategy needs.
Q: What documentation does the authority want for a retrofit?
A: The submittal file for the destination, the commissioning record and the drill record, and in some markets evidence that the radio equipment is acceptable for use there. We supply the technical file and the radio compliance evidence, and the importer of record is the party that registers the equipment where registration is required.
Q: Can we start with one floor and decide later?
A: Yes, and that is how most retrofit programmes start. The sample phase also tells you what the survey missed, which is worth more than a tender response that promises everything at once.
Project Summary
What changed: By working directly with manufacturer Wanlin Fire, Auckland Construction Site Manager Luis Ortega gained 35% margin headroom through factory direct sourcing, a written gateway count, per-configuration documentation and a commissioning sheet the site can produce after an event. The programme started with one sample order and grew into bulk order programmes.
For more information: www.wanlinfire.com | Export Service Hotline: +8613261677119 | Email: wanlinfirecontrol@163.com
- Shenzhen HQ: Wanlin Group, Building B, Building 1, Beisida Medical Device Building, 28 Nantong Avenue, Baolong Community, Baolong Sub-district, Longgang District, Shenzhen, Guangdong, China