Your venue doesn’t work like the others. Your system doesn’t have to either.
In GVenue almost everything is configured per venue, and what’s missing we build for you: you talk to the person who programs, we deliver it in stages, and it switches on only at your venue.
Before writing a single line, most of what venues ask for is already a setting. These are real examples of what each venue adjusts in GVenue today, without touching anyone else:
Floor and tables
Open a table with name and ID, or without asking for any data.
Send the order ticket the moment the waiter taps “Send”, or later.
A waitress PIN on every order, or a waiter PIN on the order PC.
Only the till charges tables, or waiters charge too.
Ask “free the table or keep it?” once the bill is paid.
Who serves each table, picked by tapping the floor plan.
Automatic screen lock after a while without use.
Till and payments
Quick sale without opening a table, and PedidosYa as its own channel.
Mandatory change float: no table opens without it.
Cash payment discount, at the percentage you choose.
Table payment by bank transfer with a QR, and Mercado Pago only if you turn it on.
Comp and birthday buttons that ask who authorizes them.
The final closing waits for the bar count, or just warns you.
Bar and kitchen
The same product at a different price in each area.
2-for-1 and happy hour by day of the week and time slot.
Printers and stations: where each menu category goes.
The bar ticket without prices, in large print or one per product.
Ticket margin adjusted if the printer cuts off an edge.
Stock counts by staff, or keep going without counting from an opening.
Door and tickets
Ticket tiers with their own price, allocation and sales window.
Move to the next tier automatically when the current one sells out.
The door scanner also reads national ID cards.
Sell tickets or assign a table from the same scanner.
ID blacklist and ticket types only one person can sell.
Discount codes per event, with a usage cap.
Members and loyalty
Membership levels, each with its own range of member numbers.
The points-to-balance rate, and whether points can go to another member.
A daily cap on the points a member can transfer.
Monthly allowances per membership, with a daily cap.
Membership dues with automatic suspension after however many overdue you choose.
Bonus balance by level when a member tops up in advance.
Every panel screen set to “no access”, “view” or “view and edit”.
Locked profiles: the cashier works only from her board; the kitchen, only its screen.
Each fixed device opens its own screen: order PC, till, kitchen and bar tablets.
Sound and announcements
The week’s music scheduled by time slots.
The caller’s voice: female, male, or alternating between both.
How many times each call repeats, and whether it says the name or just the number.
Also notify by WhatsApp, plus the tone and zone of each announcement.
Modules
Over forty modules and add-ons that switch on per venue, one at a time.
Switching a module off hides it from the screens, but keeps its data.
The restaurant’s service day opens by itself from the weekly schedule.
Test mode: try orders, printing and payments without touching real operations.
What venues asked us for, and we built
53 things built at the request of a nightclub, a bar with a kitchen, a members club, a beach club, a theater or a promoter. Today they live in the system, and each venue turns them on if it wants them.
Floor and waitstaff
Waiter PIN on the order PC: the screen locks, and every order is recorded under whoever typed their PIN.
Report by waiter: tables served, orders, sales and average check, per night or by date range.
“Picked up” on the order-ready sign: you see what has left the pass and what is still waiting.
A list of tables charged by waiters with a “received” check: the till knows what each one handed in.
Communal table: one long table with several groups, each with its own bill.
Join, move and renumber tables mid-service, and move guests to another room.
Open a table with a registered customer’s ID, which suggests their phone number without showing it in full.
Search tables by number or by name, with wildcards.
Free all paid tables in one go.
Order from your seat with your ticket code, paying before it’s brought to you.
Birthday menu loaded onto the table by the runner.
Kitchen and bar
Order printing agent: a PC on the kitchen network prints every order by itself, nothing to install.
Kitchen tablet and bar tablet: each opens straight into its own order screen.
Pickup bar ticket: no prices, large print, the cashier’s name or one per product.
Cross-bar sales: pay at one bar, pick up at another, and stock drops where it’s handed over.
Promotions by day of the week and by time slot.
A ticker and clock showing all of the night’s promotions on screen.
Printed menu built from the bar catalog.
In-house delivery: phone orders with customer search, and orders from the venue’s website.
Till and payments
Void a table payment with a mandatory reason: the balance comes back and who and why stays on record.
Void a bar sale with a reason: it restocks, refunds the balance, removes the points and cancels the order ticket.
No table opens without a change float: there’s always change.
Cash payment discount, calculated automatically.
Table orders paid by bank transfer with a QR on screen.
Comps and birthdays in quick sale, with who authorized them shown in the closing.
Losses (bills that went unpaid) kept separate and visible in the closing.
Each guest’s credit balance, always visible when charging.
Members and loyalty
Member numbers by level: each membership has its own range, and numbers from cancellations are reused.
Member card with a different frame per level, with its own shape, not just a color.
Swap points for balance and give points to another member from the card, with a WhatsApp code.
Monthly membership allowances used from the table, added to the bill as “Membership $0”.
Members desk for the cashier: look up, deduct, sign up and collect dues, all included in the cash count.
Membership dues and a card that opens the door, showing the photo and dues status.
Memberships that credit a balance, plus a bonus by level when topping up in advance.
Member balance and points over the venue’s WhatsApp, with a single-use link.
Door and tickets
Restricted ticket types: only the authorized person at the box office can sell them.
ID card reader at the door and on every screen that asks for an ID.
ID scanned with a phone, one member after another, without reconnecting.
Assign the table when scanning the ticket: the whole purchase sits together.
Door sales with a sequentially numbered municipal ticket.
Promoter lists with an allowance, and comp drinks are set by a supervisor.
Discount codes per event, with a usage cap.
Reports
Night traceability: table bills reconcile to the peso, and if something doesn’t add up, it says by how much.
The night minute by minute, to replay it and compare it with another.
Test mode with a banner on every screen that, when finished, deletes only what the test created.
Sound and announcements
Voice caller: “Order 9 is ready for pickup” over the speakers, lowering the music.
Argentine voices, female and male, with the option to alternate them order by order.
Each ready order is announced in the right zone.
On-the-spot announcements with tone and zone, on top of the scheduled ones.
Integrations
Bank transfers through Talo to charge tables and deposits.
Mercado Pago Point card terminal built into the sales screen.
PedidosYa as its own till channel, with its own payment method.
The venue’s WhatsApp for codes, notices and member queries.
What slows you down today — and how GVenue solves it
The system makes you work its way
GVenue is built the other way around: hundreds of settings per venue, and when something is missing, we build it for how your place actually works.
Every change is a ticket nobody answers
You talk to the person who programs. We look at it together, we measure it, and you get it in stages.
An update for someone else changes your screens
Everything new is born switched off and turns on per venue. What we build for you doesn’t move anything at another venue, and vice versa.
What changes when the system adapts to you
With GV A Medida
You talk to the person who programs, not to a ticket queue.
What you ask for is built on the same system you already use: same data, same till, same reports.
It turns on only at your venue, by a setting, and you can switch it off without losing data.
Delivered in stages, tested in your venue before it goes live.
If it serves other venues, it joins the catalog and keeps improving.
What you no longer handle separately
Explaining your problem to someone who passes it on to someone else.
A separate tool that doesn’t talk to your till or your stock.
An update that changes your screens without asking.
Finding out on a busy night that something wasn’t ready.
Paying for a one-off that nobody maintains.
How we work
You talk to the person who programs. You tell us what you need the way you’d tell your manager, and we ask whatever is needed to understand how your venue works.
First, a survey: we check whether it already exists and is just switched off, because many times the answer is a setting and not a new development. If it has to be built, we agree on the scope before starting.
We deliver in stages. Everything new is born switched off and turns on only at your venue, by a setting: what we build for you doesn’t change anyone else’s screens. You can try it in test mode before using it on a real night.
Live support: we’re there the night it goes live, remotely or at your venue, and we adjust what the real operation demands.
How it’s priced
Quoted by scope: it depends on what it is and how long it takes to build. You know the price before we start. If it turns out to be useful to other venues, it joins the catalog for everyone.
🌎Anywhere in the worldIt runs in the cloud: it works from any country, on a PC, a tablet or a phone.
🗣️In the language you needToday it speaks Spanish and English, and another language can be added on request.
⚙️100% configurableHours, names, permissions, prices and screens adapt to the way each client works.
👨💻You talk directly to the developerNo help desk, no middlemen: whatever you ask is heard by the person who builds the system, and if it helps your business, it gets built.
Frequently asked questions
How much does custom development cost?
It’s quoted by scope: it depends on what it is and how long it takes to build. You know the price before we start.
Does what you build for me change other venues?
No. Everything new is born switched off and turns on per venue, by a setting. Other venues only see it if they turn it on.
What if it already exists?
Then there’s nothing to build: many requests are a setting that is switched off. That’s the first thing we check.
Can I try it before using it on a real night?
Yes. It’s delivered in stages and you can try it in test mode, which keeps orders, printing and payments out of the real operation.
Do I need to use GVenue?
Yes: custom development is built on top of the system, with the same data, till and reports. You combine it with whichever modules you use.