I connect the platforms European retailers actually run on — Shopify, Amazon, bol.com, Exact Online, Fortnox, Mollie, PostNL — so stock, orders, payments and shipments stay in step without anyone retyping them.
Europe is not one market but a dozen that look alike from the outside. The VAT code changes at the border, the payment method people actually use changes with it, and the carrier that is cheap in one country is unavailable in the next.
Named because they are what clients actually run, not to imply any partnership. No reseller agreement is held with any of these publishers and no commission is taken from one.
The floor decides. A stock figure is only worth what the shelf agrees with. Every integration I build is judged against what is actually there, not against what a dashboard says.
Every engagement is scoped after a conversation, in a written proposal that fixes the scope, the price and the date before anything begins. Delivered first, invoiced afterwards, no deposit.
Shopify, WooCommerce, Amazon and bol.com kept in step with the system that actually holds your stock — one figure, every channel.
Sales, fees and settlements landing in Exact Online, Fortnox, e-conomic or Xero with the VAT codes each country expects.
Mollie, Adyen, Stripe and Klarna settlements matched to orders and posted to your books, fee by fee.
PostNL, DHL, DPD, GLS and Bring connected for labels, pickups and tracking that updates itself.
Moving off spreadsheets or a local package onto Exact, Fortnox or Odoo, with history intact and figures that reconcile afterwards.
A written read on the flows you already run: what fails silently, what duplicates, and what a channel change will break next.
Entry prices. Prices exclude VAT. Hong Kong levies none; where VAT is due in your country it is accounted for by you under the reverse charge. The firm figure is the one in the written proposal, prepared once I understand the work. Nothing is invoiced before delivery.
Not everything needs a project. These are scoped tightly enough to quote up front, and each is the small version of something larger — a way to find out whether we work well together before committing to anything.
They follow the same rule as everything else: the work is delivered first and paid for afterwards. Ask for a quote and you receive one, at the price shown; the invoice follows once the work is in your hands.
One integration you already run, examined end to end: what it does, where it fails quietly, and whether it is worth rebuilding.
The keys and connections your integrations depend on, checked for what is over-permissioned, expiring or shared where it should not be.
Your orders, stock or customer history pulled out of a system that makes it difficult, in a file you can actually open and check.
You have a proposal, an architecture or a supplier quote in front of you, and nobody in-house who can judge it.
The document to agree before anything is posted: which sale gets which code, in which country, and what happens to platform fees.
What to write down before asking anyone to quote an integration — so the quotes you receive are comparable and the one you accept is deliverable.
Watching a transfer you already run, whoever built it, so a silent failure stops being something your accountant finds in March.
Written documentation for a flow somebody built and left behind, so the next person does not start by guessing.
The month that would not close, worked through line by line until the difference has a name and a cause.
The figure in your ERP, the figure on each channel and the figure on the shelf, compared — with the reason they drifted apart.
A single sales channel connected to the system that holds your stock, so the same unit is never sold twice on that channel.
A new channel or system about to go live, reviewed against the things that reliably go wrong in the first fortnight.
Two ways in, and they are not the same. Request a quote is where you start if you have not commissioned anything yet: you receive a written price, the work is delivered, and only then is an invoice issued.
Already delivered? Pay for it is for clients who have the work in their hands and want to settle it by card rather than by transfer. Nothing is started by paying, and a payment made without a corresponding delivery is refunded in full.
Prices exclude VAT. Hong Kong levies none; where VAT is due in your country it is accounted for by you under the reverse charge. Prices are fixed for the scope described on each card; anything beyond it is quoted separately before it is done.
These are not products. A Shopify-to-Exact connection is never identical twice — the chart of accounts differs, platform fees split differently, and the country of the buyer decides the VAT codes. What is repeatable is the shape of the work and roughly how long it takes, so these carry an indicative figure rather than a price tag.
One authoritative stock figure, several destinations, no overselling.
Shopify, Amazon, bol.com and your own store reading from a single source, so the same unit is never sold twice.
Settlements matched order by order, fees split out, exceptions reported.
iDEAL, Bancontact and card settlements matched to orders and posted, with fees split out per transaction.
Higher-volume settlements reconciled and posted, with the deferred payment methods separated from the immediate ones.
Labels from the order, tracking flowing back on its own.
PostNL, DHL, DPD or Bring connected so labels print from the order and tracking flows back on its own.
Off spreadsheets and onto a system that reconciles afterwards.
Years of stock, customer and order history moved out of Excel into Exact, Fortnox or Odoo, reconciled afterwards.
Indicative figures based on similar work. Prices exclude VAT. Hong Kong levies none; where VAT is due in your country it is accounted for by you under the reverse charge. Each of these is adapted to the client it is built for — the chart of accounts, the fee structure and the tax codes are never the same twice — so the firm price, the delivery date and what is included appear in your written proposal. Delivered first, invoiced afterwards.
I have been writing software for a living since the nineties, back when connecting two systems meant a fixed-width file and a modem that had to be free at three in the morning.
Most of that career has been spent on the unglamorous side of the trade: the plumbing between business systems. Order flows, stock synchronisation, settlement files that have to balance to the cent. Work that nobody notices when it runs and everybody notices when it stops.
I lived and worked in Hong Kong for years, which is where the company is registered and where I learned how quickly a business outgrows the spreadsheet holding it together. These days the work is European, and the pattern is the same everywhere: a retailer in Rotterdam or Malmö is selling on three channels, settling through Mollie or Klarna, shipping with PostNL, and keeping books in Exact or Fortnox — with somebody retyping the numbers between them every Friday.
That is the gap Atlas Automations exists to close. I work with clients across the Netherlands, Belgium, Germany, the Nordics and France, in the same working day as they do.
You deal with me from the first message to delivery. Nothing is handed to a colleague halfway through, and nothing is subcontracted without telling you first. The trade-off is honest: work I cannot deliver in the time I quoted gets declined rather than accepted and stretched.
Dusan Bily · info@theatlasautomations.com
It starts with a conversation. Twenty minutes is usually enough to tell whether a project is worth quoting — and occasionally enough to tell you that you do not need one.
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 channels you sell through, what holds your stock, and what breaks today. No charge, 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 provide platform credentials and a test data set. The clock starts there, not at signature. I build, test against your data and put it in service.
Configuration, documentation and rights hand over. The invoice follows delivery. Fifteen days to raise anything.
It depends on the platforms involved and the state of what you already run. Connecting one marketplace to a clean Xero file is nothing like reconciling four channels, two payment providers and a chart of accounts nobody has tidied since 2021.
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 figure.
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.
It is a deliberate arrangement rather than a courtesy: the most common thing that goes wrong when buying software work across a border — paying for something that never arrives — cannot happen to you here.
Euros by default. If you would rather see and pay in Swedish kronor, switch currency at the top of any page — the prices, the basket and the checkout all follow, and the amount you see is the amount you are charged.
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.
Whichever you choose at the moment you order becomes the currency of the invoice and of any refund. Prices exclude VAT. Hong Kong levies none; where VAT is due in your country it is accounted for by you under the reverse charge.
That is where the company is incorporated, and where I lived and worked for years. The registration number, the registered office and the date of incorporation are all published in the legal notice — nothing about the setup is hidden.
For a client in the European Union it changes little in practice. Invoices are issued in euros, VAT is accounted for by you under the reverse charge, and the Privacy Policy sets out which data rules apply and why.
Shopify, WooCommerce, Amazon, bol.com, Magento and Lightspeed on the sales side; Exact Online, Twinfield, Fortnox, e-conomic, Xero and Odoo on the accounting side; Mollie, Adyen, Stripe and Klarna for payments; PostNL, DHL, DPD, GLS, Bring and Sendcloud for delivery.
If yours is not on that list, ask. Most platforms publish an interface, and the ones that do not can usually still be reached through a scheduled export.
They do, regularly, and with less notice than anyone would like. No supplier can promise otherwise. What can be done is to build so a failure is loud rather than silent: everything I 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 platform change months later is separate work, quoted separately. Nothing renews automatically and there is no retainer to cancel.
The short pieces of work are: their scope is closed, so the published price is the price. Everything larger is not — a Shopify-to-Exact connection is never identical twice, because the chart of accounts differs, platform fees split differently, and the country of the buyer decides the VAT codes.
The figures published under "what I build" are indicative, based on similar work. The firm price comes from a written proposal after we have talked.
Everything on this site is delivered first and invoiced afterwards, without exception. There is no deposit and nothing is charged before you have the work.
The short pieces of work carry a card payment option purely as a way to settle the invoice — faster than a transfer from another country, and reconciled automatically. It is a payment method, not a shop: nothing is started by paying.
If you have not commissioned anything yet, request a quote. A payment made without a corresponding delivery is refunded in full, which costs us both time.
You do, once the invoice is paid — together with the documentation another developer would need to take it over. Holding a client's systems hostage is a business model, just not this one.
I keep ownership of my own pre-existing components and libraries, and you get a free, perpetual licence to use them as part of what is delivered.
Seller account keys and API credentials are held in an encrypted secrets manager, separate from anything else, and deleted when the engagement ends.
Where the work involves your customers' personal data, you remain responsible for it and I act on your instructions under a written agreement signed before anything moves.
One person, from the first message to delivery. Nothing is passed to a colleague halfway through and nothing is subcontracted without telling you first.
The trade-off is honest: work I cannot deliver within the time I quoted gets declined rather than accepted and stretched.
Which channels you sell through, what holds your stock and books, and what breaks today. That is enough for me to say whether it is feasible, how long it takes and what it costs. I reply within two working days.
