Dropshipping Setup Services on 1C-Bitrix

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.
FAQ
Our competencies:
Development stages
Latest works
  • image_website-b2b-advance_0.png
    B2B ADVANCE company website development
    1167
  • 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
    563
  • image_bitrix-bitrix-24-1c_mirsanbel_458_0.webp
    Development based on 1C Enterprise for MIRSANBEL
    743
  • 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

Dropshipping on 1C-Bitrix: An Online Store Without a Warehouse

The main technical challenge of a dropshipping store isn't the storefront — it's inventory synchronization. A customer places an order, but the product went out of stock at the supplier 10 minutes ago — and you get a refund, a negative review, and a reputation hit on the marketplace. We build dropshipping stores on 1C-Bitrix with full chain automation: catalog parsing, inventory sync every 5–15 minutes, automatic order forwarding to suppliers, and tracking in the customer's personal account.

Why 1C-Bitrix for Dropshipping

  • "Online Store" module (sale) — cart, sale.order.ajax, payment handlers, personal account — out of the box. No need to assemble e-commerce from plugins
  • Exchange via CommerceML — if the supplier uses 1C, the standard catalog module is set up in a couple of days. Export of catalog.xml + offers.xml → automatic import
  • Multi-supplier — one product from three suppliers at different prices? Bitrix, through price types (b_catalog_group) and multi-warehouse (b_catalog_store), lets you manage everything in a single storefront and display the best offer
  • SEObitrix:catalog.seo.filter for indexable filters, meta tag templates with infoblock property substitution, auto-generated clean URLs
  • Scalability — from 100 to 500,000+ products. With proper faceted index configuration (b_catalog_iblock_index), a catalog with half a million SKUs works without degradation

Architecture: Catalog Import

Suppliers provide data in different ways — each requires its own approach:

  • YML/XML feeds (Yandex.Market format) — the most common. Parsed via XMLReader (not SimpleXML — on large feeds of 500 MB it will consume all memory)
  • CSV/Excel — field mapping via config, validation, handling of broken encodings (yes, in 2026 suppliers still send CSV in Windows-1251)
  • Supplier API — direct real-time access to the catalog, the most reliable option
  • CommerceML — standard exchange format with 1C

Our importer handles the routine:

  • Scheduled loading via a Bitrix agent (CAgent::AddAgent) — every 15–60 minutes, configured per supplier
  • Supplier category mapping → catalog infoblock sections. No manual dragging — rules are set once
  • Image downloading and optimization: resize via CFile::ResizeImageGet, compression, WebP conversion
  • Incremental price and inventory updates — without recreating infoblock elements. We update only changed fields via CIBlockElement::SetPropertyValues and CCatalogProduct::Update
  • Unique description generation — paraphrasing or AI services
  • Markup rules: percentage, fixed amount, separate rules by catalog section

Inventory Synchronization — The Critical Part

In dropshipping, you don't control the warehouse. Discrepancy between the feed and actual availability means direct losses:

  • Synchronization every 5–60 minutes (depends on the supplier's API/feed)
  • Auto-hiding products with zero stock — CIBlockElement::Update(['ACTIVE' => 'N']). Not a single "empty" card in catalog.section
  • Manager alerts on mass discrepancies — if 30% of the catalog suddenly goes to zero, it's more likely a feed glitch than a real clearance sale
  • Multi-supplier: one product from multiple sources — via different warehouses in b_catalog_store. The system selects the offer with availability and the best price

Order Processing

Automatic order forwarding to the supplier — no manual copying:

  • Sending via API, email (template from b_event_message), or export to the supplier's dashboard
  • Splitting items across suppliers — if the sale.basket contains products from different sources, the order is split into shipments
  • Receiving the tracking number → saving to the order property → notifying the buyer via \Bitrix\Sale\Notify
  • Handling partial availability: product available from one supplier, not from another — automatic order splitting

Pricing

Markup is what builds the margin:

  • Percentage — 30% on top of the wholesale price across the entire catalog
  • Tiered — up to 1,000 → 50%, 1,000–5,000 → 30%, over 5,000 → 20%. On cheap products the absolute margin is minimal — a high percentage is needed
  • Category-based — electronics 15%, accessories 60%. Each niche has its own rules
  • Psychological rounding — 990 instead of 987. Implemented via a custom markup rule
  • Competitor monitoring — price parsing and auto-adjustment
  • RRP — the supplier's recommended retail price as an upper guideline

Multi-Supplier

One supplier — one risk. Multi-supplier expands the assortment and provides insurance:

  • Merging catalogs into a unified infoblock section structure
  • Deduplication — by article number (PROPERTY_ARTICLE) or EAN. One product = one infoblock element, multiple offers in b_catalog_store
  • Automatic supplier selection: availability → price → delivery speed
  • Separate accounting: purchase prices in a dedicated price type (PURCHASE), order history, statistics
  • Dashboard with reliability ratings — who misses deadlines, who has inventory discrepancies

Content Uniqueness

Dozens of stores copy descriptions from the supplier's feed — and lose in SEO:

  • Unique descriptions — for top categories that drive the main traffic. The rest — template generation from properties
  • Meta tags by template — title and description via infoblock SEO settings: {=this.Name} buy in Minsk | {=parent.Name} — price from {=this.catalog.price.BASE}
  • UGC — reviews (iblock.vote), Q&A, photos from customers. Live content works better than copywriting
  • SEO filtersbitrix:catalog.seo.filter creates indexable pages for filter intersections: "red Nike sneakers size 42" with unique meta tags

Logistics

Delivery in dropshipping is the supplier's domain, but the buyer sees your brand:

  • Delivery times accounting for supplier processing — not just carrier transit time
  • Tracking in the personal account via CDEK, Boxberry, Russian Post APIs
  • Consolidating shipments from multiple suppliers (when an intermediate warehouse is available)
  • Returns — coordination between buyer and supplier through a unified interface in the admin panel
  • Branded packaging by arrangement with the supplier

Legal Aspects

  • Commission or agency agreement with the supplier — the legal foundation
  • Online cash register: receipt under your store's name, integration via sale.cashbox
  • Warranty: you are responsible to the buyer, regardless of who ships
  • Returns: coordination of three parties — buyer, store, supplier

Timeline and Stages

Stage Timeline
Connecting 1 supplier (catalog import) 3–5 days
Store setup (design, payment, delivery) 1–2 weeks
Order automation 3–5 days
SEO setup and content uniqueness 1–2 weeks
MVP launch 3–4 weeks
Connecting additional suppliers 2–3 days each

We launch dropshipping stores with minimal investment and help scale — from one supplier to dozens, from a hundred SKUs to hundreds of thousands.