MERCHANT GUIDE · SYNCHRONIZATION

1C ↔ WooCommerce Sync — setup

Use this guide when 1C is the source of truth for catalog, prices, and stock, and WooCommerce is the storefront. The plugin keeps the catalog aligned on a schedule and sends new WooCommerce orders back to 1C so the accounting side does not wait for manual entry.

Before you begin

1C 8.3+ with the CommerceML 2 exchange node enabled for the store you want to connect.
A dedicated 1C exchange user. Do not reuse a human admin account; the plugin needs predictable API permissions.
WooCommerce products should have stable SKUs. The SKU is the safest join key between the accounting catalog and the web catalog.
A real cron runner for production stores. WP-Cron works for testing, but a system cron gives imports a reliable cadence.

Data flow

Data	Direction	Cadence
Products: SKU, name, category	1C → WooCommerce	Scheduled import or manual run
Prices and sale prices	1C → WooCommerce	Scheduled import
Stock levels, including warehouse totals	1C → WooCommerce	Scheduled import
New WooCommerce orders	WooCommerce → 1C	Queued after checkout
Order status changes	WooCommerce → 1C	On WooCommerce lifecycle events

Setup sequence

Buy the 1C ↔ WooCommerce license, download the ZIP, and install it from WordPress → Plugins → Add New → Upload Plugin.
Activate the license from the plugin's License tab. The first successful validation binds the key to this WordPress domain.
In the Connection tab, enter the 1C exchange URL, username, and password. Save, then run the connection test before importing data.
Map 1C groups to WooCommerce categories. Start narrow: import one known product group first, review the result, then open more groups.
Run a dry import. Check the preview counts for new products, adopted SKUs, skipped rows, price changes, and stock changes.
Enable the schedule only after the dry import looks correct. For stores with large catalogs, use off-peak hours for the first full import.

Catalog rules

Matching: Existing WooCommerce products are adopted by SKU. The plugin should not create a duplicate when the SKU already exists.
New products: New products imported from 1C should land as drafts first so a human can review images, descriptions, and SEO before publishing.
Missing in 1C: A WooCommerce product that does not exist in 1C is flagged for review. It should not be silently deleted.
Manual edits: Treat price and stock as accounting-owned fields. If a product must be managed manually in WooCommerce, exclude it from the sync.

Order export

When a customer places an order, the plugin queues an export job instead of blocking checkout. The exported document should include line SKUs, quantities, prices, discounts, customer data, delivery address, and the WooCommerce order number. If 1C is unreachable, the order stays in WooCommerce and the export job can be retried.