Purchase Order & Replenishment Checklist
Checklist for low-stock signals, replenishment requests, supplier selection, purchase orders, and receive confirmation — so bars and retail do not run dry mid-show.
View resource →Guideguide
Inventory vs POS: How Product Sales Should Update Stock
POS records sales; inventory records on-hand stock. This guide explains mapping, depletion multipliers, preview/post workflows, and reconciliation when bars run mixed cashless and retail models.
- Topic
- Inventory management
- Audience
- Venues · Festivals · Promoters
- Read time
- 16 min read
“POS tells you what sold. Inventory tells you what you have left. Reconciliation starts when both speak the same SKU language.”
Use this resource to
- Separate ticketing capacity from sellable product stock
- Design POS-to-stock mapping with depletion multipliers and exceptions
- Run preview/post workflows and end-of-event variance reviews finance trusts
What's included in this resource
- Inventory vs POS is not a philosophical debate — it is an operational contract. Point of sale records transactions: menus, modifiers, tax, tips, voids, and settlement batches. Inventory records on-hand stock: locations, receiving, transfers, counts, replenishment, and wastage. When product sales should update stock, you need explicit mapping, depletion rules, and reconciliation habits — especially for bars running cashless and retail together.
- POS optimises the sale moment — speed, modifiers, and payment capture. Inventory optimises supply — what to order, where it sits, and what vanished through sales, waste, or theft. Ticket inventory (capacity) is a third layer; do not confuse admission caps with kegs, merch units, or catering ingredients.
- Every POS SKU that should reduce stock needs a stock item (or kit), a depletion multiplier, and documented exceptions — combos, free pours, staff meals, and sponsor activations. The POS product mapping checklist is the field sign-off finance and ops can share before trading.
- • Preview depletion against opening on-hand before peak trading • Post sales-driven movements per batch or trading window — not only at strike • Investigate modifiers and unmapped SKUs before blaming “shrink” • Run stock counts when POS and ledger variance exceeds your threshold • Document exceptions (comps, transfers, emergency buys) with owner and timestamp
Key sections
A quick outline of the operational areas covered in the full guide.
- Inventory vs POS is not a philosophical debate — it is an operational contract. Point of sale records transactions: menus, modifiers, tax, tips, voids, and settlement batches. Inventory records on-hand stock: locations, receiving, transfers, counts, replenishment, and wastage. When product sales should update stock, you need explicit mapping, depletion rules, and reconciliation habits — especially for bars running cashless and retail together.
- POS optimises the sale moment — speed, modifiers, and payment capture. Inventory optimises supply — what to order, where it sits, and what vanished through sales, waste, or theft. Ticket inventory (capacity) is a third layer; do not confuse admission caps with kegs, merch units, or catering ingredients.
- Every POS SKU that should reduce stock needs a stock item (or kit), a depletion multiplier, and documented exceptions — combos, free pours, staff meals, and sponsor activations. The POS product mapping checklist is the field sign-off finance and ops can share before trading.
- • Preview depletion against opening on-hand before peak trading • Post sales-driven movements per batch or trading window — not only at strike • Investigate modifiers and unmapped SKUs before blaming “shrink” • Run stock counts when POS and ledger variance exceeds your threshold • Document exceptions (comps, transfers, emergency buys) with owner and timestamp
Overview
Inventory vs POS is not a philosophical debate — it is an operational contract. Point of sale records transactions: menus, modifiers, tax, tips, voids, and settlement batches. Inventory records on-hand stock: locations, receiving, transfers, counts, replenishment, and wastage. When product sales should update stock, you need explicit mapping, depletion rules, and reconciliation habits — especially for bars running cashless and retail together.
What POS does vs what inventory does
POS optimises the sale moment — speed, modifiers, and payment capture. Inventory optimises supply — what to order, where it sits, and what vanished through sales, waste, or theft. Ticket inventory (capacity) is a third layer; do not confuse admission caps with kegs, merch units, or catering ingredients.
Mapping products and depletion rules
Every POS SKU that should reduce stock needs a stock item (or kit), a depletion multiplier, and documented exceptions — combos, free pours, staff meals, and sponsor activations. The POS product mapping checklist is the field sign-off finance and ops can share before trading.
Preview, post, and reconcile
• Preview depletion against opening on-hand before peak trading • Post sales-driven movements per batch or trading window — not only at strike • Investigate modifiers and unmapped SKUs before blaming “shrink” • Run stock counts when POS and ledger variance exceeds your threshold • Document exceptions (comps, transfers, emergency buys) with owner and timestamp
Solution paths by venue type
Bar-heavy programmes often start with bar inventory management software; multi-site festivals may need festival or venue inventory modules with POS inventory connectors. Choose the path that matches how many locations and vendors touch the same catalogue.
How EventSuite helps
EventSuite Inventory connects catalog, locations, receiving, transfers, replenishment, and POS-driven depletion on one record — so reporting can show stock variance beside commerce totals. Map products with the checklist, align counts with the stock count template, then book a demo to model preview/post for your bar mix.
Related EventSuite modules
Connect checklist rows to the product modules teams use for live delivery.
Inventory
Track stock, replenishment, and POS-linked inventory controls.
Explore module →POS
Menus, devices, settlement batches, and on-site revenue controls.
Explore module →Payments
Connect ticketing, POS, and settlement workflows.
Explore module →Marketplace
Vendor listings, procurement packages, and fulfilment workflows.
Explore module →Reporting
Understand sales, attendance, and operational outcomes from one analytics layer.
Explore module →Related resources
More practical resources from the EventSuite library.
Cashless Payments and POS for Events
Cashless payments and POS are not just payment tools. For festivals and venues they reduce queues, improve reconciliation, support vendors, unlock offers and vouchers, lift revenue per attendee, and sharpen post-event reporting — when ticketing, commerce, and finance share one commercial spine.
View resource →Event Budget Template
Use this event budget template to plan income, costs, deposits, supplier spend, staffing, ticketing revenue, vendor revenue, POS income, sponsorship, contingency, and post-event reconciliation — so commercial, ops, and finance share one workbook before doors open.
View resource →Common questions
Should every POS item deplete stock automatically?+
Only items tied to a tracked stock record with an agreed multiplier. Service charges, deposits, and non-stock fees should be excluded explicitly — not left unmapped by accident.
What is a depletion multiplier?+
The ratio between what sold and what leaves stock — for example one cocktail selling one unit of a bottled spirit, or a pitcher consuming multiple units. Document it per SKU or recipe.
When do we need a stock count if POS is connected?+
Whenever variance exceeds your tolerance, after major menu changes, or when investigating theft, waste, or mapping errors. POS does not replace physical truth.
How does this relate to cashless reconciliation?+
Cashless and card batches prove money movement; depletion proves stock movement. Finance needs both aligned — see the POS reconciliation article and cashless guide for settlement discipline.
Use this guide with EventSuite
Connect resource owners to ticketing, vendors, payments, and reporting modules so operational work stays tied to live delivery.