Choosing equipment for an ISP starts with the service you need to deliver and the site where it will operate. A product with more ports or a newer wireless standard is not automatically the right purchase. A useful shortlist explains the job of each device, the evidence supporting its selection and the questions that still need to be resolved before ordering.
This guide proposes a purchasing workflow for operators planning a new site or expanding an existing one. It does not prescribe a universal router size, radio setting or traffic threshold. Treat the examples as ways to organize your assessment, then verify the exact hardware revision, software and installation requirements with the manufacturer and your technical team.
Describe the service before choosing a model
Write down the services the site will provide, who will use them and where their traffic will travel. Identify subscriber authentication, internet routing, local switching, wireless access and management as separate responsibilities. One device may perform several of those jobs, but that should be a deliberate design decision rather than an assumption based on its product name.
Record the number of currently active connections, expected concurrent use and any measured peak traffic. Distinguish observed demand from a sales forecast. A forecast is useful for planning, but it should not be presented as an established measurement. Include the applications and support expectations that matter to the customer, such as a business needing reliable video calls during office hours.
Draw the proposed connection path and label the interfaces between devices. This makes hidden dependencies easier to see: an access point may need a suitable power source, a switch may need a compatible optical module, and the billing gateway may depend on a management route that the site firewall must permit. Resolve those dependencies before comparing prices.
Compare specifications for the exact product
Use the manufacturer's product page and installation guide for the precise model and revision. Keep the URL and date of review in the shortlist. A reseller description can help identify availability, but it should not replace the manufacturer's interface, power and environmental specifications. If two documents disagree, ask the supplier to resolve the discrepancy in writing.
For example, MikroTik lists the CRS354-48P-4S+2Q+RM with four 10G SFP+ ports and two 40G QSFP+ ports. It should not be described as having four 25G SFP28 uplinks. That distinction matters when selecting modules and planning the connection at the other end. Port counts and link rates also do not establish performance for every routing or subscriber workload.
As another example, Ubiquiti's U7 Lite specification identifies a 2.5 GbE uplink and UniFi Network software requirements. Those facts help assess the surrounding network and management system. They do not imply RouterOS compatibility or automatic adoption by another platform. Verify integration separately from the basic hardware specification.
Budget power and installation requirements together
List every device that needs power and identify its supported supply method. For PoE equipment, check both the powered device requirements and the switch or injector specification. Confirm compatibility rather than relying on the fact that both products mention PoE. Include the aggregate power budget, individual port limits and any accessories required by the manufacturer.
Review the proposed installation location before ordering. Check ventilation, mounting, access for maintenance, exposure to water and the path taken by cables. Do not assume an indoor device becomes suitable for outdoor use merely because it is placed in an improvised box. An enclosure can change heat and condensation conditions as well as exposure, so its design needs a proper assessment.
Ask a qualified installer to review electrical protection and backup power arrangements. Acceptance testing should stay within documented operating conditions and appropriate test procedures. Do not improvise voltage, humidity or heat stress experiments on equipment intended for a customer site. Where specialist environmental qualification is required, use an appropriately equipped professional service.
Evaluate capacity with the intended workload
Measure the current bottleneck before deciding which component to replace. High port utilization, slow subscriber authentication and weak wireless coverage are different problems. Buying a faster uplink will not necessarily address a routing limitation or an unsuitable access point location. Record the evidence connecting the proposed purchase to the symptom you intend to solve.
For a new site, describe a representative workload and a growth assumption. Compare vendor performance results only after checking the test conditions. Packet size, enabled services and configuration can affect whether a published benchmark resembles your deployment. Avoid turning a CPU clock speed or memory amount into a universal subscriber capacity claim.
Plan a controlled pilot with representative services before a large purchase where possible. Agree on the observations that will count as success: application behavior, service stability, authentication and management access, for example. Record unsuccessful results too. The purpose of the pilot is to find an unsuitable choice before it is repeated across multiple sites.
Verify the management and billing integration
Check the current CENTRANET provisioning guide and confirm support for the selected hardware and installed software. Keep subscriber service separate from the management connection in the acceptance plan. A router appearing in a dashboard is useful evidence of management reachability, but it does not establish that customer authentication, name resolution and internet access all work.
For third-party equipment, identify which system will manage it. An access point behind a billing gateway may participate in delivering service without being directly provisioned by CENTRANET. Document that boundary so support staff know which console and credentials they need. Do not advertise a direct integration until it has been documented and tested.
Use an authorized test subscriber to check the intended service journey in a controlled environment. Include the relevant account states and expected recovery behavior. Record what was actually observed rather than marking a checklist complete because a setup command returned successfully. Keep test credentials out of the procurement document and ordinary support messages.
Compare the total cost of ownership
Put the complete installation cost beside the purchase price. Include compatible power supplies, mounting hardware, optical modules, patch leads, cabling, installation labor and management requirements. Ask the supplier to identify which items are included and which must be ordered separately. A lower device price can be misleading when the missing accessories are needed to operate it.
Consider maintenance access and replacement availability. If a failure requires a lengthy site visit or a difficult import, an appropriate spare strategy may matter more than a small price difference. Confirm warranty terms and the process for returning a failed unit. Do not assume a local listing automatically includes manufacturer-backed support for your particular purchase.
Document the assumptions behind future expansion. Buying spare capacity can be sensible, but the cost should correspond to a plausible growth plan. Record what event would trigger the next upgrade and who will review the measurements. This makes the purchasing decision explainable later without pretending that a forecast was certain.
Prepare the deployment and handover record
Before installation, assign responsibility for configuration, physical work, testing and customer communication. Prepare a recovery plan appropriate to the device and confirm how an authorized technician will reach it if remote management fails. Preserve existing configuration using the manufacturer's supported procedure before changing a live system.
At handover, record the installed model, revision, serial number, software version, location and role. Include a simple connection diagram, relevant warranty information and links to the documents used during acceptance. Store administrative secrets separately with access restricted to the people who need them. The ordinary record should explain where authorized access is managed without exposing credentials.
Close the purchasing exercise with a comparison of expected and observed results. Note unresolved limitations, their operational effect and the person responsible for follow-up. A successful shortlist becomes useful evidence for the next site only when the deployment outcome is recorded honestly. Revisit the choice if the workload, environment or software support changes.
References and next step
- MikroTik CRS354 specification: https://mikrotik.com/product/crs354_48p_4s_2q_rm
- Ubiquiti U7 Lite specification: https://techspecs.ui.com/unifi/wifi/u7-lite
- CENTRANET provisioning guide: https://centranetispbilling.com/docs/mikrotik-provisioning
Contact CENTRANET with your site diagram and service requirements to discuss the integration checks before purchasing.