POS Hardware
List terminals, handhelds, customer displays, cash drawers and any device that is difficult or expensive to replace.
Audit • Ownership • Reliability • Cost • Risk • Upgrade Plan
A technology audit helps a business see what it actually owns, what it depends on, what is becoming unreliable, and what deserves attention first. Use this checklist before opening a location, replacing a major system, changing vendors, adding another location, or modernizing an existing technology stack.
The goal is not to replace everything that is old. Upgrade when reliability, support, compatibility, security, cost, workflow or business requirements justify the change.
Inventory the systems first. For each one, document the vendor, account owner, hardware, software, monthly cost, support contact, integrations, internet dependence, offline behavior, backup/recovery method and current problems. Then separate findings into three groups: fix now because operations are at risk, plan an upgrade because the system is becoming a constraint, or keep and monitor because it still serves the business well.
Main Principle
Start by documenting the current environment and the problems it creates. Otherwise the business can replace hardware without fixing the workflow, buy overlapping software, or remove a system another part of the operation still depends on.
Step 1
Build one list of the business's critical systems and devices. The inventory should be useful enough that another authorized person could understand the environment without relying on one employee's memory.
| Document | Examples | Why It Matters |
|---|---|---|
| System / Device | POS, router, phone service, CRM, website, ordering, signage player. | Defines what is actually in the stack. |
| Vendor / Provider | Internet carrier, software company, processor, equipment vendor. | Shows who supplies or supports the system. |
| Business Owner / Admin | Internal person or business-controlled account. | Prevents access from depending only on a vendor or former employee. |
| Location / Serial / Model | Physical location, model, serial number, device name. | Helps with compatibility, warranty, replacement and support. |
| Monthly / Annual Cost | Subscriptions, connectivity, support, licenses. | Reveals overlapping or underused services. |
| Dependencies | Internet, POS integration, API, local printer, payment terminal. | Shows what else may fail when this system fails. |
Step 2
Step 3
List terminals, handhelds, customer displays, cash drawers and any device that is difficult or expensive to replace.
Document terminals, processor relationship, integration, settlement workflow and who supports payment problems.
Document models, routing, paper/ribbon needs, spare units and which stations depend on each device.
Review item structure, prices, modifiers, taxes and whether online or display menus stay synchronized.
Verify what happens to orders, printing and payments during internet or cloud outages.
Flag hardware or software that is no longer supported, difficult to service or incompatible with required integrations.
Step 4
Step 5
Check mobile usability, hours, location, contact information, forms, admin access and domain ownership.
Test ordering, modifiers, prices, taxes/fees, fulfillment options, notifications and order routing.
Verify menu accuracy, mobile readability, current prices and stable QR destinations.
Review screens, media players, playlists, dayparts, expired promotions and offline playback.
Verify links, QR/NFC destinations and customer-facing calls to action still go to the intended accounts/pages.
Confirm core public-facing business information such as hours, phone and website has not drifted across important listings.
Step 6
A technically healthy system can still be a business risk when nobody knows who owns the account or how to remove old users.
| Review | Audit Questions |
|---|---|
| Admin Access | Does the business have an authorized administrator for every critical system? |
| Former Employees / Vendors | Have outdated users, API keys and access permissions been removed? |
| Billing | Are payment methods, renewal contacts and billing emails current? |
| Recovery | Are recovery email/phone methods controlled by the business? |
| Integrations | Which apps connect to which systems, what data moves, and who owns the credentials? |
| Exports | Can important customer, menu, transaction or configuration data be exported if a vendor changes? |
Step 7
Look beyond one invoice. Technology cost can be spread across several vendors and payment relationships.
Primary internet, backup internet, static IP or other network services.
POS, CRM, phone, signage, website, ordering and other monthly/annual subscriptions.
Leases, financing, warranties, replacements and spare devices.
Processing and payment-related charges should be evaluated with the actual agreement and transaction mix.
Installation, support retainers, IT management, service calls and after-hours support.
Manual re-entry, duplicate systems and unreliable integrations consume staff time even when they do not appear as a software fee.
Step 8
Unknown admin ownership, unsupported critical hardware/software, no access to the main business number or domain, shared passwords for sensitive accounts, no documented internet/payment outage process, failing kitchen-routing hardware, expired integrations, or a system the business cannot export data from should be investigated before they become an emergency.
Step 9
Not every finding deserves the same urgency. Prioritize by operational impact and business risk.
Problems that can stop sales, payments, customer access, critical communication or data recovery—or systems with a serious ownership/support gap.
Systems that still work but are becoming expensive, unreliable, unsupported, difficult to integrate or unable to meet near-term business plans.
Technology that remains reliable, supported, secure enough for the use case and aligned with the business workflow.
Upgrade Rule
Useful upgrade triggers include recurring failures, lack of support, security or compatibility problems, growth constraints, poor workflow, excessive total cost, missing integrations, or a credible business-continuity risk.
Master Checklist
Commercial Next Step
RH Now can help review POS/business technology, internet, phones, CRM/software, websites, menus, digital signage and other connected systems, then prioritize what should be fixed, replaced, integrated or left alone.
10D.6 Business Technology Series
Frequently Asked Questions
There is no universal schedule. Review critical systems regularly and run a deeper audit before major changes such as opening a location, changing vendors, replacing a POS/network, or when recurring failures and support problems appear.
No. Age alone is not a sufficient reason. Reliability, support status, compatibility, security, total cost and business requirements are more useful upgrade triggers.
Prioritize issues that can stop sales, payments, customer access, critical communication, data recovery or other essential operations.
Include the system/device, vendor, model/serial when relevant, location, account owner, administrator, cost, support contact, dependencies and major integrations.
Yes. Include software, internet, phone, CRM, signage, website, ordering, support and other recurring technology costs so overlapping or unused services become visible.
Confirm account ownership, data export, number/domain ownership, hardware compatibility, integrations, contracts, migration timing, staff training and rollback/failover planning.
RH Now can help coordinate business technology planning across several operational and customer-facing areas and help identify the next practical steps.
Related RH Now Resources
Reviewed by RH Now • Last reviewed: October 10, 2026
Technology requirements, vendor support status, security needs, integrations and business-continuity risks vary by system and organization. Use the audit as a planning framework and verify critical technical requirements with the vendors and professionals involved.