What a configuration could hand over
During implementation we can design a transfer of the approved configuration into POHODA as the basis for a document. The fields and the procedure are verified against the supported XML interface and the version in use.
Address book
The customer could be linked to an existing address in POHODA's address book by company ID, so a repeat enquiry does not create the same company twice.
Issued offers
An approved configuration can become an offer with items and a price through XML import, which your salesperson then prints and emails from POHODA like any other document.
Received orders
Once the customer accepts, the same data could continue as a received order, from which POHODA produces the invoice and the stock issue.
Stock and text items
Parts you keep in stock would go in as stock items. Dimensions, colour and the 3D preview link would travel as text items or as the document note.
What we need to connect it
The transfer would run through POHODA mServer, an HTTP server built into POHODA that accepts an XML request and returns an XML response.
mServer reserves one running instance of POHODA for itself, so we need a computer or server where it can run alongside your accountants' daily work.
Stormware recommends running it inside the internal network, so we agree a VPN or another secure route with your administrator, plus a POHODA user with rights to the needed agendas only.
Before the first live document we try the import on a copy of your accounting unit and check numbering series, warehouses and VAT classification together.
Worth deciding up front
- We recommend installing mServer on a server operating system, not on a computer with a public IP address.
- Decide whether the configurator should only read stock levels or whether an order should also reserve stock.
- Every POHODA document carries its own VAT rate and currency, so the mapping has to match the rates you have set up.
Questions about this connection
Will offers be written into POHODA automatically?
During implementation we can design it so an offer is written once a salesperson approves it. While mServer is not running, the request waits and nothing is lost; we agree how retries work.
Do we need a different POHODA version for this?
XML communication is part of POHODA, but the available fields change between versions. Before the design we check your version and the XML schemas for offers and orders.
What if our POHODA runs on a hosted server?
mServer still needs its own running instance of POHODA. Where it can run and how we connect to it securely is something we work out with you and the hosting provider.
Other integrations
Put POHODA to work in your sales.
Tell us what you sell and how an enquiry is handled today. On the demo you will see the configurator, and we will go through which data could flow from it into your system.