Payments are experiencing issues due to temporary restrictions in Russia. If your payment does not go through, please submit a support request.Our support team is available 24/7 — we are always here to help with hosting and server issues.We are now accepting requests for dedicated server rental and colocation services in our data center.Reminder: we recommend enabling backups for additional data protection.A new VPS/VDS lineup with NVMe storage and improved performance is now available.Maintenance work on some servers has been completed. All services are operating normally.
Article8 min readViews0

Item Missing from 1C Export: When to Deactivate It on the Site

We examine why the absence of an item in a change package proves nothing, and why mass deactivation is permissible only after a complete export with verified coverage has successfully finished.

Comments 0

A full set of items passes the control check; an incomplete lot is halted before processing
In this article

A product must not be deactivated solely because it is absent from the current exchange package. A safe basis for deactivation appears only after a successfully completed full export: it must cover the same catalog and the same filters, and quantity control must not show a suspicious reduction.

A full export transmits the entire set of objects that meet the configured filters. An update package transmits only the changed objects. Therefore, the absence of a position in these two cases means different things: in a full snapshot, it means "does not belong to the confirmed set," while in a delta, it simply means "did not change this time."

Full export and change package answer different questions

The documentation for configuring the site exchange states that during a full export, all data passing the configured filters is transmitted, while in "Changes Only" mode, only the changed data is sent. It also notes that deactivating missing items is tied to a successful full export.

The word "full" does not mean "the entire product catalog of the database." A full set refers to the data within a specific exchange node, organization, warehouse, group, product type, or other active filters. If a filter changes, yesterday's item may disappear from the file not because it was removed from sale, but because the scope was narrowed.

On the "1C-Bitrix: Site Management" side, actions are available for items missing from the import file: do nothing, deactivate, or delete. However, a separately installed exchange module uses its own settings; the official description of the integration form warns that the built-in form settings are then ignored, and for missing items, only deactivation may be available.

Working rule: absence becomes a fact only when the source confirms a full, successfully accepted set with unchanged coverage.

Why a delta is not a list of missing items

On a small example: products A, B, C, and D are active on the site. The change package contains only A. After processing it, B, C, and D must remain unchanged—the package provided no information about them. However, if a full snapshot of A, B, and C is successfully accepted with their previous filters, the absence of D can serve as the basis for a preselected action.

A change package containing A preserves items B–D, while a full snapshot of A–C marks D as missing
Educational model: a change package transmits only A and leaves B–D unchanged; a successful full snapshot of A–C allows D to be considered missing within the verified coverage.

There is a catch: the same file containing A could be the final part of a full exchange, a standard delta, or a fragment of an interrupted transfer. A decision cannot be made based on the content of a single file; the status of the entire session, its mode, and confirmation of completion are required.

Four Conditions Before Mass Deactivation

  1. The mode is fixed as a full export, not a change transfer or a retransmission of an individual package.

  2. The exchange completed successfully: all parts were accepted, the final step was executed, and there are no critical errors.

  3. The scope matches expectations: the same exchange node, information block, organization, warehouses, groups, and filters.

  4. The control check is plausible: the quantity and composition did not unexpectedly collapse, and several known control products are present.

If even one condition is not met, the safe action is to leave the product status unchanged and raise a signal for verification. This is especially important after a timeout, filter change, or sudden reduction in the number of objects: automatic removal of all missing items turns technical incompleteness into a mass change of the storefront.

What to Do with a Missing Product

Element activity, product quantity, and purchase availability are distinct states. A product quantity of zero is not equivalent to deactivation, and deactivation is not equivalent to deletion. The choice depends on whether you need to preserve the product card, history, links, and the ability to quickly restore the item.

Action

What the store sees

When appropriate

Main risk

Do nothing

The card and current state are preserved

Reach or completion is unconfirmed; delta

An obsolete item may remain accessible

Deactivate

The item is hidden from the standard storefront

A complete successful snapshot and a rollback rule are defined

The card will disappear from the catalog until the next valid activation

Delete

The object or associated data are deleted; the exact volume depends on the mechanism

Only under a specific retention policy and after a backup

Lost links, prices, stock levels, and complex recovery

Reset quantity to zero

The card may remain visible; purchase depends on accounting settings

The product must remain in the catalog as unavailable

If purchases without stock are allowed, a zero quantity will not block the order

For custom deletion logic, it is crucial to check the specific API. For example, Bitrix\Catalog\Model\Product::delete deletes the catalog product record along with associated prices, warehouse stock levels, subscriptions, and other catalog data, but leaves the information block element intact. This is not a universal description of any import mode, but a boundary specific to this method.

Zero quantity also requires conditions. According to the product availability documentation, a simple product becomes unavailable when quantity accounting is enabled, purchases without stock are prohibited, and the quantity is zero or less. If any of these conditions differ, the expected purchase block may not occur.

Testing Logic on a Training Model

To verify the solution, I ran a small model on November 14, 2026, in Node.js 24.22.1. The initial set included A, B, C, and D. The model did not connect to 1C-Bitrix nor check a specific exchange module version; it only validated the decision-making rule.

Scenario

Input

Model result

Output

Change package

A

A, B, C, D are active

The absence of B–D proves nothing

Successful full snapshot

A, B, C

A, B, C are active; D is deactivated

D is missing from the verified coverage

Full exchange failed with an error

A

A, B, C, D are active

An incomplete session does not change missing items

Full exchange, but the scope has changed

A

A, B, C, D are active

New selections must first be confirmed

Both launches yielded identical results; scenario checks completed successfully. This is a completed test of the training model, not a statement about production site behavior. The 1C version, exchange module, product edition, and specific project settings must still be verified on a copy.

How to Perform Acceptance Testing on a Store Copy

Perform the check on a copy with anonymized data. Before starting, create a backup of the database and files, record the versions of 1C, the exchange module, and 1C-Bitrix: Site Management, and stop the automatic exchange for this test copy.

  1. Select four control items: a regular product, a product with variants, an item with zero stock, and a product that should disappear from the full set.

  2. Record their XML_ID, activity status, quantity, prices, sections, and variant states before the exchange.

  3. Run the change package for only one product. Ensure the other three are not deactivated and their fields have not changed without reason.

  4. Run a successful full export with the previous filters. Verify the action applies only to the item that was truly excluded from this set.

  5. Repeat the full exchange without changing data. The result must be idempotent: a repeat must not create new products or expand the list of deactivated items.

  6. Terminate the exchange on the test environment before the final step or reproduce a controlled error. Missing items must not change their status en masse.

  7. Change one filter and confirm that protection stops mass deactivation until manual verification of the new coverage.

  8. Restore the original settings, recover the control item via a standard full exchange, and compare the log, counters, and cards with the original snapshot.

Stop conditions should be defined in advance: critical exchange error, lack of final confirmation, unexpected drop in count, node or filter change, or disappearance of the control item. If any such sign appears, mass deactivation is blocked rather than manually completed on the production database.

The recovery plan must also be specific: restore the previous selections, repeat the full exchange in the test environment, verify the activation of control items, and only then migrate the solution to the production workflow. Deletion must not be used as a method to clear the consequences of an unclear exchange.

Products with Product Variants Are Checked Separately

For a product with variants, you must determine in advance what counts as missing: the parent card, an individual product variant/SKU, or both levels. A complete set may contain a parent but lack one product variant/SKU; an automatic rule must not hide the entire card if other product variants/SKUs remain available.

Separately verify reactivation. An item that returns in the next full snapshot must be restored predictably along with the correct prices, stock levels, and product variants/SKUs—not merely receive an activity flag.

Solution Boundaries

The described rule applies to catalog exchanges where the system distinguishes between a full set and changes. It does not prove the configuration of any custom handler and does not replace the documentation for your version. If the integration transmits only events without a full snapshot, the absence of an event cannot serve as grounds for deactivation; a separate reconciliation process is required.

For broader verification of the exchange, use the 18 integration acceptance test scenarios for the site with 1C. If similar product cards appear after the exchange, first analyze the causes of duplicate products. Do not run another full export over an unknown state.

Practical next step: find three signs in the last exchange log — full export mode, successful completion, and unchanged coverage. If any one is missing, do not deactivate the missing items. First, reproduce the four scenarios on a copy and record the expected result for the product, product variant, and parent card.

Discussion 0

Share your experience and ask questions. Comments without links appear after editorial review.

No comments yet. Start the discussion.