Connect KORONA POS
Prepare KORONA, connect it to CMS Max, choose pricing and inventory settings, and run the first synchronization.
Before you start
You need a KORONA account with access to Settings > Data Exchange and permission to create or configure an APIv3 connection. Keep these account-specific details ready:
- API endpoint, including the regional KORONA host and
/web/api/v3 - Account ID
- API login
- API password
Do not copy an endpoint from another store. KORONA accounts can use different numbered hosts.
CMS Max reads products, tags, Commodity Groups, Price Groups, organizational units, and product stock. It does not modify those records in KORONA, acknowledge changes, or export orders in this release.
In KORONA Sync > Categories, Products includes the group and its nested groups; Direct Products includes only that group. Both show active (deleted), for example 0 (182). The first number counts imported products not reported deleted in KORONA, including website-only exclusions. Brackets count retained products reported deleted in KORONA. Click either number to view that set. Each column header explains its scope and count format. These counts reflect the last import, not a live KORONA lookup.
Prepare KORONA
- In KORONA Studio, open Settings > Data Exchange.
- Add or open the APIv3 widget.
- Create a dedicated login for CMS Max instead of sharing a staff login.
- Grant read access to products, tags, Commodity Groups, Price Groups, and organizational units.
- If CMS Max will track stock, also grant access to product stock. The selected organizational units must have warehouses.
- Copy the endpoint, Account ID, login, and password for CMS Max.
KORONA subscription permissions can affect stock access. If the connection succeeds but inventory does not, confirm product-stock access with KORONA support.
Connect CMS Max
- In CMS Max, install and activate KORONA POS from Plugins. Only one POS connector can be installed on a site.
- Open eCommerce > KORONA Sync > Settings > Credentials.
- Enter the account-specific API Endpoint, Account ID, API Login, and API Password.
- Save the settings. CMS Max validates the connection and securely stores the credentials.
- Confirm the Price Group that supplies website prices. CMS Max preselects the most likely standard retail group, but does not combine prices from multiple groups.
- With Global inventory enabled in Store Settings, choose Combine All Locations, Use One Location, or Do Not Track Stock:
- Combine All Locations adds stock from every warehouse-enabled organizational unit.
- Use One Location imports stock from the selected warehouse location.
- Do Not Track Stock keeps imported products sellable without requesting KORONA stock.
- Save again after confirming the Price Group and inventory choice.
Under Sync Rules > Inventory, Honour KORONA Track Inventory is on by default, including for existing connections. With this option on, products with Track Inventory disabled in KORONA remain untracked and sellable. Turn this option off to import those products as tracked with zero stock and an Out of Stock status, even if KORONA returns a positive quantity. Products that track inventory in KORONA keep their normal stock counts. This applies to global and store inventory when Use POS inventory is Yes; Do Not Track Stock still keeps global inventory untracked. This checkbox appears while POS inventory is enabled; its saved choice is retained when POS inventory is off. After changing the option, save and sync products and inventory to refresh all products; subsequent inventory scans preserve the selected behavior. Whether out-of-stock products appear on the website depends on your storefront settings.
Select the question-mark icon beside Honour KORONA Track Inventory to see the KORONA checkbox this option refers to. In KORONA, open a product and look under Additional Information > Quantity > Track Inventory.

Stock by store
After enabling store inventory or changing warehouse mappings, run an inventory scan before relying on the new store quantities. Apply Fetched Products & Categories to Site preserves existing store stock that depends on KORONA counts when its saved inventory was fetched for a different inventory mode or mapping. Source-untracked products are set to tracked zero stock without a quantity snapshot when Honour KORONA Track Inventory is off and POS inventory is enabled. Product details can still be applied; a fresh inventory scan supplies the current store balances.
To keep retail stock separate and exclude HQ, create your retail locations under eCommerce > Manage Stores, then choose Inventory by store under Store Settings > Features > Stores & Inventory > Inventory Mode. In KORONA Sync > Settings > Credentials, use Store warehouse mappings to select a KORONA warehouse beside each retail store. Leave excluded warehouses such as HQ unselected, then save and run Sync Inventory Only.
Settings saves preserve hidden warehouse mappings if inventory mode changed in another tab. To remove mappings, clear the warehouse selections in the visible store rows and save.
Each warehouse can supply one store. Only mapped warehouses contribute POS stock; active stores without a mapping receive zero when their POS-managed products sync. Set Use POS inventory → No to stop applying POS stock to new and existing products; existing stock balances remain unchanged. Product and inventory syncs share these mappings, and the product stock table shows the separate store counts and their total. Targeted stock reads for newly imported and restored products also use only the mapped warehouses. For products using KORONA stock counts, applying products fetched under an older inventory setup preserves existing store stock, tracking and availability; run an inventory scan to refresh them under the current mappings.
Changing mappings or switching inventory mode refreshes the selected warehouses completely on the next inventory sync. When returning to Global inventory with Do Not Track Stock saved, the next scheduled or manual product sync performs a full product refresh to restore untracked, sellable products. An inventory-only scan does not restore this setting. Missing or disabled warehouses and archived or missing stores stop synchronization until you correct or clear their mappings; existing stock is preserved. Check KORONA Status also reports mapping problems.
For products using KORONA stock counts, an invalid count for a mapped warehouse, such as a barcode scanned into the quantity field, leaves all store balances for that product unchanged. Other products keep syncing. The product appears under Needs Attention on KORONA Sync > Products, and its History shows the count, the product number and the KORONA warehouse. Product name or price updates do not clear this warning. Correct the count in KORONA; the next inventory sync updates the product’s store balances and clears the error. When Honour KORONA Track Inventory is off and POS inventory is enabled, source-untracked products use zero stock instead of warehouse counts, so invalid counts do not create a failed row or stock warning for those products.
The selected Price Group supplies the shared website product price in both inventory modes when POS price syncing is enabled. Customers can see pickup availability by store without choosing a store to see prices. Set the delivery/shipping stock source in Store Settings. This staged feature is not in production use. Complete the checkout phase before enabling live multi-store ordering: checkout must retain the inventory store ID, and customer pickup routing is still pending. Returning to Global inventory resumes the saved global KORONA inventory choice.
Changing the connector, endpoint, or Account ID later resets the saved KORONA revision history and remote selections. Treat that as connecting a different account and review every setting again. The next product run is automatically a full import so records missing from the replacement account can be reconciled safely.
Review product rules
Open Product Rules before the first import. New KORONA connections create products as drafts and sync product identity, price, and inventory. CMS Max retains existing names, descriptions, shipping and tax. New connections save both Follow new product rules choices as on, but the toggles remain hidden and inactive while new-product Visibility is Draft. Sale syncing is enabled, but sale prices and dates remain unchanged unless custom sale mappings supply them. With Liquor Max active, names sync only for non-liquor products. Category syncing defaults to on; disable it to stop importing and assigning POS categories.
If LiquorMax is active, Name and Missing Categories default to Non Liquor Products. This protects Central beverage names and categories while still allowing ordinary KORONA products to use their Commodity Groups.
Enable Only Create In-Stock Products to leave new out-of-stock products in KORONA Sync, without creating them in Products, until stock arrives. This is off unless explicitly enabled. Choose Public visibility to publish eligible new products. Subsequent stock changes retain the same product, visibility, content, and images; Store Settings > Hide Out-of-Stock Products controls storefront visibility. Products without inventory tracking count as in stock. After a product sync has deferred creation for stock, an inventory-only sync can create that product when stock arrives, provided it has no mapping error. Products staged by Fetch All Products & Categories from KORONA stay uncreated during inventory-only syncs until you review and apply them with a product sync. Unchanged out-of-stock deferrals do not repeat catalogue work or mark the run as failed.
In global inventory mode, enabling inventory updates also applies valid stock counts already fetched into KORONA Sync on the next inventory sync, even when KORONA has no newer stock revision. Products without a fetched stock snapshot and invalid stock snapshots are excluded from this recovery, including when a settings change clears their warning. Recovering stock leaves pending product updates eligible for the same sync.
First-stock creation remains part of its inventory sync until product processing finishes. Cancelling the sync stops further stock recovery and prevents queued creation work from publishing products after cancellation.
Under Existing Product Rules, Visibility and Crawl each have a Follow new product rules toggle when new-product Visibility is Public or Draft if No Liquor Data. With Draft selected, both toggles are hidden and inactive: product sync preserves manual visibility and Crawl choices. Saved follow choices return when you select Public or Draft if No Liquor Data again. They start on for new KORONA connections. Existing connections without a saved choice keep both off, preserving their current products until explicitly enabled. With Visibility on and the new-product rule set to Public, a stocked product created as a zero-price Draft becomes Public when a later product sync applies a positive price. Stock running out does not make it Draft. Crawl follows the new-product Crawl rule independently. On replaces manual Public, Draft, Crawl or Don’t Crawl choices on each product sync according to the corresponding rule, including drafting unmatched liquor products under Draft if No Liquor Data. Visibility following only changes Public or Draft products; Users-only and Password Protected products keep their access setting. If zero price drafts a protected product, it stays Draft when a positive price returns; restore the intended visibility in Products. Explicitly choosing Public permits future visibility following. Crawl following remains independent. Off preserves the corresponding product value. Changing either toggle marks eligible products pending; run the normal product sync to apply the rules. Completed Liquor Max enrichment keeps eligible positive-price products Public on later product syncs, including under the Draft rule. Source deletion, category exclusions and zero-price protection still apply; these toggles do not override archive rules. Visibility or Crawl changes also schedule the normal throttled sitemap update on sites eligible for a sitemap.
Products with a zero price remain drafts. KORONA scheduled prices become the CMS Max regular price; they are not automatically treated as sales. Configure tax behavior in CMS Max because KORONA sectors are not TaxJar product tax codes.
Check the connection
- Open eCommerce > KORONA Sync > Dashboard.
- Select Check KORONA Status.
- Wait for the background check, then select View Details.
- Resolve any failed credential, Price Group, location, or product-stock check before importing.
This check is read-only and does not advance KORONA revision tracking.
Run the first synchronization
The button names below assume category syncing is enabled, which is the default. They omit categories when disabled and include brands when brand syncing is enabled.
For a new site, use a review-first workflow:
- From More sync options, select Fetch All Products & Categories from KORONA. This downloads the full KORONA catalogue and current inventory without creating or changing CMS Max products.
- Review KORONA Sync > Categories. Manage product deletion and restoration in KORONA. To exclude an entire Commodity Group from this website only, archive it in CMS Max; this also excludes its products from POS updates and does not change KORONA. Configure Excluded from LiquorMax where applicable.
- Review KORONA Sync > Products, including Needs Attention, mapped values, prices, and representative inventory quantities. Products reported deleted in KORONA are hidden by default. Choose Product Status > Deleted in KORONA or All to show their red rows labelled Deleted in KORONA. Explicit filter selections remain effective. Website-only archives share the same red background, but only source-deleted products receive the Deleted in KORONA label.
- Select Apply Fetched Products & Categories to Site.
- Wait for all stages to finish and confirm that Pending Updates and Needs Attention are both zero, or review every remaining exception.
- Check several public product pages before enabling automated synchronization.
After the first successful import, the main Sync action and scheduled runs request newer product, Commodity Group, and inventory revisions, plus targeted inventory snapshots when needed as described below. KORONA returns deleted records as inactive so CMS Max can archive them without downloading the complete catalogue again. CMS Max advances each revision only after the returned pages have been stored and applied safely.
Tracked products without a saved warehouse inventory snapshot receive a targeted stock read during incremental inventory syncs. CMS Max backfills up to 100 products per run, using the selected inventory locations. Restored products also receive a fresh snapshot during the next inventory sync, even when old warehouse counts are saved. Remaining products stay eligible even when only one warehouse changes. Failed backfills appear in the sync log and remain eligible for retry; a failed linked-product update also retains retry work. Successful zero-stock snapshots do not cause repeated requests.
Preview mappings
Choose a Sample POS Product in Mapping Preview on the Mappings tab. This shared selection previews values for both Product Field Mapping and Brand Mapping. Sample selections are saved automatically in the database and shared by the site’s administrators. Changing a sample does not save other edits to the connector settings. If a selected record has been removed, CMS Max selects an available sample instead.
When a product, brand, or product-tag mapping uses tags, product imports refresh KORONA tag names, including tags on products absent from the incremental product feed. Product, brand, and product-tag mappings use the refreshed names, including custom SKU and GTIN mappings. If the tag feed cannot be read, the import continues with fetched product changes and saved tag names; review the tag-sync failure in the sync log and check API permissions.
When a brand maps directly to one tag name, such as tags.0.name, CMS Max identifies it by the KORONA tag ID. Renaming that tag preserves the POS brand and its CMS brand link. An automatically managed CMS brand follows the new name when it is not shared with another POS brand; manually linked or independently managed CMS brands keep their titles. Existing name-based POS brands adopt the tag ID when all their linked products, including archived products, identify the same tag. If a legacy POS brand covers different tags, its manual CMS brand link is carried forward to each tag as its products are processed. Conflicting manual links are retained for review. Composite mappings and tags without IDs continue to use name-based matching. Previously created unused brands are retained for review.
On the Brands tab, the small restore arrow beside Manually linked removes the manual override and resolves a CMS brand using the current POS brand name. It reuses an existing matching brand, or creates one when Create New CMS Max Brands is enabled. The manually selected brand is left untouched. If queue publication is interrupted, the saved product changes remain available through Apply Fetched … to Site. On success, the status becomes Linked and linked products are queued for syncing under the configured brand assignment rules. If matching is ambiguous, the matching brand is archived, or no match exists with creation disabled, the manual link is kept and an error explains what needs attention. Automatically managed, unshared CMS brands follow subsequent POS renames; independently managed or shared CMS brands keep their titles. Tag changes and brand relinking keep existing inventory warnings visible in Needs Attention until a valid inventory reading arrives; other fetched product changes can still be applied.
Archived product and category rows, and source-deleted brand rows, have a red background when shown. Website-only product archives share this styling; only source-deleted products receive the Deleted in KORONA label. Categories default Archive Status to Active. Choose Archived or All POS categories to inspect website-archived or source-deleted groups. Brands default Brand Status to Active in POS; choose Deleted in POS or All to inspect source-deleted brands. Needs Attention on all three lists opens without the active-only default and clears an active-only status selection when opened from the list, so deletion failures remain visible. Other filters and explicit status choices in its URL remain effective.
Products includes this group and its children; Direct Products includes only this group. Both show active (deleted) with separate links. Active means KORONA has not reported the imported product deleted, including products excluded only from the website. The bracketed number is retained source-deleted history, so 0 (182) means no active source products and 182 historical records. Counts reflect the last import rather than a live KORONA lookup. The CMS Max Products screen instead counts website catalogue products: its default Active status includes drafts, while category storefront counts include public products only. A source-deleted row can display both Deleted in KORONA and Name differs when its linked website name also differs.
Archive or restore source products in KORONA, then run Sync. Archiving an individual product in CMS Max creates a website-only exclusion and stops its POS updates. Restoring that website exclusion is allowed only while the source product is not known to be deleted in KORONA. If KORONA has deleted it, restore it in KORONA first and sync; CMS Max restores the linked product unless it was manually excluded. Routine syncs also archive previously restored CMS Max records that are still marked deleted in KORONA, even when no newer product revision is returned.
Choose an automation schedule

Enable Product Updates (includes inventory) for routine catalogue changes and Sync Inventory Only to refresh stock more often. Both use the dedicated POS synchronization queue. Either schedule can run at an interval or daily, weekly, or monthly.
If KORONA API access is interrupted or revoked, you can still disable both schedules and save the settings. CMS Max verifies the connection again when you replace the credentials or change a KORONA account-specific selection.
KORONA publishes a daily-limit response but does not publish one universal polling allowance for every account. Start conservatively, monitor Recent Runs for rate-limit warnings, and confirm the recommended frequency and daily allowance with KORONA for the customer's subscription.
Recover from a problem
Run the main Sync action again after correcting a temporary connection or data issue. Successfully linked products are updated rather than duplicated.
For inventory-only recovery, an administrator with server access can run php artisan nexus:inventory:import --tenant=TENANT_ID --full --no-interaction. This queues a complete stock read and updates linked products without fetching product details or categories. Add --now to execute it immediately. Use a full inventory scan to rebuild existing stock baselines, including incomplete warehouse maps. The index-only migration preserves existing product data. The normal Sync Inventory action uses stock changes and targeted reads for missing inventory snapshots.
Use Re-fetch All Products, Categories & Inventory only for recovery, source-deletion reconciliation, or a setting change that requires every KORONA record to be reconsidered. It is a full source read, not the normal incremental synchronization.
If products and Commodity Groups have been deleted and recreated in KORONA, run Re-fetch All Products, Categories & Inventory. CMS Max can reuse an existing website product when its SKU uniquely matches the replacement and KORONA has confirmed the previous record deleted. Automatically managed categories can be reused when their name and parent match uniquely. Existing content and visibility follow your saved update rules. Website exclusions, explicit category links, active owners, and ambiguous matches remain protected; review remaining conflicts in Needs Attention.
Store prices
With Inventory by store enabled, product sync saves a separate price for each mapped store. The mapped warehouse's KORONA Price Group supplies its dated price; a matching Store Price override takes precedence. Configure these prices in KORONA; no additional price-group mapping is needed in CMS Max. Unmapped warehouses do not supply store prices.
The product’s Pricing & Inventory tab includes editable Prices by Store inside Pricing. You can maintain prices for every active store, including stores without a POS mapping. Leave a store price blank to make that item unavailable to the store-price resolver. In this mode, the editor manages each store’s prices. Switch Enable Sale on to edit the separate Sales by Store table, where sale prices and their optional start and end dates are visible together. Save the product to apply changes. These sale prices are managed in CMS Max and are retained when KORONA updates a store’s regular price. KORONA promotions are not imported as store sales. Global inventory mode retains one price and the existing sale-price fields.
The shop, cart and checkout use one shared product price and sale across all stores; store prices and sales do not change what customers pay yet. Edit Price and the sale fields in Global inventory mode to change the website price. To maintain prices manually, select Don't change for price ownership. Inventory-only scans do not refresh prices.
KORONA product links populate product-level store prices. The website uses the shared product price; there is no storefront price selector.