What are FTTP and FTTC? Full fibre and part-fibre broadband
Fibre to the Premises (FTTP) carries fibre to the customer's property. Fibre to the Cabinet (FTTC) carries fibre to a street cabinet and uses copper for the final connection. The distinction affects the available products and installation arrangements. A broadband provider may build infrastructure or buy access from a wholesale supplier, which sells connectivity to other providers for resale.
Running the retail business requires more than a network connection. The provider needs to record customers and packages, check what can be supplied at an address, arrange delivery, generate bills, collect payment and handle support. This page explains the fibre broadband lifecycle and the ordering and billing systems used to manage it.
For example, a business requests connections at two sites. Each address is checked, an eligible product is selected and an order is submitted. Appointments and equipment are coordinated for each location. Confirmed service information then supports the correct recurring charges, while the customer account retains the history needed for installation and payment enquiries.
FTTP management software needs to keep the location, supplier request, service identifier and retail package related. Customer relationship management (CRM) adds the contacts and communications; billing identifies what is due and what has been paid. Two sites on one account may have different installation dates and packages, so neither the order status nor the bill should obscure individual services.
Coverage must be verified for the actual premises and supplier product. A technology label or general coverage map is not a confirmed order. The UK wholesale broadband guide explains the access arrangements; SOGEA ordering covers a relevant single-order copper-based product. ISP management describes the wider commercial and customer relationship around these delivery workflows.
FTTP and FTTC provisioning: availability, installation and orders
Provisioning is the process of establishing or changing the service that was ordered. For FTTP, start with the correct premises, returned availability and product selection. Collect contact details and installation information before submitting the supplier request. Retain the reference used to trace it through later responses.
An installation may need an engineer visit or access arrangements, depending on the existing connection and the supplier process. Agree who provides access, who supplies equipment and who confirms the customer handover. A requested appointment or an order acknowledgement does not prove that the service is ready to use.
FTTP order management software should distinguish submission, supplier acceptance, subsequent changes and confirmed progress. If a request is rejected, investigate its specific feedback rather than treating every failure as the same problem. Record the owner and next action so support can explain what remains outstanding.
FTTC requirements need the same careful review of current supplier products and permitted order types. Do not assume that one broadband integration supports every access technology in the same way. The intended catalogue mapping and workflow must be demonstrated against the actual offer before customers are promised a delivery route.
Bulk ordering can organise several new connections or planned changes while retaining individual outcomes. For a multi-site customer, one premises may be progressing while another needs access details. Each site needs its own references and customer update. The ISP operations guide and customer communications guide explain how responsibilities and communication history support that coordination.
Ask software suppliers to demonstrate a successful installation, a rejected order and a changed appointment. Review how status updates reach staff and how the service is passed to billing and support. Where an Application Programming Interface (API) exchanges messages between systems, confirm which supplier actions it actually implements rather than assuming general connectivity means complete order coverage.
FTTP and FTTC billing software: packages, charges and invoices
Fibre billing software translates the customer's package into recurring charges and any agreed installation, equipment or additional service fees. Service references need to identify the connection behind each amount. This matters for customers with several locations and for staff investigating a change to the bill after a package upgrade.
Agree how the service start is evidenced, which billing cycle applies and how changes or cancellations will be reviewed. Test the first invoice and a transition between packages. If partial periods are required, establish how they are calculated and explained. The ISP billing guide covers those account-lifecycle decisions in more detail.
Billing and payment collection are different stages. A completed billing run records what is owed; collection results and reconciliation establish what has been received and matched to the account. Unallocated receipts, failed payments and disputed invoices need clear owners and separate follow-up. Do not assess financial performance from invoice totals alone.
For example, a customer may ask why a new location is charged differently from an existing one. The response needs the package agreement, relevant service dates and charge settings, not merely a statement that the supplier order completed. Keep the explanation with the account so another colleague can continue the conversation. The invoicing guide explains the supporting records.
When choosing software, follow a residential account and a multi-site account from enquiry through installation, billing and a support query. Review migration from the existing system, supplier-data ownership and the ability to identify unresolved orders and unpaid balances. Those practical tests show how the parts of the operation work together.
How Axiom supports FTTP and FTTC workflows
Axiom links broadband customer accounts, supported supplier requests, service references, communications and financial records. The configured broadband integrations support FTTP availability checks, catalogue selection and relevant provision or migration requests, with appointment details where applicable. Staff can use order history to review supplier responses in the customer context instead of treating each message as a separate case.
Supported bulk workflows retain individual requests and processing outcomes. FTTC products, order mapping and any bulk requirements must be confirmed against the intended supplier configuration rather than inferred from FTTP support. Configured broadband packages and service subscriptions feed invoicing, while payment and balance records support financial review. Charge-start, partial-period and cancellation requirements should be tested with the intended commercial setup.
For a multi-site enquiry, customer-linked service and order references help staff identify the relevant location before reviewing its supplier progress. The associated subscription and invoice records then provide the commercial context, rather than assuming every site has the same status.
Operational Intelligence adds recorded events, account notifications and communication history to help teams identify customers needing attention. The detailed supplier and billing records remain the evidence for investigations. A demo can follow a supplier product through a residential or multi-site order and a resulting invoice, including an appointment change or disputed charge. This establishes which operational steps are handled by the supported integration, how the account information is shared and which responsibilities remain with the provider or its partners.