· 27 min read
How to divide ticket inventory between your website and sales partners

Your website says sold out. A partner still has tickets, another partner is asking for more, and somebody has just promised a group booking over email. You know the room isn't full yet. What you don't know is how many more people you can safely promise admission to.
Divide ticket inventory by starting with one agreed admission limit, subtracting the places already committed, and giving each independent seller a controlled allowance. If a partner can send buyers into your existing checkout instead, start there. You can recognise the partner's sales without giving another business a separate supply of tickets to manage.
The difficult part comes later, when you want unused partner tickets back. A slow sales report doesn't prove those places are free. Before offering them elsewhere, you need to close the partner's authority to sell them, resolve purchases still underway and confirm the exact quantity returned.
This guide walks through that process for a paid event with a fixed audience capacity. We'll work through a fictional allocation, the agreement each seller needs, a controlled return and the final checks before doors. The numbers are teaching examples, not recommended capacities, sales targets or platform settings.
First, find out what the partner actually needs
A sales partner might be a promoter sharing your event with their audience, a tourism business packaging admission with accommodation, or a box office taking payment through its own system. These arrangements can all bring buyers. They don't all need independent ticket inventory.
Ask where the purchase finishes. If the buyer follows a partner's link and buys through your ordinary event checkout, the partner may only need sales attribution and an agreed commission. Attribution means recording which partner gets credit for the sale. It doesn't mean reserving a block of admissions for that partner.
That distinction saves a lot of unnecessary work. You can keep availability and ticket issuing together while letting several people promote the event. The partner has a reason to sell, the buyer receives the normal ticket, and your team doesn't have to collect a second list before opening the doors.
Loopyah's promoter tools provide individual promoter links and record tickets bought through them. That is a relevant option when the commercial arrangement is promotion through your existing selling process. Don't assume a promoter link also creates an exclusive stock allowance or connects an unrelated ticket seller's checkout. Confirm the actual arrangement you need.
An independent allocation makes more sense when the partner has a real reason to sell elsewhere. It might sell an approved package through its own booking system, fulfil an existing distribution contract or operate a staffed local box office. In that case, agree how many admissions it can commit and how you will recognise each valid ticket.
Ask whether the partner needs guaranteed availability, a particular price, its own payment collection or simply a report proving its contribution. Those are separate requests. A guarantee of twenty admissions cannot be replaced by an ordinary link if your website could sell out first. Equally, a request to track twenty successful referrals doesn't require you to reserve twenty places.
Before signing anything, write a plain description of the sale. For example, the partner sends customers to the organizer's checkout and receives the agreed commission on qualifying purchases. Or the partner can sell up to its stated allowance through its own system until the agreed cutoff. Anyone reading the arrangement should know which of those promises you're making.
Work out how many audience places you can distribute
Start with the approved event layout and the people responsible for venue capacity. A building's advertised maximum isn't automatically your audience inventory. Your stage, seating, access routes, production equipment and event conditions can change what is available for this performance.
Great Britain's Health and Safety Executive discusses audience capacity alongside exits, circulation and site arrangements in its venue and site design guidance. Use the applicable requirements and competent advice for your location. A ticketing calculation records the limit your event has established; it doesn't establish a safe limit by itself.
Separate audience admissions from working personnel in your sales records, while keeping everyone within the venue's relevant occupancy controls. You need to know what the approved audience limit already allows for. Don't subtract staff twice, and don't remove them from the safety calculation because they haven't bought tickets.
For our fictional event, assume the responsible team has approved 600 audience admissions for this specific layout and made separate arrangements for working personnel within the applicable overall limits. Of those 600, you reserve 30 for existing guest commitments and retain 20 as production holds. Production holds are places withheld while the final equipment and sightline arrangements are checked.
That leaves 550 admissions available for paid distribution. This is the quantity you can divide between your website and independent sellers. The 50 withheld places are still accounted for, even if there are no buyer names against them yet. An empty record isn't spare inventory when somebody retains the right to use it.
You might initially assign 350 paid places to your website, 120 to Partner A and 80 to Partner B. Together, those allowances equal 550. Add the 30 guest commitments and 20 production holds and you reach the approved 600 audience places. No place appears in two allowances.
The website's 350 is its starting sales authority, not a forecast of website demand. Partner A's 120 is a maximum commitment under its agreement, not proof that it will sell 120 tickets. Label both clearly. Sales forecasts belong in the commercial plan; allowances belong in the control of what each seller can promise.
If guest entitlements come from sponsorship agreements, our guide to sponsor and exhibitor guest allocations explains that separate workflow. Those commitments can reduce paid inventory, but reclaiming them follows their own terms. Don't borrow a sponsor's places because a sales partner has customers waiting.
Choose a starting split you can explain commercially
There isn't a useful universal percentage for website sales versus partners. Give an allowance a reason. The partner should provide access to buyers, an agreed service or a contractual benefit that makes reserving those places worthwhile.
Ask what evidence supports the request. Previous completed sales for a comparable event are more useful than follower counts alone. For a new partner, ask about the audience, the proposed offer, the selling dates and the activity it will actually run. You can start with a smaller controlled allowance and review it rather than treating an optimistic pitch as demand already secured.
Think about timing too. A travel partner may need a decision earlier because it is packaging several services. A local promoter may produce most enquiries close to the event. Those differences affect the review dates and whether a return is useful. Tickets returned after your own selling opportunity has passed may protect capacity without helping revenue.
Your own channels deserve the same scrutiny. Keeping nearly everything on your website doesn't help if you have no plan to reach buyers. But handing out large blocks to partners can make your website look unavailable while those blocks remain unsold. The aim is to keep places available where credible demand exists, with enough control to move them when the evidence changes.
In Loopyah's November 2025 survey of 500 US event attendees, question 6 asked where people usually discover upcoming events. The Event Attendee Insights Report shows that people selected several routes, including social media, friends and ticketing websites. The chart reproduces all the answer categories so you can see the range.
| Label | Respondents % |
|---|---|
| Social posts or ads | 65 |
| Friends or word of mouth | 56.4 |
| Venue or event email | 26.6 |
| Influencers or creators | 15 |
| Ticket sites or apps | 28.8 |
| Search engines | 37.6 |
| Local news or magazines | 21.6 |
| AI search engines | 3.8 |
Source: Loopyah Event Attendee Insights Report, question 6, 500 US attendees, November 2025. Values are unweighted respondent shares. Respondents could choose up to three answers, so they do not add to 100%. Short chart labels retain the original categories' meaning. Discovery is not purchase attribution, and these results do not tell you how much inventory any partner deserves.
Use your own event records to make that decision. A buyer may discover you through a friend, read a partner's newsletter and eventually buy on your website. An attributed sale tells you how the tracking rules credited that purchase. It doesn't establish every influence behind it or prove that the sale would disappear without the partner.
When you review a channel, compare what it sold with the offer, timing and activity you agreed. If a partner hasn't started its campaign, low sales may be expected. If it has completed every promised promotion with little response, retaining a large allowance needs a stronger explanation.
Keep one current record of sales authority
You need a record that answers two questions separately. How many valid admissions have already been committed? How many additional admissions can each seller still commit? A combined sales total only answers part of the problem.
For an independent seller, the unsold part of its allowance remains unavailable elsewhere while that seller can still use it. Suppose Partner A has sold 45 of its 120 admissions. You have 45 issued or otherwise committed sales and 75 places it can still sell. You don't have 75 free places to add to the website.
This is where apparently sensible spreadsheets cause trouble. One colleague subtracts actual sales from capacity, another sees unused partner places and adds them to the public release. The partner then sells from its original allowance. Both sellers have followed their own numbers, and the event has made more promises than it can honour.
Set a single owner for allocation changes, with a deputy who can cover absence. The owner doesn't need to approve every sale. They control changes to the quantities sellers are allowed to commit and reconcile the records when those quantities move. Everyone else should know where the current approved limits are recorded.
A practical allocation record includes the event and performance, admission type, partner, current allowance, completed admissions, unresolved purchases, remaining selling authority, last confirmed report and return deadline. Add a change reference, approving person and effective time for every transfer. For reserved seating, include the exact seat identifiers rather than relying on a total alone.
Define the units. An order for four people consumes four admissions even if there is one payment. A package for two adults consumes the admissions described in the package. An add-on that grants no entry shouldn't reduce audience inventory. You can only reconcile reports after everyone agrees what the quantity counts.
Use the ticketing system's supported stock and permission controls where they provide them. A planning record is useful for commercial agreements and changes, but it shouldn't replace working system limits. If an external seller cannot be technically capped, you have a different risk to manage. A written maximum helps establish the promise; it doesn't physically stop further sales.
Our broader ticket management guide covers orders, changes, entry and financial records. This allocation record adds the authority each channel still has to make new commitments. Keep that distinction visible when you combine reports for management.
Confirm what happens during a purchase
A buyer can be halfway through checkout when you change an allowance. Their payment may complete after the partner's latest report was generated. Until you understand that behaviour, you can't decide that the reported remainder is ready to sell somewhere else.
Ask each provider how it handles temporary reservations, abandoned checkouts, delayed payments and failed transactions. A temporary reservation means stock set aside while a purchase is underway. The actual duration and release behaviour depend on the system. Don't invent a standard waiting period because it would make your return schedule convenient.
Work through the last available ticket. If two customers reach payment at once, which one can complete? Does the other receive a clear unavailable message? Does a delayed payment remain capable of producing a ticket after stock appears to return? Ask for a supported explanation and test the scenario in the appropriate test environment.
Now test a change in allowance. If you lower the seller's maximum while somebody is paying, does the system preserve that purchase, refuse the change or create an exception? You need the answer before a busy on-sale, not when the returned quantity is already live on your website.
For separate systems, treat updates as delayed unless there is a verified connection that handles these cases. A scheduled export, a notification or a dashboard refresh doesn't necessarily control what another checkout can sell. Check what the connection actually does, what happens when it fails and which team receives the failure.
Make the same distinction with refunds. Returning money, invalidating a ticket and releasing its stock can be separate actions. A refunded ticket shouldn't create a new place for sale while the original credential remains valid. Verify the provider's supported process and decide whether returned stock goes back to the original seller or to the organizer.
Write the fallback while everyone is available. If a seller can't confirm its current commitments, pause the affected release and investigate. Your response should name the person who can stop sales, the person who can obtain the report and the person who tells buyers what is happening. A shared concern without those responsibilities won't resolve a live discrepancy.
Put the operating rules in the partner agreement
The agreement needs to describe the admission being sold, the quantity the partner can commit and the limits of its authority. Identify the event, performance date, entry type and included benefits. A seller shouldn't have to guess whether an event ticket also includes a workshop, hospitality area or later session.
State whether the allowance is exclusive to that seller until a deadline, subject to periodic review or available only on request. Explain how extra stock is approved. If the partner sells its initial allowance quickly, it can ask for more; it cannot increase the quantity itself because your public website still shows availability.
Include the reporting arrangement. Specify the required ticket-level or order-level information, how it will be transferred, the reporting cutoff and the relevant time zone. Decide which reports are provisional and which confirm the final sales position. Your finance and door teams may need different information from the same sale.
Agree who collects payment, who is the seller to the customer, who issues the ticket and who handles support. Then confirm refund, cancellation, transfer and dispute responsibilities. Those decisions can affect the contract and local legal requirements, so use appropriate advice for the actual arrangement rather than copying an internet template into a signed distribution agreement.
Pricing needs its own approval. State the authorised offer and whether the partner can discount, bundle or add charges. For covered US live-event ticket sales, the FTC's fees rule guidance explains upfront total-price requirements and the treatment of mandatory charges. Check its scope and applicable local rules for your event. Your partner's advertisement matters as well as the last checkout screen.
For personal information, agree what each party needs, its responsibilities, security, access and retention. The UK's ICO explains the purposes and responsibilities to document in data sharing agreements. The guidance is being reviewed following changes in UK law. Confirm the requirements that apply to your operation; an allocation spreadsheet doesn't establish a lawful basis for sharing buyer details.
Finally, include the stop-selling and return procedure. The useful wording identifies the exact stock, the cutoff, how outstanding purchases are resolved and who confirms the return. Keep a process for late discrepancies and buyer problems after the cutoff. A deadline without a reconciliation step leaves you guessing at precisely the moment you want to move tickets.
Review sales without treating every unsold place as a failure
Set review points around actions you can still take. A review before a partner's campaign begins tells you something different from a review after the final promotion. Pick dates that leave time to change activity or transfer stock while customers can still buy it.
Ask the partner for its completed sales, unresolved purchases and current remaining authority at the agreed reporting time. Compare those with the approved allocation and the previous change record. Investigate any mismatch before discussing whether it deserves more places. A growing sales total is encouraging, but it doesn't excuse a broken stock record.
Suppose our website has sold 300 of its 350 admissions, Partner A has sold 45 of 120 and Partner B has sold 60 of 80. There are 405 paid admissions committed across the three channels. Assume there are no unresolved purchases at this review point. The remaining paid authority is 50 on the website, 75 with A and 20 with B. Those quantities add to the original 550 paid places.
If website buyers are now waiting, the commercial question is whether some of A's 75 should move. Ask about its upcoming activity, confirmed groups and obligations under the agreement. It may have a genuine sale in progress that isn't yet in the completed total. It may also have no credible plan to sell most of its remaining allowance.
Discuss the decision directly. You can agree that A retains a smaller allowance for its final activity while returning the rest. Confirm that the change is permitted or agreed, rather than assuming a review clause gives you unlimited freedom to withdraw stock. The organizer's demand and the partner's commitments both matter.
Don't describe returned tickets as recovered revenue. They are new availability in another channel. Revenue depends on customers completing purchases after the transfer. If your website has no waiting demand and little promotion left, returning the places may simplify the final operation without producing another sale.
Record why you changed the allowance. Was the partner late with agreed activity, was its audience a poor fit, or did your own marketing outperform the forecast? That explanation will help the next event more than a league table that labels every low-volume partner ineffective. Keep commercial judgment connected to what actually happened.
Reclaim an allocation in a controlled sequence
Let's move 50 places from Partner A to the website. At the review point, A has 45 completed admissions and 75 remaining under its original allowance. You agree that it will retain 25 additional places after the transfer. Its new total allowance will be 70, including the 45 already sold.
First, confirm the exact event, performance, admission type, quantity and effective time in the change request. Name the person approving the transfer and the person changing each system. If the agreement doesn't already permit the change, obtain the required agreement before touching live stock.
Next, stop A from selling the 50 being returned. The method depends on its tools. It may reduce its allowance, pause sales while the final report is produced or disable a defined group of unused ticket credentials. Obtain confirmation that the old authority has ended. An intention to stop later is not a completed return.
Resolve purchases still underway under the agreed process. If three additional admissions complete before the stop takes effect, A now has 48 completed admissions. To retain the same 25 future places, its revised total allowance becomes 73 and it returns 47, not 50. Alternatively, the parties can agree that its final allowance remains 70, leaving 22 future places. Choose and record one outcome.
Only after confirming the actual return do you increase website availability. In the clean example with no additional purchases, A's total allowance falls from 120 to 70 and the website's rises from 350 to 400. Partner B remains at 80. The three paid allowances still total 550, and the guest commitments and production holds remain unchanged.
Check both systems and the allocation record after the change. Confirm the new remaining quantity as well as the new maximum. A system might show a total cap, an additional quantity or a remaining balance; entering 70 in the wrong field could mean something very different. Read the control's meaning before saving.
Keep the return evidence with its change reference. Record when A stopped selling the returned stock, the final committed count, the quantity accepted back and the time the website release opened. The order matters. If another colleague asks why the website cannot open the extra places yet, they should see the outstanding confirmation immediately.
Use a return confirmation that both teams can act on
A return message needs enough detail for somebody outside the original conversation to make the right change. You don't need a long report for every adjustment. You do need a shared record that distinguishes the requested return from the quantity actually accepted.
For the clean transfer in our example, the request could read like this. Partner A is returning 50 general-admission places for the named performance. It currently has authority for 120 in total and has reported 45 completed admissions. The proposed new allowance is 70 in total, leaving 25 additional admissions it can sell. The website allowance will increase to 400 only after the return is confirmed.
Add the actual cutoff and time zone, the change reference and the contacts responsible on both sides. Ask A to confirm its purchase route has been restricted as agreed, its final committed count and whether any purchases remain unresolved. If it reports a different position, leave the website change pending while the allocation owner resolves the discrepancy.
The acceptance can then be shorter. Record that A's final committed count is 45, that no unresolved purchases remain under the agreed closing process, and that its remaining selling authority is 25. Confirm the 50-place return has been accepted and identify when the website's total allowance changed from 350 to 400. Keep the system confirmation with that record.
The person opening website stock should check these fields before acting:
The event, performance and admission type match the release being changed.
The final committed count includes the relevant completed and otherwise binding purchases.
Outstanding purchases have been resolved or specifically reserved within the retained allowance.
The independent seller's old authority has ended for the places being returned.
The returned quantity agrees with the new allowances and the unchanged event limit.
The change has an approver, an effective time and evidence of the resulting system quantities.
Avoid replying with a bare yes to a long email chain. Somebody may later read that as agreement to the original request even though a subsequent message changed the quantity. Repeat the accepted quantity and the resulting limits in the final confirmation. It takes a few lines and removes a lot of interpretation.
A deputy should be able to use this record without phoning the usual owner. Test that during preparation. Ask a colleague to explain how many places A can still sell and how many the website can still sell. If they need the conversation history to answer, improve the confirmation before the first live return.
Check whether another allocation is worth the cost
Before expanding an independent partner's allowance, estimate what an extra sale contributes and what the arrangement costs to operate. Ticket revenue alone can make a complicated channel look more attractive than it is. Your team may be spending paid time correcting records, answering duplicate support requests and reconciling late reports.
Use your own costs and keep the assumptions visible. A partner offering access to an otherwise unreachable audience may justify more administration than one sending existing customers through a second checkout. That is a commercial judgment, not something a tracking report can settle automatically.
Compare the independent arrangement with a simpler referral arrangement where both are feasible. Would directing buyers through the organizer's checkout preserve the partner's customer offer? Would it remove the guarantee of stock that makes the package possible? Discuss the actual trade rather than insisting every partner use the same method.
Also look at the consequence of a smaller allowance. If A uses its retained 25 places quickly, can you approve a further transfer while other stock remains available? If the answer is yes, a smaller initial block may be workable. If the partner requires a firm long-term guarantee to sell its package, that flexibility may not satisfy the deal.
Write the decision alongside the allowance. For example, you might retain an independent allocation because the partner sells an approved package, but move ordinary promotional partners to tracked links. You then have fewer separate stock balances to reconcile while preserving the distribution arrangement that needs its own supply.
Handle the awkward cases before event day
A partner says it has sold more than its allowance. Pause further affected sales, verify the records and establish which customers hold valid commitments. Don't silently delete excess orders or tell people to try their luck at the door. Escalate to the responsible commercial, customer support and venue teams, then communicate the authorised remedy to affected buyers.
Another partner has stopped responding. Its empty-looking report still doesn't establish that unused tickets are free. Follow the agreement's escalation and cutoff provisions, obtain the available system evidence and involve the person authorised to decide the next step. If you cannot establish the commitment count, keep disputed places out of a fresh release while you resolve it.
A customer wants to change from a partner purchase to a website ticket. Start with the existing valid admission. Identify who can change or refund it and how the original credential becomes invalid where replacement is required. Issuing a fresh ticket first creates a period in which the same person may hold two usable admissions.
A group booking is awaiting payment. Decide whether it is a confirmed commitment, a temporary hold with an expiry or simply an enquiry. The status depends on your accepted terms and system behaviour. Don't let a salesperson call it sold for revenue reporting while the inventory owner treats the same places as freely available.
A partner wants to keep its unsold block until doors. That may be an agreed commercial entitlement. If you want a different arrangement, discuss the return while there is still time to act. You can also consider directing its final buyers through the organizer's checkout after a completed return, provided attribution and payment terms are agreed.
A production change appears to free extra places. Keep it separate from partner returns. The responsible team must confirm those places are suitable for the approved event layout before ticketing releases them. A partner giving back tickets doesn't increase capacity; a confirmed layout change may alter available inventory through a different approval.
Reserved seating adds another check. Return specific seats and verify that none retains a valid external ticket before selling it again. Also review what the remaining seat choices look like for buyers. A transfer of scattered single seats may be technically correct while offering little useful availability to customers trying to attend together.
Keep availability messages and the door plan consistent
Channel availability and event availability aren't always the same. If your website has sold its allowance while a partner still has valid stock, saying the whole event is sold out can mislead customers and confuse your support team. Describe the actual position and, where appropriate, direct people to the authorised route that still has tickets.
Likewise, a small remaining website allowance doesn't justify a statement about the event's total remaining tickets if independent sellers retain further stock. The UK's Competition and Markets Authority discusses scarcity and countdown messages in its guidance on online urgency claims. Use accurate, supportable wording for your market and explain relevant limits. A channel-specific statement should identify the channel.
Make a planned final report before doors and decide what happens to late transactions. If independent sales end earlier, verify that their purchase routes are closed and that all committed tickets reach the supported admission process. If they continue, you need a verified way for those tickets to become usable at entry without relying on yesterday's export.
Great Britain's HSE advises planning ticketing and entry controls where arrivals may exceed capacity in its crowd control guidance. For your event, brief the door team on every authorised ticket route, duplicate scans, cancelled credentials and the person handling exceptions. The queue is a poor place to negotiate which seller was allowed another ten places.
Door sales need an allowance too. Don't assume a quiet first hour means advance ticket holders won't arrive. If your event permits walk-up sales, use the current uncommitted inventory and the event's entry controls. Coordinate late partner sales and the door together so they cannot independently use the same remainder.
Loopyah's ticket selling tools let you set ticket releases with their own quantities and prices. Those controls can support the stock offered through that selling process. Separately verify any external seller's operation; a quantity set in one platform isn't evidence that another business's checkout is restricted to the same total.
Give the exception desk current ticket references and a clear escalation route. Limit buyer information to what staff need for their job. When someone presents an unexpected partner confirmation, check the sale and its status discreetly. A legitimate customer shouldn't have to resolve the disagreement between your businesses while everyone behind them listens.
Close the money records separately from the stock
Inventory reconciliation establishes which admissions were committed and which remained unused. Financial reconciliation establishes what customers paid, what you owe each partner and what money reached the relevant account. You need both. A returned place doesn't create a refund if nobody bought it, and a ticket sale doesn't prove the money has reached your bank.
Use the agreed basis for commission and settlement. In a fictional USD example, suppose Partner B sells 60 tickets at $40 each, with no refunds or discounts. Gross ticket sales are $2,400. If the contract pays B $4 per completed qualifying ticket, its commission is $240 and $2,160 remains before any other applicable fees, taxes or event costs. Those figures illustrate this invented contract only.
If B collected the customer payments, reconcile what it remits against the sales and deductions. If you collected payment and owe B commission, reconcile the amount payable instead. The same sales total can produce opposite payment directions. Record who holds the money rather than using one column called partner payout for every arrangement.
Refunds need the same clarity. Check whether the agreement reverses commission, who funds the refund and whether other fees remain. Use the event's refund policy and the applicable selling terms. Don't assume that changing the stock balance automatically settles any amount owed between the businesses.
After the event, compare the partner's allowance, completed valid admissions, recorded check-ins, returns, refunds and unresolved exceptions. Avoid treating check-ins as the final sales count. A paid buyer can be absent, a scan can be missing and a complimentary guest can enter without contributing ticket revenue.
Review what the allocation prevented you from selling elsewhere. You may find a partner sold modestly but reached a valuable audience your own channels didn't reach. You may also find it retained too much stock until after demand had passed. Use those findings to change the next starting allowance, review date or sales method.
For your next event, take the largest independent allocation and follow one return through the process before opening sales. Confirm who can stop selling, how outstanding purchases resolve and what evidence allows the website to receive the places. When those steps are clear, you can move inventory with confidence instead of asking two sellers to promise they won't sell the same ticket.
Author: By the Loopyah Content Team
The Loopyah Content Team shares expert insights, practical guides, and industry updates to help event organizers create unforgettable experiences and stay ahead in the event planning world.









