Push (WooCommerce → UnoPim)

The push side of the connector — what travels from WooCommerce back to UnoPim, what triggers it, and what you'll see appear in UnoPim afterwards.

What gets pushed

Five entity types are pushed back to UnoPim:

Push is for catalogue data only. Stock changes, orders, customers, and prices that exist only in WooCommerce do not push.

Triggers

When a push gets skipped

Even when the trigger fires, a push won't go out if any of these apply:

When a push is skipped, the Logs page records why, with an info row.

Family resolution

Every UnoPim product belongs to a family. The connector decides which family to use in this order:

1. The product's existing family (if it was pulled from UnoPim, this is already set).
2. The Default family you configured on the Core Fields tab.

If neither is set, the push is skipped with a "missing family" error. The product still saves in WooCommerce — only the push to UnoPim is held back. Setting a Default family fixes this for every product at once.

What the push actually contains

A push for one product carries:

• The product code (UnoPim's identifier).
• The family.
• The product type (product for simple, configurable for variable).
• The category assignments.
• The tag assignments.
• The associations (upsells, cross-sells, grouped products).
• All mapped attribute values, scoped correctly per locale, channel, or currency.
• The per-channel active/inactive status.

Each value is sent in the right scope automatically:

You don't have to think about scope yourself — the connector reads each attribute's settings and wraps the value correctly.

Variable products

If the WooCommerce product is variable:

1. The parent is sent as a configurable product, declaring which attributes are the variant axes.
2. Each variation is sent as its own simple product, linked to the parent.
3. Variant images push alongside their variation.

Attribute and option push

When you add or change a product attribute in WooCommerce, the connector mirrors it back:

Image push

When a product is pushed, its featured image and gallery images upload to UnoPim and get linked to that product. Images are uploaded in the background, so a slow image upload doesn't hold up the rest of the push. If an image fails, the rest of the product still goes through, and the image is retried on the next push.

Bulk push

Click Push All Products (or Categories, or Attributes) on the Sync page to send everything in one go. The connector batches the work — typically 50 items at a time — so it doesn't slow your site down. Every gate above still applies: bulk push respects the channel toggle, debounce, and Default family rules just like an individual save.

Delete handling

Off by default. If you turn on Write-back deletes in General Settings:

• Trashing a product in WooCommerce records the intent but doesn't delete in UnoPim yet (since trash is reversible).
• Permanently deleting a product (or a term) deletes it in UnoPim as well.

With it off, deletes only affect WooCommerce; UnoPim continues to think the entity exists.

Common patterns

Push to one channel only

You have multiple channels enabled in the connector but want products to land in a single UnoPim channel.

• Open Channels & Stores, toggle Push off for every channel except the one you want.

Don't push a particular product type

If, say, you don't want subscription products to push to UnoPim, the connector supports skipping specific products if your developer wants to extend it.

Send extra fields you haven't mapped

By default, the connector only pushes fields you've explicitly mapped. If you want every WooCommerce field with a value to go across, the connector also supports a "send unmapped fields" mode if your developer wants to extend it. Note that UnoPim must have matching attribute codes for those fields, or it will reject the push.

Troubleshooting

Next: Variants