Pharmaceutical marking · CEDM · Kazakhstan
Hundreds of codes a day —
not one of them by hand
A branch employee scans the packages. Markér verifies every code in the state system, groups it into a document by product and fills in the prices. Only the signature is left to a human.
Withdrawal notices · Transfer acts
Press it — or plug in a scanner: it types the code like a keyboard
The main scenario
The path of a single code
Four steps stand between the package in hand and the document in the state system. Markér takes three of them itself.
The identification code is cut out of whatever the scanner emitted: the product GTIN and the package serial number. The crypto tail is dropped — the state system has no use for it. If the scanner lost its separators, the boundary is found by the standard length.
And what happens instead of the happy path
Someone else's code, one already withdrawn, or one scanned twice. It stays visible in the list but never reaches the document.
The state system did not answer. The code is neither lost nor assumed valid — it waits to be checked again.
Try it right here
What Markér actually reads
Paste a DataMatrix string — or scan a package straight into this field. The parsing runs in your browser, with the same code that runs in the system.
010487001234001721RQ7fK2nP4xW9d⟨GS⟩91EE06⟨GS⟩92dGVzdHNpZ25hdHVyZQ==
↑ Crypto tail · dropped
Who does what
Two roles — two different screens
The interface is not shared: an employee only sees scanning, an organization sees setup and documents.
Scans and presses “withdraw”. Configures nothing.
- Works in one selected branch — every scan is tied to it
- An unreadable code is assembled by hand, checked against the expiry date on the box
- Signs in by phone number: an employee needs no mailbox
- On sign-out we warn if any codes are left unclosed
What comes out
The two documents it is all for
Both reach CEDM ready to be signed — with products, quantities and prices.
| GTIN | Product | Qty | Price, ₸ |
|---|---|---|---|
| 04870012340017 | Paracetamol 500 mg · 20 tabs | 12 | 1,240 |
| 04870009812043 | Amoxicillin 250 mg · 16 caps | 4 | 3,780 |
| 04870019430512 | Omeprazole 20 mg · 28 caps | 7 | 2,150 |
The numbers this work is made of
codes in one document — a long list is split automatically
roles in the cabinet: employee and organization
interface languages: English, Russian, Kazakh
types of CEDM documents
Honestly
What Markér does not do
Limits are better known before the rollout than after it.
It does not sign documents
Signing requires the organization's digital signature and the NCA RK SDK. Markér brings a document to the “ready to sign” state — a human signs it in the CEDM cabinet.
It does not delete sent documents
They cannot be deleted in the state system either: a sent document describes goods that really left circulation, and the only trace of that operation must stay.
It does not keep CEDM access in plain text
The organization's login, password and tokens are encrypted. The credentials are entered by the organization itself — they reach us no other way.
It does not look for counterparties among other clients
Every organization keeps its own list of counterparties, and a BIN is checked against the CEDM registry.
We are around
Support that knows CEDM
Marking breaks not inside the app but where it meets the state system. So support here works on CEDM rejections, not on “the button does not click”. Write in English, Russian or Kazakh.
We set it up with you
We help you create branches and employees and check the CEDM credentials — so the first code is scanned the same day, not a week of emails later.
We work through rejections
If the state system rejected a code or refused a document, we tell you what exactly it disliked and what to do next.
A human answers
On the other side are people who work with marking every day — not a bot retelling the manual in its own words.
Start with a single package
Sign in and scan the first code. CEDM credentials are entered by the organization itself, in its own cabinet.