Grandus integration — two-way, with no manual intervention
The normalised catalogue is transferred to Grandus every 5 minutes and orders come back to your ERP. No developer needed.
A bridge between the PIM and the online shop
Grandus is your e-commerce platform; Monokaido sits above it as the PIM. Orders are taken over by a third system — your ERP, Cybersoft i6 for example. Without a connector, a person does the work between them: retyping the same products into the shop, and the orders from it into the ERP.
Visit grandus.skThe whole catalogue in Grandus, always up to date
Everything the shop displays
Products, categories (parents first), photos, parameters, prices including MSRP, and stock levels by location and by variant.
What is sent and what is not
You set which category branches are transferred to Grandus, and you can exclude individual products from the transfer.
Synchronisation every 5 minutes
Only changed products are transferred, oldest first, with a limit per cycle. A forced transfer also restores deleted ones.
Photo compression
Photos over 2 MB are compressed automatically before they are sent — which saves both data volume and space on the target storage.
Orders out, statuses back
A webhook sends the order to the ERP the moment it is created — there is no waiting for the next synchronisation cycle.
Orders from Grandus to your ERP
Every order from the shop is sent to the ERP together with the customer's details, the items and the discounts.
A status change shows up in the shop
When the ERP changes an order's status, the platform releases or re-reserves the stock and notifies the customer.
Protection against selling unavailable goods
Stock reservations are atomic — the customer never sees availability that has disappeared in the meantime.
Nothing is lost, even in an outage
If a webhook does not get through, the platform retries it every hour until the order is delivered.
Optimised for load and reliability
The connector is built for catalogues that change every day.
Reference data in a Redis cache
The connector keeps categories, units and parameters in memory, so with a large catalogue it does not fetch them from the target API for every product.
ETag / 304 revalidation
On the first transfer and on a forced one, the whole catalogue goes — for an unchanged product the target API answers with a 304 code and the transfer skips it. That shortens both the cycle and the API's response time.
Updates addressed by ID
After the first send, the platform remembers the product's ID in Grandus and sends further changes straight to it.
A real-time overview
You see the status of every transfer — whether it is running, waiting or has failed — and you can run any of them again.
Want to connect your online shop on Grandus?
We'll show you the first catalogue transfer to Grandus and an order's journey back to the ERP.



