Skip to main content

Product field mappings and matching rules

Field mappings choose what information syncs. Matching rules help identify which product to link. They do different jobs.

If your account has access to Integration settings, find both under Products. Customer access is being rolled out separately. If the form is unavailable, ask support to configure these settings.

Field mappings​

Choose a WooCommerce field and an Epos Now field for each mapping. Information flows from your product master to the other platform; selecting the fields does not change that direction.

  • Sync on create: copy this field when Slynk first creates the product on the other platform.
  • Sync on update: copy this field when Slynk updates an existing linked product on the other platform.

For example, with WooCommerce as product master, a Regular price → Sale price mapping with both options on copies the WooCommerce price when an Epos Now product is created and on later product updates. Turn off Sync on update if you want to maintain the Epos Now price separately after creation.

Saving a mapping does not immediately update every product. It applies when products next sync. Some Slynk control and measurement fields have a fixed target, which the form selects automatically.

Custom field keys​

Choose Custom field, then enter the exact WooCommerce metadata key. This is the saved key, such as sln_epn_size, rather than the label shown on a product screen. Include any leading underscore.

The WooCommerce meta-field reference lists Slynk's keys. It is not a catalogue of every field on your website. For another plugin's field, check that plugin's documentation or ask your web developer for its saved key and value format. Do not guess from the displayed label.

Review the field pair and create/update choices before saving. Changing a custom key does not rename or delete old metadata already saved on WooCommerce.

Matching rules​

Matching rules apply when product sync needs to find an existing product to link. They do not replace the links already saved in the Product Linker.

Add up to three rules, in order of preference. Slynk uses the first rule that finds exactly one matching product. For example, matching SKU to SKU works when both platforms use the same unique SKU. Avoid names or identifiers shared by several products: an ambiguous match needs attention before the sync can proceed.

Available fields depend on your product sync direction. With Epos Now as product master, WooCommerce matching uses the product ID or SKU. The form shows the supported choices.

If there is no existing match, Slynk can create a product when product creation is enabled. Link products already present on both platforms before enabling creation to avoid duplicates.

To inspect or fix existing links, use the Product Linker guide.