Speciality
Uniconta middleware
For companies running Uniconta who want their webshop or CMS in sync. The middleware connects Uniconta to your system, so orders, products, stock and customers move on their own.
How it fits together
Through the API
Middleware
.NET 8 API
Uniconta
ERP
Data flows
- Orders – Webshop → Uniconta
- Products, prices and stock – Uniconta → webshop/CMS
- Customers and accounts – Matched before they are created
- Invoices and status – Uniconta → webshop
What goes wrong in a Uniconta integration
None of this is theory. These are faults we have found in production – the kind a bookkeeper has to correct by hand afterwards.
VAT inferred from the item number
An item at DKK 25,750 was posted as 20,600. The VAT was guessed from the item-number range instead of coming across with the order.
Duplicate customer accounts
Matching looked only at email and address – and did so case-sensitively. The same customer was created again and again, even with an identical EAN number.
A business customer created as a private person
The company name never made it onto the address. The invoice went to the individual instead of the company.
The sales order left behind after invoicing
Uniconta does not delete it on posting. The order list grew by one duplicate for every single invoice.
EAN numbers with an invalid check digit
Rejected by the recipient's own system – weeks after the order went out, and long after anyone could remember why.
Try the middleware yourself
Create a demo account in the middleware's own portal and test the whole API – products, debtors, orders, invoices and PDF. Everything is fictional data, and nothing touches real accounts. The account works for 14 days.
Your account includes
- Your own fictional company with products, debtors and orders
- API credentials (client id and secret) you can always look up again
- An order log of everything you send
- Swagger for trying every endpoint
How to get started
- 1Create an account with your email and a password.
- 2Under "My access" you find your client id and secret.
- 3Open Swagger from the portal, log in with the credentials and send, for example, an order.
Five questions for your current supplier
Use them whoever you end up choosing. The answers reveal whether the integration was built or merely switched on.
- 1
What happens when two customers share an address spelled differently?
- 2
How do you match a customer account – on EAN, company number, email or address? And in which order?
- 3
Are amounts posted with or without VAT – and can that setting be set wrong?
- 4
What happens to the sales order once the invoice has been posted?
- 5
What happens when the integration fails? Can you see it, or do you find out in the accounts?
Technical foundation
The middleware is built with: .NET 8 · C# · ASP.NET Core · REST API · JWT
It can run on your own server
The middleware is your own instance – not a shared service with other companies' orders running through it. Want it on your hardware, it runs on your hardware. Want us to operate it, we will.
Frequently asked questions
What does it need on the Uniconta side?
A user the integration can log in with. You create it, you own it, and you can close the access again whenever you want.
Can you take over an integration that is already running?
Yes. We go through what it actually sends to Uniconta, find what is wrong and fix it – whoever built it.
We do not use Magento. Can you still help?
Yes. Magento 2 is the first finished module. Everything else connects through the API, and we are happy to build the module for your system – including one built specifically for you.
What happens if an order fails?
It is logged with both what was sent and what Uniconta answered, and it can be run again. An integration that fails silently is the expensive kind.
Should your webshop be in sync with Uniconta?
We are happy to look through your setup – with no obligation.