First-Time Setup
The end-to-end walkthrough for going live. Plan for 30–60 minutes for a fresh catalogue, longer if you have lots of custom attributes to map.
If you're just kicking the tyres, the Quick Start is shorter. This page assumes you're putting real catalogue data behind the connector.
Pre-flight checklist
Before you start:
- The connector is installed and activated — see Installation
- You have your UnoPim address, API client ID, client secret, and an admin username and password
- You've decided which UnoPim channels go to which WordPress sites (multisite only)
- You've backed up your store (most hosts have a one-click option)
- You have a list of any custom WooCommerce product attributes you want to wire up to UnoPim
Step 1 — Connect
In UnoPim Configuration, fill the form and click Test & Save.
| Field | Required |
|---|---|
| UnoPim address | yes |
| Client ID | yes |
| Client Secret | yes (on first save) |
| Admin Username | yes |
| Admin Password | yes (on first save) |
The password and secret can be left blank when you re-save the form later — the connector keeps the values you saved before.
A green Connected badge appears once your credentials are accepted.
Errors? See Troubleshooting → Connection errors.
Step 2 — Channels and stores
Open the Channels & Stores tab and click Refresh channels.
Each UnoPim channel appears as a row, with these per-channel controls:
- Site — only visible on multisite; tells the connector which WordPress site this channel syncs to
- Pull enabled — let UnoPim updates flow into this channel
- Push enabled — let WooCommerce edits push back to UnoPim
- Sync interval — how often the connector should auto-pull (every 5 minutes, every 15 minutes, hourly, daily, or disabled for manual-only)
- Cooldown seconds — how long after a push to ignore the next opposite-direction event for the same product (default 60 seconds; prevents ping-pong loops)
- Languages — which languages this channel actively syncs
- Currencies — which currencies this channel uses
Click Save channels.
Going slow on go-live day
Set every channel's sync interval to disabled for now. You'll trigger the first pull manually and turn the schedule back on later, after you've reviewed the result.
See Channels & Stores for the full reference.
Step 3 — General settings
Open the Settings sub-page. Two calls to make before the first pull:
| Setting | Default | What most stores choose |
|---|---|---|
| Dry-run | off | Turn on for the first full pull — see Dry Run |
| On-delete | trash | trash is reversible; delete is permanent; skip ignores delete events |
You can change either later, but picking before the first pull avoids surprises.
See General Settings.
Step 4 — Apply default mappings
Open Field Mapping → Core Fields and click Apply WC defaults.
This wires up the standard product fields (SKU, name, regular price, sale price, stock, description, status). Click any row to pick a different UnoPim attribute if your install uses different codes.
Click Save mapping.
Default family
Below the table is a Default family input. The connector uses this when you push a product to UnoPim and that product hasn't been told which UnoPim family it belongs to. Pick a sensible default — usually default_family or your most common product type.
Step 5 — Map your custom attributes
Open Field Mapping → Attributes.
This is where the real catalogue work happens. The page is scoped per (channel, language) so you can map the same WooCommerce field to a different UnoPim attribute on different channels.
- Pick a channel and a language at the top.
- The left column lists WooCommerce fields. The right column is a live UnoPim attribute search.
- Click + Add WooCommerce field to add a row, then pick a field on the left and a UnoPim attribute on the right.
- Optional: click Auto-map to take a first pass automatically.
- Click Save mapping.
Need a custom WooCommerce field that doesn't appear in the left column? Click + Add custom column and type the field key.
Save your mapping as a preset
Click Save preset and give it a name. You can load the same set of mappings on another channel without redoing the work. See Attribute Mapping → Presets.
Step 6 — Map your categories
Open Field Mapping → Categories.
- Left column: your WooCommerce product categories
- Right column: UnoPim categories (live search)
- Click Save mapping
Unmapped WooCommerce categories will be left out on push. Unmapped UnoPim categories will create a new WooCommerce category on pull.
See Category Mapping.
Step 7 — Dry-run your first full pull
Why dry-run?
Dry-run mode logs every change the connector would make without actually writing anything. You'll see the exact list of products, attributes and categories that will be created or updated — with no risk to your live catalogue.
- Make sure Dry run is on in General Settings.
- Open the Sync tab.
- Click Pull Full.
- Watch the Logs page for 5–15 minutes (depending on catalogue size).
- Review the entries. Each one shows what would change.
Once you're happy, turn dry-run off and click Pull Full again. This time the writes really happen.
Step 8 — Try a push
- Open a product. Edit the price or description. Save.
- Within seconds, the change appears in UnoPim.
If it didn't, the Logs page will tell you why. Common causes:
| What you see | Meaning | Fix |
|---|---|---|
| No log row at all | Push is off for this channel, or you're inside the cooldown window | Check Channels & Stores |
| "skipped" row | A custom rule is blocking the push | Ask your developer if you have customisations |
| HTTP 401 / 403 | Sign-in expired | Re-save the Connection tab |
| HTTP 422 | UnoPim rejected the data — usually a wrong attribute or family | Check the message in the log row |
| "missing family" | Product has no family set | Set a default family on the Core Fields tab |
Step 9 — Turn schedules back on
Once the manual pull and a sample push both work:
- Go to Channels & Stores.
- Set each channel's Sync interval to your chosen cadence — hourly is the safe default.
- Save.
For longer or more specific recurring jobs, use the Scheduled Jobs tab.
Step 10 — Lock down access
All admin pages are restricted to administrators and shop managers by default. If you have other roles you don't want touching the connector, your developer can adjust permissions for those roles.
You're live
Watchpoints for the first 24 hours:
- Open the Logs page and filter by errors. Anything new beyond the first hour is a real signal.
- If you ever feel scheduled syncs are running late, see Troubleshooting → Cron not firing.
What's next
- Settings Overview — every option in one place
- Troubleshooting — when something looks wrong