-
What this checklist is for
-
Seven checks before you sign
-
1. Define the duty cycle first
-
2. Get every critical number in writing
-
3. Separate hardware, software, and content rights
-
4. Compare total cost of ownership, not first invoice
-
5. Inspect a sample against the written spec
-
6. Confirm the service and update path
-
7. Run an acceptance test in real conditions
-
1. Define the duty cycle first
-
Common mistakes that ruin this checklist
What this checklist is for
I’m a quality and brand compliance manager at a B2B supplier in the indoor entertainment space. I review roughly 180 unique products per month before they go to customers, and I’ve rejected just under 9% of first deliveries in 2024. The rejections were rarely about looking cheap. They were about specifications that couldn’t be verified, licenses that didn’t cover the use case, and service terms that looked fine until someone needed support.
This checklist is for people who buy equipment for a commercial venue. The item may be an arcade machine for a family entertainment center, a chest press machine for a gym, a Forbidden Island board game set for a board game café, or even a custom VR project built in Unity. The checklist does not show you how to run a game development course. It shows you how to verify that the product will survive the way your customers will use it.
Searching for a Namco video game console is a collector path, not an operator path. But the history matters. Bandai Namco Entertainment, founded in 2006, inherited an arcade legacy where machines had to endure thousands of impatient plays. That legacy is a useful reminder: quality is not a feeling. It is a measurable outcome.
Seven checks before you sign
Use these checks in order. If you are not the person signing the purchase order, send this list to whoever owns acceptance.
- Define the duty cycle first.
- Get every critical number in writing.
- Separate hardware, software, and content rights.
- Compare total cost of ownership, not first invoice.
- Inspect a sample against the written spec.
- Confirm the service and update path.
- Run an acceptance test in real conditions.
1. Define the duty cycle first
A quote is meaningless until the workload is clear. Take a chest press machine. In a corporate gym, it may get twenty minutes of use per day. In a busy fitness floor, that same machine can get four hours of use per day. The second situation needs stronger cables, easier access for cleaning, and more reliable spare parts. The first may not.
Write one operating profile before you read any brochure: 'This product will be operated by unsupervised visitors for roughly X minutes per day, seven days a week.' If the product specification does not mention duty cycle, cycle rating, or service life for the main wearing parts, it is not yet a commercial spec.
The same rule applies to tabletop games. A Forbidden Island board game in a private home may last for years. In a café, guests will count the pieces, shuffle cards thousands of times, and spill drinks near the boards. The product needs a replaceable component plan, not just a pretty box.
2. Get every critical number in writing
I’ve lost count of verbal promises that arrived as marketing fluff later. The fix is simple: ask for the spec sheet and look for numbers.
For an arcade machine, the numbers matter: display brightness, tested input switch life, power supply range, and operating temperature. For a chest press machine, ask for frame tube dimensions, cable fatigue test data, max user weight, seat adjustment travel, and replacement part numbers. For a board game library, request component counts, card and box dimensions, paper or board weights, and print registration tolerance.
If you hear the phrase 'industry standard' without a number, that is a warning sign, not proof. Industry standards do not help you when a machine stops working after 1,000 plays and nobody measured what the vendor meant by 'standard.'
3. Separate hardware, software, and content rights
If the product includes games or licensed artwork, ask which rights are included in the price. Hardware is not a license. A cabinet with famous characters, a board game that uses an official property, or a VR game made from third-party assets all need written permission for commercial use.
I’ve only worked with domestic vendors, so I can’t speak to every international licensing nuance. But I can tell you that layering the approval of rights documents into your acceptance process works everywhere. If a supplier won’t show you the license or permission letter before delivery, do not assume it exists.
4. Compare total cost of ownership, not first invoice
I have a bias here: I believe total value matters more than sticker price. That is not a slogan. It is arithmetic.
The lower quote can cost more than the difference when you include downtime, freight, installation, spare parts, training, and a service call. If a venue earns $400 per day, a $1,500 price difference disappears after four days of unexpected downtime. The same $1,500 disappears faster if a broken part stops one game in a multi-game area and parents move to another location.
Write the total cost list before comparing prices: base equipment, freight, taxes, installation, training, consumables, spare parts, license renewals, and downtime. If one supplier is cheaper but cannot fill the service column, that low number is not a saving. It is a risk with a price sticker.
5. Inspect a sample against the written spec
Do not do a side-by-side product comparison as the main inspection. Instead, put the delivered sample next to the written requirements from step two.
I implemented this verification protocol in 2022, and it immediately showed me how many small differences become big costs later. Smaller wheels on a delivered chest press machine, a lighter power supply in an arcade cabinet, a different grade of board material in a board game box—each one looks insignificant in photos. Each one changes how long the product will last in a commercial space.
If possible, run a simple blind test with your staff: let them use the final sample without telling them the intended brand or price point. Ask them which one feels durable, not which one looks shiny. Their hands will usually catch what the brochure missed.
6. Confirm the service and update path
Every product will break or need an update. The only question is how fast the fix will happen.
For hardware, ask for maximum response time, spare parts availability for the next three to five years, and which parts are considered wear items. For software, especially a Unity VR project, ask which Unity version was used, how the project is handed over, and who updates the game when a new headset operating system changes something.
Beware of warranty phrases that sound absolute. If a supplier says 'five year warranty,' check whether it covers consumable parts, software compatibility, and freight for repair. A warranty that does not include the part that breaks is not a warranty. It is a poster.
7. Run an acceptance test in real conditions
The last check is also the most skipped. Do not accept a product from a demo room. Run the acceptance test where customers will use it.
For a chest press machine, run the motion repeatedly under load and listen for loose bolts. For a board game café, open the game, count every component, and shuffle the deck a few hundred times to test the card coating. For an arcade machine, let a child abuse the controls for ten minutes and watch whether the machine recovers. If it needs a technician to reset it after normal play, the design is wrong.
For VR, the same logic applies. People ask me how to make a VR game in Unity, and the honest answer is that Unity is the easy part to search for. The hard part is making a VR game that can run on a specific headset, with a stable frame rate, in a space that does not look like the developer’s office, for a user who has never touched VR before. The acceptance test should include first-time users, not just the developer.
Set pass-fail metrics before the test: no crashes in forty sessions, frame time stays under the target on the exact headset, first-time users can complete the activity without staff help, and the project files are deliverable with understandable documentation. If the developer cannot sit with you for the test, that is as important as any frame-rate stat.
Common mistakes that ruin this checklist
This checklist is practical, but it fails if you do any of these three things.
- You skip the duty cycle step because the product has a famous name. Famous names do not change the fact that a home-grade unit and a commercial-grade unit are different products.
- You inspect only after the full order arrives. Always sample first. If you negotiate inspection after delivery, you have already paid for the problem.
- You use warranty years as the total cost answer. Read the exclusions: consumables, software, shipping, and unauthorized repairs are where the risk lives.
My experience is based mostly on mid-volume commercial orders, not resort-scale rollouts or very small hobby purchases. If your context is different, adjust sample sizes and service levels. But do not adjust the order of the steps. Define the use, measure the spec, and inspect before you pay. That is how you get quality without paying for it twice.