Zapier pricing for retail workflows in 2026
Budget for Zapier using the retail work it runs. Compare tasks, plan limits and overages for product updates, orders and customer-support handoffs.
- Published
- Last updated
Zapier pricing starts with a free plan of 100 tasks a month. Professional starts at USD $19.99 a month, billed annually, excluding tax. For a retailer, the bill grows with successful automation actions, so a catalogue update can use more tasks than an order notification.
How Zapier charges for automation
Zapier charges for a subscription with a task allowance, plus extra usage when pay-per-task billing is enabled. A Zap is the workflow you build. A task measures billable work that the workflow completes.
Starting subscription prices
These are entry prices with an annual commitment, excluding tax. Higher task allowances cost more.
| Plan | Starting price | Billing commitment | Included entry allowance |
|---|---|---|---|
| Free | USD $0 | No paid commitment | 100 tasks a month |
| Professional | USD $19.99 a month | USD $239.88 billed annually | 750 tasks a month |
| Team | USD $69 a month | USD $828 billed annually | Select the required task tier |
| Enterprise | Custom quote | Contract terms | Contract allowance |
The annual totals above are the monthly equivalent multiplied by 12. Zapier also has monthly billing. Use the same task tier and billing period when comparing quotes. See Zapier’s pricing explanation for its entry-plan allowances and annual billing basis.
Zapier supports Australian-dollar payments. Its currency policy says non-US-dollar charges use the exchange rate at payment. An Australian-dollar invoice can therefore change between payments.
Website prices exclude tax. Under Zapier’s tax policy, Australian GST applies unless you supply an Australian Business Number and confirm GST registration. The checkout and invoice show the tax charged.
Zap workflows, Tables and Forms belong to the platform plans. Zapier Agents uses a separate activity quota, while Chatbots has separate plans. Zapier Model Context Protocol (MCP) uses two tasks per successful tool call. Include those calls in the shared task budget.
When enabled on a paid plan, pay-per-task billing keeps workflows running after the included allowance. The exact rate depends on your plan and billing cycle and appears in Billing settings. Total usage can reach three times the plan allowance, including the original allowance, before workflows stop. Disabling pay-per-task billing stops workflows at the included limit instead.
Count tasks in a retail workflow
Count the successful billable actions after each trigger. Under Zapier’s task rules, triggers and polling checks use no tasks. Filter, Paths and Formatter steps also use no tasks. Actions that error or never run use no tasks.
Order notification
For an illustrative order alert, use Shopify’s New Order trigger, then Slack’s Send Channel Message action. The trigger costs zero tasks. One successful channel message uses one task, so 600 order notifications use 600 tasks.
The Shopify app directory lists New Order as an instant trigger. The Slack app directory documents Send Channel Message. A support handoff that posts the order number and issue into a staff channel follows this one-message counting pattern.
Catalogue update with several actions
Suppose your catalogue team keeps an approved-change table with the product and variant identifiers already filled in. The Zapier Tables connector has an instant New or Updated Record trigger. A filter can let only approved records continue.
For each qualifying record, this illustrative workflow runs three Shopify actions:
- Update Product changes the description or tags.
- Update Product Variant changes the variant price.
- Update Inventory Quantity changes stock at the chosen location.
If every action succeeds, one approved record uses three tasks. Processing 200 records uses 600 tasks. This assumes one product variant and one inventory update per record, with no lookup or extra notification. More variants require their own action count.
Paths can send different records through different branches. Count the successful actions in every branch that actually runs. A filter that stops an unapproved record prevents the later actions from consuming tasks.
Retries and replay
Failed actions don’t consume tasks. Successful retries consume tasks. Zapier’s replay guidance distinguishes retrying failed steps from replaying an entire run.
If a product update succeeds and the following notification fails, failed-step replay retries the notification. Replaying the entire run repeats successful actions too, and those actions count again. Choose the replay mode carefully before resending customer messages or repeating inventory adjustments.
Match plan limits to catalogue and support needs
Choose the plan for the apps and people involved before selecting its task allowance. Free has two-step workflows. Shopify is a premium app, so even the one-action order alert needs Professional or higher.
Professional supports multi-step workflows and premium apps for one user. Team includes 25 users, shared workflows and shared app connections. It suits a store where catalogue staff and support leads need to maintain the same automations. Enterprise adds advanced permissions and app controls for organisations restricting who can change connections or actions.
The plan comparison lists polling intervals of 15 minutes on Free, two minutes on Professional and one minute on Team and Enterprise. These intervals apply to polling triggers. Instant triggers, including Shopify New Order and Updated Inventory, work differently.
Zapier’s scheduling controls put Schedule by Zapier on paid plans. An app’s minimum polling interval can also limit how often Zapier checks it. Paying for a faster plan cannot shorten that app minimum.
Match the action to the information your staff need. Update Product changes product details, while Update Product Variant changes fields such as price. Stock quantities use Update Inventory Quantity. Updating a description alone won’t refresh the stock figure used in an order-support answer.
Allow for processing time after the trigger. Zapier and connected apps impose separate rate limits. A burst of inventory changes can be throttled even when tasks remain. A higher task allowance therefore doesn’t guarantee that every stock update reaches its destination immediately.
Estimate quiet and busy trading periods
Estimate monthly tasks by multiplying qualifying events by successful billable actions, then adding the workflows together. The following figures are illustrative and assume the ordinary one-task actions described above.
Illustrative monthly task budget
| Workflow | Tasks per event | Quiet-period events | Quiet-period tasks | Busy-period events | Busy-period tasks |
|---|---|---|---|---|---|
| Order notification | 1 | 600 | 600 | 1,800 | 1,800 |
| Approved catalogue record | 3 | 200 | 600 | 800 | 2,400 |
| Support handoff message | 1 | 150 | 150 | 450 | 450 |
| Total | 1,350 | 4,650 |
The busy period adds 3,300 tasks. The entry Professional allowance of 750 tasks doesn’t cover even the quiet example. Select a higher allowance before committing to the subscription.
For a hypothetical 2,000-task allowance, the quiet period stays within the allowance and the busy period adds 2,650 overage tasks. With pay-per-task billing enabled, 4,650 total tasks remains below the 6,000-task ceiling for that allowance.
Calculate the extra bill as 2,650 multiplied by the account’s displayed overage rate. Compare that result with the price difference for a larger task allowance. Add a separate reserve for replays or additional actions that aren’t included in this example.
Keep implementation labour separate from Zapier charges. Budget for mapping product identifiers, testing field updates and maintaining connections. The store platform and messaging app subscriptions remain separate costs too. Add any applicable tax after calculating subscription and overage charges.
Set a budget and a review point
Review the allowance whenever you add an action, connect another store or increase catalogue-update frequency. In the quiet example, adding one billable action to each order adds 600 monthly tasks. You can estimate that increase before publishing the workflow.
After launch, open Zap history’s Task usage tab. It sorts workflows by tasks used, highest first. Open an unexpectedly costly workflow’s individual runs and compare record identifiers. Repeated updates to the same record can reveal a loop or an overly broad trigger.
Use the billing usage views for the account total. Zap history’s task view excludes MCP usage, so it can understate the usage behind your invoice. Account permissions can also restrict which workflows a member sees.
Assign the billing owner a review after the first trading week and before a major promotion. Set the expected event counts alongside the task allowance and overage rate. If ordinary trading already needs overages, compare a larger allowance before the next billing period. For the wider support budget, compare the charging models in the customer service software pricing.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.