Four eyes (pictures 04 and 09)
Some decisions are too big for one person, so the platform asks a second person before anything goes out. The one who wrote the order can never be the one who approves it, and the one who asked for approval can never give it. That rule is built in and cannot be switched off.
Anna sells worktops and may give ten percent off. A customer asks for fifteen, so the order waits until her manager approves it. On the purchase side, an order above the buyer's limit waits the same way. In customer service, a credit note or a return can take the same route. One engine covers nine kinds of documents with one rule.
Framework agreement (picture 07)
A framework agreement is a price list that you and one customer have agreed on, with a validity and a notice period. It lives on the customer's card, and from then on every new order for that customer takes its prices from the agreement. Nobody types them again.
The kitchen fitter orders worktops every third week. Without an agreement, the seller types price, terms and reference each time. With one, she picks the customer and the quantity, and the line fills itself in at the agreed price. If a customer has no agreement yet, the order page says so and offers a button to write one.
Public tenders and open requests (pictures 01 and 03)
Every public tender published in the EU comes into the platform each morning. You tell the platform what to watch, such as product codes, words and countries. Matching tenders land in your queue with their deadline, so you never open a tenders website again.
Private requests work the other way round. A buyer writes what it needs once and puts it on the open board. Suppliers in the register are matched to it and answer with a price, without an account. The buyer compares the answers and picks the winner.