Colocation breaks generic billing software because you are selling physical space, a power envelope and a set of hands. Four or five recurring lines, each measured differently.
Mario Marin6 min readColocation is the product line that breaks generic billing software, because you are not selling a service you provision — you are selling access to physical space, a power envelope, and a set of hands. Four or five recurring line items per customer, each measured differently, plus ad-hoc work that has to be captured before someone forgets to bill it.
Here is what a colocation contract actually contains, and what your billing system has to be able to express.
Space. Rack units, a full rack, a cage, or a suite. Priced per unit per month, and the unit has to correspond to a real position in a real rack — because when the customer asks which rack their hardware is in, "somewhere in row 4" is not an answer.
Power. Almost always the real constraint and usually the largest line. Sold as a committed capacity in kW, as metered consumption, or as a commit with metered overage. Covered in detail in power billing: kW commit versus metered.
Connectivity. IP transit on a committed rate with overage, or a flat port, or blended. Plus the IP addresses themselves.
Cross-connects. A physical cable between your customer and someone else in the building. Recurring, per connection, and individually small enough that they go unbilled with remarkable regularity.
Remote hands. Labour. Hourly or per-incident, often with a bundled allowance, and the only line item on this list that is created by an event rather than a contract.
Three reasons, and they compound.
The unit of sale is physical. A shared hosting plan does not need to know where it is. A colocation contract is meaningless without a rack, a position and a circuit, so if your billing system has no concept of a rack, that information lives somewhere else — and the two records drift.
The contract is negotiated. Colocation is rarely bought from a checkout. Quotes, terms, escalators and per-customer pricing are normal, which a self-serve storefront model handles badly.
Consumption is continuous. Power and transit produce a number every month that has to be measured, applied against a commitment, and turned into a line. If a human reads a meter and types it into an invoice, that is a monthly error opportunity forever.
Worth a section of their own because they are the most commonly leaked revenue in colocation. Each one is a modest monthly amount, they accumulate over years, they are ordered by engineers rather than by finance, and nothing physically disappears when a customer stops needing one.
Two failure modes, both common. Cross-connects installed and never added to the contract — pure lost revenue. And cross-connects billed years after the customer removed the cable, which is worse, because it is a refund conversation plus a credibility problem.
The fix is treating a cross-connect as an inventory object with two ends, a state and a billing link, rather than as a line typed onto an invoice. Then a physical audit of the meet-me room can be reconciled against what you bill, and that reconciliation is a query rather than a spreadsheet exercise.
The problem with remote hands is not pricing, it is capture. A technician does twenty minutes of work at 3 a.m. and the billing event only exists if somebody writes it down.
What works: the ticket is the billing record. The technician logs the time against the ticket, the ticket is attached to the customer, and unbilled billable time appears on a report somebody reviews before the monthly run. What does not work: an intention to invoice it later.
Decide these in the contract, not per incident — the included allowance if any, the increment you round to, whether out-of-hours carries a multiplier, and what counts as billable versus your own fault. That last one prevents most disputes: work required because your power feed failed is not remote hands.
Colocation contracts run for years, which means fixed pricing has to account for cost changes over the term. An annual escalator — a defined percentage on the anniversary — is normal and is far easier than renegotiating. It only works if the billing system applies it automatically; an escalator that requires someone to remember is an escalator that gets skipped.
Also settle what happens at the end. Auto-renewal for a further term, month-to-month, or expiry, and the notice period for each. Ambiguity here is expensive, because the customer's hardware is in your building and neither side has a clean exit.
Most billing platforms in this category answer the first two with "use a DCIM product", which is a legitimate architecture and a second subscription plus an integration. We priced that route in which platforms include DCIM, IPAM and colocation.
Rack and U-space management with chassis and blade support, power tracking, hardware inventory and IPAM are included on every FluxBilling tier from €4.95/month, and colocation services are billed against those same records rather than against a separate system. IP transit overage invoicing runs as a scheduled step in the daily billing pass, so committed-rate overages become invoice lines instead of a report someone reads. Termination releases the rack unit and the IP allocation through the records that assigned them.
Honest limits: cross-connects are modelled through inventory and recurring products rather than as a dedicated cross-connect object with two named endpoints, and there is no meet-me-room topology view. If cross-connect management at scale is central to your operation, ask us for specifics before assuming it does what you need.
See DCIM, IPAM and VPS, dedicated and colocation billing models compared.
Audit your cross-connects and your remote-hands time this quarter. Walk the meet-me room, list what is physically connected, and compare it to what you invoice. Almost every colocation provider who does this for the first time finds revenue in both directions, and it is the cheapest money in the building.
Power is what a datacenter actually runs out of, and it is the line item most often priced badly. Bundle it and you subsidise your densest customers with your sparsest.
Hosting providers assume GDPR is the customer’s problem because the data is on the customer’s server. For your billing system that is exactly wrong, and it is where a subject access request lands.
A PDF is a picture of an invoice, not an electronic one. Why cross-border hosting businesses get caught by rolling national mandates, and the identifier data to start collecting now.