Skip to content
CMS Max Documentation

POS Sync

Connect a supported point-of-sale system and keep products, categories, prices, and inventory synchronized with CMS Max.

In this guide, Connector Sync means the installed connector’s navigation label, such as KORONA Sync or RMH Sync. Buttons follow the same naming: View KORONA Sync and Check KORONA Status, for example.

POS Sync imports products and inventory from a connected point-of-sale system into CMS Max. It can also keep product information updated automatically.

Connect a POS system

  1. Install and activate Ecommerce, Liquor Max when applicable, and RMH (Retail Management Hero), NCR, Clover POS, KORONA POS, RICS POS, or LiquorBee POS from Plugins. Only one POS connector can be installed at a time.
  2. Open eCommerce > Connector Sync > Settings (for example, KORONA Sync).
  3. Enter the credentials supplied for your POS connector on the Credentials tab.
  4. Save the settings before fetching products or editing mappings.

LiquorBee POS logo

LiquorBee POS is an all-in-one, cloud-connected operating system built for liquor stores, covering sales, inventory, purchasing, receiving, reporting, promotions, loyalty, and cash management. Liquor Max must be installed and activated before LiquorBee POS can be installed. Liquor Max cannot be deactivated or uninstalled while LiquorBee POS is active; deactivate LiquorBee first. Enter the API URL, Merchant ID, Client ID, and Client Secret supplied by LiquorBee in the standard Credentials tab. The saved secret remains masked unless you use the eye icon to reveal it; you can replace it by entering a new value. Saving checks the Merchant ID against the stores assigned by LiquorBee and verifies catalog access. If the credentials have exactly one store, CMS Max automatically uses the precise ID returned by LiquorBee. The encrypted Nexus connection keeps the secret protected at rest.

The integration imports product identity, merchant SKU, UPC, name, description, regular price, lower sale price, category, and on-hand inventory through the normal POS Sync workflow. CMS Max uses LiquorBee's unique Item ID as its synchronization SKU because merchant SKUs can repeat; the original merchant SKU is sent with orders when available, but omitted when blank. New LiquorBee products start as drafts for review. Inventory comes with each product, so LiquorBee does not show a separate Sync Inventory Only schedule. When LiquorMax is enabled, liquor categories remain eligible for catalogue enrichment while MIXER products stay in Ecommerce without being treated as liquor. Order export is off initially; when enabled, captured orders are submitted to LiquorBee under their CMS Max order number. Every order product must be linked to an imported LiquorBee Item ID; a matching merchant SKU alone is not enough. CMS Max checks exported order statuses every 15 minutes; a Ready pickup order is marked ready for pickup and sends the usual customer email once. Closed is recorded but does not automatically mark an order fulfilled, because LiquorBee uses it for both cancellations and completed orders.

RICS Software

RICS Software logo

Install RICS POS with Ecommerce active, then open the Credentials tab:

  1. Enter the RICS API Token supplied by RICS support with permission to read inventory, products and product details, then click Save. No store code is needed for this step.
  2. The Credentials tab reopens with named Primary Store and Additional Inventory Stores selectors. Store 1 is selected when it is available; otherwise a sole available store is selected. If several stores are available without store 1, choose the primary store yourself before syncing.
  3. Review the Primary Store that supplies your website's catalog and selling prices. Its stock always counts. Optionally choose Additional Inventory Stores whose stock should count. At most 20 stores can count, including the primary store.
  4. Save any changes to your selections.

Saving validates the key and loads the available store names automatically. It does not import products or change RICS. Syncing remains disabled while no primary store is selected. Existing connections retain their saved stores. Connections without stored names acquire them on a successful save; if names are temporarily unavailable, their saved selections remain usable. A rejected new or replacement token preserves the existing connection. Names remain available when you reopen settings, even after the lookup cache expires. Use the full store names to avoid selecting a location your organization has marked as disabled.

The logo is sourced from the official RICS Software website.

New RICS connections use Products with size and width variations under Product Structure. A RICS product family becomes one shop product, with individual sizes and widths as variations. The product catalog supplies descriptions and size-grid labels; inventory supplies each size/width item, its stable ID, current price and stock. Product Details resolves reused SKUs when several historical product records share a code. Color-specific RICS SKUs remain separate families. Source size/width combinations are imported as provided; no extra combinations are invented. RICS’s literal SIZE value in its explicit One Size Fits All : size grid is a placeholder, so an item without another dimension imports as a simple product. Real single sizes, such as M or shoe size 9, remain variations. Existing manually configured variations are preserved.

  1. Run Fetch POS Products to stage families and inventory without changing shop products. Families start with synchronization disabled.
  2. Link each family to the appropriate CMS Max Product, reviewing duplicated SKUs and custom or decorated listings. Unique exact SKUs can resolve automatically during apply; approximate matches are not automatic.
  3. Use Map Variations for linked families. Existing variations match by their complete size/width options, with color checked where present. Select an explicit shop variation when options differ or several variations match. Enable Allow New Variations for Unmatched RICS Sizes only after reviewing the existing options. Linking a family to a different shop product clears its variation mappings and any previous approval to create unmatched variations. Changing a variation mapping preserves the replacement variation’s manual disabled state. Saving either a product link or variation mapping does not apply RICS catalog data. Linking a disabled family keeps automatic updates disabled until you explicitly enable or apply it.
  4. Enable synchronization for the reviewed family and apply it separately. A new product or a product with no variations can receive its source size/width combinations. Repeated applies preserve the same variation links. Existing product names, SKUs, images, option labels and variation SKUs are preserved; descriptions and additional mapped fields follow their existing-product ownership rules, and enabled price, GTIN and inventory ownership controls update the linked variations. New products receive the configured description, sale, shipping and tax mappings and start as drafts by default. Grouped connections without an explicit creation visibility use Draft, including when saving settings unchanged. New products and sizes receive valid UPCs even when existing-product GTIN changes are disabled.

Missing prices remain unknown rather than becoming zero. Existing known prices remain usable; unpriced new sizes remain uncreated and are flagged for review while priced variations apply. They can be created after a later fetch supplies their prices. A size absent from a complete inventory snapshot, or discontinued in source metadata, is disabled and its POS-managed stock cleared on apply; its variation and images are retained. If it returns, the connector restores the source-disabled variation. RICS IsSellableOnline = false disables the individual variation without clearing its physical stock. If every active item is restricted, the parent is hidden. A simple restricted or discontinued product is also hidden, including when inventory is managed manually. When the restriction is lifted, only the source-imposed restriction is removed; manually disabled variations remain disabled. Missing or null online flags impose no additional online restriction. Products without a RICS counterpart remain manually managed. Use POS inventory controls inventory at creation and during subsequent updates. With it off, new products use the selected initial stock status and existing products retain CMS Max inventory. Previously saved separate creation and update choices remain effective until a shared Yes/No choice is selected. The creation visibility setting supports Draft if No Liquor Data. Existing products preserve manual visibility and crawl choices, and follow category assignment rules; disabling category synchronization preserves their assigned categories. Ambiguous categories are flagged for review while the rest of the import continues. New products with an unresolved category remain unassigned. If brand synchronization is enabled with an explicit mapping, grouped products follow the brand creation and assignment settings; manually assigned brands remain unchanged when brand updates are disabled. A zero-price product remains a draft on creation and updates. A grouped product takes the lowest positive price among its active sizes, so it is a zero-price product only when every known size price is zero. A zero-price variation remains disabled even when its parent has a positive manual price. If all grouped variations are disabled, the parent is hidden so its old simple-product stock cannot be purchased. With price synchronization off, set a positive shop variation price before it can be restored by a subsequent apply. Archiving a POS category archives its linked products; restoring it allows the connector to restore products archived by that category. Changing Product Structure or inventory stores requires a fresh inventory snapshot before applying products.

New grouped-product name mappings use Description, then Summary, then the SKU when both are blank. Saved custom mappings and existing shop titles are preserved. Include Colour in New Product Titles appends source colours missing from the generated title; it starts enabled for new connections and is disabled when this setting is absent. Apply uses the current name, SKU and price mappings against fetched source data; existing shop titles and SKUs remain unchanged. Colour-specific SKUs remain separate products; this setting does not create a Colour selector. To display colour in product specifications, enable Ecommerce product attributes and map a Colour attribute group to Colors.*.TagTree in the POS attribute mappings. Grouped imports update only the mapped attribute groups, preserving other manually assigned attributes.

Run the product-and-inventory import after saving. Inventory-only imports refresh staged items and already-linked families. Manually archived products remain archived and excluded from shop updates while their source items can still be fetched; their presence does not block inventory imports. After changing the API token or primary store, fetch the complete product catalog before importing inventory. A failed or incomplete catalog fetch keeps inventory blocked until a complete refetch succeeds. Reused SKUs are resolved using Product Details even when the previous product family is absent from the latest catalog. Stock for each item is summed across selected stores. An incomplete product or inventory snapshot blocks apply, including source-driven category archival. Rejected catalogue snapshots are fetched again without mixing their staged rows into the replacement snapshot. Rate-limited queued catalogue and inventory fetches resume at validated pages, including SKU-filtered Product Details pages. Inventory checks item IDs and totals across those pages, including earlier attempts, before retiring missing combinations. Cancellation stops further family updates and follow-up processing; already applied families remain updated. A later successful run retains pending category redirects and follow-up work. These totals are not an atomic reservation across stores.

Connections saved without a product structure retain Individual items (legacy), where each item has its own product. Switch an unlinked connection to grouped products before fetching. Switching an unused connection back to Individual restores the default item-ID SKU mapping while retaining custom SKU mappings. Existing POS product links require review before changing structure; grouped staging must be cleared before switching back. Enable product variants in Ecommerce store settings to manage variant options in the shop admin.

RICS orders and refunds must be recorded manually in RICS. This connector does not import images or write stock back to RICS. The primary store must expose every item you want to sell, including zero-stock items. Review the first import before enabling automation. Unchanged inventory snapshots do not reapply linked products. During inventory-only runs, updates limited to stock, price or source availability preserve published page CSS and tenant caches; catalog changes retain their normal follow-up processing. A new item with an ambiguous reused SKU flags the affected families for a full catalog fetch while other products continue updating. Check Connector Status checks read access, with hourly monitoring using the shared POS health notification channel.

Saved bLoyal API Keys, Access Keys, API tokens, and passwords appear as masked values when you reopen connector settings. Anyone who can access the settings page can use the eye icon beside a sensitive field to reveal or hide its value. Edit the value in place to change it. Other connection fields remain visible. For RMH and NCR, the Endpoint, Loyalty Engine Endpoint, and Access Key are discovered when you save and appear under Advanced.

The Automation tab controls the product-and-inventory schedule and, where supported, the inventory-only schedule. Native NCR Counterpoint also has separate image filename and content-verification schedules. All automatic schedules start disabled on a new connection; enable them after reviewing the mappings and source settings. When enabled, the lightweight Counterpoint filename scan is scheduled for midnight each day, while full content verification is scheduled for 2:00 AM each Sunday so image downloads do not compete with the main catalogue import. Disable the applicable schedules to pause automatic imports; manual sync actions remain available. The Orders section on the Credentials tab controls bLoyal and LiquorBee order exports independently. New bLoyal connections start with POS Order Processing (SubmitCart) selected, even when order export is turned off before saving. Saving verifies the bLoyal account before enabling export; if discovery is unavailable on the first save, CMS Max saves the credentials with order export paused until the settings can be verified. Existing connections retain their selected workflow. Native NCR Counterpoint, Clover, KORONA, and RICS order export are not available yet. The two supported bLoyal workflows are:

  • POS Order Processing (SubmitCart) sends the complete captured order to bLoyal using SubmitCart. Choose this when RMH or another local POS fulfils the web order.
  • CMS Max Fulfilment (Inventory Only) sends only an inventory reduction. Choose this only when CMS Max fulfils the order itself.

When order export is enabled, CMS Max exports only after payment has been captured, and never exports a cancelled order. In POS Order Processing (SubmitCart), CMS Max sends the customer, products, applied discounts and their available CMS Max reason codes, pickup or shipping details, externally calculated tax, and captured payment. Coupon discounts appear at order level, while supported product and customer-group savings appear on their merchandise lines. CMS Max discovers the order source from bLoyal and saves the sole eligible web store and its sole web-cart device automatically. A saved device can also identify its unique web store. Existing source selections are retained. When discovery returns multiple possible sources, choose the intended store or device under Advanced order settings; blank source values continue to use the API key context. For pickup, CMS Max selects the bLoyal web store's pickup-capable default when it is unambiguous, or the sole pickup-capable location. If multiple locations are available without a clear default, choose one before enabling order export. A configured default location is sent; otherwise CMS Max asks bLoyal which location has stock for the entire cart and uses it only when there is exactly one match. bLoyal creates the downstream sales and inventory activity, so CMS Max does not send a separate inventory adjustment. In Inventory Only, CMS Max sends the inventory reduction and does not send a complete order. Orders awaiting payment or fraud review are withheld. If Authorize.Net later approves a reviewed payment, CMS Max releases that order automatically. A PayPal payment that PayPal is still reviewing is withheld the same way, and CMS Max releases the order when PayPal clears it. Manual-payment orders are released when an administrator selects Mark as Paid on the order. The Manual Payment Tender Code is not a gateway credential and is not used for captured gateway payments. Confirmed-paid manual orders use CMSMaxTender by default; bLoyal creates the tender from the submitted code. An existing custom tender can be retained under Advanced order settings. Unpaid pay-at-store orders are not exported as captured. Paid PayPal orders are exported with the tender code PayPal by default; a different code can be set in PayPal Tender Code under Advanced order settings, which appears once the store has connected PayPal. Paya ACH orders are not exported. CardPointe's Hold Payment mode is not eligible for automatic POS order export because it authorizes the card without capturing payment.

If a customer-group discount cannot be represented as exact per-unit cents, CMS Max keeps it at order level so the captured payment remains balanced.

For POS Order Processing, every exported product must have a SKU and a quantity greater than zero so bLoyal can identify and process it correctly in RMH. If any product is missing a SKU or has an invalid quantity, CMS Max fails the whole export instead of sending an incomplete paid order. Taxed orders are likewise withheld if their original merchandise-versus-shipping tax allocation is unavailable, preventing CMS Max from guessing an incorrect allocation. Fulfilment tips are sent separately from products and shipping, with the full paid amount preserved. These cases remain visible in Order Export History for correction and retry. Terminal export failures notify CMS Max internally through the same Slack channel as POS health checks, with the tenant, order, failure reason, and a link to review exports. Store admins and customers are not emailed about internal POS export failures. Normal order-notification emails are unchanged.

Tax-provider rounding can leave the product and shipping tax breakdown a few cents above or below the charged tax on orders with several taxed lines. CMS Max allows a bounded difference based on the number of positively taxed product lines and any positive shipping tax allocation: half that count, rounded up, capped at the number of positively taxed product lines. It distributes the correction one cent per already-taxed product line, largest tax first, keeping cart order for ties. Shipping tax, untaxed products, and the customer's payment remain unchanged. Differences above that limit or missing tax allocations still withhold the export for review.

CMS Max records an order as Accepted by bLoyal only after bLoyal acknowledges the selected request. SubmitCart must also return a cart identifier. This confirms that bLoyal accepted responsibility for downstream processing; it does not by itself confirm that RMH has downloaded the order. Open Order Export History from the POS Sync dashboard to inspect the acknowledgement identifier and response, or retry an eligible failed export.

Refunds and cancellations are not exported automatically in this first order-export release. Until return export is added, staff must mirror every CMS Max refund or cancellation in bLoyal/RMH so its sales, inventory, and loyalty records remain correct. If a partially refunded order is still waiting to export, CMS Max sends the original captured order so staff can apply the matching return downstream.

Under Credentials > Orders, CMS Max loads pickup locations from bLoyal and selects one automatically only when there is a sole location or a clear web-store default. If multiple locations have no clear default, select one before enabling order export. A saved pickup code that bLoyal no longer lists is shown for correction even when the account has only one available location. CMS Max fills the source store and device when bLoyal has one eligible choice. Choose them under Advanced order settings when there are several. If bLoyal is temporarily unavailable, existing saved values remain displayed and are not erased. Inventory-feed provisioning is separate from these SubmitCart settings. Manually confirmed payments use CMSMaxTender unless an existing custom tender is selected under Advanced order settings. PayPal orders export under the tender PayPal unless you enter a PayPal Tender Code under Advanced order settings; leave it blank to use the default. The field appears once the store has connected PayPal, or while it still has PayPal orders after a disconnect. If the store accepts gift cards, set its bLoyal/RMH Gift Card Tender Code here before exporting orders paid partly or fully with gift cards. Customer choice among multiple available pickup locations is a separate follow-up.

For NCR Counterpoint, obtain the HTTPS API endpoint, company alias, and API username and password from the Counterpoint installer. Enter the company's key from the NCR TXT file under Credentials → Developer API Key. It is encrypted in storage and masked until you click reveal. Leaving it blank preserves a saved key. Every connection needs its own saved key; server environment variables cannot supply one. The installer must place the matching signed XML key file on the Counterpoint API server and assign the Counterpoint user an API role permitting Items, Item Categories, Inventory Locations, and Inventory GET requests. If Use Location-Specific Pricing is enabled, the role must also permit GET /Item/{ItemNo}/Inventory/{LocId}. Verify SSL certificate under Credentials is enabled by default for new connections. Turn it off only temporarily for a self-signed certificate while a trusted certificate is arranged. This applies only to this connection; HTTPS remains required, but disabling verification means CMS Max cannot confirm the server identity, risking credential theft and altered responses. Connections without a saved preference verify certificates. Saving retains the displayed choice independently for that connection. On the first save, CMS Max selects the main/default Catalog & Pricing Location when available, otherwise it uses the first location returned by Counterpoint. The complete company item list remains authoritative; by default this location supplies location-specific prices when an item exists there, and company pricing is retained when it does not. If the merchant uses the same prices at every location, turn off Use Location-Specific Pricing under Credentials to use company prices and skip the extra location item requests. Changing this setting marks the next product fetch as a full fetch. CMS Max also selects every accessible Inventory Location. Reopen Credentials to review the discovered locations and remove service, damaged-stock, display, or other locations whose inventory should not be sold online. The location fields are required after this initial discovery. CMS Max adds the selected locations' Counterpoint QTY_AVAIL values together. Existing NCR sites already connected through bLoyal continue using their saved connection. Native conversion is unavailable until their product and category identities can be migrated without losing storefront links.

The Counterpoint API role also needs permission for GET /Item/{ItemNo}/Inventory/{LocId} when location-specific pricing is on. Incremental product fetches use it to confirm that a saved location price still belongs to an existing location record; if the record was removed, the company price applies.

After saving a native Counterpoint connection, the API password remains filled in on Credentials. It is masked until you select the reveal button. Only administrators with access to this settings page should open or reveal it. Once credentials have been verified and saved, changes to unrelated sync settings can be saved during a Counterpoint API outage; changing the connection details still requires a successful API check.

On production, Counterpoint syncs automatically maintain the integration password. The installer should allow GET /Company, GET /User/{UserId} and self-service PATCH /User/Password, and provide a dedicated integration user that is not shared with another application or environment. CMS Max caches the company's password lifetime for 30 days and checks password age at most daily. Within 20 days of expiry, it attempts a change at most once per day and updates the saved credential only after the new password authenticates successfully. The old password and any unverified replacement remain encrypted for recovery; a lost response does not cause blind repeat changes. A warning is logged when maintenance cannot complete. Normal POS Setup Check stays read-only. Automatic maintenance defaults off outside production; the server administrator can override either default with COUNTERPOINT_ROTATE_PASSWORDS. Keep syncs scheduled so maintenance gets an opportunity to run before expiry.

For Clover, follow the complete Clover setup and first sync guide. Select the merchant's API environment and use a Merchant ID plus a merchant-specific inventory token.

Counterpoint password warnings are checked daily at midnight in the application timezone without using the POS sync queue. CMS Max emails info@cmsmax.com if the last known expiry is within 14 days or has passed, a password change remains unverified for an hour, or expiry information is still unknown after a day. Reminders repeat daily; an expired password is flagged on the next daily check even if a warning was sent earlier. The monitor does not contact Counterpoint or reset passwords. Rotation waits for in-flight API requests; later requests reload the saved credential. Password recovery survives worker restarts and cache clears because both credentials are held encrypted in the tenant database. Keep normal database backups and protect the application encryption key. Independent uptime monitoring is still needed if the application scheduler or email delivery stops entirely.

If the saved account details, password, developer API key or certificate-verification choice change while the settings page is open, reload the page before saving. CMS Max rejects an outdated form rather than overwriting those newer choices, including changes made while a save is being verified. Ordinary password-maintenance status updates do not require a reload. Recovery retries do not reset the age of an unresolved password change. Reminder limits follow calendar days in the application timezone, so a slightly earlier midnight check still sends that day's warning.

Clover order export is not available yet, so CMS Max keeps it disabled even though catalogue and inventory synchronization can run normally.

For KORONA, follow the complete KORONA setup and first sync guide. On the first credential save, CMS Max loads all active Price Groups and chooses the most likely standard retail group. Combine All Locations is the default with Global inventory, but you can instead use one warehouse location or disable stock tracking.

With Inventory by store enabled in Ecommerce Store Settings, map POS locations to CMS Max stores on the Credentials tab. KORONA uses Store warehouse mappings and native NCR Counterpoint uses Store inventory location mappings. Map one retail location per store and leave HQ unmapped. Store names and Available for online shopping are managed under eCommerce → Manage Stores. Unmapped stores receive zero POS stock. Run a full inventory scan after configuring mappings. See KORONA stock by store for its warehouse setup.

Check the POS status

Open eCommerce > Connector Sync > Dashboard, or select View Connector Sync at the top of the active POS plugin's settings page, and select Check Connector Status in the Connection section. For RMH and legacy NCR connections through bLoyal, the check confirms that the login domain and credentials work, that the POS has enabled the product, inventory, category, and department change feeds CMS Max expects, and that the selected order workflow has the required endpoint. For native NCR Counterpoint, it checks Items, Item Categories, and inventory access for every selected location. With location-specific pricing enabled, it also checks per-item location inventory access when an item is available to sample; otherwise it warns that this permission remains unverified. For Clover, it checks product, category, and item-stock access. For KORONA, it checks the saved credentials, Products, Commodity Groups, selected Price Group, organizational units, selected inventory mode, and stock permission.

The check runs in the background so the dashboard remains responsive while the POS answers. The result remains visible in the Connection section as Ready, Action needed, or Unavailable. Select View Details to see the individual checks. Before the first import, the product check notes that the catalog assignment will be confirmed by the first product sync. If a completed product sync receives no products, the check warns that the default catalog assignment needs attention. The details also note when no positive inventory has been received, but zero stock alone does not make an otherwise working inventory feed unhealthy.

For bLoyal connections, the details always check SubmitCart prerequisites, including when order export is disabled or the inventory-only workflow is selected. They check the saved Loyalty Engine endpoint and validate the source store, web cart device, and pickup location against the current bLoyal configuration. Invalid overrides identify the only eligible replacement when one exists, or list the available choices. They fail the connection check only when SubmitCart order export is enabled; otherwise they remain warnings and do not trigger failure alerts. Blank source overrides use API-key routing, and blank pickup settings retain automatic selection. Missing eligible choices, a missing or invalid Loyalty Engine endpoint, or unavailable configuration discovery produce warnings. An invalid optional Loyalty Engine endpoint does not fail Grid discovery or inventory-only connection health; it remains a required capability failure when SubmitCart exports are enabled. These configuration checks do not confirm SubmitCart permissions or downstream order acceptance; verify those with a test order. Changing these order settings invalidates the previous result, so run a fresh status check after saving.

The POS status check is read-only. It does not change connector settings, reset or acknowledge change feeds, advance Counterpoint timestamp or KORONA revision cursors, or update POS data. Run it manually after configuring a connection or changing its POS permissions or inventory location.

When automatic monitoring is configured by CMS Max, active POS connections are checked hourly if Enable Automated Sync is on for either products or inventory. Busy connections are checked later so the check does not interrupt a sync. Failed checks notify the support team with the tenant, POS, and diagnostic details. An unchanged failure sends a daily reminder rather than an alert every hour; a new failure or a failure that returns after recovery alerts again. Warnings remain visible in the dashboard but do not send failure alerts. Pausing the connection or disabling both automated schedules excludes it from monitoring.

POS stock updates

When a refund puts stock back, CMS Max can pass that restock to a POS whose connector supports it, so the POS count does not stay too low. The update is sent only for an order that was exported to the POS and only once that export has been accepted. Each update appears under POS Stock Updates, which you reach from the POS Stock Updates button on the POS Sync dashboard or from the link in a failure email. The page opens on the updates that need attention.

Status Meaning
Waiting for order export The order has not been accepted by the POS yet, so there is no sale to put stock back against. CMS Max sends the update once the export is accepted.
Sending Ready to send, or being sent. An update that shows No progress for over an hour under its status is stuck: nothing has picked it up, usually because the POS queue is not running. The POS Sync dashboard warns about it, and you can Retry it or Mark handled in POS (see below).
Sent to POS The POS recorded the restock.
Not sent This update does not go to the POS, and what to do depends on the reason shown on the row. If the order was not sent to this POS, there is nothing to do: the POS never took that stock off. If the order's export is accepted later (for example, one held back until its payment is captured), CMS Max sends the update then. If the POS records returns another way (a bLoyal SubmitCart order, for example), CMS Max could not tell which order the restock belongs to, the order sold an item under several product codes (so CMS Max cannot tell which one to restock, and you record the whole return in the POS; the refund screen says so beforehand), or the row says the POS connector no longer supports stock updates, record the return in the POS yourself. If the order went to a different POS connection, record it in that POS.
Failed CMS Max could not send the update. The reason is shown on the row. When the details say the POS may already have recorded the restock, the POS did not answer, so it is not known whether it received the update.
Handled in POS You confirmed you corrected the stock in the POS, or that it already had the restock.

If an update fails, CMS Max emails the store's order-notification recipients and shows a warning on the POS Sync dashboard. The dashboard also warns about an update stuck at Sending. For a failed or stuck update choose:

  • Retry to send it again. A stuck update is queued again at once; if it stays at Sending, check that the POS queue is running. If the failure says the POS may already have recorded the restock, the details say whether a retry is safe. When it is, the POS ignores a repeat and there is nothing to correct in the POS yourself. Otherwise check the POS first: retrying could add the stock twice.
  • Mark handled in POS once you have corrected the stock in the POS yourself, or confirmed that it already has the restock. CMS Max then never sends that update. When the details of a stuck update say the POS may already have recorded the restock, a send began and left no answer: check the POS before you correct anything. You can also mark handled an update that keeps waiting for an order that will never reach the POS.

Restocks made before CMS Max started passing them to the POS are never sent afterwards; correct those in the POS by hand.

With bLoyal, restocks are sent only for orders exported with CMS Max Fulfilment (Inventory Only). If your store uses POS Order Processing (SubmitCart), bLoyal records the sale itself, so the update shows Not sent and you record the return in your POS (the update names it: RMH or NCR). Stock kept for product options exists only in CMS Max and is not sent. If bLoyal already holds a stock update under the restock's reference that CMS Max did not send, the update shows Failed and names the reference: check the product's stock in your POS, record the restock there if it is short, then mark the update handled.

Review POS connections across sites

CMS Max staff with full central dashboard access can open Reports > POS Connections in the central admin panel. The report lists sites with an enabled POS connector, their latest completed status check and its result, imported POS product count, combined inventory quantity, products with positive stock, sync status, latest sync run, and product errors. Full scan interval and Inventory scan interval show the configured automation frequencies, such as 45 minutes or 5 minutes, or the calendar schedule in the site timezone. Disabled automation shows Disabled; unavailable data and older saved reports show Unknown until a successful refresh. Counts and inventory exclude deleted POS products. Open Check details to read the individual diagnostic results. Cards above the table show how many sites use each POS and how many of them have a sync error (a failed status check, a failed latest sync run, or site data that could not be read). Click a card to show only that POS's sites, or All POS sites to show every site; Show > Sync errors lists the sites behind the error counts. The report is read from every site once an hour and saved, so the page opens straight away; the line under the title says when it was last read. Click Refresh to read every site again now: a popup shows how many sites have been read, and the page shows the new results once every site is read. Stop closes the popup and keeps the previous results.

Search by site or domain, filter by connector, or use the attention filter to find failed checks, zero or negative inventory, paused sync, product errors, unreadable sites, and connections without a recorded check. Additional columns include the last product import and latest run time.

The report keeps its saved snapshot until the next completed hourly read or manual refresh. Refresh reads each site’s saved POS data; it does not contact the POS or run a status check. Health results apply only to the currently saved connection credentials and endpoints. After those change, Not checked is shown until a matching check completes. An unreadable site shows unavailable totals rather than zero inventory.

Configure mappings

With Liquor Max active, map Vintage to the POS field containing a four-digit year or NV. Field names vary by store; inspect the fetched values before choosing a source. Accepted years run from 1900 through next year, and NV is case-insensitive. Vintage applies only to products with Beverage Type → Wine. For products without beverage data, POS values remain stored and apply when Wine beverage data is added by Central enrichment or a tenant edit. On the product edit page, selecting Wine or opening Wine data with an empty vintage prefills the mapped POS value before saving. A selected year or NV is preserved on that save. A vintage left blank or cleared after prefill is filled from valid mapped POS data when Wine data is first created or the type changes to Wine. Clearing an existing Wine vintage without changing its type survives that save; the blank remains until another POS field changes, the Vintage mapping changes, or a forced full apply runs. An eligible apply fills it again, even under Don’t change. Later POS updates follow the configured update rule. Mapping vintage does not create beverage data or infer a beverage type. Under Existing Product Rules → Vintage, Sync updates saved vintages and Don’t change preserves them; a missing vintage can still be filled. Blank or invalid POS values preserve the saved vintage. No vintage mapping is enabled automatically.

Open Product Mappings to choose how POS fields populate CMS Max products. When Ecommerce brands are enabled in store settings, the separate Brand Mapping section beneath the other product fields lets you enter POS source paths; its CMS Max destination is always Brand. For KORONA, this can be a custom product field; select the Record button beside Sample POS Product (for example, KORONA Record) for its exact path. For bLoyal, map Brand to ProductBrandName; POS Sync resolves it from the product's Product Brand assignment after Enable Brands is turned on under Sync Rules. Supplemental spreadsheet attributes are not read by POS Sync. When store-level brands are off, the Brand mapping and Brand Rules controls are hidden without deleting saved choices. Category Mappings appears when Enable Categories is on under Sync Rules.

When Ecommerce product tags are enabled, use Tag Mappings for KORONA, Clover, RMH/bLoyal, or NCR Counterpoint. Fetch products, enter a tag group name, and add one or more field paths from a sample POS product. Use the Record button beside Sample POS Product (for example, KORONA Record) to inspect its imported fields. New KORONA mappings start with tags.*.name; Clover mappings start with tags.elements.*.name. These paths map every tag name in the connector's array, while an indexed path maps only one. Saving reuses an existing group with that name or creates a filterable group. Changing the name of a linked group renames it. If a linked group has been deleted, enter a replacement group name or remove its mapping before saving. Optional fallback paths are used when the primary paths have no value. A product sync creates tag values from those fields and replaces the product's assignments within mapped groups; tags in other groups stay assigned. Clear a mapping to stop managing its group. The sample value is a preview of the fetched record, so fetch again after changing POS data.

  1. Fetch products if no sample records are available yet. Product, category, and tag mapping editors appear after the fetch, and their field choices come from the fields present in the fetched POS records.
  2. To create a starting point automatically, select Suggest with AI. Your POS connector queues an analysis of field names and sample values from up to 10 products spread evenly across the imported catalogue using the configured AI provider. You can leave the page while it runs; the suggestions load when the analysis finishes or when you return. Clover suggestions retain Clover's documented field semantics while assessing how the individual merchant populates optional and display fields. KORONA uses connector-owned selectors instead, so AI suggestions are not shown on its mapping screen.
  3. Select a sample POS product or category to preview the mapped CMS Max values. These selections are saved automatically in the database and shared by the site’s administrators; if a selected record has been removed, an available sample is used instead.
  4. For a sample product, select the Record button beside Sample POS Product (for example, KORONA Record) to inspect every imported field and its dot-notation field path.
  5. Review the AI Mapping Suggestions box to see the chosen POS path, confidence, reason, and real source examples for each field. Only medium- and high-confidence suggestions are shown. Fields owned by a connector's separate inventory feed are not suggested as product mappings. Existing mappings remain unchanged during this review.
  6. Leave the suggestions you want checked, then select Apply Suggested Mappings to update those fields in the editable mappings below. Existing mappings for other fields are kept. Adjust the source and fallback fields as needed.
  7. Save the settings before starting a sync. Applying an AI proposal to the form does not save it automatically.

Changing saved mappings marks affected imported products for another update. The dashboard will show when updates are waiting to be applied. Connector settings and manual product/category controls cannot be changed while a POS sync is queued or running. The settings page shows a warning, temporarily disables the affected controls, and checks more frequently until the run finishes so it unlocks automatically. The sync monitor detects runs that have stopped reporting progress, marks them finished, and then unlocks the form. Save the settings before starting another sync.

The imported products table shows each configured product mapping in its own column. If no mappings have been saved, it shows the connector's default mapping columns and values instead. Use the column manager to show, hide, or reorder those columns. RMH and NCR do not include Quantity in their default product mappings because bLoyal supplies authoritative stock through its separate inventory feed.

When the category and department change feeds are enabled, routine product syncs also receive taxonomy changes. With category updates enabled in Sync Rules, changing a POS category or department name updates the linked CMS Max category, its mapped content, and the public URLs beneath it. CMS Max creates redirects from existing category and product URLs to their new locations. A disabled category or department feed falls back to the classifications included with each product.

In Global inventory mode, native NCR Counterpoint’s Credentials → Show stock by location on product pages displays the last synced sellable quantity for each selected inventory location on product detail pages. It is on by default and makes no live POS request when a customer views the page. The displayed quantities are capped by the product's aggregate sellable stock, so a negative balance at another location cannot make the page promise more units than the cart allows. Saved locations appear immediately in the location selectors; type a name or ID to search Counterpoint for another location. Storefront location names lists the selected inventory locations automatically, including on existing connections. Leave a name blank to use Counterpoint's description; the field's placeholder shows the automatic name when available. Automatic descriptions remain separate from saved custom names, so refreshed POS descriptions and a different account do not inherit stale automatic overrides. Custom names and visibility choices are preserved. Override a name or turn off Show on product pages for that location as needed. If Counterpoint is unavailable or has no description, the location ID is displayed until a name is available. Hiding a location from the page does not remove its stock from the inventory total. Run an inventory sync first so the breakdown is available.

In Global inventory mode, expand Customise storefront location names to edit these optional overrides. The section is collapsed by default; automatic names and saved overrides still apply while it is collapsed. Product pages use a custom name when provided, otherwise the retained Counterpoint description, with the ID as a fallback only when neither name is available.

In Store inventory mode, the same CMS store balances, stock adjustments and storefront availability display used by KORONA apply to Counterpoint. The mapping table replaces Counterpoint’s Global-mode Inventory Locations and storefront-name controls. Counterpoint continues using its configured Catalog & Pricing Location for the ordinary shared product price; store inventory does not enable separate POS prices per store. Existing Global inventory connections retain their selected locations, display settings and aggregate stock behavior.

Location dropdowns include the ID in parentheses to distinguish locations with similar names. The Storefront name placeholder and automatic storefront name use the description alone, without appending the ID.

Inventory sync progress uses the same custom location names, then saved Counterpoint descriptions, falling back to the location ID when no name is available. This includes locations hidden from the storefront and does not require a live POS lookup.

A successful location refresh determines which locations can be newly selected, including when Counterpoint returns an empty list. Previously selected locations retain their labels rather than being silently removed. If Counterpoint is unavailable, selectors use the last successful list and retained labels.

Location selectors retain the last successfully retrieved Counterpoint descriptions separately from storefront overrides. Once learned, those names remain available when the cache expires or the POS is offline. Searching refreshes the descriptions when Counterpoint is reachable. Names are scoped to the saved endpoint, company and API user, so another connection does not inherit them.

Choose product rules

Native Counterpoint connections with imported products also show Accessory Options. Search imported Webtype (PROF_COD_2) codes, add an option group name, then search for its accessory item numbers. In Webtype accessory choices, the Webtype and Accessory SKUs dropdowns show up to 50 imported choices when opened. Type to find more. Saved choices keep their labels even when they are outside the initial list. Saving the first accessory mapping enables Store Settings → Features → Pricing Methods → Enable Product Options automatically; you can turn it off afterward, and later mapping saves will respect that choice. On the next Apply, matching products gain optional dropdown choices with a blank choice to remove a selection. Each accessory's Counterpoint item number becomes the option SKU and PRC_1 its added price; later POS description changes refresh the option label. The accessory itself may remain excluded from the ecommerce catalogue, but source-deleted accessories are not offered. Renaming a group preserves its option choices and existing carts. Removing a rule removes only its previously managed choices; other product options are preserved. An accessory removed after a customer added it to a cart cannot be checked out until that cart item is removed and added again. These choices are attached to the parent cart item, not added as separate accessory cart lines, and their individual Counterpoint stock is not checked.

For native NCR Counterpoint, enable Get code descriptions from files under Credentials if the merchant provides attribute-code files. Otherwise, expand Counterpoint brand codes under Sync Rules before enabling Missing Brands → Create and enter readable brand names manually. Several codes can have the same name—for example, KNM and KENMORE can both become Kenmore. Codes without a file or manual description keep their original text, so review imported brand codes before applying products to the site.

When file-based code descriptions are enabled but both configured lookup files are missing, the POS Sync dashboard's recent activity records a warning. Check the filenames in Credentials and ask the merchant to make the files available. Product imports continue using saved or manual names; previously downloaded descriptions are not deleted.

Lookup files are checked before product imports. Changed code descriptions trigger a full product fetch so existing products receive the updated names. Unchanged descriptions, including files with reordered rows, do not force an incremental sync into a full fetch.

Use the Sync Rules tab to configure product creation and updates. Inventory uses one shared choice for new and existing products; the other rules determine initial visibility, category creation, and which POS-owned fields may overwrite CMS Max values.

Defaults below apply to new connections. Existing connections retain saved choices and effective sync behavior when a setting is unset. For legacy connections, missing category visibility displays as Public, missing product visibility displays as Public or Draft if No Liquor Data with active Liquor Max, missing tax ownership is Sync, missing new-product crawl settings mean Crawl, and missing name and category creation scopes display as Don't change and All products, respectively. Saving unrelated settings preserves those choices, except that a Don't Crawl saved with Draft visibility is saved as Crawl (see Crawl Setting below).

Existing Product Rules shows controls for mapped fields and built-in connector features. Connector defaults and saved legacy paths count as mappings; a mapping with neither a source nor a fallback path does not. Description, shipping and tax controls appear when at least one field in their group is mapped. Sale controls appear for mapped sale fields and for native bLoyal sales. Inventory ownership is configured separately under Sync Rules > Inventory > Use POS inventory when a stock source is available, except with KORONA Unlimited inventory in Global mode. Category Assignment is available while Enable Categories is on, and Images is available for native Counterpoint connections. Hidden ownership controls retain their saved choices. Clearing both paths of a mapping preserves that field on existing products, even with Sync selected. Restoring a path resumes updates using the saved choice. A configured path returning zero or an empty value can still update or clear the field. KORONA provides independent Visibility and Crawl Follow new product rules toggles when new-product Visibility is Public or Draft if No Liquor Data. Under Draft, both are hidden and inactive while retaining their saved choices. They default on for new connections; existing connections without saved choices retain both off. Enabling them marks eligible products pending for the next product sync. Other connectors preserve existing visibility and crawl. New Product Rules controls initial visibility, crawl behavior and stock status when POS inventory is off.

Use POS inventory defaults to Yes and controls quantities, stock tracking and stock status for both new and existing products. Yes applies POS inventory when a product is created and during later product or inventory updates. No creates products with zero quantity and inventory tracking off, using the Initial Stock Status under New Product Rules; existing products retain their CMS Max inventory values. This choice does not enable or disable inventory fetching. Connectors with a separate inventory schedule keep that schedule; LiquorBee has no separate inventory schedule. Storefront stock checks use the values stored in CMS Max.

Connections with different saved creation and update inventory rules show Keep saved settings. Saving other settings preserves those rules. Select Yes or No to use one rule for both creation and updates. Matching saved rules remain selected, including when the control is hidden. The control appears when a stock source is available: a native connector feed or an effective Quantity mapping. All live connectors provide native stock; clearing a product mapping does not disable their inventory feed. Demo connections require a Quantity source or fallback. In Global inventory mode, KORONA’s Do Not Track Stock strategy hides the control and keeps products untracked.

Under Category Rules, turn Enable Categories off to stop creating, assigning, updating, or source-archiving CMS Max categories. Products are not archived merely because their POS category hierarchy is deleted while category management is off, and products previously archived with a deleted category hierarchy remain archived. This also hides the category-specific controls, Category Mappings tab, and Connector Sync > Categories navigation. Existing imported category records, mappings, and category preferences remain available if categories are enabled again. Without Liquor Max, newly configured connections create missing categories for all products. New CMS Max categories default to Draft. Saved category-creation choices take precedence.

For native Counterpoint, open Category Mappings and choose a source under Product categories. New connections start with Counterpoint categories, which uses the category and subcategory already assigned in Counterpoint. Fields on each product lets you choose the fields for a main category, an optional subcategory beneath it, and an optional separate category. Pick an Example product to see its actual value beside each field name; the fields used by one merchant may not suit another. If a product has no main-category value, it falls back to its standard Counterpoint category. If separate product fields hold readable category names, expand Category names (optional) to select them. Otherwise, enable file descriptions under Credentials, or enter code-to-name pairs under Category code names (optional) when file descriptions are off. Unlisted codes remain visible as codes so they can be reviewed later. Changing the category source, profile paths, or code names makes the next product fetch a full fetch so existing items can be recategorized.

Under Tag Mappings, enter a tag group name and choose the POS item field that supplies its values. You do not need to create the group separately: saving reuses a group with that name or creates a filterable group, and product sync creates its values. A newly created group appears as a storefront filter after its first product sync; there is no separate step to make it public. Existing groups retain their current filter setting. Editing the name of an existing mapping renames that group. Counterpoint attribute slots such as ATTR_COD_1 through ATTR_COD_6 are merchant-defined; preview their imported values and lookup descriptions to decide which fields represent Finish, Style, Size, Capacity, or Condition. The sample-value column shows the POS code beside its description when available. Condition comes from its configured item field, not an assumed meaning of the SKU suffix.

For Counterpoint, Credentials → Code descriptions → Get code descriptions from files lets CMS Max refresh attribute and profile names from text files on the API server during product fetches. The filenames default to ATTRCODES.txt and PROFCODES.txt, but you can change each to match the files supplied by your POS provider. Only those filenames are requested. Each description is used only for the attribute or profile fields marked valid in the file. Downloaded attribute labels are used for tag values and brand names; downloaded profile labels are used for category names. For categories and brands, a downloaded name takes priority and a saved manual name fills any gap. The manual category- and brand-code editors are hidden while file sourcing is on; their saved names remain available if file sourcing is turned off. Manual tag names continue to override downloaded descriptions. When either file changes, the next product fetch rechecks the full catalogue so existing products can pick up the updated labels. Leave the option off to use manual names or raw codes without requesting files.

Linked Category Details defaults to CMS Max controls linked category details and determines whether CMS Max or the POS owns category names, mapped content, URLs, and parents. CMS Max ownership preserves editorial changes while products and category links continue syncing. POS ownership updates POS-created and manually linked CMS Max categories whenever their POS category changes.

When Ecommerce brands are available, turn on Enable Brands under Brand Rules to import POS brands. Create New CMS Max Brands controls whether an unmapped POS brand can create one; New Brand Visibility defaults to Public and can be set to Draft. Existing Product Brand Assignments controls whether the POS can change a linked product's brand. Connector Sync > Brands lists each distinct imported POS brand and lets you link it to an existing CMS Max brand. The restore arrow beside Manually linked removes that override and returns to matching the current POS brand name, reusing a matching CMS brand or creating one when allowed. The previously selected CMS brand is left untouched. If no usable match can be resolved, the manual link remains and the action explains the conflict. Scheduled product imports check for Product Brand name changes. Connector-created brand names and URLs follow those changes; manually linked CMS Max brand names are preserved. Turning brand sync off stops POS brand processing without removing existing brand assignments. If Ecommerce brands are later re-enabled, the next bLoyal product sync automatically performs the complete product import required to recover Brand details omitted while the feature was unavailable. A newly created public brand receives its brand URL and product-list content immediately. Brand assignment does not change the product's own URL.

Native Counterpoint starts with ATTR_COD_2 as its Brand mapping, matching the available Items with Web Info export. Counterpoint attribute slots can differ by merchant, so inspect a fetched raw item and change the Brand source under Product Mappings before enabling brand creation when necessary. ITEM_VEND_NO is the vendor number and is not used as a brand fallback.

Existing Product Rules > Category Assignment is available while Enable Categories is on, independently of product-field mappings. The default Sync assigns each product to the CMS Max category linked to its current POS category. Choose Don't change to retain manual assignments when the POS category changes. Explicit POS-to-CMS category links can still replace the primary category, and an empty primary can still be filled. This policy does not rename or move categories.

For RMH and legacy NCR connections through bLoyal, Product Availability includes Only Sync Web-Enabled Products. Leave it on to archive products that bLoyal marks as unavailable for the web. Native NCR Counterpoint provides Only Sync E-commerce Items; when enabled, items without Counterpoint's E-commerce Item setting are archived. Disable the applicable rule and run Re-fetch All Products, Categories & Inventory to restore previously archived products. Clover, KORONA, RICS, and LiquorBee do not expose an equivalent website-availability setting; the availability control is hidden for these connectors. RICS always honours its individual IsSellableOnline flag: grouped variations are disabled, restricted simple products are hidden, and legacy individual-item products are archived. Clover items marked unavailable remain in the catalogue as out of stock.

Without Liquor Max, Name defaults to Don't change, preserving existing CMS Max product names. Tax Code defaults to Don't change for every connector. Saved choices take precedence over these defaults.

When Liquor Max is active, Name can update all products, only non-liquor products, or no existing products. All connectors default to Non Liquor Products so Liquor Max names remain intact while ordinary product names continue updating from the POS. A POS-owned name change also updates the public URL during product follow-up and creates a redirect from the previous URL.

Missing Categories has the same Non Liquor Products scope when Liquor Max is active. It creates categories for POS categories marked Excluded from LiquorMax. Applying an individually excluded product also creates and assigns its POS categories under this scope; liquor products retain the taxonomy supplied by the Central catalogue. All connectors with Liquor Max active use this scope by default. Enable Categories defaults to on; turn it off to stop importing and assigning POS categories. Intentionally unlinked categories that are outside the selected creation scope are not counted under Needs Attention. This is separate from archiving a POS category, which excludes its products from synchronization entirely.

On Connector Sync > Products (for example, KORONA Sync > Products), use Exclude from Liquor Max to exclude an individual product while keeping ordinary POS product updates enabled. The Liquor Max column shows individual and primary POS category policy. Apply can use an eligible associated category when the primary is archived or deleted, so its policy can differ. Use the Liquor Max exclusion filter to list products excluded individually; category-only exclusions remain in Not excluded individually. Applying an exclusion clears the linked product's liquor flags, beverage attributes, and beverage category assignment, resets obsolete Central sync errors, and prevents Central enrichment. Ordinary manual category assignments follow the category update rules; product apply assigns the POS category when allowed. If the POS category resolves to a Liquor Max beverage category, it is skipped for an excluded product, including associated categories. Without an ordinary category assignment, the product remains uncategorized. Existing beverage associations also clear when category sync is disabled, set to Don’t change, or blocked by an unresolved POS hierarchy; ordinary manual associations remain. Beverage category assignments clear even when the POS hierarchy is unresolved. A featured image marked as imported from Central is detached, while manual replacements are preserved. When apply restores the POS name, catalogue follow-up refreshes its URL slug and redirects the old link. The setting persists across full and delta imports. Linked catalogue products receive search and catalogue follow-up updates even when ordinary POS product sync is disabled. If exclusion changes the product URL, its previous beverage URL redirects to the new URL. Remove Liquor Max Exclusion restores the category-derived policy; a category exclusion continues to apply. If ordinary POS product sync is disabled, removing the individual exclusion saves the policy but leaves catalogue liquor flags disabled until product sync is enabled and applied. Existing drafts retain their visibility during ordinary POS updates on other connectors, or when KORONA’s Visibility > Follow new product rules toggle is off or inactive under the Draft new-product rule. With that toggle on and new-product Visibility set to Public or Draft if No Liquor Data, the selected new-product rule applies, while completed Liquor Max enrichment and zero-price protection are respected.

Products configured to use Liquor Max are still created when their POS record has no usable GTIN. CMS Max skips Central enrichment for those products and lists them in the missing-liquor-data dashboard until a GTIN is supplied or Liquor Max is disabled for the product.

Products excluded from Liquor Max individually or through their POS category do not show the Liquor Max tab in the product editor. Remove the exclusion in POS Sync to restore the controls. Central Sync shows Not applicable for these products in the Products table, and Sync to Central Yes/No filters omit them. Products that are eligible but have no liquor data keep the tab. Excluded products retain their ordinary primary category editor and general AI image action even when saved liquor data remains. Central image searches and suggestions are unavailable while excluded. Bulk edits skip their liquor fields, and missing-liquor-data warnings omit them. Removing or deactivating the POS connector releases its retained exclusion policies. Image generation queued before exclusion is skipped with an admin warning; an image already generated is retained without being applied.

Under Sync Rules > Name Formatting, Title Case Product Names and Title Case Category Names independently convert imported names such as RED WINE to Red Wine when creating website records. Both rules default to on for new and existing connections without a saved preference. Explicitly saved off choices remain off. Pending name-formatting work applies to unchanged fetched records during catalog sync without requiring a settings save. Work waits for any active sync to finish and is prepared by the background sync monitor. Formatting changes update only eligible names; they preserve stock reduced by website sales, other product fields and existing sync errors. Save and sync to apply a later change to fetched records, including categories without products. Saving a preference for the first time reapplies existing records even when selecting off. Existing product names follow the Name update rule, and existing category names follow Linked Category Details. RICS grouped products use title casing on creation; later syncs preserve their manually managed names. Custom category name overrides retain their exact casing. Category matching checks both the POS name (or your custom override) and its formatted version under the same parent, so formatting units or pack sizes does not create a duplicate of an existing category. Multiple matches require an explicit CMS Max category link. Categories beneath a deleted POS ancestor remain archived, with formatting work dormant until the ancestor is restored. Imported POS names remain unchanged. Title casing capitalizes words while preserving beverage abbreviations such as IPA, VSOP, XO, USA, CBD and THC, Roman numerals, pack markers such as 12PK, and bottle units such as 750ml and 1.75L. All-uppercase O’/O' and Mc names keep their prefixes, such as O'Doul's and McCormick. Only all-uppercase names are formatted. Names containing any lowercase letters keep their complete original casing, including mixed-case names such as McCormick VODKA and bLoyal Product. Liquor Max Central title updates remain independently controlled by Central synchronization.

New Product Rules > Visibility defaults to Draft for every connector, with or without Liquor Max, unless another visibility rule has been saved. Select Public to publish new products immediately, or Draft if No Liquor Data to publish after Liquor Max enrichment. With Draft if No Liquor Data, new POS products that use Liquor Max start as drafts while Central enrichment runs. Products that receive beverage data become public. Configure POS category exclusions before the first product import so non-liquor products start public. Newly imported products in POS categories excluded from Liquor Max use Public. If you exclude a category after its products were imported as drafts, a later KORONA product sync makes its eligible positive-price products Public under this conditional rule when Visibility > Follow new product rules is on. With that toggle off, or on other connectors, those existing drafts retain their visibility; publish them from Products if they should be visible. Products still using Liquor Max without beverage data remain Draft under the conditional rule. Completed enrichment keeps eligible positive-price KORONA products Public on subsequent product syncs, including under the Draft new-product rule, where visibility-follow is inactive. If Liquor Max is turned off, the saved conditional choice remains available in settings, and new products using it use Public instead.

New Product Rules > Crawl Setting shows when Visibility is Public or Draft if No Liquor Data and chooses Crawl (the default) or Don't Crawl for the products the POS creates. With Draft, the setting is hidden and new products use Crawl, including drafts that Liquor Max enrichment publishes. Saving with Draft replaces a Don't Crawl saved earlier with Crawl. Once one of those drafts is public, whether you publish it or Liquor Max enrichment does, set Don't Crawl on the product or with Quick Change if search engines shouldn't index it. For KORONA, the two Follow new product rules toggles are hidden and inactive under Draft, preserving existing manual visibility and Crawl choices. Their saved choices return when Visibility changes to Public or Draft if No Liquor Data. Under those rules, each enabled toggle applies its creation default on existing-product sync, replacing manual Public, Draft, Crawl or Don’t Crawl choices. Visibility following preserves Users-only and Password Protected access. If zero price drafts a protected product, price recovery leaves it Draft until you restore its intended visibility in Products; explicitly choosing Public permits future visibility following. Crawl following remains independent. Publication changes schedule the normal throttled sitemap update on eligible sites. With Public selected, positive-price drafts become Public, including products previously drafted at zero price. Turn the corresponding toggle off to preserve manual visibility or crawl choices. Existing connections keep both toggles off unless enabled. Other connectors retain existing values. To change them, edit a product or select products in Ecommerce > Products > Quick Change and choose Make Public, Make Draft, Crawl, or Don't Crawl. Ordinary POS updates preserve those manual choices unless the corresponding KORONA follow toggle is enabled and new-product Visibility is Public or Draft if No Liquor Data. The zero-price draft safeguard and Liquor Max enrichment still apply. A public product set to Don't Crawl asks search engines not to index it and is left out of site search, product search results and llms.txt, and out of the sitemap according to the normal sitemap update lifecycle. It still shows on category and brand product lists and opens from its link. Admin lists and Publish Settings show it as Unlisted.

POS product creation and updates keep products with a zero price as drafts. A product drafted from Users-only or Password Protected access stays Draft after price recovery until you restore its intended visibility in Products. On KORONA with Visibility > Follow new product rules on, a later positive price publishes an eligible existing Draft when the rule is Public, or when the conditional rule and completed Liquor Max enrichment permit publication. With the toggle off or inactive under Draft, or on other connectors, a positive price alone preserves Draft; publish it from Products if it should be visible.

For native Counterpoint, the default price mapping uses REG_PRC and falls back to PRC_1 when the regular price is missing or zero and Price 1 is positive. A custom mapping with no positive fallback retains a zero price.

Under Product Mappings > Counterpoint sale pricing, Mapped sale fields uses the ordinary Sale Price, Sale Starts At and Sale Ends At mappings. It is the default for existing connections. Choose Ordered sale rules to combine ongoing discounts with dated promotions. Add rules in priority order, select each price field, and optionally require a matching source value or a start/end date range. The first currently eligible positive price below the mapped regular price wins; this is not a lowest-price comparison. A date-range rule with missing, invalid, reversed or expired dates is skipped. Date-only and midnight end dates include the whole final day in the site's timezone. The result is previewed for the selected sample product.

Load profile sale example prepares an unsaved dated promotion from PROF_NO_2, PROF_DAT_2 and PROF_DAT_3, followed by an ongoing sale from PROF_NO_1. Confirm these merchant-defined fields with the installer before saving. No slot universally means sale, ad price or after-rebate price. Do not map an after-rebate cost as the checkout price.

Ordered rules require at least one rule. Applying them replaces manually entered sales on linked products and clears the sale when no rule qualifies. They replace all three ordinary sale mappings, but still obey Sale Price and Dates > Don't change for existing products. Saving rule changes marks cached products for application without requiring another full fetch. Later product syncs reconsider cached records when a sale-rule start or end is due, even if the POS record has not changed, and fall back to the next eligible rule or regular price. This makes no extra per-product POS requests. Inventory-only sync does not process these transitions. The selected promotion's saved end date prevents it remaining active after expiry even if the next product sync is delayed.

Switching back to Mapped sale fields replaces previously applied rule-managed sales with the configured sale mappings. If a replacement mapping is absent, its old rule-managed sale price or dates are cleared on the next apply. This cleanup applies only to the CMS Max product that received the rule-managed sale; relinking to another product does not clear that product's manual sale. Existing manual sales that rules never applied are preserved. Sale Price and Dates > Don't change still prevents changes to existing products. Applying a re-enabled product also records its next promotion start or end, even if it was disabled when the rules were first configured.

Native NCR Counterpoint provides an Existing Product Rules > Images control, independently of product-field mappings. It is disabled by default. Choose Sync to enable image sync. When enabled, the separate image schedules download the item's primary Counterpoint image as the featured image and add its alternate images to the gallery in the background. For condition-suffixed item numbers with no exact images, CMS Max also checks matching images under the base model number. If the current featured image was uploaded separately but has the same filename and byte size as Counterpoint, it is reused rather than uploaded again. Later filename scans add, rename, or remove images previously imported from Counterpoint while preserving unrelated CMS Max gallery images. Scans keep the saved gallery order, append new alternates, and keep a replacement image in the same slot when its filename is unchanged. Full content verification also detects an image replaced without changing its filename. Counterpoint stores images separately from item records, so product imports do not download images or wait for image processing.

With image sync enabled and products applied, use Sync Images on the POS Sync Dashboard to start a manual filename scan. Its dropdown offers Full Image Verification for checking whether existing files changed without being renamed. The first scan may download many files; run it when the POS is quiet. Both actions process images in the background, with results shown in recent activity.

If Counterpoint rejects a slash-containing item number with a plain routing 404, the image scan skips that item and records a warning in recent activity. Existing images are preserved. CMS Max does not remove the slash or substitute another SKU to find images.

To publish existing draft categories, open Ecommerce > Categories, select the categories, and choose Make Public. Make Draft hides selected categories again. These actions leave product visibility unchanged. The POS Category Rules visibility setting applies to newly created categories.

On POS Sync > Categories, an active row with an empty CMS Max Category selector offers Create & link category. Confirm to create or reuse its CMS Max category using the POS storefront name and hierarchy, including missing parents up to an existing link. Existing category details and descendant links are preserved; descendant categories are not created by this action. Ambiguous matches or categories owned by another POS row show an error. The action leaves automatic creation settings unchanged and can create the selected category when automatic creation is disabled. With Missing Categories > Non Liquor Products and Liquor Max active, the action is disabled with an explanation until the selected group is excluded from Liquor Max or the setting changes. Excluded groups cannot use beverage categories or beverage parents, including when exclusion is inherited while recovering a source-deleted category link. Unresolved, missing or cyclic POS parents must be corrected before creating the link. Newly created categories use the saved category visibility. The link follows normal automatic category rules and shows Linked; selecting a category from the dropdown creates a Manually linked override instead. Affected products in the selected group and its children, plus direct products of any newly linked parents, are marked pending before queue publication and queued to apply the saved category assignment rules. If publication fails, use Apply Fetched Products & Categories to Site to retry the saved work. Previously synced products retain redirects from their former URLs when applying the link changes their category paths. Existing inventory warnings remain visible. The action is unavailable for archived or source-deleted groups and while catalog changes are blocked by a sync or settings update.

Imported products, categories, and brands can be linked to a different CMS Max record from the imported catalog pages. Archived product rows, archived or source-deleted category rows, and source-deleted brand rows have a red background when shown. POS Sync > Categories defaults Archive Status to Active, hiding website-archived categories and categories deleted in the POS. Choose Archived or clear this filter to All POS categories to inspect them. POS Sync > Brands defaults Brand Status to Active in POS; choose Deleted in POS or clear it to All to inspect source-deleted brands. Source-present brands linked to archived CMS Max brands remain visible. Needs Attention on Products, Categories and Brands opens without the active-only status default, so deletion errors remain visible. The Products badge also includes errors on archived imported products. Opening that tab clears an active-only selection while retaining other filters; explicit status choices in its URL or made on that tab remain effective. In an RMH hierarchy, a department is the parent and a category is its child. The Categories list sorts names alphabetically at each level while keeping children beneath their parent. Filter categories by type to show only departments, or select a department to inspect its categories. The Products column includes products anywhere beneath that hierarchy level, while Direct Products includes only products assigned exactly there. Each shows active (archived/deleted), with separate links on both numbers. For KORONA, active means not reported deleted in KORONA, including website-only exclusions; brackets show products reported deleted in KORONA. For other connectors, the split uses the imported records' local archive status. For example, 0 (182) means no active products and 182 retained historical records. The column headers explain the category scope and the active/history count format. Counts reflect imported data, not a live POS lookup. Select a brand product count to open the Products page filtered to that brand, including archived products. Liquor Max policy confirmations use those same totals. Excluding a POS category archives its imported child categories and affected imported products after confirmation. When a category is deleted in the POS, the sync archives its CMS Max category. If products are still assigned to that category or its subcategories, for example ones added in CMS Max, it stays, and the POS category shows Error under Connector Sync > Categories and on its Needs Attention tab. Hover its Active icon, or turn on the Error column, to see the reason. Move or remove those products and the next sync archives it.

POS names: Product edit pages, Products tables, admin order details, coupon matching-product previews, and the connector's imported product table use the same POS-name display. Product names apply a saved Name mapping to the fields from the latest import, including combined and fallback paths. Without a saved mapping, the display uses the normalized imported name. RICS family names also follow the current colour-title option, so matching colour suffixes stay gray and mapping or colour-option changes appear without another import. The display shows the connector and name, for example RMH Name: CARAVELLA LEMONCELLO 750, with no difference-message badge. Matching names remain visible in gray; a name that differs from the saved website title is highlighted, including differences in capitalization. Category and brand lists and edit forms use the same display for their imported names; shared categories compare against their effective website link. Empty names and source-deleted or archived source records are omitted from website views. The imported catalog's Imported name mismatch filter compares stored imported names with linked, non-archived website names. The POS-name label is internal admin information. It does not appear on storefront pages, checkout, customer order pages, customer emails, or printable invoices. Admin order details show the current linked POS name beneath the saved order-item name; they do not replace the name recorded when the order was placed. This information does not change either name or override sync rules, and viewing it never requests live POS data.

For KORONA, CMS Max imports the complete Commodity Group ancestry and assigns each product to its leaf group. Subsequent runs request only products and Commodity Groups newer than their saved revisions; groups deleted from KORONA are returned as inactive and archived in CMS Max. The mapping screen describes the automatic KORONA behavior while retaining its editable source paths: Automatic GTIN from Product Codes scans the available product codes for a recognizable GTIN, and Current Price from Selected Price Group selects the newest price in the configured Price Group whose start date has arrived. If a different field is required, save a custom mapping. From an imported KORONA product's action menu, select Open in KORONA to edit that source record in KORONA Studio.

KORONA scheduled prices update the CMS Max regular price. CMS Max does not infer a sale from an older price or automatically translate KORONA promotions, because the product price timeline does not identify a reliable regular-price/sale-price pair. Sale Price and Dates defaults to Sync for every connector. Existing sale prices and dates remain unchanged when those fields have no mappings. A mapped sale date without a time starts at 12:00 AM, and a mapped sale end date without a time lasts until 11:59:59 PM, in the store's timezone; a date that includes a timezone is used exactly as given. Configure intentional custom mappings to import sale values; select Don't change to preserve CMS Max-managed sales even when sale mappings exist.

CMS Max uses the first recognizable UPC/EAN/GTIN from KORONA's product-code list rather than assuming the first code is a barcode. When using POS inventory, a KORONA product with Track Inventory disabled remains untracked and sellable in CMS Max if Honour KORONA Track Inventory is on (the default), even when the selected location returns a zero stock record. Turning the preference off imports that product as tracked with zero stock instead; Do Not Track Stock still takes precedence. KORONA typed descriptions are not copied into CMS content by default, and KORONA's Listed and Sales Lock flags are not treated as website visibility controls; use explicit mappings for supported fields and manage website visibility in CMS Max.

KORONA sectors and sales-tax rates do not correspond to TaxJar product tax-category codes. During onboarding, configure CMS Max's default tax behavior and assign any exempt or specially categorized products in CMS Max. A KORONA sector named “Tax Free” is not automatically trusted as a CMS Max exemption.

After fetching Counterpoint products, use Discovered category codes on Category Mappings to open Connector Sync > Categories. This list identifies profile codes and standard item-category fallback codes separately. For placeholder names, use Set storefront name. To combine codes that truly mean the same thing, select the same CMS Max Category for both; the second link is shown as Shared category and cannot overwrite the category name. Archiving a POS category also excludes its products, so do not use Archive just to hide a label.

With Category source set to Fields on each product, Counterpoint keeps the mapped appliance type as the product's primary category and adds its additional profile category separately. For example, a dryer can belong to both Electric Dryers and Scratch & Dent. With Category Assignment set to Sync, every apply makes additional categories linked to any imported POS category follow the product's profile fields. If those fields do not assign a linked category, it is removed on the next apply, even if you added it by hand and nothing changed in Counterpoint. For example, manually cross-listing a dryer in a POS-linked Washers category will not persist. Because routine Sync performs a complete daily audit, this reaches every product, not only products that changed in Counterpoint. Additional categories with no POS link that no earlier apply assigned, such as a CMS Max-only Deals category, are preserved. If you link a POS category to a different CMS Max category, the next apply moves its products from the old category to the new one. Counterpoint categories updates the primary category without changing additional assignments.

If you archive a POS-linked additional category in eCommerce > Categories, its assignment is removed when the product is applied. Restoring that CMS Max category does not mark its products for another apply. A routine Sync restores the assignments right away only for the products it applies, such as products whose POS data changed; the rest are restored by the next routine Sync after the daily complete audit is due. To restore all of them immediately, open eCommerce > Connector Sync > Dashboard, open More sync options, choose Re-fetch All Products, Categories & Inventory, then confirm Re-fetch Everything. The label includes Brands when enabled and omits disabled components. This differs from Connector Sync > Categories > Restore, which automatically queues affected products for application. Archived CMS Max-only extras retain their assignments and become visible again when restored.

Without a mapped primary category, a condition stays additional rather than becoming primary; clearing that condition removes the additional association on the next application. A condition cannot keep a product active when its appliance category is archived or deleted in the POS. If a configured primary category cannot be resolved, the product retains its category error even when an additional condition can be assigned. Correct the primary category mapping and apply again to clear the error. These assignments follow the mapped source fields, not SKU suffixes.

Applying pending fetched products updates these associations without another POS fetch. Products that were already applied are repaired by the next routine Sync after the daily complete audit is due. To repair them immediately, open eCommerce > Connector Sync > Dashboard, open More sync options, choose Re-fetch All Products, Categories & Inventory, then confirm Re-fetch Everything. The action label includes Brands when brand syncing is enabled and omits disabled components. Don't change for category updates preserves existing additional assignments and normally preserves an existing primary category. An explicit POS-to-CMS category link can still replace the primary, and a mapped category can fill an empty primary. Disabling category synchronization prevents these assignments. Category visibility remains separately controlled.

Run a sync

Open eCommerce > Connector Sync > Dashboard and select the main Sync button for routine use. Its label lists Products, Inventory, and Categories or Brands when enabled, for example Sync Products, Categories & Inventory. This fetches available POS changes, applies them to CMS Max, updates inventory, and performs any required follow-up work. Categories and brands run with products because their changes can affect product assignments.

The Products, Categories, and Brands pages also provide the same Settings link and Sync dropdown, including More sync options.

Native Counterpoint routine syncs request only items and location inventory changed since the last safely completed boundary, with a fifteen-minute overlap. CMS Max performs a complete daily audit and does not advance either boundary when a run fails. KORONA routine product, Commodity Group, and inventory syncs request only records newer than the last successfully imported revision. Inventory keeps a separate revision for every warehouse location so single-location and combined-location stock remain accurate. No acknowledgement is sent to either native Counterpoint or KORONA. If a request fails before all pages are safely applied, CMS Max keeps the previous cursor or revision and safely replays the records on the next attempt. Each routine KORONA sync also re-evaluates already-stored scheduled prices, so a future KORONA price becomes active after its start time even when merely reaching that time does not create another product revision.

When the POS reports that a product has been deleted, the next product sync archives its linked CMS Max product. If the POS later returns that product, CMS Max restores the same linked product unless it was manually excluded from synchronization.

Manage KORONA product deletion and restoration in KORONA, then run Sync. CMS Max archive controls create website-only exclusions and do not change KORONA. CMS Max blocks restoring a product already known to be deleted in KORONA. Routine syncs also archive stale restored records that still carry that source-deleted state, without requiring a newer KORONA revision. Restoring a website-only exclusion for a product still present in KORONA remains available.

The More sync options menu also provides narrower maintenance operations:

  • Fetch Changes to Products & Categories from [POS] Only downloads POS changes without applying them. Before the first import, its label is Fetch All Products & Categories from [POS]. These examples assume category syncing is enabled. The labels omit categories when disabled and include brands when brand syncing is enabled.
  • Apply Fetched Products & Categories to Site applies previously fetched changes and appears only when work is waiting. Its label omits categories when disabled and includes brands when brand syncing is enabled.
  • Sync Inventory from [POS] refreshes inventory without running a product import.
  • Re-fetch All Products, Categories & Inventory performs a complete re-import and should be reserved for recovery or configuration changes that require every record to be reconsidered. Its label omits categories when disabled and includes brands when brand syncing is enabled.

Do not start another sync while saved settings have changed. Save the settings first so the run uses the values shown on screen.

Monitor a sync

Connector settings show POS sync progress only while a fetch or sync is active, with the current stage, product counts, elapsed time, and connector page or inventory batch details when available. The display refreshes automatically and disappears when the run completes, fails, or is cancelled. Percentages appear only when the dashboard has an expected total. Product and beverage update stages can show an approximate time remaining once enough processing samples exist; this estimate applies to the current stage, not the entire sync.

The dashboard shows the current or latest run in ordered stages: fetching from the POS, updating products, updating beverage data when Liquor Max is active, and product follow-up. It shows counts where the work size is known, including processed and total products during follow-up URL and search updates. Follow-up identifies preparation and category URL refreshes before product updates, then cache clearing and category counts. These phases remain visibly active without a percentage. Where no reliable total exists, the stage moves without showing a misleading percentage or completion estimate. Narrow operations such as Fetch products retain the full stage layout but mark stages that are outside that operation as Not included. A completion notification appears when an active run finishes while the dashboard is open.

While inventory is being synchronized, the dashboard also shows whether CMS Max is requesting inventory, updating linked product stock, confirming receipt with the POS, verifying an uncertain confirmation, or checking for another page. These steps include the inventory batch number and may repeat when the POS returns inventory in more than one page. The total number of batches is not known in advance, but an increasing batch number confirms that processing is continuing. Native Counterpoint additionally shows the current inventory location, its position in the selected location list, and the API page being requested. bLoyal feeds require an acknowledgement for each batch; if that response is lost, CMS Max checks whether the feed advanced before retrying. Native Counterpoint and KORONA advance their saved cursor only after the returned inventory has been applied and require no acknowledgement.

Native Counterpoint product fetches also show the current company product or location-pricing page. Counterpoint does not report a total page count, so the increasing page number confirms that a long initial fetch is continuing without presenting an unreliable percentage.

If the POS is not ready to provide another data sync, the current run shows Waiting for POS and the time until CMS Max tries again. The sync resumes automatically from its unfinished step, so completed product fetching is not repeated; no manual action is required.

For RICS Products with size and width variations, inventory progress shows received rows, the provider total and completed pages as data arrives, including quota waits and resumed runs. An inconsistent catalog is rejected before applying products. CMS Max records diagnostics and makes one controlled fresh catalog attempt; another rejection follows normal error reporting. Existing product and variation links are preserved.

Temporary POS request failures appear as a warning on the active run. The warning shows how many requests have failed, confirms that CMS Max is continuing to retry, and includes a short description of the latest issue. An inventory warning clears after the POS accepts the affected batch. These request failures do not mean the overall sync has failed.

For KORONA, temporary connection failures, service failures, and rate limits retry automatically. A daily API limit waits for the normal queued retry rather than holding a worker open. Authentication, permission, missing-account, and other permanent failures appear with a safe action-oriented message in the sync activity.

Use Recent Runs for daily summaries in the site's timezone. Each day shows counts by sync type, its latest activity, and any active runs, cancellations or runs needing attention. Full product fetches are counted separately from other product syncs. Days follow when each run was queued, including runs that finish after midnight. Expand a day to see individual runs and open their details; View more runs loads another six within that day, while View more days shows older daily summaries. Choose All types or a specific run type to filter both the daily counts and the individual runs. Select the runs needing attention button beside a day to see its affected runs, even when newer syncs succeeded. The rows show the recorded sync error or the number of sync failures or failed beverage data checks. Select a run for details, or Show all runs to return to the full day. The Products Needing Attention card counts non-archived POS products with a current sync error. Products or categories that could not be matched or updated appear under Connector Sync > Products > Needs Attention with the recorded reason.

Open the products processed during a run and select View Changes to compare every captured CMS Max product value before and after that sync. Price and sale-price changes are displayed as currency. Newly created products are recorded without repeating all of their initial values, so they do not show this action. Older events created before change tracking was introduced continue to show their changed field names but do not have a before-and-after comparison.

See a product's POS data

When a product is linked to a POS product, its edit page shows the connector name, for example KORONA Name: …, beside Product Name. The hint applies the current Name mapping to the saved POS fields from the latest import, including combined fields and fallback paths. For example, mapping Name and UnitOfMeasure shows both values joined by a space. The hint is highlighted when this mapped name differs from the website name, including capitalization, without adding a separate difference message. If no mapped value is available, the hint uses the stored imported name.

Select Product Source to list every field saved from the POS for that product, with the value from the latest import, in a scrolling box. With Liquor Max active, the button is in the header of the Liquor Max section on the Liquor Max tab, beside Sync from Central when the product has a GTIN. Without Liquor Max, it is at the top of the page. Fields CMS Max adds during the sync and sensitive values such as keys and passwords are not listed. Each tab has a fixed-height scrolling area that fits the screen, keeping the tabs available above the field list.

Saved POS stock shows the stock quantity currently saved from the POS, and CMS Max stock shows the linked website product's saved quantity. These values are separate from the raw source fields and remain visible when that payload is empty. Zero is shown explicitly; a linked product with stock tracking off shows Unlimited, a tracked product with no saved quantity shows Not set, and an unlinked POS record shows Not linked for CMS Max stock. The same stock summary appears in the POS product Record action and the central product's tenant View data action.

The fields are split into three tabs. Mapped Fields lists the fields the import reads, with the product field or tag group each one feeds under Maps To; a field read only when the main field is empty shows (fallback). That covers your POS Sync product mappings, Brand Mapping while brands are on, and Tag Mappings while product tags are on. SKU, GTIN, name, price and, for some POS systems, quantity use the POS system's default fields until you map them; every other product field is read only after you map it. Unmapped Fields lists the other populated fields. Empty fields contains fields sent as null, empty text, or an empty list. Zero, false, and the literal text "null" remain in the populated tabs. The modal opens on Mapped Fields, then Unmapped Fields if no populated fields are mapped, or Empty fields if all saved fields are empty. For RMH and NCR through bLoyal, the POS's on-sale flag sets the sale price from Price, replacing your Sale Price, Sale Starts At and Sale Ends At mappings; when the POS marks a product not on sale, all three are cleared. The sale runs from 12:00 AM on the product's bLoyal sale Start Date to 11:59:59 PM on its End Date, in the store's timezone; the record shows these dates as SaleStartLocal and SaleEndLocal. If bLoyal can't supply current sale dates, the sale is held for 26 hours and renewed by every successful sync while bLoyal still reports it. bLoyal doesn't report a product when a scheduled sale starts or ends on its own, so the first scheduled product sync after 12:15 AM store time each day re-fetches the whole catalog (a schedule that never runs after 12:15 AM, such as a daily 12:05 AM sync, re-fetches on its next run). It is skipped when a full re-fetch has already run that day, and doesn't run while scheduled product syncs are off. On Product Mappings, the Sale Price row shows the dates the sample product's sale runs. The tabs don't show this.

Under Connector Sync > Products (for example, KORONA Sync > Products), the product Record action (for example, RMH Record) shows the same Mapped Fields, Unmapped Fields, and Empty fields tabs. The Record popup beside a sample product in the plugin mapping settings uses this same view; Maps To reflects the saved product and tag mappings. This also works for POS products that are not linked to a CMS Max product or are archived.

On the central product and pending update pages, each store in Tenant Prices shows POS Name: … under the store name when its product is linked to a POS product, so you can compare what each store's POS calls the item. Suspicious Pricing lists each store on its own line with its price and POS Name lines from the last scan; click Refresh there to update them. Select View data beside a store to open that tenant product's saved POS fields with the same mapped, unmapped, and empty-field tabs, using the tenant's mappings. Select the tenant name or price to open its product editor. Products without an active POS source show an availability message. A product whose store unchecked Sync with Liquor Max Central Database remains visible in Tenant Prices with an Unsynced badge. Its price, edit link and View data remain available. POS-linked products with Central sync unchecked are excluded from the other Central store lists; checking the box again and saving lists them again. POS syncs keep an unchecked product unchecked.

The Tenant Prices list on product and pending update edit pages includes all matching, non-archived products. Its Unsynced badge reports Central sync status, whether the product was added by hand, excluded from Liquor Max or explicitly opted out. The header counts products and distinct tenants, including unsynced matches. This differs from the Tenant Prices comparison on Duplicate Products, which omits POS-linked products with Central sync unchecked, and the Tenant Prices column on Suspicious Pricing, which includes only synced products.

Each row in the edit page's Tenant Prices also shows the store product's GTIN beneath the name. On the central beverage product edit page, its badge color matches the corresponding GTINs label above the table, so you can compare prices for each code. Codes that differ only by leading zeros share a color. Select the copy button beside a GTIN above the table to copy it. The full code remains visible on mobile.

On Central's Suspicious Products list, the POS Product column, next to Central Product, shows each store's linked name and price above its POS product names, two stores side by side per line. A store with several products matching the central product lists each POS name. A store whose products aren't linked to a POS product shows No POS product, and POS name unavailable means the store's POS names couldn't be read this time; reload the page to try again.

The Assigned Bottle Size dropdown saves immediately and queues the product for tenant sync. Choosing a size, including through Suggested or bulk Apply Suggested Sizes, also copies its configured shipping weight, width, height and length to the central product; unconfigured measurements and clearing the size leave existing measurements unchanged. The size and non-null measurements sync to GTIN-matched tenant products that have central sync enabled. Its current size is first, followed by the title-derived Suggested size. Unassigned products show None selected, with the suggestion first in the options; opening the dropdown does not assign a size. Search for another size or clear the selection as needed. Products without a beverage type show Set beverage type first. instead of the dropdown. Set the beverage type in the central product editor to enable bottle-size editing. The bulk Apply Suggested Sizes action applies suggestions to selected products.

The POS name and Product Source appear only while a POS connector is active and the product is linked to a POS product. They are hidden once the POS reports the item deleted, and while the product's POS record shows as Archived under Connector Sync > Products (for example, KORONA Sync > Products), for example after the product is archived in CMS Max.

Schedule automatic updates

Open Settings > Automation to configure two schedules:

  • Product Updates (includes inventory) processes product changes and refreshes inventory. Choose a frequency that fits the POS provider's request allowance and how quickly catalogue changes need to appear.
  • Sync Inventory Only refreshes stock without processing the product catalog. It is quick, so run it more often than the product updates to keep website stock current. Turn this off if the product update schedule refreshes stock often enough.

Each schedule can run at an interval or at a chosen time daily, on selected weekdays, or on a chosen day each month. A monthly date that does not exist in a shorter month runs on that month's last day. Schedules use the site's configured timezone. Daily and weekly syncs run at most once per local day, including when daylight saving time repeats an hour. The dashboard shows when each automatic run is due next.

Next Expected Run previews the schedule you are editing. Saving a changed schedule resets its previous dispatch history. A first image scan that missed its initial scheduled time shows Due now and catches up when the scheduler can run it.

For native NCR Counterpoint, Image Filename Scan defaults to a daily midnight run. It scans linked imported products in bounded batches, compares the available filenames, and downloads only new or renamed files. Verify Existing Image Contents defaults to Sunday at 2:00 AM. It first checks response validators or Counterpoint's file size and modification date using a one-byte request. The complete image is downloaded only when that metadata changes or the server provides no reliable metadata, in which case CMS Max compares the downloaded contents. Configure content verification for a quiet period at the store.

Recover from a problem

  1. Open the failed run on the dashboard and review its summary.
  2. Resolve any credential, mapping, or matching issue shown under Needs Attention.
  3. Run the main Sync action again. Successfully completed records are not duplicated.
  4. Use Re-fetch All Products, Categories & Inventory only when a complete source re-import is required.

Contact CMS Max support before clearing imported data on a production site.

If records have been deleted and recreated in your POS, a full re-fetch can reconnect replacement products to existing website products when their synchronization SKU uniquely matches and the POS has confirmed the old record deleted. Automatically managed categories and departments can be reused when their name and website parent match uniquely. Saved update rules still control website content and visibility. Website exclusions, explicit category links, active owners and ambiguous matches remain protected; review unresolved matches in Needs Attention. RICS grouped products keep their separate product and size-linking workflow.

Reconnected products retain their individual Liquor Max exclusions. Recreated categories retain their explicit and inherited Liquor Max exclusions. Replacement products cannot take over website products protected by a category exclusion. Prior POS-managed brands and accessory options are reconciled against the replacement's values under your saved update rules. When a POS-owned name change updates an established product's website address, the previous address redirects to it. Category matching uses storefront-name overrides when present. Active website category matches take precedence over archived recovery candidates. An archived category is reused only when one candidate passes all recovery checks; otherwise normal sync creates a category. Exclusions from an associated fallback category apply on the first sync, including when category management is disabled.

RMH FTP tiered pricing

In RMH → Credentials, turn on Advanced, then Allow FTP tiered pricing. Enter the FTP host, port, username, password, remote directory, and CSV filename. The connection uses FTP with explicit TLS (FTPES). Leave Verify TLS certificate on unless the server requires a self-signed certificate. Passwords are saved encrypted and remain masked in the form.

Choose the import days and time in your site timezone. Automatic imports run at most once per scheduled local date, including when daylight saving time repeats an hour. The default is Thursday at 02:00; select every day for daily imports. A blank CSV filename selects the last CSV filename in natural sort order in the remote directory. For daily exports, schedule the import after publication in your site timezone. Save before the scheduled import runs. If scheduling is briefly delayed, an import can start up to 10 minutes late; after that, it waits for the next scheduled time. Enabling imports or saving a schedule whose time was within the last 10 minutes can start an import immediately.

The CSV matches item lookup codes to product GTINs and supplies up to four quantity/price pairs. Each import replaces tiers on matching products. The first zero quantity ends the tier list; a zero first quantity removes the product’s tiers. Unmatched products remain unchanged. Normal product prices are not updated. Imported tiers store the difference between the CSV base price and CSV tier price as a fixed discount. For example, CSV base $15.99 and tier $14.99 store a $1 discount, even if the website base price differs. The website applies that discount to its current normal price; active local or global sales override tier pricing.

Files are limited to 10 MiB and 50,000 product rows. Invalid prices (including zero-priced active tiers), incomplete rows, or duplicate/decreasing tier quantities skip that product and preserve its existing tiers, while valid products import. Skipped rows are logged for the CMS Max support team and are not displayed in the admin panel. Contact support if a product’s tiers do not update. Scheduled imports keep valid product updates without repeating the import for skipped rows; transfer failures and rejected whole files are retried. File-size/row-limit errors and a missing header reject the whole file before any writes. SQL export footer lines are ignored; eight NULL tier fields explicitly mean no tiers. Reimporting an identical file preserves the same discount amounts.

Turning off Allow FTP tiered pricing stops imports and keeps the saved connection details and existing product tiers.