WooCommerce Variants and HirePOS Items

Edited

By default, the WooCommerce and HirePOS integration (via Zapier) assumes a one-to-one relationship between a WooCommerce product and a HirePOS item.

If you use WooCommerce variable products (products with variants), this relationship changes.

How Variants Should Be Mapped

When using variants, each WooCommerce variant should have its own matching item in HirePOS.

For example:

WooCommerce Product

Variant

Variant SKU

HirePOS Item Code

Chair Cover

Red

CC-R

CC-R

Chair Cover

Blue

CC-B

CC-B

Chair Cover

Green

CC-G

CC-G

Although customers see a single "Chair Cover" product in WooCommerce, HirePOS manages each colour as a separate item.

This allows each variant to have its own availability, stock levels, pricing, maintenance history, and bookings.

Zapier Matching Logic

When an order is received from WooCommerce, Zapier should use the Variant SKU where one exists.

Recommended logic:

  1. If the order line contains a Variant SKU, use the Variant SKU.

  2. If no Variant SKU exists, use the Product SKU.

The resulting value should be used to identify the matching HirePOS item.

Example

Customer selects:

  • Product: Chair Cover

  • Variant: Red

WooCommerce sends:

  • Product SKU: CC

  • Variant SKU: CC-R

Zapier uses:

  • CC-R

HirePOS then matches this to the item with Item Code:

  • CC-R

Recommended Setup

For variable products, it is recommended that each WooCommerce Variant SKU matches the corresponding HirePOS Item Code exactly.

This avoids the need for additional lookup tables, code concatenation, or custom Zapier logic and makes troubleshooting significantly easier.

Was this article helpful?

Sorry about that! Care to tell us more?

Thanks for the feedback!

There was an issue submitting your feedback
Please check your connection and try again.