Skip to main content
The Nuweb platform is an event management and ticketing system. You use it to create events, sell tickets and products, manage customers, process payments, control venue access, and run on-site operations — all from a single admin dashboard. This documentation is a reference for everything the platform can do. Whether you’re setting up your first event or looking up how a specific feature works, start here to understand how the pieces fit together.

How the Platform Is Structured

Everything in the platform revolves around a few core concepts. Understanding these will help you navigate both the system and this documentation.

Companies

A company is your account on the platform. It’s where all your events, customers, orders, and settings live. Each company has its own ticket shop — a public-facing website where customers browse and purchase. Companies can operate independently or as part of a parent–child structure, where a parent company manages shared settings and features across multiple child companies.

Events

Events are the central building block. An event has a date, a location (physical, online, or both), and one or more things to sell. Events can be standalone or grouped into a schedule for recurring or multi-date series. Each event is configured with its own capacity controls, access control rules, sales periods, and page customisations.

Sale Items

A sale item is anything a customer can purchase — tickets, products, guest list entries, donations, season tickets, or bundles. Each sale item is configured with its own pricing, stock, on-sale dates, and sales channel visibility. Sale items are sold through an inventory — the entity that owns and lists them. Events are the most common inventory, but sale items can also belong to EPOS shops or to the company itself (for items sold independently of any event). Sale items can be enhanced with add-ons, restricted to customer groups, and organised into groups that control how they appear to customers.

Orders & Customers

When a customer completes a purchase, it becomes an order. Orders contain individual order items — each with a unique barcode — and support refunds, modifications, and transfers. Customers are created automatically when someone makes a purchase or registers an account. You can manage customer profiles, merge duplicates, and segment customers into groups for targeted access and pricing.

Sales Channels

Sale items can be made available across multiple sales channels, and each channel serves a different selling context:
ChannelDescription
Ticket ShopYour customer-facing website. Customers browse events, select items, and check out on their own. The shop supports event listings, search, a global basket across multiple events, and guest checkout. Its appearance is controlled through the CMS.
Box OfficeStaff-assisted web sales — at the door, over the phone, or anywhere a staff member is helping a customer. Runs inside the shop with staff authentication, adding operational tools like instant checkout, named orders, and additional payment methods.
Mobile Box OfficeStaff-assisted sales through the Box Office Pro mobile app, designed for on-the-ground selling with connected hardware.
KioskSelf-service purchasing for customers at a physical location, without staff involvement.
APIProgrammatic sales through the public API, enabling third-party integrations and custom sales flows.
Each sale item can be independently enabled or disabled per channel, so you can control exactly where each item is available for purchase. The documentation is organised into sections that mirror how the platform works: Use the sidebar to drill into any section, or use the search to jump directly to a specific feature.

Beyond the Core Platform

This tab covers the admin platform and ticket shop. For other parts of the ecosystem, see the other documentation tabs:
  • Mobile Apps — Access Control Pro, Box Office Pro, and EPOS Pro for on-site operations with mobile devices.
  • API Reference — Public API for building integrations, automating workflows, and accessing platform data programmatically.
  • Webhook Reference — Real-time event notifications for external systems.