Integration of 1C-Bitrix with AliExpress

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

1C-Bitrix Integration with AliExpress

AliExpress for Russian sellers operates through AliExpress Russia platform (seller.aliexpress.ru). API differs from global AliExpress — uses Solution API with authorization via appKey/appSecret and access_token via OAuth 2.0. Exchange format — JSON over HTTPS. No feed upload — entire catalog managed via API, making integration closer to Ozon than Yandex.Market.

Authorization and Token Retrieval

To work with API you need register application in AliExpress developer panel. After registration you get appKey and appSecret. Seller authorization — via OAuth: redirect to AliExpress page, seller confirms access, in response — access_token with lifetime (usually 30 days) and refresh_token for update.

Token stored on Bitrix side — in module options (COption::SetOptionString) or separate table. Cron agent updates token before expiration.

Product Creation: aliexpress.solution.product.post

Method aliexpress.solution.product.post creates product. Request structure:

  • category_id — AliExpress category. Category tree retrieved via aliexpress.solution.seller.category.tree.query.
  • product_attributes — array of product attributes. Each attribute has attribute_name_id and value. Mandatory attributes depend on category — obtained via aliexpress.solution.product.schema.get.
  • sku_info_list — array of SKUs (variants). Each SKU contains: price, inventory, barcode, values of varying attributes (color, size), photo binding.
  • image_url_list — main product photos (up to 6, minimum 800×800 px).

Mapping to Bitrix infoblock:

AliExpress Field Bitrix Field Note
product_title NAME Up to 128 characters
product_description DETAIL_TEXT HTML, up to 40,000 characters
brand_name "Brand" property AliExpress directory
image_url_list DETAIL_PICTURE + properties URL must be public
sku_info_list[].price TO price In store's currency
sku_info_list[].inventory TO inventory By warehouse
sku_info_list[].barcode TO property EAN-13

Description feature. AliExpress allows HTML in description, including <img> — can insert infographics and additional photos directly in description. Images in description upload via aliexpress.solution.feed.image.upload and return URL on AliExpress CDN.

Categories and Attributes

AliExpress category system — three-level. For each final category there's set of mandatory and recommended attributes. Attributes are:

  • Text — free input (model, material).
  • Reference — selection from list (attribute_value_id). Values obtained via aliexpress.solution.product.schema.get.
  • SKU-attributes — vary between SKUs (color, size). Bound to specific product variant.

When bulk mapping infoblock properties to AliExpress attributes, create correspondence table. For reference attributes — store pairs "Bitrix property value → AliExpress attribute_value_id".

Price and Inventory Management

Prices. Update via aliexpress.solution.product.price.update. AliExpress works with multiple currencies — price specified in currency configured for store. Discounts set via promotions in personal account or API.

Inventory. aliexpress.solution.product.inventory.update — updates inventory by SKU. Limit — 200 SKUs per request. For store with 5000+ items, synchronization takes minutes with batch processing.

Cron agent in Bitrix: every 15–30 minutes selects products with changed inventory/prices and sends batch requests. To track changes use TIMESTAMP_X field of infoblock element and b_catalog_store_product.TIMESTAMP_X for inventory.

Order Processing

Get orders: aliexpress.solution.order.get with filters by status and date. AliExpress order statuses:

AliExpress Status Action in Bitrix
PLACE_ORDER_SUCCESS Order creation
WAIT_SELLER_SEND_GOODS Paid, awaiting shipment
SELLER_PART_SEND_GOODS Partial shipment
WAIT_BUYER_ACCEPT_GOODS Shipped, awaiting receipt
FINISH Completed

Shipment confirmed via aliexpress.solution.order.fulfill — transmit tracking number and delivery service. AliExpress strictly monitors shipment deadlines — delay leads to penalties and rating drop.

On Bitrix side: order created in sale module, products mapped by SKU-article to trade offers. Buyer data (name, address) passed to order properties.

AliExpress Integration Specifics

Product moderation. AliExpress checks each product. Average time — 1–2 days. Rejection reasons: image mismatch (watermarks, third-party logos), prohibited items, incorrect brand.

Multi-language. If selling to multiple countries — product must be localized via aliexpress.solution.product.translate. Or create separate listings for each market.

Rate limiting. Limit depends on application level: basic — ~40 requests per second. With bulk sync, implement request queue with frequency control.

Timeline

Scale Timeline
Up to 500 products, basic mapping 5–7 days
500–3000, SKU, inventory sync 1–1.5 weeks
3000+, full automation with orders 1.5–2 weeks