Syncing the catalog with an online store

How it works

Sklads remains the source of truth for Products, Variants, prices, stock, marking, and images. The online store receives a complete catalog snapshot from Sklads and keeps its own copy. The store never connects to the Sklads database.

The snapshot is built automatically every few minutes. A new catalog version, or revision, is created only when data changes: a name, description, price, stock level, marking, image, or the set of Products. Every snapshot is signed with a secret key and is resent if the store is temporarily unavailable.

Prepare the catalog

Only active Products with at least one active Variant are included. Drafts and archived records are never sent.

Every active Variant needs a retail price in rubles. A missing price blocks the whole snapshot until the data is fixed. To send only the ready part of the catalog, limit the storefront to selected categories, brands, or merchandising groups.

The Product description is always sent. The full Variant description is sent when the storefront settings use the contract version Catalog v1.1 with Variant descriptions. The site must support this version, so select it only after the site developers confirm. If you switch back to Catalog v1, the next snapshot is sent without Variant descriptions.

Images are sent in display order, with the primary image first. Internal Variant reference photos are never included.

Set the marking classification

In the Variant form, open Identifiers and barcodes and fill in Marking:

• Not determined is the default. The Product is shown in the store, but the store blocks online sales for it.
• Required or Not required also need the TN VED EAEU code, the OKPD2 code, and the Classification basis, for example the decision and the date it was checked.

Chestny ZNAK codes of individual units are never included in the snapshot.

Connect a storefront

1. Open Export / Import → Storefronts.
2. In the New storefront form, enter a name and the catalog endpoint provided by the store developer. The address must start with https://. Internal and local addresses are not allowed.
3. Optionally select categories, brands, and merchandising groups, and review the allowed image domains.
4. Select Create integration. The storefront is created disabled and its page opens.

Set the signing secret

Sklads signs every catalog delivery with this secret, and the store must hold the same value. On the storefront page, in the Store connection panel, choose one option:

• Generate secret. Sklads creates a secret and shows it once. Copy it and give it to the store developers through a secure channel.
• Enter the secret received from the store, if the store issued the secret itself.

After saving, Sklads shows only the secret's fingerprint, for example 1a2b3c4d. Use it to compare the secret with the store without revealing it. To replace the secret, generate a new one. Deliveries are rejected until the store has the new value.

If the panel says that secret storage is not configured, contact the server administrator. It is set up once for the whole Sklads installation.

Check and enable

1. Select Check connection. Sklads checks the address and the secret and sends an empty request without data. The signature is verified by the first real delivery.
2. Open Snapshot preview. You see the number of Products and Variants, the snapshot size, and a list of issues. Each issue shows its exact path, for example products.17.variants.2.price.currency, plus the SKU and a link to the Product. The preview sends nothing.
3. Fix the issues in the catalog and open the preview again.
4. Select Enable. The first snapshot is built and sent within a few minutes.

Monitor deliveries

The storefront page shows its state, the latest build, the latest successful delivery, and an event journal.

• Build and send now runs a build without waiting for the schedule. If the catalog has not changed, no new delivery is created.
• Network errors and temporary store outages are retried automatically with increasing delays.
• If the store rejects the snapshot, for example because of an invalid signature or a format mismatch, the delivery gets the Error status and is not retried automatically. Fix the cause and select Retry delivery.
• Resend the latest revision sends the latest revision again, for example after the store restored its data.
• The Stale label means there was no successful synchronization within the time set in the settings.

If the page warns that the synchronization worker is not running, contact the server administrator. Without the worker, snapshots are neither built nor sent.

Automatic reconciliation by the store

The store can check the catalog state in Sklads on its own and fetch a missed snapshot without an operator. This needs an API key.

1. In the Store connection panel, select Issue key. Sklads shows the key once.
2. Give the store developers the key itself through a secure channel, together with the Storefront ID and Reconciliation API address from the same panel. These fields have a Copy button.

The key list shows when each key was issued and when the store last used it. Two keys can be active at once. To change the key without downtime, issue a new one, wait until the store switches to it, and select Revoke on the old one.

Disable and archive

Disable pauses building and sending. Pending deliveries continue after the storefront is enabled again. Archive stops synchronization completely. The revision and delivery history is kept.