I don’t want to install CryptoPro and certificates on every computer and in 1C itself
Truemark
You sign in the browser, in Truemark. No CryptoPro or certificates inside 1C.
1C integration
You create a UTD in Truemark, and the draft arrives in 1C with the full code hierarchy: pallets, boxes, group packages and units. No CryptoPro, certificates or OMS inside 1C: signing and the exchange with Chestny ZNAK stay in Truemark.
Truemark · UTD-1021
(00)146012340000090015(00)1460123400000000140104601234000478215…(00)1460123400000000211CDraft UTD-1021
Directly
You can connect 1C to Chestny ZNAK directly, but before the first marked product you’ll have to go through the whole list and then maintain it. Through Truemark, 1C only needs the add-on and a token.
I don’t want to install CryptoPro and certificates on every computer and in 1C itself
Truemark
You sign in the browser, in Truemark. No CryptoPro or certificates inside 1C.
We have 1C on a Linux server, and the crypto provider with the certificate would have to go there
Truemark
No crypto provider needed on the server: the add-on loads UTDs by token. It only needs internet access to api.truemark.ru.
I was issued a non-exportable FNS key, and it still has to be delivered to the server
Truemark
No need to deliver the key to the server: signing stays in the browser, in Truemark
I don’t know how to create and set up an OMS inside a 1C configuration
Truemark
No OMS needed in 1C: code orders and the exchange with Chestny ZNAK stay in Truemark
I still have to set up token renewal and automatic exchange with Chestny ZNAK
Truemark
In 1C you paste the token from the account: connection in 5 steps with no programmer. The exchange with Chestny ZNAK stays in Truemark.
Chestny ZNAK changes constantly, and I have to wait for the vendor’s release and update 1C
Truemark
The exchange with Chestny ZNAK lives in Truemark, so Truemark gets updated. Your 1C doesn’t need to be touched
Configurations
The add-on connects through the standard “Additional reports and data processors” mechanism, and the configuration itself doesn’t need changes. Check a customized 1C in the demo: 7 days of full access for free.
Connecting
1C needs internet access to api.truemark.ru. Step by step with pictures: in the knowledge base.
In the account: profile → “Settings” → “API” tab → “Download the 1C add-on”. The truemark1c.epf file is saved.
Or download it here: ZIP, 67 KBIn the same place, “Generate” and “Copy”. The full token is shown once; a lost one is replaced with the “Regenerate” button.
“Additional reports and data processors” → add the truemark1c.epf file. The “Integration with TrueMark” command appears.
In the “Authorization in TrueMark” window, in the “Access token” field. The token is saved in 1C, so you don’t have to enter it every time.
The add-on shows your company’s UTDs from Truemark marked “Posted” or “Not posted”. Double-click a line → “Load new document” → “Run”.
Loading e-document · UTD-1022
Load new document
Refill existing
RunWhat gets into 1C
With the goods from the UTD, as created in Truemark
Shipping and group packages and the units nested in them
Added to the 1C database together with the document
Edited the UTD in Truemark? Use “Refill existing”, and the document in 1C updates
The document in 1C is for accounting. The UTD goes to the trading partner via your EDI provider from 1C, or is signed and sent from Truemark via EDO Lite.
Open a UTD in XML and check the codesThe UTD is built in Truemark, and codes get into it the way that suits your warehouse
Aggregation: automatically without a scanner, manually with a scanner or from a packing file. Boxes and pallets carry an SSCC in a GS1-128 barcode. About aggregation
Comparison
| Task | 1C directly | Via Truemark |
|---|---|---|
| CryptoPro on the server | You install and maintain it yourself | Not needed in 1C |
| Certificates and the FNS key | You deliver them to the server | Signing in the browser, in Truemark |
| OMS | You create and set it up in the configuration | Not needed in 1C |
| Connecting | A project of several weeks | The add-on and a token, 5 steps |
| Chestny ZNAK changes | You wait for the vendor’s release and update 1C | Truemark gets updated; you don’t touch 1C |
| Aggregation | Manually, with a scanner | Without a scanner from the order’s packing layout, with a scanner or from a file |
| Code hierarchy in the UTD | You build it yourself | Arrives in 1C ready |
| Codes in the UTD | Usually by scanning | From the order, a file, a scanner, a handheld terminal, as whole boxes |
| Code checks in the warehouse | With your own tools | App for any handheld terminal model |
Incoming UTDs from suppliers are also received in Truemark, with every code checked before signing. About UTD receipt
API
The add-on runs on Truemark API requests: the UTD list, the document XML and the code hierarchy. Right now the API is built for the add-on; extending it for large companies’ tasks is discussed on request.
UTD listcompany documents for a period and by statusDocument XMLthe UTD file as it will go to the trading partnerCode hierarchypackages and nested units120 per minuterequests per tokenPricing
Mini has no 1C integration. Marking codes are paid to Chestny ZNAK separately, ₽0.61 including VAT; Truemark doesn’t resell codes.
from ₽2,325a month, paid annually
from ₽4,159a month, paid annually
₽0no card required
Questions
Didn’t find an answer? Write to us, and an expert will reply in 15 minutes on average. Step-by-step guide: in the knowledge base.
No. Signing, the OMS and the exchange with Chestny ZNAK stay in Truemark. In 1C you add the add-on and paste the token from the account.
You create a UTD in Truemark, and the add-on loads it into 1C as a sales document. The codes arrive with the full hierarchy: shipping and group packages and the units nested in them. No need to rebuild the nesting.
1C:Trade Management 11, 1C:ERP, 1C:Complex Automation, 1C:Accounting PROF and CORP 3.0, 1C:Small Business Management, and work in the 1C:Fresh cloud.
Five steps: download the add-on, create a token, add the add-on to 1C, paste the token and load the first UTD. No programmer or configuration changes needed.
The token is tied to one company and is shown in full once. If it might have reached outsiders, click “Regenerate”, and the old one stops working immediately. The document in 1C is for accounting: you send it to the trading partner yourself, via your EDI provider or from Truemark.
The exchange with Chestny ZNAK lives in Truemark, so Truemark gets updated. No need to wait for a release and update 1C.
Yes, of any nesting: units, group packages and sets, boxes, pallets. The whole nesting arrives in 1C ready.
Yes: from a code order, from a file or as whole boxes by the package code. A scanner at the computer and handheld terminals work too.
Not for 1C integration. For warehouse work, any handheld terminal model on Android 7.0 or newer with a built-in scanner in Broadcast mode will do: it builds boxes, group packages and sets, fills UTDs and receives goods.
All 49 groups from the Chestny ZNAK reference list in one plan.
The add-on connects without changing the configuration, but a heavily customized 1C is better checked in the demo: 7 days of full access for free.
The whole cycle: code orders, label printing, application and introduction into circulation, aggregation, UTD shipment with export to 1C, receipt of incoming UTDs, Wildberries and Ozon.
Opti and Maxi; you can try it in the demo for 7 days free. Mini has no 1C integration.
Right now the Truemark API is built for our 1C add-on. Extending it for large companies’ tasks is discussed on request: tell us about your system and task.
The add-on and the token are in the account settings. 7 days of full access for free, no card required.
Or leave a request
We’ll answer about volumes, pricing and getting started. Leave your phone or email and your question in the request form.