Onboarding Path

The connector doesn't ship with a wizard. Setup is just the right order of tabs. This page is that order, with the reasoning.

If you want the absolute shortest path, use the Quick Start. For a full production walkthrough, follow First-Time Setup. This page sits between the two — useful when you're onboarding a new WooCommerce store onto an existing UnoPim.

The seven-step path

 1. Install         →  2. Connect          →  3. Refresh channels
                                                       │
                                                       ▼
 7. Schedule        ←  6. Dry-run + Pull   ←  5. Map  ←  4. Decide policy

1. Install (5 min)

Upload the plugin and activate it. The connector sets up its tables and defaults automatically.

→ Installation

2. Connect (2 min)

Paste your UnoPim address, API client ID and secret, and an admin username and password. Test & Save confirms the credentials before saving them.

Why this comes first: every other tab needs an active sign-in to fetch your channels, languages and currencies.

→ Connection

3. Refresh channels (1 min)

Click Refresh channels in Channels & Stores. Your UnoPim channels, languages and currencies get pulled in. Map each channel to a WordPress site (multisite only) or accept the single default.

Why before mapping: the Attribute Mapping tab is scoped per (channel, language). Without channels, that page has nothing to scope to.

→ Channels & Stores

4. Decide settings (3 min)

Open Settings. Two calls to make:

DecisionDefaultMost stores choose
Dry-runoffTurn on for the first pull, off afterwards
On-deletetrashtrash (reversible)

You can change either later, but picking before the first pull avoids surprises.

→ General Settings

5. Map (15–60 min — scales with the size of your custom-attribute schema)

Three sub-tabs:

  1. Core Fields — click Apply WC defaults, then Save. Done in 30 seconds.
  2. Attributes — for each WooCommerce custom attribute or field you care about, pick the matching UnoPim attribute. Use Auto-map to bootstrap, then refine.
  3. Categories — wire your WooCommerce categories to UnoPim categories.

Why mapping is the longest step: this is the only step where the connector can't guess. Every store has a different attribute schema. Block off uninterrupted time for it, and save presets so you can repeat the work on other channels.

→ Field Mapping

6. Dry-run and first full pull (varies)

  1. Turn Dry run on in Settings.
  2. Click Pull Full on the Sync tab.
  3. Watch the Logs page.
  4. Review what would change. If you're happy, turn dry-run off and click Pull Full again.

Why dry-run first: it surfaces mapping mistakes before they touch live products. Cheaper than rolling back an unintended overwrite.

→ Sync

7. Schedule (1 min)

Back in Channels & Stores, set each channel's Sync interval to your chosen cadence. hourly is the safe default; every 15 minutes is responsive without hammering your host.

For longer recurring jobs that don't fit per-channel cron, see Scheduled Jobs.

→ Scheduled Jobs

Time budget

Catalogue sizeSetup timeFirst pull
<100 products, default family only30 min<1 min
1,000 products, ~20 attributes1 hour5–15 min
10,000 products, custom families2–4 hours (mostly mapping)30–90 min
100,000+ products, multiple channels1–2 daysSeveral hours, run overnight

What can wait

  • Multilingual content — only if you use WPML
  • Per-role permissions — only if multiple operators share one WordPress install
  • Custom rules — only if your store has special needs the UI can't express

Common day-one missteps

  • Skipping dry-run: fixing 2,000 wrongly-mapped products is much harder than reading 2,000 dry-run log lines.
  • Setting "every 5 minutes" on day one: if the first full pull is still queued, faster schedules pile work on top of an already-busy queue. Start hourly, speed up later.
  • Not refreshing channels after changing the UnoPim address: the connector treats a new address as a new instance. Re-save Connection.
  • Mapping every single field: only map what you actually use in UnoPim. Unused mappings just create noise in the logs.

When onboarding is "done"

  • A small WooCommerce edit pushes to UnoPim within seconds.
  • A small UnoPim edit pulls into WooCommerce on the next scheduled tick.
  • The Logs page is mostly green; no recurring errors.
  • Your team knows where Logs lives and how to read it.

Then you're not just set up — you're operational.

Next steps