> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://learn.nuwebgroup.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://learn.nuwebgroup.com/_mcp/server.

# How do ticket allocations work across multiple sales channels?

> How venues divide ticket stock between direct sales, box office, agents and partners, and manage shared pools, fixed allocations, permissions and reconciliation.

**Ticket allocations let an event operator divide or control inventory for different sales channels, such as an official ticket shop, box office, promoter or external ticket agency.** The operator sets which tickets each channel may sell, whether the stock is exclusive or shared, and when unused tickets can return to other channels.

The underlying event capacity does not increase when a new seller receives an allocation. The platform is distributing access to existing stock, not creating more admissions.

## What does a multi-channel ticket allocation control?

**An allocation controls which inventory a seller can access and, depending on the platform, how much of that inventory the seller may commit.** It may also carry dates, product restrictions, price bands or customer-eligibility rules.

A venue could sell tickets on its own website while reserving a group of seats for a corporate partner. An external agency could receive permission to sell 150 general-admission places. A box-office team could retain seats for accessible bookings or local customers. These are different commercial arrangements, but each requires inventory and permission rules.

An allocation is not necessarily a separate database of tickets. Some systems ring-fence specific seats or quantities; others offer multiple channels access to one shared pool while applying seller-specific ceilings.

## How do fixed allocations differ from shared inventory?

**Fixed allocations set aside identifiable stock or quantities; shared inventory lets authorised sellers compete for a common pool subject to real-time availability.**

| Model                     | How it works                                                                 | Main trade-off                                                             |
| ------------------------- | ---------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
| **Exclusive allocation**  | Specific seats or quantities are reserved for a particular seller or purpose | Clear separation, but stock may remain unsold elsewhere                    |
| **Shared inventory pool** | Multiple channels request stock from one authoritative pool                  | Better stock utilisation, but stronger real-time coordination is essential |
| **Hybrid allocation**     | Some inventory is exclusive; the remainder is shared                         | Flexible, but requires clear priority and release rules                    |

The word *allocation* can also refer to a price band or a reserved operational group. Its precise meaning depends on the platform. Ticketsolve, for example, documents distinct agent, public, box-office and reserved allocation levels, with additional rules for exclusive seats.

If an external seller cannot connect to real-time inventory, a fixed allotment may be simpler to control. If several sellers can transact against the same authoritative reservation service, shared inventory can reduce the need to manually redistribute unsold stock.

## How does the inventory add up across sellers?

Consider a hypothetical event with **1,200 admission places released for sale**. The operator chooses fixed allocations:

| Channel                   | Initially allocated |    Sold | Still allocated but unsold |
| ------------------------- | ------------------: | ------: | -------------------------: |
| **Official website**      |                 800 |     600 |                        200 |
| **External ticket agent** |                 250 |     100 |                        150 |
| **Venue box office**      |                 150 |      90 |                         60 |
| **Total**                 |           **1,200** | **790** |                    **410** |

The event has 410 unsold places within these allocations, assuming no separate basket reservations or operational holds. But the official website can offer only 200 of them under the current fixed-allocation rules. The other 210 remain assigned to the agent and box office.

Suppose the agent returns 100 unused places and the operator transfers them to the official website. The revised allocations become 900 online, 150 for the agent and 150 for the box office. Total released stock remains 1,200; completed sales remain 790; the official website's remaining unsold allocation increases from 200 to 300.

This is a simplified fixed-pool example. Real implementations must account for active baskets, refunds, complimentary tickets, held seats, transfers and potentially linked packages before calculating what can safely be reallocated.

## How do operators reclaim or redistribute unused allocations?

**Allocation release lets an organiser return unsold stock to another seller or to general availability, but only stock without valid commitments should be reassigned.**

Release rules may be manual, scheduled or conditional on sales performance. A theatre might return agency tickets to its website several days before opening night. A festival might release a promoter's unused allocation after an agreed deadline. A dynamic system might activate a later pricing or distribution stage when the current allocation is exhausted.

Before changing allocations, the operator needs to establish which units are sold, in active baskets, held for specific purposes or promised under an external settlement agreement. For reserved seats, returning a seat should not invalidate a customer's already confirmed order.

The technical and contractual processes are separate. Moving inventory between channels in a dashboard does not automatically settle the finances or amend the terms with the partner.

## Who can see, sell or edit an allocation?

**Allocation visibility, sales permissions and configuration ownership are distinct forms of control.** A partner may be allowed to sell from a stock group without permission to increase its limit or release another partner's seats.

Typical roles include a partner who sees only its sales and remaining allowance, a box-office operator who can sell restricted seats, an event manager who can approve reallocations, and a finance user who can reconcile order revenue without editing stock.

These distinctions matter because a single broad account may expose other sellers' customer records, commercial terms or inventory. A well-designed implementation limits both what a user can do and which events or allocations that user can access. Permissions should be enforced by the underlying system, not merely by hiding buttons in a dashboard.

## How are sales reconciled across channels?

**Multi-channel reconciliation compares what each seller has committed with the event's central inventory and financial records.** It should separate ticket validity from seller settlement.

A third-party agency might process the payment under its own merchant arrangement, while the venue's access-control system needs a valid ticket identifier for admission. Another partner might sell through the venue's existing checkout and receive a commission. The payment, customer-data and ticket-fulfilment responsibilities differ considerably.

Useful reporting distinguishes allocation issued, confirmed sales, cancellations, active reservations, ticket transfers and remaining stock. Where channels operate in separate systems, teams should agree when records are imported, which barcodes are accepted, how duplicates are detected and when discrepancies are resolved.

Ask prospective technology providers whether the same event can combine shared and exclusive pools, whether partners have restricted access, how stock is released and how the platform prevents commitments from exceeding capacity across channels.

**The practical result:** allocations can extend an event's distribution network without surrendering control of its capacity—but only when stock, permissions and reconciliation are designed together.

## Related explanations

#### [How do ticket allocations work across multiple sellers?](/distribution-access/how-do-ticket-allocations-work-across-multiple-sellers)

Distribution & Access · Sales channels

#### [How do ticketing platforms manage capacity across related events?](/events-inventory/how-do-ticketing-platforms-manage-capacity-across-related-events)

Events & Inventory · Allocations and holds

#### [How do ticketing platforms manage sales holds and house seats?](/events-inventory/how-do-ticketing-platforms-manage-sales-holds-and-house-seats)

Events & Inventory · Allocations and holds

#### [What is a ticket allocation?](/events-inventory/what-is-a-ticket-allocation)

Events & Inventory · Allocations and holds

[More in Events & Inventory →](/events-inventory)