Task and use cases
Who it is for
• Warehouses using 1C
• Organizations tracking assets and inventory
• Production sites with WMS or ERP
• Checkpoints, parking and scale workflows
Problem
If RFID events do not reach the accounting system, operators copy data manually. This creates errors, delays and duplicate accounting.
How it works
• Catalogs are synchronized: items, assets, warehouses and responsible persons
• Receiving, transfer, shipping and stocktaking documents are generated
• Statuses are exchanged in real time
• Error logs and retry mechanisms are included
• Testing starts on a database copy
Solution components
• 1C/ERP/WMS exchange specification
• HTTP services, web services or API
• Data mapping and quality checks
• Error log and retries
• Pilot operation
Limitations — clearly
• Heavily customized 1C configurations require assessment before estimates
• If another contractor supports 1C, responsibilities are agreed in writing
• Duplicate and dirty reference data in 1C affects the result
FAQ
Do we need to rewrite 1C?
No, the goal is to connect through standard mechanisms where possible.
Who modifies 1C?
We can do it or provide a specification for your 1C team.
What if we do not use 1C?
We connect to ERP/WMS through API.
See also
• RFID software — /en/rfid-po
• RFID for warehouses — /en/rfid-sklad
• Asset and inventory tracking — /en/rfid-uchet-tmc