A middleware service that connects a webshop to the Pantheon ERP in both directions: orders, statuses, stock, prices and products stay aligned, and every sale ends as a fiscalized invoice in the customer's inbox. A platform-independent core, one connector per platform. First connector: WooCommerce.
Trade runs on the webshop, the business runs in the Pantheon ERP, and the two are separate worlds.
01Orders are re-keyed by hand.
02Statuses drift apart: paid in the store, still open in the ERP.
03Stock and prices disagree between the two.
04Croatian fiscalization happens, if at all, as a separate manual step.
What was needed was a service that makes the two systems behave as one.
What was needed was a service that makes the two systems behave as one.
The service stands on the same foundations as our one-way Pantheon middleware, only it runs both ways. Everything specific to a store lives in a thin connector; everything beneath it is shared.
An order arrives through a platform connector, or directly as our canonical JSON on the published endpoint. It is written into Pantheon through stored procedures after the customer is ensured. A store that can send an HTTP request can send orders.
Swipe the diagram sideways.
Store to ERP for paid and cancelled, ERP to store for confirmed, processing, shipped and completed. Transitions are idempotent, so they create neither loops nor duplicate events.
Swipe the diagram sideways.
A change that starts in the store reaches Pantheon, and a change that starts in Pantheon reaches the store, through the same connector.
Swipe the diagram sideways.
The connector is a tightly bounded interface with a handful of operations: fetch order, set status, update stock and price, upsert product. A new platform means implementing that interface, not building a new service.
Swipe the diagram sideways.
Croatian fiscalization built in-house: ZKI, digitally signed XML, the exchange with FINA, the JIR and a QR code on the invoice. The PDF is emailed the moment the sale is fiscalized.
Swipe the diagram sideways.
Like the one-way middleware, it runs as two independent processes from one codebase. The second one also pushes ERP changes back into the store.
Swipe the diagram sideways.
Receives events from the store: a signature-checked webhook, or canonical JSON with token authentication. Validates, enqueues the job and returns 200 OK immediately. The store never waits on the ERP.
Writes orders into Pantheon, mirrors statuses, syncs stock, prices and products, fiscalizes and emails the invoice, pushing ERP changes back into the store through the connector, with retries at every step.
Both connections, the store and the Pantheon ERP, reconnect automatically after a drop. Local state, idempotency keys and the audit record live in PostgreSQL, with Redis as the broker. The ERP and the store are the sources of truth.
A full connector, REST API and webhooks. Integration-tested.
Orders are posted as canonical JSON to our published endpoint, against the OpenAPI spec. No connector needed.
Shopify, Magento, PrestaShop or a custom store, by implementing the same connector interface. The core stays untouched.
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 merchant gets a URL and credentials and never thinks about servers, updates or certificates.
Either way it is the same code, documentation and behaviour. The only difference is who holds the server.
The project is in active development. The whole loop is built and integration-tested against a live Pantheon instance and a staging store: order in, customer ensured, ERP order, status mirroring, fiscalization, PDF, email.
It is containerized and observable. The production fiscalization-certificate cutover is documented as a runbook, the same procedure already carried out on our one-way Pantheon middleware, which is in production.
Tell us which platform your store runs on. We'll come back within one business day with a clear plan.
A brand and catalog site for a performance-footwear company, its own CMS, and a B2B portal where dealers order wholesale by size run.
