Can the ERP be rolled out cluster by cluster?+−
Yes, and that is the recommended path. The system first runs for one pilot cluster in parallel with the existing records, the results are reconciled with the finance team, and only then does the cluster switch to the ERP; the rest follow the same template. The switch is planned between seasons so that the system does not change in the middle of sowing or harvest.
How does the ERP work with the accounting system of each legal entity?+−
The local accounting system, BAS in Ukraine, remains the bookkeeping and tax system of each legal entity. The ERP exchanges master data, documents and balances with it through the integration layer: management accounting, consolidation and agricultural processes live in the ERP, while statutory reporting stays in the accounting system. The holding does not have to replace bookkeeping in all companies at once.
How long does an ERP rollout in an agroholding take?+−
It depends on the number of legal entities, clusters and systems to integrate, so the timeline is set after the assessment. The rollout goes in stages: shared master data, a pilot cluster, then the remaining clusters from the template. The holding gets the first result, consolidated reports for the pilot, after the pilot stage rather than at the end of the whole project.
How much does an agroholding ERP cost?+−
An agroholding ERP is almost always a personal product: its cost is defined by modules, legal entities and integrations and by the master data and history to migrate, not by users. After the assessment askcust estimates the first stage, shared master data and a pilot cluster, with a fixed scope agreed in writing. If a separate module, such as fuel or land lease accounting, is needed by other farms too, askcust can build it for free.
Can telematics and elevators already in use be connected?+−
Yes. Telematics such as Wialon, elevator weighing software and bank statements are connected through the integration layer as data sources, without being replaced. Their data flows into consolidated reports: actual field operations into field costs, grain intake and shipments into cluster stocks. If a cluster uses different telematics, a separate adapter is added for it.
Who owns the system and the data?+−
The holding: an agroholding ERP is usually a personal product, so the code goes to the client's repository, the system runs on the holding's servers or cloud account, and askcust's access is limited to development and support. The ERP can be developed further with askcust, an in-house IT team or another contractor, and documentation is handed over with the code. Only a module built for free for the market stays with askcust, and the holding's data stays with the holding.