Sub-agent travel portal: tiers, credit and markups without spreadsheet chaos

The spreadsheet is not a hierarchy

Most networks start honestly: a shared sheet for partner markups, another for credit limits, a folder of branded logos, and WhatsApp when someone needs an exception. It works for ten agencies. At fifty, someone books on yesterday’s net rate. At a hundred, a sub-agency’s own retailer sells a deal they were never meant to see. Month-end becomes archaeology — matching deposits, unpaid invoices and “who got which markup” from memory.

The failure is not effort. It is treating agency hierarchy travel as documents instead of as a live model. Inheritance with overrides — branding, pricing, credit, payment options and permissions cascading unless a child tier changes them — has to live in the booking engine, or every sale invents a new exception path.

What a sub-agent travel portal actually has to enforce

A sub agent travel portal is not a search box with a logo. At book time it must know who is selling, which parent owns the commercial relationship, what markup and fee stack applies, and whether the agency credit wallet or deposit covers the sale. If any of those answers come from a side file, agents invent workarounds and finance inherits the mess.

Visibility matters as much as price. Private fares, consolidator deals and certain suppliers should appear only for accredited tiers. Sub-agencies need their own users, reports and often their own white-label desk — while still inheriting rules from above. That is distribution as a product: one catalogue, many commercial faces, one ledger trail.

Markup rules that survive the next fare sheet

Markup is where networks leak money quietly. A single percentage per PNR ignores cabin, supplier, market, currency and tier. Net fares need sell-side rules; commissionable content needs a different treatment; fees should combine cleanly on the invoice. Effective dates matter when a commercial change lands mid-week and half the desk is still quoting the old sheet.

Good markup configuration is boring on purpose: percentage or flat, by airline, cabin, destination, supplier, product or agency tier, with currencies and windows the engine evaluates at shop and book. Child tiers may add their own margin inside limits you set — without editing a master spreadsheet that five people also edit.

Agency credit wallet: authority at the moment of booking

Credit limits, floating deposits and prepaid wallets only protect the master agency if they are authoritative when the agent clicks book. A balance that updates overnight is a suggestion, not a control. Low-balance alerts, blocked over-limit sales and instant restoration when a receipt posts keep the desk selling without a supervisor chasing every top-up in chat.

The same ledger should feed statements. If the agency credit wallet lives in one tool and invoices in another, reconciliation becomes a second job. Bookings should draw the balance live; documents and mid-office posts should follow the same numbers so partner statements match what the portal showed at sale.

What operators should demand from the hierarchy model

• Master → sub-agency → further tiers (and corporates) with inheritance and explicit overrides
• Markup and fee rules by supplier, product, market, currency and tier, with effective dates
• Agency credit wallet, deposits and limits enforced at book — not reconciled days later
• White-label branding and domain options per tier you choose to enable
• Fare and supplier visibility restricted by accreditation and commercial eligibility
• Roles, queues and approvals for over-limit or high-value bookings before ticketing
• Sales, ledger and commission statements per agency using the same figures mid-office reconciles
• Optional secured feeds so top-tier partners can power their own platforms from your catalogue

Treat the checklist as product requirements, not demo theatre.

Where Nucleus fits in the Elkanio suite

Elkanio Nucleus is the B2B travel booking platform for agency networks: a white-label sub agent travel portal with multi-tier agency hierarchy travel, markup rules, and credit, deposits and wallets per agency. Agents search across up to nine travel verticals on one desk — supply through Synapse, your own airline and hotel contracts through Nexus — while Vector posts invoices, tax and reconciliation as you sell.

Concretely, Nucleus lets you: define hierarchy and branding per tier; set markup and commission rules the engine applies at shop and book; run agency credit wallet balances live against bookings; hold over-limit sales for approval; and produce partner statements from the same ledger mid-office trusts. Licensing, IATA accreditation and acquiring remain yours. The platform is the layer that stops commercial policy from living only in spreadsheets.

A practical roll-out sequence

Start with the master agency and one pilot tier of real partners — not a perfect org chart on paper. Load the markups and credit limits you already use, enable the suppliers those partners sell, and watch whether bookings stop needing “can you unlock this?” messages. Wire Vector early so the first clean partner statement is part of the pilot, not a later project.

Only then deepen the tree: sub-sub-agencies, corporate accounts, tighter visibility on private content, and optional APIs for partners who want your feed in their own UI. Measure success as fewer commercial exceptions, fewer unpaid over-limit surprises, and statements partners accept without a week of reconciliation calls. You do not need a vanity count of agencies; you need hierarchy, markup and credit that behave the same on Tuesday afternoon as they do in the pitch deck.

Closing

Sub-agent growth fails in the gap between the commercial agreement and the booking click. Put tiers, markups and the agency credit wallet in the portal that agents already use, keep inheritance honest, and let mid-office read the same numbers. That is a B2B travel booking platform for a network — not a search box with a shared drive attached.

Related glossary terms