An ERP integration moves one agreed record between two systems. The record can be an order, a stock figure or an invoice status. “Connect everything” is not the first job. Where it connects is written as the name of the ERP and the direction of the record: from the ERP to the screen, from the screen to the ERP, or not both at once.
Why one record is enough
The first release does not copy every table in both directions. A copy erases which side is right. If the order is born on the screen and only a status goes to the ERP, the thing that moves is that status. If stock is born in the ERP and the screen only reads it, the thing that moves is that quantity. The two are two decisions. They do not melt into one sentence.
Where it connects
The link goes to the ERP version you name and to the door that version opens. If there is no door, a file exchange can be a temporary bridge. The bridge is not presented as the integration itself. HED Creative does not write the name of that door in Berlin or Ankara before the code repository is opened in your name.
Who owns the field
If the same field can be written freely in both systems, the morning shows two numbers. Discovery picks the home of the field. The other side reads, or writes only in a state you allow. Invoice status is the usual case: the status comes from the ERP, and the screen does not change it.
What stays unconnected
A staff note, a draft price and a report that still has no name do not enter the first release. They hide inside the sentence “everything”. A short list lets the project finish. A list that says “all modules” means the project does not start.
To start, the name of the ERP, the kind of record, and the direction are enough. One sample order or one invoice line makes the field name concrete.
Write the record that will move into the web app development brief. The neighbouring job, where a form lands: CRM link.