Charter seats & hotel allotment White-label shopsTrade portalsPartner APIPricing rules engineInventory sharingWallets, not credit
Your seats and your rooms, sold by a network you control.
A seat sells once. A room sells every night. Load either one and it reaches your trade network, your agencies’ own consumer shops and trade portals on their own domains, and partner systems calling your API — every channel drawing on the same stock, the same rules and the same ledger.
Own blocks and partner blocks side by side — with stops and transit times, seats left, and the price each agency is allowed to see.
Departures --:--
TimeFlightRouteViaSeatsStatus
06:40MS714CAI→ISTDirect18Open
07:15PC744SAW→BEYIST01:304Last seats
08:05TK722BEY→CDGDirect26Discounted
09:30XY210CAI→DXBDirect9Shared
10:10NP101CAI→HRGDirect31Open
11:45SM402HRG→AYTIST02:1012Discounted
Illustrative flights. Your board shows your own blocks and the blocks partners share with you.
4Selling channels from one inventory — your network, their shop, their portal, their system
2Kinds of inventory — charter seat blocks and contracted room allotment
100%Of every fare, markup and refund written to an auditable ledger
0Seats that can be sold twice — inventory locks inside the transaction
Forty-five seconds
A seat held, then sold — start to finish.
One unbroken recording of the real system at ordinary speed, from a sub-agency’s desk. Nothing is cut and nothing is staged.
blocksmaster.net/portal
Recorded in the live system. The operator, the desks, the airlines and the passenger are invented for the demonstration.
01
Pick the trip
The destination list holds only the cities this desk can actually sell, and the calendar lights only the days there is a seat left.
02
Read the fare
Departure and arrival on their own cities’ clocks, the real flying time between them, the free baggage — and a price that already has this desk’s pricing grade applied to it.
03
Take the passenger
Passport or national ID, checked as it is typed. A passenger already booked on the same flight on the same document is flagged before the seat is taken.
04
Hold it, or sell it
Two hours free, a day for twelve dollars, three days for twenty-five — your ladder, your fees. The hold cost is charged at once and the seat comes out of the block; the fare is not due until the ticket is issued.
05
Issue the ticket
The wallet is charged, the e-ticket number exists, and the total says plainly what was fare and what was hold. No invoice, no credit, no waiting on an account.
The actual screens
Not an impression of the product. The product.
Photographs of the running system. The operator and the passengers are invented for the demonstration; every layout, figure and total is real.
Every time on the clock it belongs to.
A flight leaves on the departure city’s clock and lands on the arrival city’s. Cairo 08:40 is eleven in the morning in Dubai, and the four hours fifteen between them is the only number that means anything. Blocks Master stores the moment behind each time, so the duration is right, the flight comes off sale at its real departure, and an agent in New York sees the same truth as one in Cairo.
Sell the seat, or sell the time
Holds the way a low-cost airline does them: two hours free, a day for twelve dollars a passenger, three for twenty-five — your ladder, your fees. The hold cost is charged at once and is not refundable; the fare waits until the ticket is issued. Nothing can be held closer to departure than your cut-off, and anything not issued in time releases itself.
Profit per flight, empty seats and all
Income, fees and net fare against every block you took — with the seats that never sold carried as the loss they are. Worked out from what was recorded at the time of sale, so last month’s profit stays last month’s profit.
The block, seat by seat
Every flight with what is sold and what is left, a manifest a click away, and a flight that can be taken off sale without being cancelled. Schedules generate a whole season of departures in one go.
Every booking, and who is behind it
The desk that sold it, the staff member who keyed it, the client it was for and the wallet that paid. Holds show their deadline with an Issue link beside them. Out as PDF or spreadsheet whenever accounting asks.
Open your block to a partner, on your terms
Share by Office ID and bound it: which flights, how many seats each, a spending cap, a sales cut-off, an end date. Revoke it in one click. What the partner does with it inside its own network is theirs to decide.
Prices that react to the sale in front of them
Stack rules on a grade — a markup on a partner’s seats, a discount on returns, a premium inside 48 hours. Every matching rule adds up, and a discount can never take a fare below what you paid.
A network, not a customer list
Each desk has its own Office ID, its own currency, its own wallet and its own pricing grade — and its own clients underneath it. You see all of it; they see only their own.
Money in, before seats out
Every desk, client and API account with the balance it is spending. Issue or take back funds and the screen moves at once. Nobody can spend money that is not there, so there is no credit to chase.
A partner API, and a door to the documentation
Partners search, book, hold, cancel and reconcile from their own system — idempotent requests, rate-limit headers, webhooks and a sandbox. Keys are issued by us, never from this page: you get the secret to hand over, the developer gets everything else by email. The documentation sits behind a sign-in, and you can see who has asked for it.
Rates you read, then rates you set
The published rate arrives on its own three times a day. Your own adjustment sits beside it — fixed or percentage, per pair — so what you sell at is a decision rather than whatever a feed happened to say. Every change is logged.
What is still unsold, at a glance
Only the flights with seats left, sold against remaining, so the block that needs a push this week is at the top of the screen rather than the one somebody happened to remember.
Ticketed, and the money already moved
A reference code, an e-ticket number, and a total that says what was fare and what was hold. The ticket goes out by email as a branded PDF, and by WhatsApp if the schedule later changes.
The demand you had to turn away
When a block is full the ask is recorded rather than lost. A cancellation at three in the morning emails everyone waiting, in the order they asked — and next season you know how many seats you should have taken.
Who did what, and when
Every booking, refund, price change, wallet movement and setting change, with the person and the desk behind it. Searchable, and not editable by anyone — including you.
The morning number
Bookings, revenue, passengers and average booking value, with the split by booking class underneath — the first screen after signing in, for the question you ask first.
Click any screen to open it full size — the whole window, at a resolution you can read the figures off.
Fifteen of twenty-two screens. The rest — client and sub-agency statements, cabin classes, top-up requests, manifests, users and roles, agency settings — are in the portal.
What you distribute
Two kinds of inventory. One set of books.
Seats and rooms behave nothing alike and are contracted nothing alike — so they are modelled separately, and then run through the same wallets, the same pricing grades and the same statements. Licensed one at a time: take flights, take hotels, or take both.
Flights
Charter seat blocks
Load the block once, with its fare classes, baggage and the terms you sell it on. Everything after that — who may see it, what they pay, how long they can hold it — is a setting rather than a conversation.
The unit is a seat, sold once.
Fare classes with their own seat counts, pooled upward as the cheaper ones sell out
One way, return and open-jaw, priced as one journey rather than two halves
Departure in the departure city’s clock, arrival in the arrival city’s, and the real moment stored behind both
Hold, cancellation and name-change terms set per flight, pre-filled from your defaults
A manifest per flight, and a waiting list when the block is gone
Hotels
Contracted room allotment
Properties, room types, and a contract per season carrying the rooms you hold and the rates you hold them at. Search prices a real stay against a real contract, in the currency the contract is written in.
The unit is a room-night, and that changes everything.
Allotment counted per night, because rooms sell one night at a time
Rates written as date periods, because a price does not change just because a night passed
A stay is sellable only to its tightest night — the guest needs the same room throughout
Board and view options priced separately, per room or per person, children by occupancy
Cancellation terms per contract, in days before arrival, priced in nights or cash
Each product is switched on per agency. A desk licensed for flights alone never sees a hotel tab — not greyed out, not there.
How it works
Three steps from a chartered aircraft to a selling network.
1
Load the block
Enter the flight once: route, times, cabins and how many seats you hold in each. Set the net price you paid and the price you sell at, per adult, child and infant. Add baggage tiers if the carrier allows them.
2
Set who pays what
Create pricing grades — Partner −6%, Standard, Walk-up +4% — and assign one to each sub-agency. They see their own price, never yours. Sub-agencies can then add their own markup per client on top.
3
Fund them and let them sell
Top up a sub-agency’s wallet and they can book against it immediately. Every booking draws the wallet down, locks the seat, issues a ticket and lands on their statement and yours — the same second.
Distribution
One inventory. Four ways it reaches a buyer.
Load the block once. It then sells through your own trade network, through your agencies’ own consumer shops, through their own trade portals, and through partner systems that never see a screen — all drawing on the same seats, the same prices and the same ledger.
01Included
Your own network
Sub-agencies, on your portal
yourbrand.com/portal
The desks you appoint sign in, see the grade you gave them, and spend a wallet you funded. No credit, no invoices chased, no seat sold twice.
02Licensed add-on
B2C white label
Their shop, their domain
book.niletravel.com
A consumer storefront on the agency’s own address, in their logo and colours, with their banner across the top. It searches your real inventory at a retail price you never see on a trade screen — and the customer pays by card into the agency’s own payment account, or holds the seat free while they decide.
03Licensed add-on
B2B white label
Their trade portal, their domain
trade.niletravel.com
The same trade portal, signed in, on the agency’s own name — so their sub-agents never learn whose software it is. Wallet rather than card, because this side of the business runs on credit you control.
04Licensed add-on
Partner API
Their system, talking to yours
POST/bm/partner/v1/bookings
An online travel agent or an airline’s own site searches, prices, holds, books and cancels without a person clicking anything. Same prices, same rules, same wallet — it runs the platform’s own code rather than a second implementation that drifts.
On a white-label domain, nothing says Blocks Master.
Not the page source, not a stray link tag, not the sign-in screen, not the browser tab. The platform’s own admin screens are pushed off the client’s domain entirely, and the shop is served whole from that address the day it is pointed here — no scripts fetched from somewhere else that could be gone next year.
Partner API
Sell through systems, not only through screens.
An integrated partner is the one that does not leave. They have spent their own engineering budget pointing at your inventory — and every booking they make arrives priced by your rules, drawn from your seats and written to your ledger.
One authenticated request returns the flights a partner may sell and the price they pay — their grade and markup already applied, so there is no second price list to keep in step.
Build against a sandbox
A test key searches and prices your real schedules at your real terms, and its bookings take no seat, charge no wallet and reach no passenger. Going live is a change of credentials, not a change of code.
A retry cannot double-book
Send an Idempotency-Key and the call happens at most once however many times it arrives. A request that timed out with a family on the phone is repeated safely, and the answer says it was a replay.
Import it, do not transcribe it
An OpenAPI description and a Postman collection, both generated from the live route table so they cannot describe a version that does not exist. Every request arrives with a worked example that runs on the first send.
Told what went wrong, in a word they can branch on
A published catalogue of every failure worth handling — the wallet short, the seats gone while they were deciding, a hold lapsed — each with what it means and what to do about it.
Pushed to, not polled
Webhooks for confirmations, cancellations, holds about to lapse and flights that moved — signed, retried on a ladder, and carrying a delivery number so a repeat is recognised.
A key that only works from their servers
Restrict a key to the addresses it is allowed to call from, and a stolen secret is useless anywhere else. You tick the addresses it has actually been calling from — no typing, and nothing to ask the partner for.
You are not the help desk.
Credentials are issued by you and never self-served: the developer is emailed everything except the secret, and the secret is shown once, to you, to hand over. The documentation sits behind a sign-in you approve, and it is written to be complete enough that an integrator never has to ask you a technical question.
The platform
Everything the back office was doing by hand.
New
Return and open-jaw search
One way, return or multi-city — out to Istanbul, back from Antalya. Each leg opens as its own list with previous / next day, the nearest available date as a remark, and a calendar that lights only the days you actually fly.
Sort, compare, select
Results sorted by price by default, or by departure or arrival time in one tap. Big times, the flight number, stops with transit airport and duration, and seats left on every card.
New
Hold now, issue later
Sell time as well as seats: two hours free, a day for a fee, three days for more — your ladder, your fees, per passenger or per booking. The hold cost is charged at once and is not refundable, the fare waits until issue, nothing can be held inside your cut-off, and anything not issued in time releases itself. Your own staff get a free short hold.
IATA baggage allowance
Every flight states what is included: backpack 40×30×20, carry-on 55×40×23 with its kilos, checked bags by piece or weight up to 158 cm — plus paid extra tiers per passenger.
Passport or national ID
Passenger details in the order a check-in desk reads them: name, then the travel document — passport with place of issue and expiry, or a national ID — then contact details.
New
Pricing rule engine
Stack rules on a grade by source, partner, trip type and hours before departure. Every matching rule adds up, fixed amounts are per passenger, discounts never go below cost, and discounted fares are flagged in search.
Grades and client markups
Named grades for sub-agencies, a grade for your own staff, and each sub-agency’s own markup for its clients — agency-wide or per client, every change in the audit log.
A network, not a customer list
Main agencies above their sub-agencies, each with a unique Office ID. Every user, wallet, price and booking is scoped to the right tier — no one sees another’s clients, prices or balances.
New
Inventory sharing with limits
Share by Office ID and decide exactly what: which flights, seats per flight, a spending cap, a sales cut-off and an end date. The partner chooses which of its sub-agencies see it.
Wallets instead of credit risk
Sub-agencies spend a balance you funded; their clients spend an allowance carved out of it. Nobody can spend money that is not there, and every movement is a ledger line.
Cancellations priced by your policy
A fee ladder by hours before departure. The agent sees the exact fee and refund before confirming; seats go back to inventory and the refund to the wallet in one transaction.
Multi-currency, reconciled
Buy in the operator’s currency, sell in the agency’s. Conversion runs at the rates you maintain, and every booking keeps the rate it used — so a statement from six months ago still adds up.
Reports that name names
Bookings reports showing the sub-agency, the staff member who booked and the client, plus client and sub-agency statements — on screen, as PDF or as a spreadsheet.
Branded e-tickets
Your logo, big departure and arrival times, the flight number up front, PNR and e-ticket numbers — on screen, as a PDF and in the confirmation email.
Schedule-change alerts
Move a flight or a whole schedule and every affected booking is flagged, the agency is alerted and passengers are told by email and WhatsApp.
Security built in
Two-step email codes for administrators, trusted devices, login throttling, a private sign-in address, and a logged “log in as” so support can see exactly what an agent sees.
New
Two clocks on every flight
Departure is the departure city’s time and arrival is the arrival city’s — Cairo 08:40 to Dubai 13:55 is four hours fifteen, not five. Each flight stores the real moment behind both, so durations are right and a buyer in another time zone sees the same truth.
Off sale the moment it departs
A flight stops selling at its own departure instant, in its own city’s time — not at midnight, and not whenever somebody remembers. Searches, holds and the waiting list all stop with it.
A waiting list for a full block
When the seats are gone the ask is recorded rather than lost. A cancellation at three in the morning emails everyone waiting, in the order they asked — and next season you know how much demand you turned away.
Name changes by your own rule
Allow them or do not; set a fee and a cut-off the way you set the refund ladder. The agent sees the fee before committing, the wallet is charged, and the old and new names both stay in the log.
New
Profit per flight, empty seats included
Income and fees against the net fare you paid, with every seat that never sold carried as the loss it is. Figures come from what was recorded at the time of sale, so last month’s profit does not move when today’s prices do.
Rates that refresh themselves
Published rates read three times a day, on their own. Each agency can then put its own markup on top — fixed or percentage — so the rate you sell at is a decision, not whatever a feed happened to say.
Top-ups and low-balance warnings
A desk asks for a top-up from inside the portal and you approve it; the ledger line writes itself. Set a floor per wallet and the warning arrives before a sale is refused at the counter.
New
A partner API an integrator cannot get stuck on
Search, hold, book, issue, cancel and reconcile from a partner’s own system. An OpenAPI description and a Postman collection generated from the live routes, a sandbox key whose bookings take no seats, idempotent requests so a timeout cannot double-book, a published catalogue of every error worth handling, signed webhooks, and a written promise about what will never change inside v1.
New
Keys locked to a partner’s own servers
Restrict a key to the addresses it may call from and a leaked secret is useless anywhere else. You tick the addresses it has actually been calling from rather than asking for them — and it remembers several, because a partner behind a load balancer calls from more than one.
New
A consumer shop on your agency’s own domain
Their logo, their colours, a rotating banner and their own sign-in picture — searching your real inventory at a retail price that never appears on a trade screen. Light and dark, built to be read on a phone in daylight, and served whole from their address rather than fetched from somewhere that may be gone next year.
New
Their trade portal, on their own name
The same signed-in portal their sub-agents already use, wearing the agency’s brand on the agency’s domain — down to the sign-in screen and the browser tab. Nothing in the page, the source or the address gives away whose software it is.
New
Card payments that never touch us
Each agency connects its own payment account and the customer pays that agency directly, under the agency’s own merchant agreement. The platform is never the merchant and there is deliberately nowhere to put one — holding other people’s money is a licensed business, and this is not it.
New
Allotment counted per night
Rooms sell one night at a time, so allotment is per night while rates are date periods — a price does not change because a night passed. A stay is sellable only to its tightest night, because the guest needs the same room throughout.
Contracts, seasons and board
A contract per season carrying the rooms you hold and the rate you hold them at, in the contract’s own currency. Board and view options priced per room or per person, children by occupancy, and a release date after which unsold rooms go back.
A calendar that marks nights with rooms
The same calendar the flights use, marking the nights that survive every test a search applies — in season, not stopped, rooms free, covered by a rate. A desk stops guessing dates and being told no.
New
Terms set per flight, not per company
A seasonal rotation and a one-off pilgrimage charter are not sold on the same terms. Hold, cancellation and name-change ladders live on the flight, pre-filled from your defaults — and a change to those defaults reaches the flights nobody has booked yet, while a flight with a passenger on it keeps the terms they agreed to.
A history log nobody can edit
Every booking, refund, price change, wallet movement and setting change, with the person and the desk behind it — searchable, and not editable by anyone, including you.
New
Backups that leave the building
A nightly archive of the things that cannot be re-entered — bookings, passengers, tickets, wallets and every movement through them — kept on the server, emailed off it, and copied into your own Google Drive.
The overnight work, watched
Holds expiring, reminders going out, rates being read, the backup running: each one shows when it last ran and when it is next due, and says so plainly when it falls behind instead of failing in silence.
Manifests and duplicate catching
A manifest per flight in the format a handling agent expects, and a warning when the same passenger is about to be sold the same seat twice.
Travel documents cleared on a schedule
Passport numbers and expiry dates are needed right up to travel and of no use to anyone afterwards. They clear themselves once travel is far enough behind, and the booking, tickets and money stay untouched.
The portal
One address. Four very different workspaces.
Nobody is handed a menu of pages they are not allowed to open. Signing in resolves the person’s role and their agency’s tier, then builds the interface from what they can actually do. Pick one and watch it rebuild.
AAAgency AdminMain agency · runs the network
Workspace
Dashboard
Search & Book
Agency Bookings
Inventory
Flights
Cabin Classes
Inventory Sharing
Network
Sub-Agencies
Users
Finance
Wallet Control
Pricing Grades
Agency Admin
Everything: the inventory they load, the sub-agencies they sell it through, the grades those agencies pay, and the wallets funding it all.
Seats loaded1,240
Sub-agencies18
Month revenueUSD 214k
CAI–DXB82%
CAI–IST64%
HRG–IST41%
Questions
The things operators ask first.
Can my sub-agencies see what I paid for the seats?
No. A sub-agency only ever sees the price their pricing grade produces. Your net cost, your margin, and every other agency’s pricing are never sent to their browser — the prices are calculated on the server before the results are returned.
What stops two agencies selling the same seat?
Seats are reserved inside the same database transaction that takes the payment, with a guarded update that only succeeds if the seats are genuinely still available. Two simultaneous bookings for the last seat cannot both win — the second is refused before any money moves.
How do I get paid?
You do not chase invoices. A sub-agency can only book against a wallet you have already funded, so the money is with you before the seat leaves your inventory. Their balance, every transaction and a downloadable statement are always visible to both of you.
What happens when a passenger cancels?
Your cancellation policy decides. You set a fee ladder by hours before departure; the agent sees the exact fee and refund before confirming, and on confirmation the seats return to inventory and the refund is written back to the wallet that paid it, as a reversing ledger entry.
We sell in a different currency to the one we buy in.
That is the normal case. Net prices stay in the operator’s currency, wallets are held in the agency’s, and conversion happens at the rate you maintain on the platform. Every booking stores the rate it used, so a statement from six months ago still reconciles.
Can I share my block with another agency without losing control?
Yes. You share by the partner’s Office ID and set the limits: which routes, schedules or flights, how many seats per flight, how much value they may draw, a sales cut-off before departure and an end date. The partner can only narrow that further — for example, showing it to some of its sub-agencies and not others.
Can prices change with the trip or the date?
That is what pricing rules are for. On any grade you add rules by inventory source or partner, trip type (one way, return, open jaw) and hours or days before departure. Every matching rule is added up, discounts can never take a partner’s seats below your cost, and the price an agent sees in search is exactly the price the booking charges.
Can we use our own branding?
Further than most people mean by the question. Each agency uploads its own logo and terms, which appear in its portal, on its ticket PDFs and in the emails its clients receive. Beyond that, an agency can run the consumer shop and the trade portal on its OWN domain — its logo, its colours, its banner, its sign-in screen — with nothing in the page, the source or the browser tab naming this platform.
Who takes the money on a consumer sale?
The agency does, directly. Each agency connects its own payment account and the customer pays that agency under its own merchant agreement. We are never the merchant and there is deliberately nowhere in the system to put a platform-wide one — holding other people’s money makes an operator a payment intermediary, which is a licensed, capitalised and audited business. Drawing that line in the architecture is what keeps the platform out of it.
Do hotels work the same way as flights?
Underneath, yes — the same wallets, grades, markups, statements and audit log. Above, no, and deliberately: a seat is sold once while a room is sold per night, so allotment is counted per night, rates are written as date periods, and a stay is only sellable to its tightest night. Each product is licensed separately, so you can take one, the other, or both.
I am not technical. Will the API become my problem?
It is built so it does not. Your partner’s developer gets a machine-readable specification and a ready-made request collection generated from the live endpoints, a sandbox key that books nothing real, a published list of every error and what to do about it, and a written statement of what will never change. You issue the credentials and hand over one secret; the questions that would otherwise reach you are answered before they are asked.
Cleared for take-off
Put your next block in front of the whole network.
Your Office ID, your grades, your branding — set up with you, agency by agency.
Access is granted agency by agency. Send us your details and we will set up your Office ID, agree your pricing grade, and walk your team through the portal — usually within one business day.
