Catalog Synchronization

When SolaStock is connected to SolaCount, the items, units and categories you create or change in SolaStock are sent to SolaCount automatically, so both apps talk about the same products. Catalog synchronization is the page that shows the progress of that delivery, record by record, and lets an administrator retry a record that is stuck.

It deals with the catalog only. It never changes quantities, stock value or the prices you hold locally: the page says so itself - "Items and reference data sync without changing quantities or local prices."

Typical users: owners, SolaStock Administrators and integration managers; the accountant when a product is missing in SolaCount.

Where to find it

The breadcrumb reads SolaCount connection → Catalog synchronization; the first part leads back to the connection page. The page needs the permission Manage integration mappings & settings (owners and SolaStock Administrators). Without it the button on the events page is not shown and opening the address shows Access denied.

It is useful only for an organization with an active SolaCount connection. Without one, or while the connection is paused, a retry is refused (catalog connection paused).

Screen tour

Title Catalog synchronization, then one panel with a table:

Empty: Catalog is up to date - "New and changed catalog records appear here after saving." If the list cannot be loaded: Could not load synchronization status - "Delivery is pending. Retry when the connection is available."

After Retry synchronization: "Synchronization queued". A refusal shows the reason as a toast.

Statuses and what to do

Action needed

What is sent

• Items with their SKU, name, item type, unit, category, tracking setup, costing method (the organization-wide fallback is captured with the record), the availability flags (Available for sale, Available for purchase) and the default Consumption expense account.
• Units and categories they depend on.
• Non-stock items and services may be sent without an inventory unit: only an item of type Inventory needs a unit to be delivered.
• If the inventory-tracking flag of an item disagrees with its type, the type wins and the stale flag is left alone, so a simple name change never rewrites accounting settings.

Nothing here posts stock, changes stock value or creates a journal.

Notifications

When a record needs a person, integration administrators are notified (see Warehouse notifications). Opening the page shows exactly which record and why.

How a record gets onto the list

You do not create rows here. A row appears when you save:

1. an item (create, edit, activate or deactivate) in Items;
2. a unit or a category in Settings (Master Data).

SolaStock keeps one durable row per record, with a stable identity, the latest version of the record and the user who saved it. Units are delivered first, then categories, then items, so SolaCount never receives a product that points at something it has not seen. Delivery runs separately from your save, in small batches, so saving an item never waits for SolaCount. If you edit a record again before it was delivered, the row goes back to Pending with the newer version; the older one is not delivered.

What Retry synchronization does

It asks the connection to reconcile that one record. You become the acting user for the delivery (an authorized editor is recorded, never a guess), the attempt counter restarts and the current version of the record is queued again. It does not interrupt a delivery that is still in flight, it changes no quantities or local prices, and when SolaCount already holds a similar product it reports Review the existing mapping; no duplicate was created. instead of creating another. Retry does nothing while the connection is paused (catalog connection paused).

Permissions

The permission is Manage integration mappings & settings (inventory.integration.manage).

Worked example 3: a category edited twice

Hamdan renames the category Packaging to Packaging Materials and, a minute later, to Packaging & Wrapping. Only the last name is delivered. If the first delivery was already in flight, the row shows Checking delivery until SolaStock has confirmation, then Synchronized. Nothing for him to do. If the row stayed in Needs attention with The source changed. Retry to review its current version., Omar would click Retry synchronization once; the row would pick up the current name.

How it connects

• Items: saving an item or its unit or category queues it here. See Items.
• SolaCount connection: mappings between SolaStock and SolaCount records are reviewed on the connection page. See SolaCount.
• Documents: purchasing and sales documents that depend on a catalog record wait for it to be delivered and resume by themselves afterwards; see Receiving Requests and Fulfillment Requests.

Worked example 1: a new item waiting for its category

Omar creates the category Packaging Films and the item FLM-500 (Stretch film 500mm, inventory item, unit Roll) in SolaStock. On Catalog synchronization the category row is Synchronized within a minute. The item row shows Pending with Waiting for the related unit or category. for a few seconds, then Synchronized. Nothing for him to do.

Worked example 2: a unit mismatch

Mariam creates item TAPE-48 with unit Piece in SolaStock, but SolaCount already has a product with the same code whose unit is Dozen. The row shows Needs attention and The physical unit or tracking setup differs. Review the mapping before retrying. Nadia (accountant) and Omar agree that SolaStock's unit is right; Omar opens the connection page, corrects the product link, returns to Catalog synchronization and clicks Retry synchronization. The toast reads Synchronization queued and the row turns Synchronized. No duplicate product is created in SolaCount.

Tips and common problems

Related

• SolaCount · Items · Settings · Warehouse notifications · What's new