Hardware vs virtual cash register: which fits your business

If you've established that you need a cash register, the next question is: hardware, or virtual?

The short answer: the legal weight is identical. A receipt issued by a properly registered virtual cash register has exactly the same standing in front of the State Revenue Committee as one printed on a hardware register. The choice is operational, not legal.

The decision in two questions

Question 1: Where does the sale physically happen?

If the sale happens face-to-face with money changing hands at the counter, hardware is the default and a virtual CR running on a phone is the exception. If the sale happens entirely through software, virtual is the default and hardware doesn't fit.

Question 2: How much engineering do you want to own?

A hardware register is a thing you buy, register with SRC, plug in, and use. A virtual one is an API you integrate. The integration cost is real and one-time; if you can absorb it (or buy a plugin), virtual eliminates several recurring operational concerns — paper, batteries, firmware, hardware certification edge cases.

Side-by-side comparison

The most operational dimensions at a glance — full table with everything else (cost shape, setup, online channels, maintenance) lives at the reference comparison page.

Legal basis

Where the rules live in the Tax Code and Decree N 1976-Ն.

Hardware

Tax Code Article 380, plus Annexes 1–3 of Government Decree N 1976-Ն (technical requirements, registration, usage).

Virtual

Tax Code Article 380.1, plus Annexes 4–9 of Decree N 1976-Ն (electronic receipt issuance, technical requirements for electronic CR, accounting, mandatory receipt fields, e-commerce platform requirements, taxi-specific e-CR rules).

Where it sits

Physical or logical location.

Hardware

On the seller's premises — at the trading floor, mobile sale point, or service location where payment happens.

Virtual

On the provider's infrastructure (third-party servers). The seller integrates by HTTP API.

Receipt format

Hardware

Thermal-paper receipt printed at the till, with the «Ֆ» mark and 8-digit fiscal number printed on it.

Virtual

Electronic receipt — delivered to the customer by email, SMS, in-app notification, or as a downloadable PDF / link. The same fiscal mark and fiscal number, just rendered electronically.

Card-payment terminal

How card-acceptance hardware fits in.

Hardware

Often integrated into the same device (e.g. PAYMOB) so the cashier presses one button to charge the card and issue the fiscal receipt.

Virtual

Separate from the fiscal layer — handled by your payment provider on checkout, then a fiscal receipt is issued via the virtual-CR API.

Goods-marking integration

Whether the device retires DataMatrix codes through the i-Mark system at checkout.

Hardware

Most major SRC-approved hardware models support marking integration; verify with the vendor for your specific category before relying on it.

Virtual

Most virtual-CR providers support marking integration as a checkout-flow add-on; confirm coverage with your provider for the specific category.

How you plug into it

From your software's perspective.

Hardware

Cashier UI on the device itself; serial / USB / network APIs to let an external commercial program drive it from a PoS terminal.

Virtual

HTTP API. The provider issues credentials; your checkout / invoicing flow makes signed requests for each receipt.

Cost shape

Costs are different in kind, not just in amount.

Hardware CR has an upfront cost (the device, ~50,000–300,000 AMD depending on model, plus card-terminal integration if needed) and ongoing minor costs (paper, occasional repairs, firmware certification events). No per-transaction fee.

Virtual CR typically has either a flat monthly subscription or a per-receipt fee, depending on the provider. No upfront hardware. No paper. Engineering effort to integrate is the largest hidden cost — though plugins exist for common platforms (WooCommerce, Shopify) that absorb most of it.

For a single-till retail shop, hardware is usually cheaper over a 3-year horizon. For an online business, virtual wins by default (a hardware register makes no sense without a counter to put it on). The middle case — a small business with both physical and online sales — usually ends up running both.

Common mistakes when choosing

Buying hardware before checking if you even need a CR. Many B2B-services-only IEs paid by bank transfer don't need a CR at all. The decision tree saves money.

Choosing virtual to avoid "regulation" — it's not less regulated. Both are equally registered with SRC. Virtual is just a software implementation of the same rules.

Choosing hardware "for safety" if your business is online. A printer in your back office isn't a fiscalization strategy. If you sell through a website, a virtual CR talking to your checkout is the architecturally correct choice.

Underestimating the integration cost of virtual. "It's just an API" hides one-time engineering, ongoing maintenance, error handling for failed receipt-issue scenarios, and operational visibility into a system your customers don't see. If you don't have the engineering bandwidth, a plugin or a hardware register may be the lower-friction option.

When you genuinely need both

If you have:

• A physical store and an online store, or
• A marketplace operator role, where you also sell direct, or
• A growing business that started physical and is going online

the practical answer is often: a hardware register at the counter, and a virtual register integrated with the website. Each handles its channel. SRC is happy because both are registered.

Where virtual HDM came from

Background, for readers who care how the virtual track was framed in the first place: the regulator publicly opened the topic of a virtual HDM on 17 September 2019, when SRC convened a meeting on «E-commerce and virtual HDM»archive. Deputy chair Mikael Pashayan presented the concept; Hrachya Muradyan (Head of Administration, Methodology, Procedures and Service Department) walked through the legislative changes the implementation would require — including how a virtual receipt's required fields would be defined.

The technical specification arrived two years later — the 12 July 2021 «electronic HDM» integration manualarchive, 22 pages, published in December 2021. Three years after that, the regulatory amendment N 1720-Լ of 25 December 2024 formalised the addressee arrangement that's in force today. The chronology:

• September 2019 — concept publicly framed, working email «VirtualCRM@taxservice.am» created for industry input.
• Mid-2021 — first technical specification (eHDM v1) authored internally.
• December 2021 — that specification published on the SRC HDM hub.
• Late 2024 — regulatory amendment closes the loop, naming G-Solutions SNCO as the receiving body for sample units.

If you want the wire-protocol detail of what virtual HDM actually is technically, that lives on Ten years of Armenia's HDM integration protocol.

Where to go from here

• Cash-register vendors and providers — both hardware and virtual options in one catalog
• Hardware vs virtual — structured comparison — same data side-by-side
• Do I need a cash register at all?
• Ten years of Armenia's HDM integration protocol — version history of the technical spec
• How CR certification took shape — the regulator arc