It looks like you’re from {country}
Accounting
Exact Globe is the on-premise Exact, and plenty of Dutch wholesalers and manufacturers still run their whole operation on it — often with Exact Synergy next to it. It works, it is paid for, and nobody is in a hurry to migrate.
The catch for a website is not the software. It is that Globe lives on a server in your building, behind your firewall, and a webshop on the internet cannot simply ask it a question.
Exact Globe Next is Exact's on-premise ERP: financials, stock, order management, purchasing, manufacturing, running on a SQL Server database you own. Exact Synergy often sits alongside it for documents, workflows and CRM. It is a different product from Exact Online, not an older version of it — the data model is different, the extension points are different, and a connector built for one does not work with the other.
Connections to Globe are usually built one of three ways: against the SQL database directly with a read-only account, through Exact's own XML or web service layer where your version has it, or by a small service inside your network that pushes data out on a schedule. Which of those is available depends on your version and, more often, on what your IT department will sign off.
All three are consequences of one fact: the system of record is not reachable from the internet, so somebody bridges the gap by hand.
Almost every Globe site we see has one: an export that runs at 3am, lands on an FTP server, and feeds the website. When it fails, nothing tells anyone, and the shop shows yesterday's prices until a customer complains.
What you see instead
The same export, but as a monitored job with a heartbeat: a night that produces no file is an alert, not a silence, and the previous file stays in place instead of being replaced by an empty one.
Because the shop cannot write into Globe, the shop emails the order to the back office and somebody enters it. All the usual copying errors, plus a queue that is somebody's inbox.
What you see instead
A small service inside your network picks orders up over an authenticated connection and writes them into Globe, with the shop order number as reference. No inbox in the middle.
A supplier quotes a Globe connection as though it were a cloud one, then discovers in week three that opening a port is not going to be approved. The project stalls, and both sides think the other one should have asked.
What you see instead
We ask in the first conversation which of the three routes your IT will accept, and quote against that one. It is a fifteen-minute question that decides the whole schedule.
The cost pattern here is different from a cloud package. The retyping is real, but the bigger cost is usually the fragility: a nightly export nobody monitors means the website is confidently wrong for a day at a time, several times a year, and each of those days generates orders at the wrong price or promises stock that is not there.
The second cost is organisational. Because only two people can get numbers out of Globe, those two people become a bottleneck for everything — a new price list, a promotion, a report. That does not appear on any invoice, but it is why a two-week marketing idea takes six weeks.
For Globe this is often the actual reason to call us: the website in front of it is usually the oldest thing in the company, and a connection into a modern shop is half a shop project.
A connection needs two ends. Plenty of agencies will build you the API call and hand you a JSON payload; that is the easy half. The harder half is what the data lands in — a website, a webshop, a portal your customers log into, an internal tool that replaces a spreadsheet. JKC builds both ends, which is why the connections we build tend to keep working: nothing about the receiving side is a black box to us.
The connection itself: authentication, field mapping, rate limits, retries and a queue that survives the other system being down for an hour. Built against the documented API where there is one, and against whatever the vendor really offers where there is not.
WordPress sites that read from your systems instead of repeating them by hand: a careers page fed by your HR system, a team page that follows your payroll, prices and availability that are the real ones.
WooCommerce shops where the order is the last time anyone types it: it becomes an invoice in your accounting package, a label at your carrier, a stock mutation in your warehouse, and a line in your CRM, on its own.
When the process does not fit any standard product: a customer portal, a quoting tool, a planning board, a dashboard that reads three systems at once. Built on your data, with your systems as the source instead of a copy of them.
Reading is nearly always possible; writing depends on the route your IT accepts. We say which is which before quoting rather than after.
Articles, prices and customer price agreements (out of the tool)
The list a B2B shop needs to show the right price to the right logged-in customer. Usually the first flow, because it is read-only and needs no write access.
Stock per article and per warehouse (out of the tool)
On a schedule, with a buffer. A quarter-hour rhythm is normally the sweet spot; anything faster puts load on a production ERP for very little gain.
Webshop orders into Globe (into the tool)
Written as sales orders through the route your IT approves. This is the flow that needs the network conversation, and the one that removes the most manual work.
Order and delivery status back to the customer (out of the tool)
So a B2B customer can see where their order is without phoning. Cheap once the reading route exists, and it removes a surprising volume of calls.
The same four steps every time, whichever tool it is. Nothing here is a workshop you pay for: step one exists because scoping a connection wrong is the single most expensive thing that can happen to it.
Not "which fields exist" but "which fields does somebody currently move by hand, how often, and what breaks when they get it wrong". Most projects turn out to need two or three flows, not a full two-way sync of everything. That conversation is what keeps the quote where it is.
A maintained connector from the vendor, a platform like Make or Zapier, or a custom integration against the API. Cheapest first, not custom first: if a supported plugin does exactly what you need, that is the answer and we will tell you so. Custom is for the cases where the off-the-shelf option would need so much configuring that it becomes the fragile option.
Every connection ships with retries, a queue and an idempotency key, so an order that arrives while the other side is down is delivered later rather than lost, and a retry does not create a second invoice. On a test environment first where the vendor offers one, so the first thing your real administration sees is a working connection.
Which alerts you will get, what each one means, what to do about it, and who to call. Plus the credentials in your own name, in your own vault — not in ours. A connection nobody but us can maintain is a connection you do not own.
This is the part most quotes leave out. A connection that stops working without telling anyone is worse than manual work, because with manual work at least somebody notices when it does not get done. Every connection JKC builds is monitored, and the monitoring is not an upsell — it is in the service fee.
A message that does not get through raises an alert the same hour, with the record it was about. Not a dashboard you have to remember to look at.
Anything that failed sits in a queue and can be sent again once the cause is fixed, in order. Nobody goes back through yesterday to find the four orders that did not land.
APIs get versioned, deprecated and rate-limited. When a vendor announces a change that affects your connection, adjusting to it is part of the service fee, not a new project.
For Exact Globe the price depends more on your network than on your data. A route your IT already permits keeps this in the normal range; a route that has to be created and security-reviewed adds weeks, and we would rather show you that in the quote than discover it together.
A connection starts from €1,700 plus a monthly service fee, which covers the monitoring, the queue and keeping up with the vendor's API changes. Work outside a fixed scope is €95 per hour.
What moves the number is not the tool — it is how well the system on the other end is known. If JKC built your website, your webshop or your web application, we already know its data model, its edge cases and where its stock numbers really come from, and a connection into it is mostly configuration and testing. If it is a system we have never opened, we start with a short technical check of both sides and quote after that, so you are not paying hourly for us to work out the basics.
Two more things that move it, in our experience more than anything else: whether the tool has a real API or only a CSV export, and whether the sync has to go both ways. One-way is roughly half the work of two-way, because two-way means deciding, per field, which system wins when they disagree — and that decision is the expensive part, not the code.
For reading, sometimes, with a read-only account and only on views we have agreed with whoever maintains your Globe. It is fast and it is well understood, and it survives an Exact upgrade less well than a supported interface does, so we say that up front.
For writing, almost never. Writing straight into an ERP's tables skips the validation that makes the ERP trustworthy. Orders go in through Exact's own interface or through a service that uses it.
If the migration is genuinely inside a year, then yes for the writing half — building an order flow into Globe that gets thrown away is money spent twice.
The reading half is different, because the shop or portal in front of it is the same either way. We build those against an internal layer of our own, so switching the source from Globe to Exact Online later changes one piece and not the whole site.
Yes, and it is the route we propose most often for exactly that reason. A small service running inside your network makes outbound connections only: it pushes exports out and pulls new orders in on a schedule. Nothing listens on an open port, so there is nothing new for anyone to attack.
It costs a little more than a direct connection and it is a little less immediate — a five-minute poll instead of an instant push. In return it is usually the version your IT will actually approve, which makes it the faster option in calendar terms.
