Acknowledgement is the job. The supplier confirms quantity and the day. They do not see the price you sell at, and they do not see the volume you placed with the next supplier. If a spreadsheet of every open line has already gone out by email, that spreadsheet is the reason for the screen.
What they are allowed to open
Purchase number, line, quantity, the day you asked, the day they confirm, a status. Your purchase price may show if you choose to show it. Your sell price and another supplier’s volume do not. They do not retype the price. A day they cannot meet falls to the purchasing role you name.
This is not a dealer login
A dealer is the party writing a sales line to you. A supplier is the party you buy from. The fields do not mix. The boundary of a dealer login is a separate note: dealer order screen. The public question about a raw material is another door: raw-material enquiry. This screen is that question after it has come inside.
Who opens it, and who sees everything
Each supplier has a login. A shared password is out of the first release. On your side, purchasing sees every line. Planning reads the confirmed day. If both roles quietly change the supplier’s day, the confirmation means nothing. A change lands with the name of the person who typed it.
Once they confirm, the status is one of three words: waiting, confirmed, differs. A difference is quantity or the day. A long list of statuses tires the supplier and the screen stays empty. You write the words. HED Creative shortens the list in discovery.
Left out of the first release
An auction, a view of the whole supplier list, invoice approval and a public catalogue are out. So is live stock. The screen is the confirmation of a line you already placed. A fresh price negotiation is not this release. Without that sentence, the project becomes a purchasing suite.
The sample to send
One spreadsheet you send today, with the columns they must not see struck through, the person who confirms, and the role that reads the day. In discovery from Berlin or Ankara, HED Creative splits the columns into three: may see, may confirm, must never see. The third group is not a field.
Write the boundary into the web app development brief. How the line sits in the ERP is a separate decision: production record.