Keep the system that knows your positions
Adding a tool should not force an elevator to duplicate contracts or maintain two versions of a position. Vector starts with information already managed by the ERP. Read-only integration comes first, adding context without granting the new system authority to alter the source operation.
What the system contributes
The first version is read-only by design. Vector consumes positions, contracts and status from the ERP through APIs, read-only access or exports. If integration is unavailable it can operate with controlled manual input, but requires reconfirmation before contact.
An export still needs a date
Where no API is available, a controlled import can support evaluation. But a file that was correct yesterday does not establish today's position. Age, origin and any required reconfirmation accompany the information before contact is authorised.
Validate the journey before expanding it
Test contracts are selected, received values compared and changes or missing information examined. The aim is not connectivity for its own sake: the responsible team must recognise its data and understand the review process. Further integrations are justified by that observed operation.