Integrations that keep working at 3 a.m., with logs to prove it
Connections between your till, online store, delivery apps and accounting software such as Netvisor, Procountor or Fennoa, built with retries, logging and alerts, and hosted on servers I run. From €1,900, monitoring from €39 a month.
- Code in your own Git repository
- Written fixed quote in one working day
- Linux servers run by me for more than ten years
- Every failure ends in a retry, a log line or an alert
- Night run started: 6 events from POS to Netvisor.
Ready. Inject failures, then run the night or step through it.
Simplified model of a typical design: 1, 5, 15, 30 and 60 minute retry gaps, idempotency keys, a dead-letter queue and alerts. Event and voucher ids are made up; nothing here connects to any vendor.
What every integration ships with
The failure drill above is not a demo feature. It is the same checklist every integration passes before it goes live.
Retries with backoff
Temporary errors such as 503 or a timeout are retried with growing gaps, so a vendor's maintenance window does not lose a day's sales.
Idempotency keys
Each event carries a key. If the till or webhook sends it twice, the second copy is recognised and nothing is booked twice.
Dead-letter queue
Errors that retrying cannot fix, like an unmapped VAT code, are parked with the full payload for a human to decide, never dropped.
Alerts that say what to do
Email or chat alerts name the system, the count waiting and the next step. One alert per incident, not one per event.
Mapping as data
VAT codes, accounts and cost centres live in a table you can read, so the next rate change is a settings edit, not a code release.
Readable logs
Every event, attempt and answer is logged with its id, so "did Tuesday's sales reach the books?" has an answer in a minute.
Integration catalogue
Common Finnish business connections, what moves where and how. API access depends on your package and the vendor's terms, so it is confirmed with each vendor in discovery.
9 of 9 shown
NetvisorAccounting
- MOVES
- Daily sales vouchers by VAT rate, sales invoices, customers
- HOW
- Netvisor API
Visma’s support pages say the API comes with Professional and Premium packages, and Visma does not build integrations itself. Check with Visma.
ProcountorAccounting
- MOVES
- Sales vouchers, invoices and payments
- HOW
- Procountor API
API available; check access and any fees with the vendor.
FennoaAccounting
- MOVES
- Sales vouchers and invoices
- HOW
- Fennoa API
API available; check access and any fees with the vendor.
WoltDelivery
- MOVES
- Orders into the POS or kitchen display; menu availability back to Wolt
- HOW
- Wolt integration API, public developer docs and partner directory
Integration access is agreed with Wolt. Check with Wolt.
FoodoraDelivery
- MOVES
- Orders into the POS or kitchen display
- HOW
- Usually through a middleware service such as Deliverect or Mergeport
The middleware bills its own subscription. Check current options with Foodora.
ShopifyEcommerce
- MOVES
- Orders, products and stock, both ways with the till
- HOW
- Admin API and webhooks
A custom app in your own store admin; check your plan’s limits.
WooCommerceEcommerce
- MOVES
- Orders, products and stock, both ways with the till
- HOW
- REST API and webhooks
API keys created in your own admin; your server, your data.
PaytrailPayments
- MOVES
- Payment status and settlement data, matched to orders and booked to accounting
- HOW
- Payment callbacks and settlement reports
Check the provider’s current documentation. Payments stay with the provider.
StripePayments
- MOVES
- Payment events and payouts, matched to orders and booked to accounting
- HOW
- Webhooks and the API
Your own Stripe account; check the provider’s current pages.
Summaries of each vendor's public pages at the time of writing. Check API access, package requirements and any fees with the vendor. Pikselipolku does not process payments or hold card data.
Name the two systems and what should move between them. Fixed price tomorrow.
Get an integration quoteBuild once, then keep it watched
Proposed prices in euros, excluding VAT 25.5 %. The monthly fee covers hosting on my servers, monitoring and alerts. Vendor and middleware fees are billed to you directly.
Small integration
One direction, one kind of data.
- A one-way sync, a webhook or a report export
- Logs and an error alert
- Handover notes
Accounting integration
Sales into Netvisor, Procountor or Fennoa.
- Daily vouchers split by VAT rate
- Mapping table for VAT codes and accounts
- Retries, dead-letter queue and alerts
- Morning report of anything parked
Delivery platform
Wolt, or Foodora through middleware.
- Orders into the POS or kitchen display
- Availability and opening hours back
- Order-level log for disputes
| Maintenance plan | Per month | Hours included | Good for |
|---|---|---|---|
| Basic | €79 | 1 | One integration that rarely changes |
| Standard | €199 | 3 | Several connections, the odd vendor API change |
| Business | €449 | 8 | Busy venues and chains with regular changes |
Extra work €95 an hour (+50 % out of hours). Paid discovery from €490 is credited to the build. If the integration fails the failure drill in test, it does not go live and you do not pay the balance. owner to confirm
When I would not build an integration
An integration is a small system of its own. It is only worth it when it replaces real, repeated work.
- 01A maintained connector already exists between your two systems. Use it; I can review its settings in an hour or two.
- 02The data moves once a month and takes ten minutes by hand. A monthly CSV import is fine.
- 03Your package does not include API access and upgrading costs more than the time saved. Then I tell you so before any build.
From two systems to one quiet night
- 1
Confirm access
API keys, package level and test environments checked with each vendor.
- 2
Write the mapping
Every field, VAT code and account agreed with you and your accountant.
- 3
Failure drill
Outage, duplicate, bad data and expired token, all forced in test.
- 4
Run in parallel
A week where the integration and the manual routine must match.
- 5
Watch
Monitoring, alerts and a monthly note of anything that needed a human.
Questions about integrations
Do I need a particular Netvisor package for an integration?
Probably. Visma's support pages say the Netvisor API is included in the Professional and Premium packages, and that Visma does not build integrations itself; third-party developers do. Packages and terms change, so check with Visma before we start. I confirm API access in discovery, before any fixed quote.
What happens when an API changes?
Vendors announce most changes in advance and keep old versions running for a while. Monitoring plans include watching those notices and the integration's error rate; a breaking change is fixed within the plan's hours or quoted first. Unexpected failures land in the dead-letter queue and raise an alert instead of disappearing.
Can you work with our own developer?
Yes. The code lives in your Git repository with a README, an environment template and tests for the mapping rules. I can build and hand over, review your developer's work, or own the integration while your developer owns the rest. Access, logs and alerts can go to both of us.
Get an integration quote
The systems involved, what should move between them and how often. You get a written fixed price within one working day.
Pikselipolku is an independent studio and is not affiliated with Visma, Netvisor, Procountor, Fennoa, Wolt, Foodora, Deliverect, Mergeport, Shopify, WooCommerce, Paytrail, Stripe or any other product named here.
Or email hei@pikselipolku.fi