From shop to accounting
Orders leave the shop each night and reach the accounting software with the right codes and credit notes attached.
No more month-end export
An independent IT consultancy for companies running several separate business systems. We work out what should connect to what, then build it: connectors, scheduled transfers, migrations and monitoring. Scoped in writing, delivered first, invoiced after.
Almost every job we take has the same outline: something leaves one system, gets checked or reshaped on the way, and lands in another. The difference is only ever in the detail.
Orders leave the shop each night and reach the accounting software with the right codes and credit notes attached.
No more month-end export
An accepted quote creates the invoice in the billing tool, with no re-keying and no gap between the two figures.
One entry, two systems
Stock and shipments exchanged with your logistics partner on a schedule, acknowledged, and logged where you can read it.
Failures visible same day
Most work starts with a question rather than a specification: what should talk to what, and what will it cost us if it keeps failing. Each engagement is scoped after that conversation, in a written proposal that fixes the scope, the price and the date before anything begins.
Two systems that ignore each other, wired together properly — both directions, with the error cases designed in from the start.
What somebody does every Friday evening, running by itself on a schedule — with nobody having to remember it.
Moving from one platform to another without losing history, breaking references or discovering the gaps six months later.
Watching the flows you already have, whoever built them, so a silent failure stops being something your accountant finds.
A written read on what breaks, what duplicates and what can be automated — before you commit budget to any of it.
One of our catalogue kits, rebuilt around your systems, your field names and the exceptions your business actually has.
Entry prices, shown in both currencies. All prices include VAT. The firm figure is the one in the written proposal, prepared once we understand the work. Nothing is invoiced before delivery.
These are the pieces we assemble during engagements — the same connectors, scripts and monitoring kits. Clients with their own technical people sometimes prefer to put them in place themselves, so they can be bought outright at a fixed price and are sent by email within 48 hours, with the documentation needed to run them.
If you would rather we did it, every one of them can be commissioned as part of an engagement instead.
Two named systems, wired together. Configuration, mapping sheet and run notes.
Orders leave your online shop each night and land in your accounting software with the right codes attached.
An accepted quote in the CRM becomes the invoice in your billing tool, with no re-keying and no drift between the two.
A contact created on one side appears on the other, deduplicated, with one clear rule for who wins a conflict.
One stock figure pushed to every channel you sell on, so you stop selling the same unit twice.
Shipments and stock exchanged with your logistics partner by scheduled file drop, with a log you can actually read.
Enquiries from your site create a proper record instead of an email somebody has to retype on Monday.
One recurring job each: scheduled, logged, and alerting when it fails.
Three staggered reminders that send themselves and stop the moment the invoice is settled.
Invoices arriving by email are read, named, filed and handed to your accounting — the unrecognised ones flagged, never guessed.
One email each morning with yesterday's numbers, formatted so you can read it on a phone before the first meeting.
For flows you already run, whoever built them. Know before your accountant does.
Drop-in monitoring for a transfer you already have: it checks the run happened, the volume looks right, and shouts when it does not.
Structured logging you can search, so the answer to "why did it fail on Tuesday" takes a minute rather than an afternoon.
Send us read-only access. You get back a written report on every flow you run: what works, what is fragile, what to fix first.
A considered answer on one decision, in writing or in an hour of your time.
Describe what you are trying to connect. You get back a written opinion on whether the approach holds, and what it will cost you later if it does not.
One hour on one decision: which system is the source of truth, whether to build or buy, or why the flow you have keeps breaking.
Indicative prices, shown in both currencies. All prices include VAT. Components are supplied as part of an engagement rather than sold separately at a checkout: the firm figure, the delivery date and what is included appear in your written proposal. Delivered first, invoiced afterwards.
Nothing is invoiced until it has been delivered and you have looked at it. That is the whole arrangement, and it is why the steps run in this order.
Twenty minutes on which systems have to talk, what moves, and how often. No charge and no commitment.
Scope, price, delivery date and exclusions on one document, valid thirty days. Anything not on it is not billed without a new one.
You hand over credentials and a test data set. The clock starts there, not at signature. We build, test on your data and put it in service.
Configuration, documentation and rights hand over. The invoice follows delivery, payable within fourteen days. Fifteen days to raise anything.
It depends on the systems involved and the state they are in. Connecting two tools that both publish a decent interface is nothing like untangling a flow four people have edited over three years, and no honest figure exists before someone has looked.
So every request gets a free written proposal fixing the scope, the price and the date before anything begins. The entry prices on this page give you the order of magnitude; the proposal gives you the number.
The components we sell separately are the exception: those already exist, so their price is published and fixed.
For bespoke work: after delivery. No deposit, no advance, no staged payments. The invoice is issued once the work is in service and is payable within fourteen days, whatever the amount.
Our own components work the other way round, deliberately: paid at the time of order, because they exist already and reach you within 48 hours.
By email, within 48 hours. Nothing downloads automatically at checkout — you receive the files or a download link at the address you ordered with, together with the documentation and the notes needed to run it.
That is a deliberate choice: every delivery is a message we can trace, resend and answer questions about, rather than a link that quietly failed.
Because 48 hours is sooner than the fourteen days you have to change your mind, we ask you to confirm at checkout that you want it sent straight away.
Prices are shown in euros and Swedish kronor, and you can be charged in either. Switch at the top of any page and the figures, the basket and the checkout all follow.
The amounts are set separately in each currency rather than converted at a live rate. A live rate produces odd figures and can move between the moment you read a price and the moment you pay it.
Each card names what it connects. If your tool publishes an interface, an export that can be scheduled, or a reachable database, it can usually take part.
If you are not sure, ask before you buy — we answer that question for free and it takes us a minute. Buying the wrong product helps nobody.
Third-party publishers change their interfaces, and no supplier can promise otherwise. What we can do is build so the failure is loud rather than silent: every flow we deliver logs its runs and alerts on the first failure.
Faults against the agreed scope are corrected free of charge for fifteen days after delivery. Adapting to a change a publisher makes later is separate work, quoted separately. Nothing renews automatically.
You do, once the invoice is paid — along with the documentation another supplier would need to take it over. We have no interest in holding your systems hostage.
Components bought separately are licensed rather than assigned: use them across your own business, adapt them, keep them. What you cannot do is resell or republish the product itself.
Identifiers and interface keys are held in an encrypted secrets manager, separate from anything else, and deleted when the engagement ends.
Where the work involves personal data belonging to your customers, you remain the controller and we act as processor: a data processing agreement is signed before anything moves.
No. We hold no reseller agreement with any publisher and take no commission from one. Your subscriptions and licences stay contracted directly between you and them.
That matters when you ask us which tool to use: there is nothing on our side pushing the answer one way.
Which systems, roughly what moves between them, and how often. That is enough for us to say whether it is feasible, how long it takes and what it costs. We reply within two working days.