What product sync moves and what it leaves alone
Product sync keeps the same product in line in two places: your webshop and Exact Online, where a product is called an item (artikel). The main decision is who owns each field. Each field should have one owner, and the other system should follow. If both sides edit the same field freely, sooner or later one team overwrites the other's work.
In Integrator by CLATE, product sync is a beta integration per shop. Shopify, WooCommerce, Shopware and Magento each have one with Exact Online. It keeps names and prices in line and nothing else. Prices are in euros only.
Integrator does not delete, archive or unpublish products or items in either system. It runs every hour and when you press Run now. In WooCommerce, a change made in the last minute is picked up in the next run.
- Synced: product name and price.
- Not synced, stays where it is: descriptions, images, stock and sale prices.
- Stays with the shop when Exact leads: collections or categories, tags and other variants.
Matching by SKU and what happens to existing products
The SKU is the link between the two systems. On the Exact side, the SKU is the item code. A shop product and an Exact item with the same code are treated as the same product. Products without a SKU are skipped.
When the other system already has the SKU, the existing product or item is updated, not duplicated. Sending a record again does not create a second copy. If an earlier attempt to create an Exact item or a WooCommerce product got no answer, it is found again by its SKU on the next try.
Every SKU must be unique. If one SKU matches more than one Shopify variant, or more than one WooCommerce product, that record stops for review and you are asked to give each its own SKU. Clean up duplicate SKUs before you start.
In the shop to Exact direction, one record is one Shopify variant, one WooCommerce simple product or one WooCommerce variation. Variant names arrive in Exact as "Product - Options". WooCommerce grouped products have no price of their own and are not synced.
Direction 1: Exact Online leads
This is the default direction. Exact items are copied to the shop. It fits when the catalogue and prices are maintained in Exact, for example by finance or purchasing. Each Exact sales item with a code is one record, and items that cannot be sold or have ended are skipped. You can limit the sync to items with the Webshop box ticked in Exact.
For a shop product that already has the SKU, Exact's price is written. The name is written only when the product is just that SKU: a Shopify product with one variant, or a WooCommerce simple product. Names of products with several variants and WooCommerce variation names stay as they are in the shop.
A SKU the shop does not have becomes a new product, as a draft unless you choose to publish. New WooCommerce products are simple products. Variations are updated but not created. You can also choose to add only missing products and leave existing ones untouched.
The price is Exact's standard sales price. For a shop that shows prices including VAT, VAT is added at the rate of the item's sales VAT code. Items without a VAT code use a fallback rate, 21% unless you change it. Writing to WooCommerce needs a REST API key with Read/Write permission.
Direction 2: the webshop leads
Shop products are copied to Exact as sales items. This fits when products are created in the shop first and Exact needs matching items. Integrator's Exact order integrations need an Exact item for every SKU they book, and either direction provides one. By default only active shop products are synced.
In Exact, the sync owns the description, the "can be sold" flag and the default sales price. Exact keeps 60 characters of a name, so longer names are cut. Item group and VAT code are set only when an item is created, so you manage them in Exact after that. You can also choose to add only missing items and leave existing ones untouched.
Prices are written to Exact excluding VAT. If your shop enters prices including VAT, they are converted. WooCommerce uses the rate of the product's tax class for the shop's country. Shopify keeps no VAT rate per product, so you set the VAT rate of your products in the integration, and untaxed variants get 0%.
A WooCommerce tax class without one plain rate, such as a compound class, stops for review. Exact also refuses a new item whose item group has no revenue, cost of sales or stock/costs account. Integrator checks the group first and explains the problem. Those accounts can only be set in Exact itself, under Stamgegevens, Artikelgroepen.
Both ways, and what happens when both sides change the same field
Both ways means a name or price changed on either side is copied to the other. After every write, Integrator remembers per SKU what both sides agreed on: the name and the price excluding VAT. On the next run it compares each side with that memory, field by field.
When both sides changed the same field to different values, neither value is written and an issue explains it, for example "The price changed on both sides". To resolve it, make the two values equal, or change the value you want to keep again.
The first time both systems have the same SKU, equal values are simply adopted. Different values follow the side you choose for that first meeting, Exact by default. A SKU that appears on both sides later with different values stops for review.
Names are compared as Exact keeps them, at 60 characters, and prices to the cent. Names of Shopify products with several variants and WooCommerce variation names are not compared or written. Editing the field mapping only affects the Exact to shop direction.
- Nothing changed on one side: nothing is written from that side.
- The other side does not have the SKU: the product is created there.
- Only one side changed a field: that change is copied.
- One side changed the name and the other the price: both changes are kept and copied across.
- Both sides changed the same field differently: nothing is written for it until you decide.
Choosing a direction: a short checklist
One way is the simpler choice. Only one side changes names and prices, so there is nothing to merge and no conflicts to settle. Choose both ways only when people really maintain names and prices in both systems, and someone has time to resolve conflicts.
- Exact leads: prices are decided in Exact, the shop team mainly works on descriptions, images and stock, and items exist in Exact before they go online.
- The shop leads: new products are created in the webshop first, the shop team sets prices, and Exact mainly needs items to book sales.
- Both ways: both teams edit names or prices, and one person is named to resolve conflicts when both edited the same field.
- Whatever you pick: write down who owns each field and tell both teams, because edits on the following side can be overwritten by the leading side.
Before you switch it on, and when something stops
Run a dry run first. It reads up to 20 recent records with real data and shows, for each one, whether it would create a new product or update one the other system already has. It writes nothing.
When one record fails, the others continue. Integrator explains the failure with explanations the CLATE team wrote and approved, and shows an error without one as not yet explained. Once the cause is fixed, you can send the record again. If Exact has not confirmed an item, look up the item code in Exact and try again: an item that is there gets linked, one that is not gets created. If Exact refuses the login itself, the run stops until you reconnect Exact Online.
- Every product and variant has a SKU, and every SKU is unique.
- Products that exist on both sides use the same code as SKU and Exact item code.
- Prices are in euros.
- You know whether your shop enters prices including or excluding VAT.
- Exact items have the right sales VAT code, and item groups have their ledger accounts.
- Names longer than 60 characters are shortened if the name in Exact matters to you.
- For WooCommerce, the API key has Read/Write permission if the shop should be updated.
