Choose a Coordinated Source
The catalogue belongs to an Anmarto site and is shared by search and the consultant. If the Bitrix module already exports the store, do not connect an independent feed for the same assortment without agreeing on identifiers and full-replacement rules. Different codes create duplicates; a full import of an incomplete list can remove omitted products from the active assortment.
| Method | Where to Manage It | What to Check |
|---|---|---|
| Bitrix module | Connection, What to index | Sources, anonymous access, prepared and accepted counts, change queue |
| Feed URL | Catalogue → Store, /lk/catalog |
Format, completeness, product count and last update |
| Server integration | Your website's integration | Stable codes and coordinated full/partial updates |
Feeds can use YML/XML/JSON. The URL must return the catalogue itself without a manual browser login. A .xml extension does not make any arbitrary document a valid product feed: records need identifiers and mappable fields. JSON can contain a product list or an items wrapper; catalogue fields includes a structural example.
Connecting a Feed
- Open Catalogue (
/lk/catalog), then Store. Make sure you are working with the intended site. - Check Products in the catalogue and Status. If an assortment already exists, identify its source before replacing it.
- Verify the URL on the store side: it must return the complete current list, not an error page, login form or temporary test collection.
- Enter the URL in Catalogue feed. An illustrative address is
https://shop.example/catalog.yml; this is not a working feed for your store. - Select Connect a catalogue when empty, or Update the catalogue when data already exists. Wait for the result rather than starting several imports in succession.
- If a warning reports a sharp reduction, cancel and inspect the file's completeness. Confirm the smaller assortment only when the reduction is intentional.
- Compare the active product count and Range categories with your expected content. Find reference items in Products (
/lk/products). - Check the same products on the storefront: name, article number, address, price, availability and variants. A successful import does not replace these checks.
Schedule and Update States
When an automatic feed is configured, the dashboard shows its saved schedule, last update and failure reason. This page has neither an interval editor nor a separate schedule toggle. If scheduling is missing or disabled, do not treat a manual import as proof of automatic updates; ask support about your connection's scheduling.
Update in progress means the job is queued or running. The last update failed requires reading its reason. A successful update's date confirms the last completed run, not continuously current prices. Restore from archive appears for an archived catalogue; it is not the ordinary feed-reload button.
Exporting from Bitrix
Before the first export, open What to index and save exclusions: a public source with no individual configuration can be enabled automatically. Keep products and genuinely needed public content. Do not export enquiries, forms or private data; administrator permissions do not replace public visitor permissions.
After mapping fields, select Export to search now. Compare prepared and accepted documents and inspect any limit message. A parent with several offers can be one card, so do not compare this count directly with the number of variants.
Scheduled export runs a full export once daily; immediate updates send the change queue every few minutes. Both depend on Bitrix agents running and service connectivity, not a guarantee of instant results. Monitor the last export, queue size and last change delivery. Full exports remain necessary to reconcile the complete assortment.
Resolving Data Differences
For an empty catalogue, check feed access, identifiers, sources and restrictions. For a missing product, check public permissions, title, URL and the exclusion of products without prices. For an old price, inspect the original value, price group and queue. If descriptions do not change after export, look for manual overrides in Products. Continue with fields, verification and troubleshooting.