Resources · Zapier integration

CommerceHQ Zapier integrationAutomate CommerceHQ with Zapier.

The CommerceHQ Zapier integration gives you 8 triggers, 8 actions and 3 searches. All eight triggers are instant: a paid order, a refund or a fresh product starts your Zap the moment it lands in your store, even on the free plan.

See the 19 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the CommerceHQ Zapier integration actually does

The CommerceHQ Zapier integration links your store to Zapier, the tool that runs automations between apps. CommerceHQ tells Zapier when an order is paid, refunded or changed, when a customer or product appears, and Zapier can write back: customers, products, variants, images and shipments.

Three results come up again and again once the store is connected.

A catalog that fills itself in. New Product fires, then Create Product Variant adds the sizes you always sell, and Add Product Image attaches a standard visual. The product is ready before anyone touches it.

Shipments marked from the outside. Ship Order marks an order as shipped with its carrier and tracking number, so the tracking number produced elsewhere reaches the store without being retyped.

A customer base kept in shape. Find Customer looks up an existing buyer, then Update Customer corrects the email or the name in the same run.

Now the limits, because they matter as much. Zapier cannot create an order in CommerceHQ: there is no action for it. It cannot issue a refund either, only react to one with New Refunded Order. Nothing here deletes a product, a variant or a customer. And collections can be found, never created.

If you are weighing tools, the same app has its own page on Make: the CommerceHQ Make integration.

Vocabulary

Zapier words you will meet on this page

Eight terms, in plain English. Each one comes back further down without being explained again.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event that starts the Zap. Once the Zap is on, Zapier waits for it, here a paid order or a new customer in CommerceHQ.
Action
What the Zap does once it has started: the step that writes something for you, like a variant, a shipment or a customer record.
Task
The unit Zapier bills. One task is one action your Zap completes successfully, and your plan is a count of those.
Instant trigger
A trigger the app reports itself: CommerceHQ calls Zapier as soon as the event happens, so nothing waits for a scheduled check.
Polling trigger
A trigger Zapier checks on a timer, asking the app for new items at a fixed interval. None of the CommerceHQ triggers work this way.
Filter
A step that lets the Zap go on only when what arrived meets your condition, and stops it there otherwise.
Search step
A step that looks up something already in the app, such as a customer, so the steps after it can use what it found.
Cost

What a CommerceHQ Zap really costs

Zapier bills completed actions, not events. The trigger itself never costs a task, and watching the store for new orders costs nothing either.

  • TriggerNever costs a task
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps only
  • Premium appNo, CommerceHQ works on the free plan

Every action that succeeds counts on its own: a Zap that creates three variants uses three tasks per product. An action that fails is not counted. CommerceHQ is not a premium app, so it works on the free plan, which gives 100 tasks a month and unlimited Zaps. The catch: the free plan only builds two-step Zaps, one trigger and one action. Add a filter, a search or a second action and the Zap becomes multi-step, which needs a paid plan. The interval grid below concerns polling triggers only; all eight CommerceHQ triggers are instant, so it never slows them down.

Connect

Connect your CommerceHQ store to Zapier

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. A connection is your store account linked to Zapier once, then reused by every step that uses CommerceHQ.

  2. 02

    Pick CommerceHQ

    Type CommerceHQ in the search box of the dialog, select it, then click Add connection. You need an existing CommerceHQ account before this step goes anywhere.

  3. 03

    Sign in and grant access

    A new tab opens on CommerceHQ. Sign in with the store account the Zap should work on, then grant Zapier access. If the store belongs to someone else, you also need read or write rights on what the Zap will touch.

First Zap

Your first Zap: every new product gets its size variants

GoalEach time a product is created in CommerceHQ, add a Size: S and a Size: M variant at the price you set.

  1. 01

    Build: start with the trigger

    Create a Zap, choose CommerceHQ as the app and New Product as the event. Pick your connection. The trigger is instant, so there is no interval to set.

  2. 02

    Test the trigger

    Click test. Zapier brings back the three most recent products of the store, so you map the next steps on a real one rather than an empty shell.

  3. 03

    Add the first variant

    Add an action, CommerceHQ again, event Create Product Variant. Map Product from the trigger, set Price, and type Size: S in Variant Combination.

  4. 04

    Add the second variant

    Repeat with a second Create Product Variant and Size: M. This makes the Zap multi-step, so it needs a paid plan, and each product will use two tasks.

  5. 05

    Test, then publish

    Test each action and check the variants in your CommerceHQ product. When both look right, click Publish: the Zap is on and only reacts to products created from now on.

Triggers

CommerceHQ triggers on Zapier

8 events start a Zap when something happens in CommerceHQ, and 8 of them are instant: the app calls Zapier straight away, whatever your plan.

1

New Abandoned Checkout

Instant trigger

In Zapier“Triggers when new abandoned checkout is created.”

Starts the Zap when a shopper gets to the checkout and leaves without paying. You get the abandoned cart while it is still fresh, which is the whole point of chasing it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a dropshipping store that wants every abandoned basket passed to the tool that sends reminder emails, through a second app step after the trigger.
Watch out
CommerceHQ has no action that sends a message, so the follow-up always happens in another app.
2

New Customer

Instant trigger

In Zapier“Triggers when a new customer is created.”

Fires each time a new customer record appears in your store, so the rest of your tools hear about a buyer the moment CommerceHQ has one.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you run a print-on-demand shop and want each new buyer pushed into your email list the minute they exist.
Watch out
a Zap built on this trigger that also runs Create Customer in the same store creates a record that sets off the trigger again, a loop that eats tasks.
3

New Product

Instant trigger

In Zapier“Triggers when a new product is created.”

Reacts when a product is added to the catalog. It is the natural starting point for anything that should happen to a product the day it exists.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a fashion store where every new item needs the same size variants, added by Create Product Variant without a manual pass.
Watch out
a bulk import of hundreds of products sends hundreds of events at once, and Zapier can hold that flood back.
4

New Paid Order

Instant trigger

In Zapier“Triggers when new paid order is created.”

Fires when an order is paid, not merely placed. That difference matters: you only act on money that has actually come in.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a store that forwards each paid order to its supplier or its fulfillment partner the second the payment clears.
Watch out
the Zap only sees orders paid after it was published, so last week's orders never come through and need a separate import.
5

New Refunded Order

Instant trigger

In Zapier“Triggers when new refunded order is created.”

A refund recorded in CommerceHQ sets this one off. It is the trigger built for refunds, and the only side of them Zapier sees: no action can issue one for you.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
your finance person wants each refund logged in the bookkeeping tool the same day, without combing through the dashboard.
Watch out
treat this as a notice, not a control; the refund itself is already done when the Zap starts.
6

Updated Customer

Instant trigger

In Zapier“Triggers when existing customer is updated.”

Catches every change on an existing customer, such as a new email or a corrected name. Use it to keep a copy of your buyer list in step with the store.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a store owner who mirrors customers in a CRM and wants edits made in CommerceHQ to reach it without a weekly export.
Watch out
never pair it with Update Customer on the same store: each update fires the trigger again and the Zap feeds itself.
7

Updated Order

Instant trigger

In Zapier“Triggers when order is updated.”

Any change on an existing order sets the Zap going. It covers the life of the order after it was placed, where the paid and refunded triggers each cover a single moment.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
an operations lead who wants any order change copied to the shared order tracker the support team reads.
Watch out
one order can change several times, and each change is a new run, so the actions behind it add up in tasks.
8

Updated Product

Instant trigger

In Zapier“Triggers when a existing product is updated.”

Reacts when someone edits a product that already exists in the catalog.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you sell the same items on a marketplace and want catalog edits reported to whoever keeps that listing in step.
Watch out
the classic loop lives here: a Zap that answers this trigger with Update Product on the same product edits it again and restarts itself.
Actions

CommerceHQ actions on Zapier

CommerceHQ gives you 8 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Add Product Image

Action

In Zapier“Adds image to the product.”

Attaches a picture to a product you point at. Both the Product and the Image are required, so the product has to exist before this step runs.

When to use it
your designer drops the final visuals in a shared folder and you want each one attached to the right listing.
2

Create Customer

Action

In Zapier“Creates a new customer.”

Opens a customer record in your store. Email, First Name and Last Name are all required, so a contact source missing one of them will make the step fail.

When to use it
wholesale buyers sign up through a form outside the store and you want them on file before their first order.
3

Create Product

Action

In Zapier“Creates a new product.”

Adds a product to the catalog from data another app holds. Title, Product Type and Price are required; you can also set Auto Fulfilment, Track Inventory and Is Draft.

When to use it
a supplier sheet gets a new line and you want the item in your store as a draft, ready for review.
4

Create Product Variant

Action

In Zapier“Creates product variant.”

Hangs a variant on an existing product, with its own price. The Variant Combination field takes a set of properties, Size: M for example.

When to use it
right after New Product, to add the sizes or colors every item in your range comes in.
Watch out
one variant is one action, so five sizes cost five tasks.
5

Ship Order

Action

In Zapier“Marks order as shipped.”

Marks an order as shipped. Order ID, Shipping Carrier, Tracking Number and Send Notification are required, the last one deciding whether the customer hears about it.

When to use it
your warehouse tool produces the tracking number and you want CommerceHQ updated without anyone retyping it.
6

Update Customer

Action

In Zapier“Updates an existing customer.”

Rewrites an existing customer. It asks for the customer Id plus Email, First Name and Last Name, all required, so you send the full identity each time.

When to use it
after Find Customer, to fix a buyer whose email changed in your CRM.
Watch out
the Id rarely comes from another app, which is why a search usually sits just before.
7

Update Product

Action

In Zapier“Updates an existing product.”

Changes settings on a product already in the catalog: Is Draft, Auto Fulfilment and Track Inventory. Only the Product itself is required.

When to use it
take a product out of draft once its images and variants are in place, as the last step of a catalog Zap.
8

Update Product Variant

Action

In Zapier“Updates product variant.”

Edits one variant of a product. It needs the Product, the Variant, its Variant Combination and the Price, all four required.

When to use it
a supplier raises the price of one size and you want only that variant repriced.
Watch out
the Variant field points at one existing variant, so the product and the variant both have to be identified before this step runs.
Searches

CommerceHQ searches on Zapier

3 search steps look for data that already exists in CommerceHQ, so a later step can use it.

A search step sits at the bottom of the action list in the editor, under its own SEARCH heading. It fetches a record that already exists so a later step can use it. Three settings decide what happens when the lookup does not go as planned.

1

Find Collection

Search

In Zapier“Finds an existing collection.”

Looks up a collection that already exists in your store. No action creates collections, so this is the only way a Zap touches them.

When to use it
confirm that the seasonal collection is there before a catalog Zap goes further, with the default setting stopping it if not.
2

Find Customer

Search

In Zapier“Finds an existing customer.”

Retrieves an existing customer so the steps after it have the record, including what Update Customer needs to point at the right person.

When to use it
a buyer changes their email in your support tool, and you find them in CommerceHQ before updating.
Watch out
if several customers match, the first one wins unless you change the setting.
3

Find Product

Search

In Zapier“Finds an existing product.”

Fetches a product already in the catalog, which is how a Zap started elsewhere gets the Product that image and variant actions require.

When to use it
a new visual arrives from your designer and you locate the matching product before Add Product Image.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and the steps that needed it are skipped. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. CommerceHQ offers no find-or-create variant, so you will not see it on these three searches.
  3. If multiple search results are found?
    Three ways out when several records match: keep the first one, which is the default, stop the Zap, or pass all of them on at once.
When it breaks

When a CommerceHQ Zap breaks

Zapier attaches no help article to CommerceHQ, and no store-specific limit is documented. What breaks is the general mechanics of Zapier, and a store hits them in recognizable ways.

Four cases cover what goes wrong. Two of them are about timing, two about volume. If a Zap misbehaves beyond these, the Zapier troubleshooting page is the next stop.

  • Old orders never show up

    A Zap only reacts to what happens after it is published. Orders, customers and products that existed before are not picked up; moving that backlog is a separate job.

  • The Zap that restarts itself

    Updated Product followed by Update Product on the same item fires the trigger again, and again. Same story with Updated Customer and Update Customer. Tasks drain fast.

  • A bulk import gets held back

    Importing a supplier catalog creates a burst of New Product events at once. Zapier's flood protection can hold such a batch back instead of running it.

  • A required field comes through empty

    Ship Order, Update Customer and the variant actions all have required fields. If the earlier step leaves one blank, the action fails and is not billed.
Need help

Need help automating CommerceHQ with Zapier?

A person reads every message.

FAQ

CommerceHQ and Zapier: frequent questions

01Is the CommerceHQ Zapier integration free?
Yes, on the free plan, with one condition. CommerceHQ is not a premium app, so Zapier lets you connect it without paying, and the free plan gives 100 tasks a month with unlimited Zaps. The condition is the shape of the Zap: the free plan stops at two steps, one trigger and one action. As soon as you add a filter, a search such as Find Customer, or a second action like a second variant, the Zap is multi-step and needs a paid plan. Price grids move often, so check the current plans before you commit.
02How many tasks does a CommerceHQ Zap use?
One task per action that completes, and nothing for the trigger. A Zap that answers New Paid Order with a single action uses one task per paid order. A Zap that answers New Product with three Create Product Variant steps uses three tasks per product. Actions that fail are not counted. Watching the store costs nothing either, however many events come in. The bill grows with the number of actions per run multiplied by the number of runs, so a busy store with a long Zap is where the count climbs.
03Do CommerceHQ triggers run in real time?
Yes. All eight CommerceHQ triggers are instant: the store calls Zapier the moment the event happens, and the Zap starts right away. That holds on every plan, including the free one, because the interval grid only applies to polling triggers, and CommerceHQ has none. In the editor, a Zap built on an instant trigger shows a lightning bolt. There is no polling interval to wait for, whichever plan you are on.
04What does connecting CommerceHQ to Zapier take?
An existing CommerceHQ account and the right to sign in to it. In Zapier you open Apps, click + Add connection, search for CommerceHQ and confirm with Add connection, then sign in to the store in the tab that opens and grant Zapier access. If the store is not yours, you also need read or write rights on whatever the Zap will touch. Connect the store that holds your real orders and products, because most actions point at records that must already exist.
05Why does a CommerceHQ Zap keep triggering itself?
Because it writes where its own trigger is watching. Updated Product fires on any product edit, so a Zap that answers it with Update Product on that same product edits it again, which fires the trigger again. The same loop forms between Updated Customer and Update Customer. Each pass costs tasks, so the count drains quickly. Break the loop by changing the trigger, for instance New Product instead of Updated Product, or by writing to a different record than the one that started the Zap.
06What if the CommerceHQ operation you need does not exist?
Then Zapier cannot do it for this app, and it is worth knowing before building. The integration has no action to create an order, issue a refund or delete anything, and collections can be found but not created. Two workarounds stay inside what exists: react to the event with a trigger, such as New Refunded Order, and do the rest in another app; or chain a search before an update so the action gets the record it needs. If the gap is central to the project, check whether another automation tool covers it.
07Zapier, Make or n8n for CommerceHQ?
Decide on criteria rather than a ranking. On Zapier, what matters here is that all eight triggers are instant, that billing counts each completed action, and that the free plan stops at two-step Zaps. Then look at the same points on the other tools: which CommerceHQ events they react to, which actions they offer, how a run is billed, and who in your team will maintain the workflow. The answer depends on the operations you actually need and on the volume of orders your store sends through.
Same platform

Other docs you might need on this stack.

Browse all integrations