Setting up seller registration 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
    1173
  • 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
    745
  • 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

Configuring Seller Registration on Marketplace in 1C-Bitrix

Seller registration on marketplace — not standard Bitrix user registration form. Need to collect legal entity data, verify, conduct onboarding and only then grant access to seller tools. Entire process configured on top of base Bitrix user system.

Technical implementation

Seller in system — user in b_user in special group (e.g. "Sellers", b_user_group). Additional legal entity data stored in user UF fields (b_user_field) or in separate HL infoblock with link via UF_USER_ID.

Seller registration form fields:

  • Subject type (LLC / Sole proprietor / Individual)
  • Full organization name
  • Tax ID, registration number (for legal entities), State registration number
  • Legal address
  • Contact person, phone, email
  • Bank details
  • Documents link (charter, certificate) — upload via CFile

Status model:

registered → documents_pending → under_review → active | rejected

Status stored in user UF field. On transition to each status — automatic email via CEvent::Send() per event template.

Onboarding after approval

After status set to active seller automatically:

  • Added to "Sellers" group via CUser::Update(['GROUP_ID' => [...]])
  • Basic cabinet structure created (if needed)
  • Welcome email sent with instructions

Admin changes statuses via admin interface or custom /bitrix/admin/ page. Admin notification on new application — via CEvent::Send() or Bitrix24 webhook.

Timeline

Registration form configuration with extended fields, status model and notifications — 1–2 weeks. Integration with external verification services (DADATA, Tax Authority API) — additional 3–5 days.