Skip to content
Monokaidomanual
SlovenčinaEnglish

Transfers to other systems

Handing products to an ERP or a shop, the direction, the schedule, and the live run.

Available to roles AdminOpen in the app (Opens in a new tab)

A transfer sends enriched product data outward — to an ERP, to a shop on another platform, to a system you already run. It is the inverse of an import: there data is gathered, here it is handed over.

Transfers: tiles of supported systems and the list of configured transfers
Fig. 1 — Transfers. The connectable types on top; what you have actually configured below.

Controls on this screen

  1. Add transfer — Creates a configuration. Clicking a tile starts the same thing.
  2. Configure — A tile with this label is ready to use.
  3. Cybersoft i6 — Two-way product data exchange over XML POST.
  4. Grandus E-commerce — Pushes products and categories to a Grandus instance through its Admin REST API.
  5. Shoptet — Sends AI-enriched content back to your Shoptet shop.
  6. WooCommerce — Updates existing products and creates new ones.
  7. In preparation — A system that cannot be connected yet. The tile is not clickable.
  8. Configured transfers — Your actual connections. An empty list means nothing is being sent anywhere.

How a transfer works

  1. Choose the target system

    The tile decides how it communicates and what can be transferred.

  2. Enter the credentials

    The target system's address and key. From its administrator.

  3. Set the scope and schedule

    Which products, and how often.

  4. Watch it run

    The live view is a screen of its own; the history is in Transfer logs.

The product never appeared in the other system.

Check the Transfer logs — they carry the target system's reply, including a rejection for a missing field.

Can I control which products are transferred?

Yes, through the transfer's scope, and by excluding a particular vendor.

My system is not in the list.

Tiles marked in preparation are being built. For anything else, the route is the API.