UnoPim ConnectorUnoPim Connector
View Demo
  • Getting Started

    • Introduction
    • Quick Start
    • Features
    • Installation
    • First-Time Setup
    • Onboarding Path
  • Configuration

    • Connection
    • Channels & Stores
    • Settings Overview
    • General Settings
  • Mapping

    • Mapping Overview
    • Core Fields
    • Attributes
    • Categories
  • Sync & Operations

    • Sync Page
    • Scheduled Jobs
    • Logs
    • Pull Pipeline
    • Push Pipeline
    • Variants
  • Compatibility

    • Multisite
    • Multilingual (WPML)
    • HPOS
  • Help

    • Troubleshooting
    • FAQ
    • Glossary
Support
View Demo
  • Getting Started

    • Introduction
    • Quick Start
    • Features
    • Installation
    • First-Time Setup
    • Onboarding Path
  • Configuration

    • Connection
    • Channels & Stores
    • Settings Overview
    • General Settings
  • Mapping

    • Mapping Overview
    • Core Fields
    • Attributes
    • Categories
  • Sync & Operations

    • Sync Page
    • Scheduled Jobs
    • Logs
    • Pull Pipeline
    • Push Pipeline
    • Variants
  • Compatibility

    • Multisite
    • Multilingual (WPML)
    • HPOS
  • Help

    • Troubleshooting
    • FAQ
    • Glossary
Support
  • Getting Started

    • Introduction
    • Quick Start
    • Features
    • Installation
    • First-Time Setup
    • Onboarding Path
  • Configuration

    • Connection
    • Channels & Stores
    • Settings Overview
    • General Settings
  • Mapping

    • Field Mapping (Overview)
    • Core Fields Mapping
    • Attribute Mapping
    • Category Mapping
  • Sync & Operations

    • Sync
    • Scheduled Jobs
    • Logs
    • Pull (UnoPim → WooCommerce)
    • Push (WooCommerce → UnoPim)
    • Variants
  • Compatibility

    • Multisite
    • Multilingual (WPML)
    • HPOS Compatibility
  • Help

    • Troubleshooting
    • FAQ
    • Glossary

General Settings

The store-wide policy form. Lives in the Settings section of UnoPim Configuration.

At a glance

SettingDefaultWhy it matters
Dry-runoffA safety net — log what would happen without writing
Writeback deleteoffWhether deleting a product in WooCommerce also deletes it in UnoPim
On-deletetrashWhat WooCommerce does when UnoPim deletes a product
Remove data on uninstalloffWhether to scrub all data when the connector is deleted

Dry-run

A simple on/off toggle.

When on, every pull and push:

  • Builds the change it would make
  • Writes a log row showing what it would do
  • Skips the real database or API write

Good for:

  • The first full pull on a non-empty store — dry-run reveals what would be created or updated.
  • After a mapping change — toggle on, run a single-entity pull, check the log, toggle off.

Dry-run doesn't catch everything

It catches intent errors (wrong mapping, wrong target). It doesn't catch errors that only fire when UnoPim actually receives the data. Use it as a sanity pass, not a guarantee.

Writeback delete

A simple on/off toggle.

When on, deleting (or trashing) a product in WooCommerce sends a delete to UnoPim. When off, deletes only affect WooCommerce.

SettingUnoPim → WooCommerceWooCommerce → UnoPim
off (default)Honoured per On-deleteIgnored
onHonoured per On-deleteSends a delete to UnoPim

Recommended off during onboarding — that way trial deletes in WooCommerce don't propagate. Turn it on only when you trust both sides.

On-delete

A dropdown of three values.

When UnoPim signals a product, category or attribute deletion, here's what WooCommerce does:

ValueBehaviour
Trash (default)The WooCommerce item is moved to the trash. Reversible from the trash bin.
DeleteThe WooCommerce item is permanently deleted. Irreversible.
SkipThe deletion is logged but ignored. The WooCommerce item stays.

"Delete" is dangerous

Use Delete only if UnoPim is your authoritative source AND your team understands that a deletion in UnoPim wipes the matching WooCommerce item. Trash recovers from accidents.

Remove data on uninstall

A simple on/off toggle.

By default (off), deleting the connector from Plugins → Installed Plugins leaves your data intact. You can re-install later without losing tables, mappings or logs.

When on, deleting the connector wipes everything — tables, mappings, logs, scheduled syncs and saved settings. Fully scrubbed.

Set this only when you're certain

Removing the plugin without this toggle keeps your data — useful while troubleshooting. Turn it on only when you genuinely intend to scrub.

Default sync interval

The fallback when a channel has no sync interval set. Default Hourly. Same dropdown values as the per-channel setting.

In practice, you'll always set per-channel intervals on Channels & Stores — this is just the safety net.

Default family

When pushing a product to UnoPim, the connector needs to know which UnoPim family the product belongs to. If the product doesn't carry that information already, the connector falls back to the value you set here.

Set it to your most common UnoPim family code, or leave it empty if every product already has a family assigned.

See Push → Family resolution.

The connector also exposes hooks for developers who need to extend it.


Next

  • Field Mapping — wire up the actual data
  • Sync — manual triggers
Prev
Settings Overview