Tutorial — Multi-Store Sync

In this tutorial, you will keep two WooCommerce stores in sync. Products added on Store A automatically appear on Store B.

Scenario

You run:

• Store A (master) — your main store where products are created
• Store B (secondary) — mirror store (maybe a wholesale version, a different region, a staging site)

You want:

• New products on A → auto-appear on B
• Price changes on A → auto-update on B
• Stock changes on A → auto-update on B

Time Required

About 30 minutes.

Prerequisites

• Both stores have WordPress + WooCommerce
• Both stores have this plugin installed
• Both stores have admin access
• Basic REST API knowledge

Part 1 — Generate REST API Keys on Store A

Store A will be the data source. Store B will pull from it.

Step 1

On Store A: WooCommerce → Settings → Advanced → REST API → Add key.

Step 2

Fill in:

Click Generate API key.

Step 3

Copy both keys immediately:

• Consumer key — like ck_abc123...
• Consumer secret — like cs_xyz789...

Store B will use these to connect.

Part 2 — Set Up Pull Job on Store B

Store B will pull products from Store A every hour.

Step 1

On Store B: Webkul WC Addons → Jobs → Add New.

Step 2 — Tab 1: Source / Destination

The Job Editor's 6 tabs hold the full sync configuration — Source, Mapping, Transformations, Schedule, Notifications, Run & Results.

Fill in:

In the WC REST API panel:

Click Test Connection to verify.

Step 3 — Tab 2: Column Mapping

Should auto-map. Verify:

Step 4 — Tab 3: Transformations

Optional. Common tweaks:

• Add 20% markup if Store B has higher prices
• Translate values if Store B is in a different language

Step 5 — Tab 4: Schedule

Step 6 — Tab 5: Notifications

• Send on Failure: Yes
• Recipients: [email protected]

Step 7 — Save

Click Save.

Your saved sync job appears in the Jobs grid — enable the schedule, or hit Run Now to test immediately.

Part 3 — Test the Sync

Step 1 — Run Manually

Jobs page → Pull from Store A → Run Now.

Watch the progress. Takes a while on the first run (no delta yet).

Step 2 — Verify on Store B

WooCommerce → Products on Store B. You should see all products from Store A.

Step 3 — Test a Change

1. On Store A: edit a product, change the price
2. Wait up to 1 hour for cron, or click Run Now on Store B
3. On Store B: verify the price updated

Part 4 — Set Up Server Cron on Store B

WordPress cron is unreliable. See Server Cron Setup.

Quick version:

*/5 * * * * curl -s https://store-b.com/wp-cron.php > /dev/null 2>&1

Part 5 — One-Way vs Two-Way Sync

One-Way (What We Built)

Store A → Store B. Changes on B are overwritten by A.

• Simpler
• A is the source of truth
• Best for 99% of use cases

Two-Way Sync

Both stores sync to each other. Changes on B also go back to A.

• Complex (easy to create loops or conflicts)
• Useful for: multi-region stores where inventory updates can happen anywhere
• Requires careful setup

To build two-way:

1. On Store A: set up "Pull from Store B" job with Store B's REST API credentials
2. On Store B: set up "Pull from Store A" (already done)
3. Both jobs run hourly on different schedules (avoid running at the same time)
4. Use Delta Import on both to avoid looping

Part 6 — Syncing Orders

To sync orders from Store A to Store B:

1. On Store A: WooCommerce → Settings → REST API → create a second key with Read/Write
2. On Store B: create a new Job
3. Same as Part 2 but pick Entity: Orders
4. Run hourly

Why Read/Write for Orders?

When B pulls an order from A, then B might update a status (shipped, refunded). If Two-way sync is set up, the status change syncs back to A.

Part 7 — Partial Sync

Not everything needs to sync. Filter to only what matters.

Example — Only Sync Published Products

In Job Editor → Tab 3 (Transformations):

Add a filter condition:

Status equals "publish"

Store B only gets published products. Drafts stay on A.

Example — Only Sync Certain Categories

Categories contains "Wholesale"

Only products in the "Wholesale" category go to Store B (useful for a wholesale-only store).

Part 8 — Monitoring

Dashboard

Check both stores' dashboards daily.

• "Failed (Last 24h)" should be 0
• "Total Records Imported" grows over time

Email Alerts

You set these up in Part 2 Step 6. You'll hear about failures.

Spot Checks

Weekly, verify:

• Random product on A matches B
• Stock counts make sense
• Prices match (or have the expected markup)

Advanced — Multi-Region Setup

Scenario

• Store A: US customers (USD pricing)
• Store B: UK customers (GBP pricing)
• Store C: EU customers (EUR pricing)

Setup

Each secondary store (B, C) has its own sync job pulling from A with a currency transformation:

• Store B: multiply price by 0.80 (USD to GBP)
• Store C: multiply price by 0.92 (USD to EUR)

Prices auto-convert during sync.

Update exchange rates periodically in the transformation settings.

Advanced — Sync With External Systems

You can also sync with non-WooCommerce systems:

• Stripe dashboard — pull product/customer data from Stripe
• Shopify — keep WC and Shopify in sync
• ERP — SAP, NetSuite, etc. via their REST APIs

Use Source Type: REST API (generic) instead of WC REST API.

Troubleshooting

Related Pages

• Import Sources → WooCommerce REST API
• Export Destinations
• Jobs — Scheduled jobs
• Delta Import — Only sync changes
• Server Cron Setup — Reliable scheduling