Understand KORONA.studio synchronization

KORONA Event support connects the KORONA.studio ecosystem module before the account is handed over. Use this article to understand which system owns shared data and when synchronized changes become available.

Before you start

Know which KORONA.studio account owns this KORONA Event account's master data. Do not replace the KORONA.studio synchronization credentials or service URLs unless KORONA Event support asks you to. The KORONA POS external-call API key described below is separate and can be replaced through user management.

Find the synchronization status

1. In the back office, open Admin > Integrations.
2. Find KORONA.studio integration.
3. Use Last successful synchronization to see when the most recent import completed.
4. If the connection is missing or synchronization fails, contact KORONA Event support. Do not create duplicate master data in KORONA Event while the connection is being repaired.

What synchronizes in each direction

From KORONA.studio into KORONA Event:

• products and their prices
• payment methods, currencies, and sales taxes
• points of sale, cashiers, organizational units, and sectors
• tags, ticket definitions, customer groups, and economic zones
• voucher configurations and vouchers, when the voucher package is active in the KORONA account
• receipts, imported on a recurring schedule

From KORONA Event to KORONA.studio:

• invoices and fiscal delivery notes
• customer records attached to orders, including a company's Leitweg-ID when present
• tags created in KORONA Event

Customer imports also carry a KORONA.studio buyer reference into KORONA Event as the company's Leitweg-ID. KORONA Event-created e-invoices use the value stored on the customer when the invoice is issued; changing it later does not rewrite an existing invoice.

Imports process and checkpoint data in pages. After an error, KORONA Event resumes or replays the affected revision range on a later attempt. Temporary KORONA.studio service or maintenance failures are retried on the next scheduled import, usually within approximately 15 minutes. Last successful synchronization remains unchanged until an import completes successfully. After the first synchronization, imports repeat approximately every 15 minutes and exports run continuously, so changes should appear within minutes without pressing Synchronize.

External system calls

Once this feature is enabled, KORONA Event manages the receipt-cancellation callback for every imported POS profile. When fiscal delivery-note processing is enabled, it also manages the delivery-note-finalization callback. Existing external system calls on a profile remain in place, and KORONA Event does not change their KORONA numbers.

Open Admin > Integrations and find External system calls to review these callbacks. Synchronized means the calls are attached to the imported POS profiles. If a callback shows Needs repair or Not synchronized, select Synchronize and repair. The next successful full KORONA.studio import also repairs the managed callbacks.

The section continues to show the Login, a masked Password, and root Display URLs for Orders, Offers, and Agenda. Accounts with managed external system calls use the stable login KORONA_EVENT; other accounts keep their existing platform login. The masked password identifies the configured API key but cannot reveal its secret.

To configure or replace the password, you need permission to manage users:

1. Open Admin > Users and select the dedicated integration user for the KORONA POS connection.
2. Under API keys, select Create API key.
3. Copy the value from New API key immediately. It is shown only once; store it securely and enter it as Password in KORONA POS. Use the Login and required Display URLs shown under External system calls.
4. After the replacement works, select Revoke API key for the old masked key. If a secret was lost before it was stored, create another key; the masked value cannot be recovered.

Publish a saved view as a POS action

Saved views can open a filtered KORONA Event screen from the KORONA POS:

1. Open Orders or Events in the back office.
2. Apply the filters the cashier should see and save them as a view.
3. Select the saved view, open its action menu, and choose Publish as … POS action.
4. In KORONA.studio, add the resulting external system call to the applicable POS button layout.

An order view can open Orders, and an event view can open Agenda. Other saved-view and destination combinations cannot be published automatically. To stop offering an action, open the saved view menu and select Unpublish … POS action. Unpublishing deactivates the KORONA.studio call so an existing button cannot silently open a deleted target.

Automatic saved-view publication is available only on accounts with managed external system calls. If the publish action is not shown, use the Orders root Display URL and the current Login under Admin > Integrations, together with the securely stored API key, to configure an Orders action manually in KORONA.studio. A manually configured root action opens Orders without applying a saved view.

Expected result

Staff know which records are maintained in KORONA.studio, which records are exported from KORONA Event, and where to see the latest synchronization status.

Troubleshooting

Related articles

• Integration troubleshooting checklist
• Connect KORONA.entry