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 credentials or service URLs unless KORONA Event support asks you to.
Find the synchronization status
- In the back office, open Admin > Integrations.
- Find KORONA.studio integration.
- Use Last successful synchronization to see when the most recent import completed.
- 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 the integration is enabled, the External system calls section shows a Login, a Password, and Display URLs for Orders, Offers, and Agenda. Use these values in the KORONA POS configuration so POS terminals can open the matching KORONA Event screens directly.
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
| Problem | What to check |
|---|---|
| Synchronization fails immediately | Contact KORONA Event support; do not replace credentials or service URLs unless asked. |
| Section shows Not synchronized | Contact KORONA Event support before creating or changing KORONA.studio-owned records locally. |
| Products or prices are outdated | When Last successful synchronization last updated; correct the data in KORONA.studio, then wait for the next import or select Synchronize. |
| A record exists in KORONA.studio but not in KORONA Event | Whether Last successful synchronization advanced after the record changed. A failed page is resumed or replayed on a later import. |
