From a request in SuperOffice to a sales order in Visma.net.

BufferDesk replaces one task: typing the purchase orders that arrive in SuperOffice into Visma.net. This page says what it reads from each system, what it writes, and what it never changes.

What BufferDesk reads from SuperOffice

• The whole request, when an agent presses BufferCheck or BufferSend: every message, its sender and time, and the attachments.
• The request's type, so only your order requests are read, and which company it belongs to when you have more than one.
• A PO number field on the request, if you keep one. The setup adds it; its name is a setting.

SuperOffice sends the request when the agent presses the button. BufferDesk never logs in to SuperOffice and reads nothing else there.

What BufferDesk writes to Visma.net

One sales order per purchase order, with status Hold:

• the Visma customer, with the delivery address Visma already has;
• the buyer's own PO number, in the order's customer reference;
• the SuperOffice request number, in a custom field you choose (customStr1–customStr5);
• one line per item it found, with the quantity. Prices and units come from Visma, as when you type the order;
• the lines it did not find, listed in the order's note so a person can add them.

What BufferDesk reads from Visma.net

• Your customers and your items, copied once a day. That is how it finds a buyer and an item from what the order says.
• One buyer's recent orders, to point out what differs from what they usually order.
• An order after your team has released it, to count how much of what BufferDesk wrote was kept.

What BufferDesk does not do

• Release an order. Every order waits on Hold for your team.
• Change a customer, an item or a price in Visma.net.
• Reply to your customer. When an order cannot be written, a new mail goes to your own order address, never onto the customer's request.
• Guess. A buyer or an item it cannot find exactly is left unmatched and listed.

What you need

• SuperOffice Service with scripts and web panels. The setup walks your administrator through it: a PO field, three scripts, three buttons, a web panel and a first order.
• Visma.net ERP, and an administrator who approves BufferDesk for each company.
• A number: how many of an order's lines must be found in Visma before it is created. You set it.

When you do not need it

If your purchase orders already arrive as EDI or Peppol documents, you do not need BufferDesk. If only a few arrive a week, typing them is cheaper.