The dedicated billing, POS, and inventory deployment that ran counter operations for live businesses. Its invoicing, tax, stock, and day-end model now lives inside NoxOrigin as the Commerce and Finance areas.
This is not a separate product and is not sold separately. It is the operating history behind one area of the product you can buy today.
Nox-Billings was built because a real operation needed it, and it ran long enough to teach us something the general product could not learn from a spec. What it could not do — and what almost nothing can do — is hold a relationship, its delivery, and its money in the same place. That is the limitation the unified product removed, and it is why these deployments ended up as areas rather than as products.
Nothing was thrown away. The workflows, the permissions thinking, and the operational judgement all carried into NoxOrigin — they simply stopped being the whole story.
Customer and contact records with ownership and activity
Opportunities with stages, next actions, and lost reasons
Projects and tasks attached to the client
Quotes, GST invoices, payments, and receivables
Client money: quoted, billed, collected, outstanding
No. Nox-Billings was a dedicated deployment that ran real operations. Its model now lives inside NoxOrigin as Commerce + Finance. There is one product, one set of plans, and one operating record — this page is kept because the name is still searched for and because the history is genuinely part of how the product was built.
The dedicated billing, POS, and inventory deployment that ran counter operations for live businesses. Its invoicing, tax, stock, and day-end model now lives inside NoxOrigin as the Commerce and Finance areas.
Yes, and it is scoped separately from the standard plans rather than sold as a different product. Integrations, data migration, white-label or customer-branded deployments, and dedicated environments are all handled as custom scope — see the custom-scope note on the pricing page.
You gain the joins. The specialist workflows still exist as product areas inside NoxOrigin, and they now read from the same customer, project, and money records instead of holding their own copy. Migration is scoped work, and the mapping is agreed before anything moves.
Because the name is still in search indexes, in old emails, and in the vocabulary of people who dealt with us. Deleting the page would waste that. Rewriting it honestly is more useful than pretending the name never existed.