Check the KORONA.studio connection
KORONA Event support connects the KORONA.studio ecosystem module before the account is handed over. Use this article to verify that connection and understand which system owns shared data before selling anything that should appear on a KORONA POS.
Before you start
Confirm you have back-office access to Admin > Integrations and know which KORONA.studio account should own this KORONA Event account's master data. Do not replace credentials or service URLs unless KORONA Event support asks you to.
Steps
- In the back office, open Admin > Integrations.
- Find KORONA.studio integration and confirm that it is enabled.
- Check Last successful synchronization. It should show a recent timestamp rather than Not synchronized.
- Confirm that a Default cashier and Economic zone are selected when your setup requires them.
- Spot-check a known product, price, point of sale, or voucher configuration that is owned by KORONA.studio.
- If the connection is missing or synchronization fails, record the status and timestamp and 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. Use Last successful synchronization to confirm that an import completed. 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
The KORONA.studio integration section shows Last successful synchronization with a recent timestamp, imported products and points of sale appear in KORONA Event, and new invoices are exported to KORONA.studio.
Troubleshooting
| Problem | What to check |
|---|---|
| Synchronization fails immediately | Username, Password, Account ID, and URL are correct, and the KORONA.studio credentials were not changed recently. |
| Section shows Not synchronized | Whether Enable KORONA.studio integration is selected and the first Save and synchronize completed without an error message. |
| 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. |
