A production-grade integration service that connects a webshop to the Pantheon ERP, with automated Croatian fiscalization and invoice delivery by email. From order to fiscalized invoice, with no manual step.
In most installations a webshop and the Pantheon ERP are two separate worlds. Somebody has to carry every sale from one to the other.
01Orders get re-keyed into the ERP by hand.
02Invoices are issued manually, one by one.
03Croatian fiscalization, a legal requirement, sits outside the flow or in a separate tool.
04The result: a lag between order and invoice, re-keying errors, and the same sequence of steps, every day.
What was needed was a service that carries every order to a fiscalized invoice without anyone touching it.
What was needed was a service that carries every order to a fiscalized invoice without anyone touching it.
The webshop sends orders in one direction and the middleware does the rest: a clean contract on the front, safe writes and fiscalization on the back.
The middleware defines the order format: canonical JSON, published as an OpenAPI spec and validated at the edge. Every order is checked and queued, and the webshop gets 202 Accepted immediately. An ERP outage never breaks checkout.
Swipe the diagram sideways.
Every write goes through Pantheon stored procedures, never a direct INSERT into ERP tables. Writes run in transactions, document numbering stays owned by the ERP, and access runs through a dedicated integration user with least privilege.
Swipe the diagram sideways.
ZKI generation, digitally signed XML, the exchange with FINA, the JIR and a QR code on the invoice. No intermediary and no third-party fiscalization service.
Swipe the diagram sideways.
A PDF rendered by headless Chromium from templates, carrying the fiscal data and QR code, emailed to the customer over SMTP with an internal copy.
Swipe the diagram sideways.
The same order sent twice never creates two documents. Retries with exponential backoff, dead-letter handling and automatic ERP reconnect. A correlation ID follows every order from the HTTP request to the sent email.
Swipe the diagram sideways.
The service runs as two independent processes from a single codebase, so each can scale and fail on its own without taking the other down.
Swipe the diagram sideways.
Authenticates and validates incoming orders, checks for duplicates, enqueues the job and returns 202 Accepted immediately. The webshop never waits on the ERP.
Ensures the customer, syncs the order into Pantheon, runs fiscalization, renders the PDF invoice and sends the email, with retries and backoff at every step and a dead-letter record when even that doesn't get through.
The ERP is the source of truth. The middleware holds no business data, only what it needs to never lose or repeat a job.
The service runs inside their network, next to Pantheon, without exposing the ERP outward. They get the image, the docker-compose configuration and runbooks for deploy, backup and rollback. Data never leaves their environment.
We run, monitor and maintain it, with separate production and test environments. The client gets a URL and a token and never thinks about servers, updates or certificates.
Either way it is the same code, API contract and documentation. Moving from one option to the other needs no changes to the webshop or the ERP.
The contract facing the webshop, the Pantheon access layer and the fiscalization layer are generic. What differs from client to client, credentials, certificate, warehouses, tax rates, invoice templates and business rules, is environment configuration.
Onboarding a new Pantheon user comes down to configuration and a check on the test environment, not a new development cycle, whatever platform powers the webshop.
Tell us what you are re-keying by hand. We'll come back within one business day with a clear plan.