NEW! Release notes Business Engine November 2026

Services and Orders

New service pages in Admin Your services are at the heart of what you sell, so we have rebuilt the pages where you manage them. You manage versions the way you are used to, from preparing a new version to publishing it and moving existing orders over, and the version list shows how many orders are on each one. The legacy page is still available, and a link takes you there if you need it.

Tag your services and filter orders by tag Tags are short labels you put on your services, such as TV, Business or Fall campaign. Use them as keywords to group services your way, then find every order in that group with one filter on the order list in the new Admin. Combine several tags, for example Business and TV, to quickly find the customers to reach or the orders to include in a price change. Service providers can create their own tags, which only they can see. Read more here.

Hide a service from the marketplace in selected areas On each object group connected to a service, you can now hide the service from the marketplace in that group only. The service is still shown everywhere else, and you can still order it for a customer from Admin and the API, so you no longer need a copy of the service per area.

Marketplace

A marketplace for each ISP This applies if you run an open access network with several ISPs. Each ISP can now have its own branded marketplace and customer portal, alongside a joint marketplace for the whole network. Password reset and account confirmation emails link customers back to their own ISP's site. To set up a marketplace per ISP, please contact COS support.

Billing and Payments

This applies if you bill end customers through Business Engine.

Your own payment retry schedule Under Billing → Payment retries in the new Admin, you decide per customer type when a failed automatic payment is tried again, how many times, and what happens after the last try. The customer page shows how many attempts have failed and when the next one is due. The default schedule works the same way as before.

Suspend after failed payment attempts You can now suspend an account after a set number of days with failed payment attempts instead of days past due, so weekends and holidays without a retry don't count against your customers. Set it per customer type in the billing settings. If you limit suspensions per run, you can also choose whether the newest customers or the oldest debt go first. Read more here.

Pause collections for a payment arrangement When a customer promises to pay by a certain date, set Automatic payments paused until on the customer page, with a bulk action or through the API. Until that date there is no automatic charge, no past due email, no late fee and no suspension. You can also exclude a customer from autopay or auto-suspension until a date, after which they are included again automatically.

A remittance address for each payment processor Each payment processor can now have its own invoice template, so paper and PDF invoices show the right send payment to address for the customer's region. Invoices for processors without their own template look the same as before.

Pre-paid services You can now let customers pay for their service in advance. Choose pre-paid billing per customer type, and customers pay for each period before it starts, either automatically by card or themselves in the marketplace, where they can also pay several periods ahead. If a period isn't paid, the service is paused and turned on again as soon as the customer pays. Read more here.

Plan bulk price changes by billing date The order list now has a Next billing date column and filter, so you can run a price change in batches that start at the beginning of a billing period. You can also filter on orders whose latest price change was skipped or failed. Read more here.

Tickets

Hand tickets between operator and ISP This applies if you run an open access network. Tickets can now be passed back and forth between the operator and an ISP, and it's always clear who needs to act next. Needs response counts the right tickets for each side, the ISP gets an email when a ticket is handed to them, and the status can switch automatically when the ISP replies. Read more here.

SLA escalation emails The escalation rules on ticket priorities now send an email when a ticket has used the share of its SLA time you set, to the team lead, the assigned user or a specific address. Each ticket is escalated once per priority.

Network and Provisioning

Static IP as an add-on This applies if you use IP management in Business Engine.
You can now offer a static IP address as an add-on service. The address is assigned automatically from IP management when the order is provisioned. To set it up, please contact COS support.

API and Integrations

API page in Admin API documentation, your connection details and setup steps are now gathered on one page in Admin. If you need API access, request it there with a short form, and collect your credentials securely once they are ready. Read more here.

More you can do with the API The API now covers more of your daily work:

• Create Business Engine and FSM users.
• Send a customer a passwordless login link by email.
• Set metadata on areas when you create or update them.
• Read a customer's available funds.
• Read and remove stored setting values.
• Link existing tickets to FSM work orders.
• Receive the EntityDiscarded webhook when a record is discarded.

All endpoints are described in the API documentation.

Vetro Address Book This only applies if your installation is integrated with Vetro. Units in apartment buildings are now linked to their building automatically when you sync from Vetro, and their addresses come from Vetro's Address Book. The address import log shows when a unit couldn't be linked, and why. To turn on Address Book, please contact COS support. Read more here.

Field Service Management

This only applies if you use FSM for work orders.

A closer connection to FSM Provisioning errors are now sent to FSM, so the technician sees why a service can't be activated. Cancellation reasons are shared in both directions, and if you create a work order on an order that is still waiting for approval, you are asked to confirm first.

Admin and Sign-In

Sign in with Google or Microsoft You can now sign in to Business Engine with your Google or Microsoft account, and move between Business Engine, FSM and Wholesale Engine from the product switcher without signing in again. Your administrator chooses the sign-in method for each user. To turn it on, please contact COS support. 

Saved views on every list page Save the filters and sorting you use most as a view, set one as your default, and pick up where you left off.

Smaller Improvements

• Every bulk action asks you to confirm before it runs, and work orders can be discarded in bulk.
• New filters on orders (group and area), users (role), service types (speed) and objects (location source).
• The deployment portal lets installers take photos with the camera and use satellite view when they drop a pin.
• You can choose the price type on manual invoice rows and limit which roles can edit row descriptions.
• Calix Cloud now sets the SSID and password for all bands, and network element models can be marked as WiFi capable.
• Paystack verifies a new card with a small charge that is refunded straight away, and the customer is told before entering card details.
• The API can now create users, send passwordless login links and read available funds, and the EntityDiscarded webhook fires when a record is discarded.
• We fixed a number of bugs, including card updates from Stripe now syncing to Business Engine, manually created invoices including taxes and fees, and invoice tax lines showing state, county and city names.