fiscal.am

Product marking (e-Mark) and fiscal receipts

How Armenia's national product marking system works at the point of sale, which categories fall under mandatory marking, and how marked goods interact with fiscal cash registers.

Last reviewed Apr 29, 2026

Armenia is rolling out mandatory product marking for several categories of regulated goods. The system is operated by the national e-Mark operator. Marked products carry a unique DataMatrix code on the package, and at the moment of sale that code has to be "retired" through the same fiscal infrastructure that registers the receipt.

If you sell anything in the regulated categories below, marking obligations directly affect your checkout flow. Receipts for marked goods are not just receipts any more — they're how the marking lifecycle is closed.

Why fiscal.am covers this

Marking is a different system from fiscalization, run by a different operator. We cover it here because the point where it intersects the fiscal-receipt obligation is at the cash register, and that intersection is what most retailers actually have to handle. We don't try to be the canonical source on marking itself — for that, see e-Mark.

Categories under marking

Armenia introduces marking in batches via Government decrees, within the broader EAEU framework. Categories that already are or are scheduled to fall under mandatory marking include: dairy, meat and meat products, medicines, beverages, beer, alcohol, tobacco, water, oils, petroleum products, paints and varnishes, perfumery and cosmetics, animal feed. Each category's effective date is set by a separate Government decree.

Because effective dates shift and live in different decrees, we don't publish a consolidated calendar here — the risk of stale information is too high. Check the e-Mark site or the SRC clarifications portal before relying on a specific date.

If you sell goods in any of these categories, plan the integration early so you're not scrambling the week before requirements take effect.

How marking works at the cash register

For a marked product, every sale closes a unique code. The flow is:

  1. Scan. The cashier scans the DataMatrix code on the package along with the regular barcode.
  2. Validate. The integrated POS app checks with e-Mark that the code is valid, not already retired, and matches the item being rung up.
  3. Retire. When the receipt is finalised, the code is reported as "retired" to the e-Mark system. It can no longer appear on a future sale.
  4. Issue receipt. A normal fiscal receipt is issued via the cash register — but the receipt now carries the marking code as one of its line-item attributes.

A retailer who sells marked goods needs:

  • A cash register (hardware or virtual) that supports marking integration for their categories.
  • A scanner capable of reading DataMatrix codes (most modern 2D barcode scanners can do this — old 1D-only laser scanners can't).
  • An account with the e-Mark system, set up and tested before your category becomes mandatory.

What if you sell marked goods without integration

The receipt itself is still fiscally valid, but the marking obligation is not met — which is a separate compliance failure with its own penalties under the marking framework. Selling marked goods through a cash register that doesn't speak to e-Mark is not a viable long-term workaround.

Operator and tooling

  • The system is operated by e-Mark (e-mark.am). They issue codes, receive retirement reports, and handle disputes.
  • Cash-register-side marking integration is provided by apps and modules from e-Mark and partners. For the full list and current names of these tools, check e-mark.am directly.
  • Many hardware vendors and virtual cash register providers advertise e-Mark integration. Confirm category coverage with your CR vendor before relying on it.

Sources

Where to go from here