Setting up rules for placing products on the 1C-Bitrix marketplace

Our company is engaged in the development, support and maintenance of Bitrix and Bitrix24 solutions of any complexity. From simple one-page sites to complex online stores, CRM systems with 1C and telephony integration. The experience of developers is confirmed by certificates from the vendor.
Our competencies:
Development stages
Latest works
  • image_website-b2b-advance_0.png
    B2B ADVANCE company website development
    1175
  • image_bitrix-bitrix-24-1c_fixper_448_0.png
    Website development for FIXPER company
    811
  • image_bitrix-bitrix-24-1c_development_of_an_online_appointment_booking_widget_for_a_medical_center_594_0.webp
    Development based on Bitrix, Bitrix24, 1C for the company Development of an Online Appointment Booking Widget for a Medical Center
    564
  • image_bitrix-bitrix-24-1c_mirsanbel_458_0.webp
    Development based on 1C Enterprise for MIRSANBEL
    747
  • image_crm_dolbimby_434_0.webp
    Website development on CRM Bitrix24 for DOLBIMBY
    655
  • image_crm_technotorgcomplex_453_0.webp
    Development based on Bitrix24 for the company TECHNOTORGKOMPLEKS
    976

Product Placement Rules Setup on 1C-Bitrix Marketplace

Placement rules are a set of requirements that seller's products must meet for publication on the platform. Without clearly configured rules, moderation becomes arbitrary, sellers don't understand why their product was rejected, and conflicts arise.

Rule Types

Rules are divided into several levels:

Mandatory card fields — minimum data set for any product. Implemented via validation of product addition form in seller's account. Before sending to moderation, system checks completion:

$requiredFields = ['NAME', 'DETAIL_TEXT', 'PREVIEW_PICTURE', 'CATALOG_PRICE', 'CATALOG_QUANTITY'];
$errors = [];
foreach ($requiredFields as $field) {
    if (empty($arFields[$field])) {
        $errors[] = "Field '{$field}' is required";
    }
}

Image requirements — minimum quantity (usually 1–3), minimum resolution (e.g., 800×800 pixels), allowed formats. Checked via getimagesize() on image upload.

Category-based rules — different categories may require different mandatory properties. Electronics requires warranty and country of origin specification, clothing requires size chart. Configured via mapping table mp_category_rules: SECTION_ID → [required_props].

Forbidden products — list of categories or keywords whose products are not accepted. Implemented via check on addition: if product name or category falls into forbidden list — automatic rejection.

Administrative Interface for Rules

A page in /bitrix/admin/ allows administrator to configure rules without code changes:

  • List of mandatory fields (can enable/disable without code editing)
  • Photo requirements by category (minimum quantity, resolution)
  • List of forbidden categories and keywords
  • Refusal reason templates for moderators

Rules are saved in b_option (for simple settings) or in custom table (for complex hierarchical rules by categories).

Feedback to Seller

When product fails automatic check, seller should receive specific message: not "Error adding", but "Add minimum 2 product photos at 800×800 pixels resolution" or "Specify warranty period — it's mandatory for 'Electronics' category".

This reduces moderation load and repeated submissions with same errors.

Timeline

Basic validation of mandatory fields and photo rules — 3–5 days. Category-based rules configuration with administrative interface — 1–2 weeks.