Skip to main content

WooCommerce Error Messages

Catalog of the errors the iPaaS.com WooCommerce integration records, with what causes each one and what to do about it.

Overview

This article lists the errors the WooCommerce integration can record in iPaaS.com. Each error starts with a stable code you can search for on this page. Errors appear on the subscription's error and log pages in iPaaS.com (open Subscriptions > your WooCommerce subscription, then its errors or logs).

When a message says iPaaS.com tries the transfer again automatically, iPaaS.com re-runs the failed transfer itself. No action is needed unless the error keeps coming back.

iPaaS.com re-attempts every transfer that ended in an error on its own schedule (about 20 minutes later, then after longer and longer gaps) until it succeeds or the error is dismissed. For the errors whose message says it tries again, a later attempt usually succeeds without any change. Every other error fails the same way on each re-attempt until you fix its cause, so follow its Resolution first; the next re-attempt (or resending the record) then succeeds.

iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.

Some resolutions refer to your Managed Integration Service Provider (MiSP): the partner who set up and manages your iPaaS.com integration.

Every error has the same shape:

{code}: {message} {what to do}

The message says what happened and, for most errors, ends with what to do (the Resolution below gives the full answer). A message that already says what happens next (for example that iPaaS.com tries the transfer again) has no separate instruction. Each error below shows its code, a dash, and the full message (in iPaaS.com a colon follows the code, as in the shape above).

Codes follow iPaaS.com's pattern WOOC-{category}-{number}. The errors below are grouped by where they happen.

When WooCommerce refuses a call, the message includes WooCommerce's own explanation and its error code (for example woocommerce_rest_invalid_product_id). Before any store message is shown, web address query strings and anything shaped like a WooCommerce key are masked, so no secret appears in an error.

Some answers are expected and are not errors. A 404 on a record the integration is only checking for (for example, a refund that was deleted) is treated as "not there" and does not raise an error.

Errors at connection time

The connection is checked at the start of each transfer. When it fails, the transfer shows only Unable to connect to subscription with id N. The integration writes the message with its code (WOOC-VALD-1001 to WOOC-VALD-1004, WOOC-AUTH-1001, WOOC-AUTZ-1001, WOOC-NFND-1001, WOOC-BIZL-1014, or WOOC-EXTN-1001 to WOOC-EXTN-1005) to the subscription's log page at the same time. If no code appears there, check the subscription's Store URL setting.

Supported Flows

  • Connection and settings

  • Any call to the store

  • Products and variants FROM iPaaS.com

  • Stock FROM iPaaS.com

  • Orders and refunds TO iPaaS.com

  • Customers TO iPaaS.com and FROM iPaaS.com

  • Webhook registration

  • iPaaS.com lookups

  • Any data type

Error Collection

Connection and settings

Store URL setting missing

WOOC-VALD-1001 - The Store URL setting is empty. Enter the store's address in the subscription's Store URL setting, for example https://shop.example.com.

  • Description: The subscription has no Store URL. No call to the store is made.

  • Resolution: Enter the store's address in the subscription's Store URL setting, for example https://shop.example.com.

Store URL is not a web address

WOOC-VALD-1002 - The Store URL setting is not a web address. Enter the store's home address, for example https://shop.example.com.

  • Description: The Store URL could not be read as an address.

  • Resolution: Enter the store's home address, for example https://shop.example.com.

Store URL is not HTTPS

WOOC-VALD-1003 - The Store URL must start with https://. Serve the store over HTTPS and enter the https:// address.

  • Description: The store address uses http://. WooCommerce accepts the REST API key only over HTTPS, and the integration never sends the key unencrypted.

  • Resolution: Serve the store over HTTPS and enter the https:// address.

Consumer Key or Consumer Secret missing

WOOC-VALD-1004 - The Consumer Key or Consumer Secret setting is empty. In WordPress, open WooCommerce > Settings > Advanced > REST API keys, create a Read/Write key for an administrator, and enter its Consumer Key and Consumer Secret.

  • Description: The subscription is missing part of the WooCommerce REST API key. No call to the store is made.

  • Resolution: In WordPress, open WooCommerce > Settings > Advanced > REST API keys, create a Read/Write key for an administrator, and enter its Consumer Key and Consumer Secret.

Key refused

WOOC-AUTH-1001 - WooCommerce refused the REST API key ({WooCommerce's code}). Check the key in WooCommerce > Settings > Advanced > REST API keys and re-enter both values. If they are right, ask the store's host to pass the Authorization header through to WordPress.

  • Description: The Consumer Key or Consumer Secret is wrong or revoked, or the store's web server removes the Authorization header before WooCommerce sees it.

  • Resolution: Check the key in WooCommerce > Settings > Advanced > REST API keys and re-enter both values. If they are right, ask the store's host to pass the Authorization header through to WordPress.

Action not allowed

WOOC-AUTZ-1001 - WooCommerce did not allow this action ({WooCommerce's code}). Edit the key in WooCommerce > Settings > Advanced > REST API keys: set Permissions to Read/Write and choose an administrator.

  • Description: The REST API key is Read only, or its WordPress user is not an administrator or shop manager.

  • Resolution: Edit the key in WooCommerce > Settings > Advanced > REST API keys: set Permissions to Read/Write and choose an administrator.

A web page instead of data

WOOC-EXTN-1001 - The store answered with a web page instead of WooCommerce data (HTTP {status}). Allow requests to /wp-json/wc/v3/ through the store's firewall or security plugin (both reading and writing), and take the store out of maintenance mode. If the host only accepts approved IP addresses, add iPaaS.com's addresses 20.98.221.25 and 69.61.66.130, or exempt the /wp-json/wc/v3/ path from that rule.

  • Description: A firewall, security plugin, maintenance mode or caching layer answered before WooCommerce did: the store answered with something other than WooCommerce data (for example a firewall's block page with HTTP 403, or a maintenance page with HTTP 200). A server error (HTTP 500 or above) is WOOC-EXTN-1004 instead, a 503 or 429 is WOOC-EXTN-1005, and a 404 page is WOOC-NFND-1001.

  • Resolution: Allow requests to /wp-json/wc/v3/ through the store's firewall or security plugin (both reading and writing), and take the store out of maintenance mode. If the host only accepts approved IP addresses, add iPaaS.com's addresses 20.98.221.25 and 69.61.66.130, or exempt the /wp-json/wc/v3/ path from that rule.

WooCommerce REST API not found

WOOC-NFND-1001 - The store's WooCommerce REST API was not found. Check the Store URL, make sure WooCommerce is active, and in WordPress open Settings > Permalinks, choose any option except Plain and click Save Changes.

  • Description: WooCommerce is not active, the Store URL points to the wrong site, or WordPress permalinks are set to Plain.

  • Resolution: Check the Store URL, make sure WooCommerce is active, and in WordPress open Settings > Permalinks, choose any option except Plain and click Save Changes.

Store not reachable

WOOC-EXTN-1002 - The store could not be reached ({reason}). Open the Store URL in a browser; fix the address or the certificate, then retry.

  • Description: The address does not resolve, the site is down, or its HTTPS certificate is not valid. A read is tried once more within the call before this error is raised; then iPaaS.com tries the transfer again automatically.

  • Resolution: Open the Store URL in a browser; fix the address or the certificate, then retry.

Store URL redirects

WOOC-EXTN-1003 - The store sent the request to another address ({address}). Open the Store URL in a browser and enter the home page address the browser ends on (for example https://www.shop.example.com, or https://example.com/store for a store in a sub-folder), then retry.

  • Description: The Store URL is not the address the store answers on: the store redirects it, for example from shop.example.com to www.shop.example.com, or from an old domain to a new one. The integration does not follow a redirect, so the REST API key is never sent to another address. The message names the address the store sent the request to.

  • Resolution: Open the Store URL in a browser and enter the home page address the browser ends on (for example https://www.shop.example.com, or https://example.com/store for a store in a sub-folder), then retry.

Store URL changed to another store

WOOC-BIZL-1014 - The Store URL now points to {new store}, but this subscription's records are linked to the store at {first store}. To connect a different store, give it its own subscription and set this subscription's Store URL back. The same store at a new address is recognised automatically when it carries this subscription's webhooks (any webhook scope turned on), and the new address is recorded. If it is the same store and none of its webhook scopes was on, delete the Linked Store value on the subscription's Subscription Settings page, then retry. Delete it only for the same store: for a different store, this subscription's links would update unrelated records.

  • Description: The first store a subscription connects to is recorded on the subscription as Linked Store (shown on the subscription's Subscription Settings page, under the settings stored for this integration). The Store URL now names a different store. WooCommerce numbers products, orders and customers from 1 in every store, so the links made with the first store would update unrelated records in the new one: every transfer stops before anything is written.

  • Resolution: To connect a different store, give it its own subscription and set this subscription's Store URL back. The same store at a new address is recognised automatically when it carries this subscription's webhooks (any webhook scope turned on), and the new address is recorded. If it is the same store and none of its webhook scopes was on, delete the Linked Store value on the subscription's Subscription Settings page, then retry. Delete it only for the same store: for a different store, this subscription's links would update unrelated records.

Any call to the store

Store error

WOOC-EXTN-1004 - The store had an internal error (HTTP {status}). iPaaS.com tries the transfer again automatically.

  • Description: WordPress or a plugin failed while handling the request. A read is tried once more within the call before this error is raised; a write is not repeated, so a create is never sent twice.

  • Resolution: None needed if it passes on retry. If it keeps happening, check the store's PHP error log and WooCommerce > Status > Logs, or ask your web host.

Store asked to slow down

WOOC-EXTN-1005 - The store asked iPaaS.com to slow down (HTTP {status}). iPaaS.com waits {seconds} seconds and tries again.

  • Description: The store answered 429 or 503. Its host or firewall limits how many requests it accepts, or the store is in maintenance mode.

  • Resolution: No action is needed for occasional limits: iPaaS.com waits and tries again. If it is frequent, lower Concurrent Batch Executions on the subscription by 1 (never below 1), or ask the host to raise the limit for the REST API.

WooCommerce refused a value

WOOC-EXTN-1006 - WooCommerce refused to {action}: {WooCommerce's message (WooCommerce's code)}. Correct the value named in WooCommerce's message in the source record or the mapping, then transfer again.

  • Description: WooCommerce rejected a value in the record. Its own message follows, and usually names the field.

  • Resolution: Correct the value named in WooCommerce's message in the source record or the mapping, then transfer again.

Record not found

WOOC-NFND-1002 - The {record type} {id} was not found in WooCommerce. If the record was deleted in WooCommerce on purpose, remove its link in iPaaS.com (the record's external id for this subscription; your MiSP or iPaaS.com Support can do it) and transfer it again to recreate it.

  • Description: The record was deleted in WooCommerce, or the link points to a record in another store.

  • Resolution: If the record was deleted in WooCommerce on purpose, remove its link in iPaaS.com (the record's external id for this subscription; your MiSP or iPaaS.com Support can do it) and transfer it again to recreate it.

Products and variants FROM iPaaS.com

Product has no SKU

WOOC-VALD-1005 - A product needs a SKU to be created in WooCommerce. Give the product a SKU in its source system, or map one, and transfer it again.

  • Description: The product's mapped SKU is empty. The SKU is how the integration finds a product it already created, so a retry never makes a duplicate. Nothing was written.

  • Resolution: Give the product a SKU in its source system, or map one, and transfer it again.

SKU used by several products

WOOC-BIZL-1001 - {count} WooCommerce products have the SKU {sku}, so the integration cannot tell which one to update. Give each WooCommerce product its own SKU, then transfer again.

  • Description: The SKU is used by more than one product in WooCommerce.

  • Resolution: Give each WooCommerce product its own SKU, then transfer again.

Product type not supported

WOOC-BIZL-1002 - The product type {type} is not supported. Use simple, grouped, external or variable. Map Type to simple, grouped, external or variable, or leave it empty so the integration chooses from the variants.

  • Description: The mapping sets the product Type to a value other than simple, grouped, external or variable (for example a type that a WooCommerce extension adds). The integration writes only those four types. Nothing was written.

  • Resolution: Map Type to simple, grouped, external or variable, or leave it empty so the integration chooses from the variants.

Variant's product not in WooCommerce yet

WOOC-NFND-1003 - The variant's product is not in WooCommerce yet for this subscription. Transfer the product first.

  • Description: A variant was transferred on its own before its product reached WooCommerce. Nothing was created.

  • Resolution: Transfer the parent product; its variants go with it.

Category name not unique

WOOC-BIZL-1003 - {count} WooCommerce categories are named {name} under the same parent. Rename or merge the duplicate categories in Products > Categories, or use a Parent > Child path.

  • Description: The category name is not unique in the store, so the integration cannot choose. Every category and tag is looked up before any is created, so nothing is created and the product is not written. (Duplicate tag names raise WOOC-BIZL-1006.)

  • Resolution: Rename or merge the duplicate categories in Products > Categories, or use a Parent > Child path.

Variation SKU used twice

WOOC-BIZL-1004 - {count} variations of WooCommerce product {product id} have the SKU {sku}. Give each variation its own SKU in WooCommerce, then transfer again.

  • Description: The variation SKU is used more than once on the product.

  • Resolution: Give each variation its own SKU in WooCommerce, then transfer again.

Product cannot have variations

WOOC-BIZL-1005 - WooCommerce product {product id} is a {type} product, so it cannot have variations. Transfer the parent product with its variants so it becomes a variable product.

  • Description: A variant was sent for a product that is not a variable product in WooCommerce.

  • Resolution: Transfer the parent product with its variants so it becomes a variable product.

Duplicate tag names

WOOC-BIZL-1006 - {count} WooCommerce tags are named {name}. Rename or merge the duplicate tags in Products > Tags.

  • Description: The tag name is not unique in the store, so the integration cannot choose which tag to assign. Every category and tag is looked up before any is created, so nothing is created and the product is not written. (Duplicate category names raise WOOC-BIZL-1003.)

  • Resolution: Rename or merge the duplicate tags in Products > Tags.

Duplicate variations

WOOC-BIZL-1007 - {count} variations of WooCommerce product {product id} have the options {options}, so the integration cannot tell which one to update. Delete or change the duplicate variations in WooCommerce, or put the variant's SKU on the WooCommerce variation it should update, then transfer again.

  • Description: The product has duplicate variations with the same option values, and the variant has no link or SKU that picks out one of them.

  • Resolution: Delete or change the duplicate variations in WooCommerce, or put the variant's SKU on the WooCommerce variation it should update, then transfer again.

Some variations refused

WOOC-EXTN-1007 - WooCommerce refused {count} of the variations: {each SKU and WooCommerce's message}. The product itself is saved in WooCommerce without them; correct the values named and transfer the product again to add them (it is not duplicated).

  • Description: WooCommerce answered the product's variation update but rejected some of the variations in it. Up to five are listed. The product and the other variations were saved in WooCommerce. On the next transfer the product is found again by its link or its SKU, and each saved variation by its link, its SKU, or its options when it has no SKU.

  • Resolution: Correct the values named in WooCommerce's message, then transfer the product again. The variations already saved are updated, not duplicated. The exception is a variation first created in the failed transfer that has neither a SKU nor options: nothing identifies it, so the next transfer creates it again. Give such variants a SKU.

Stock FROM iPaaS.com

Product not in WooCommerce yet

WOOC-NFND-1004 - Stock was sent for a product that is not in WooCommerce yet for this subscription. Transfer the product first.

  • Description: A stock-only update never creates a product.

  • Resolution: Transfer the product; later stock changes then update it.

Variant not in WooCommerce yet

WOOC-NFND-1005 - Stock was sent for a variant that is not in WooCommerce yet for this subscription. Transfer its product first.

  • Description: A stock-only update never creates a variation.

  • Resolution: Transfer the product with its variants; later stock changes then update them.

Stock record's link not readable

WOOC-VALD-1008 - The stock record's link {link} is not in the expected form. Remove the inventory record's link in iPaaS.com and transfer the product again.

  • Description: The stored link for this inventory record was changed by hand or comes from another integration.

  • Resolution: Remove the inventory record's link in iPaaS.com and transfer the product again.

Stock is not a whole number

WOOC-VALD-1009 - The stock quantity {quantity} is not a whole number. Keep this product's stock in whole units in iPaaS.com (the total is read from its inventory there), then transfer again.

  • Description: WooCommerce stores stock as a whole number. The total of the counted locations has a fraction. The integration stops instead of rounding.

  • Resolution: Keep this product's stock in whole units in iPaaS.com (the total is read from its inventory there), then transfer again.

Current stock not readable yet

WOOC-NFND-1007 - The current stock in iPaaS.com could not be read for {id}. iPaaS.com tries the transfer again automatically.

  • Description: WooCommerce's stock is the total over the counted locations, read from iPaaS.com. iPaaS.com did not return the product or variant, or its inventory did not yet list this record (iPaaS.com's read was older than the change). The integration stops instead of writing an old or partial total, and iPaaS.com tries the transfer again automatically.

  • Resolution: No action is usually needed: the next retry normally succeeds. If it keeps failing, check that the parent product or variant still exists in iPaaS.com.

Parent id not mapped

WOOC-VALD-1010 - The stock record has no parent {product or variant} id, so the total over the Stock Locations cannot be computed. Map the inventory record's parent id into IpaasProductId or IpaasVariantId in the stock collection, then transfer again.

  • Description: The stock collection does not map the inventory record's parent id (IpaasProductId for product stock, IpaasVariantId for variant stock).

  • Resolution: Map the inventory record's parent id into IpaasProductId or IpaasVariantId in the stock collection, then transfer again.

Stock Locations match nothing

WOOC-NFND-1006 - The Stock Locations setting names locations iPaaS.com does not have, or none of this record's locations ({entries}), so no stock is written. Correct the Stock Locations setting: iPaaS.com location ids or names, comma-separated; leave it blank to count every location.

  • Description: Every Stock Locations entry is checked against iPaaS.com's list of locations, and an entry (id or name) that iPaaS.com doesn't have stops the update. When that check isn't possible (iPaaS.com returned no location list), a record whose locations match none of the entries stops instead, because a misspelt entry is the likely cause. In a company with 100 or more locations, a name can't be proven missing, so a misspelt name there is not caught: use location ids. When the setting is valid and a product simply has no stock at the listed locations, no stock is written and no error is raised.

  • Resolution: Correct the Stock Locations setting: iPaaS.com location ids or names, comma-separated; leave it blank to count every location.

Stock quantity matches neither iPaaS.com quantity

WOOC-BIZL-1008 - The stock quantity {quantity} sent for location {location} matches neither the available ({available}) nor the on-hand ({on hand}) quantity iPaaS.com holds there, so no stock is written. If it keeps failing, map StockQuantity in the stock collection to QtyAvailable or QtyOnHand (the same as the Stock Quantity Field setting), not a formula. iPaaS.com tries the transfer again automatically.

  • Description: On a stock-only update, the quantity the stock collection sends confirms that iPaaS.com's stock is current before the total is written. Either iPaaS.com's read was older than the change (the automatic retry then succeeds), or the stock collection's StockQuantity mapping is a formula (for example a safety buffer or rounding), which never matches. When a product or variant is transferred with its stock, the same mismatch is only recorded as a warning on the log page: the product is still written, with the total from iPaaS.com.

  • Resolution: If it keeps failing, map StockQuantity in the stock collection to QtyAvailable or QtyOnHand (the same as the Stock Quantity Field setting), not a formula. iPaaS.com tries the transfer again automatically.

Orders and refunds TO iPaaS.com

Not an order or refund id

WOOC-VALD-1011 - {id} is not a WooCommerce order or refund id. Transfer the order from WooCommerce again; refunds follow their order.

  • Description: The transfer named an id that is neither an order number nor an order-refund pair ({order id}-R{refund id}).

  • Resolution: Transfer the order from WooCommerce again; refunds follow their order.

Refund deleted while being sent

WOOC-BIZL-1009 - Refund {refund id} of order {order id} was deleted in WooCommerce while it was being sent, so it was not sent. No action is needed for this refund. A refund deleted after it reached iPaaS.com leaves its return there as it was: correct that return in iPaaS.com and in any system that received it.

This is recorded as a warning on the subscription's log page, not as a failed transfer. It appears only in the rare case where a refund is deleted in WooCommerce while the integration is sending it.

  • Description: Someone deleted the refund in WooCommerce between the integration listing the order's refunds and reading this one. Nothing was sent.

  • Note: A refund deleted at any other time raises no error or warning. Its Return in iPaaS.com is left as it is, and the deleted refund's id no longer appears in the order's list of refund ids (in the default templates, the transaction custom field WooCommerce Refund Ids) after the order's next update.

  • Resolution: No action is needed for this refund. A refund deleted after it reached iPaaS.com leaves its return there as it was: correct that return in iPaaS.com and in any system that received it.

iPaaS.com's own errors on an order

iPaaS.com checks each order before saving it, and some of its own errors (codes without the WOOC- prefix) can appear on an order transfer. In each case the whole order is refused and nothing is written:

  • A line SKU iPaaS.com doesn't have ("Product Id: … does not exist"): add the product in iPaaS.com (from the system that sends your catalogue), or set the stand-in SKUs (see WooCommerce Installation Instructions).

  • VALD-1024 "Required property 'method' not found" (on payments[…]): the order's payment method has no row in the payment method translation. Add a row for it (and replace any target that still says REPLACE with …: iPaaS.com refuses those orders too).

  • VALD-1024 "Required property 'status' not found": the order's status has no row in the order status translation, for example a status a WooCommerce extension adds. Add a row for it.

  • VALD-1036 "Value (REPLACE with your iPaaS.com Payment Method for …) provided for Payment Method is not valid", or the same for "Address Shipping Method": a payment or shipping method translation still holds its REPLACE with … target, or names a method your company doesn't have. Replace the target with the exact name of one of your iPaaS.com Payment Methods or Shipping Methods.

  • "Product Id: REPLACE with your SKU for products without one does not exist" (or "… fee item SKU"): the stand-in SKUs in the line SKU formula are still as shipped. Set them (see WooCommerce Installation Instructions, Set the stand-in SKUs).

  • NFND-1029 "Duplicate transaction found! Transaction Number: …": another system in your company already sent a transaction with that number (for example a second store that also numbers orders from 1). Resending fails until the number is unique: prefix the TransactionNumber mapping in Add Order, Update Order and Add Refund (see WooCommerce Integration Known Limitations 27).

  • VALD-1039 "Company, First Name, or Last Name must not be null or empty" (on a customer): a customer collection sent a customer with none of the three, usually a second customer collection that maps fewer fields than the template one and matches the same customers. Map the names in that collection, or give the collections filters that don't overlap (see WooCommerce Integration Known Limitations 28).

After the fix, resend the order from iPaaS.com or make a change to it in WooCommerce.

Customers TO iPaaS.com and FROM iPaaS.com

Customer has no email

WOOC-VALD-1012 - A customer needs an email address to be created in WooCommerce. Give the customer an email address in the source record, or map one.

  • Description: WooCommerce requires an email for every customer account. Nothing was written.

  • Resolution: Give the customer an email address in the source record, or map one.

Email used by several WooCommerce customers

WOOC-BIZL-1010 - {count} WooCommerce customers have the email {email}. Merge or correct the duplicate WordPress users, then transfer again.

  • Description: The email matches more than one WordPress user, so the integration cannot choose.

  • Resolution: Merge or correct the duplicate WordPress users, then transfer again.

Email used by several iPaaS.com customers

WOOC-BIZL-1011 - {count} iPaaS.com customers have the email {email}, so the WooCommerce customer was not linked to one of them. Merge the duplicate customers in iPaaS.com, then transfer the WooCommerce customer again.

  • Description: The email is shared by several iPaaS.com customers.

  • Resolution: Merge the duplicate customers in iPaaS.com, then transfer the WooCommerce customer again.

Email of a store staff account

WOOC-BIZL-1015 - The email {email} belongs to a store staff account ({role}) in WooCommerce, so the customer was not created or linked. Give the iPaaS.com customer its own email address, or leave it out with the collection's filter, then transfer it again. If the customer is already linked to the staff account, a new email alone does not help: also remove the customer's link in iPaaS.com (its external id for this subscription; your MiSP or iPaaS.com Support can do it), then transfer it again.

  • Description: The iPaaS.com customer has the email address of a WooCommerce administrator or shop manager, or is already linked to such an account. The integration never makes a new link to a store staff account and never updates one: doing so would overwrite the staff account's name and addresses with the customer's, so nothing is written.

  • Resolution: Give the iPaaS.com customer its own email address, or leave it out with the collection's filter, then transfer it again. If the customer is already linked to the staff account, a new email alone does not help: also remove the customer's link in iPaaS.com (its external id for this subscription; your MiSP or iPaaS.com Support can do it), then transfer it again.

Username can't change

WOOC-BIZL-1016 - The customer's username {username} is not the WooCommerce username {store username} of customer {id}, and WooCommerce does not let a username change. The rest of the customer was saved. Leave Username unmapped for customers that already exist, or map the store's username.

  • Description: The mapped Username differs from the username the customer already has in WooCommerce. WooCommerce refuses a changed username, so the integration leaves it out, saves the customer's other changes, then reports this.

  • Resolution: Leave Username unmapped for customers that already exist, or map the store's username.

Email of a customer with another username

WOOC-BIZL-1017 - The email {email} belongs to WooCommerce customer {id}, whose username is {store username}, not {username}, so the customer was not linked or changed. If it is the same person, leave Username unmapped or map the store's username. If not, give the iPaaS.com customer its own email address. Then transfer it again.

  • Description: An iPaaS.com customer not yet linked to WooCommerce has the email of a WooCommerce customer whose username differs from the mapped Username, so they may not be the same person. Nothing was written: linking would overwrite that store account's name and addresses.

  • Resolution: If it is the same person, leave Username unmapped or map the store's username. If not, give the iPaaS.com customer its own email address. Then transfer it again.

Webhook registration

Unknown webhook scope

WOOC-BIZL-1012 - {scope} is not a WooCommerce webhook this integration registers. Enable one of the integration's scopes: order.created, order.updated, customer.created or customer.updated.

  • Description: A webhook was turned on for a scope the integration does not handle. The integration checks the scope before this point, so this error is not expected to appear; it is kept listed so its code stays documented.

  • Resolution: Enable one of the integration's scopes: order.created, order.updated, customer.created or customer.updated.

Webhook key missing

WOOC-VALD-1013 - The subscription has no webhook key, so WooCommerce webhooks cannot be registered. Save the subscription again in iPaaS.com, then turn the webhook scope off and on again. If it persists, your MiSP can review the subscription.

  • Description: iPaaS.com did not supply the subscription's webhook key, so the integration could not register the webhook in WooCommerce.

  • Resolution: Save the subscription again in iPaaS.com, then turn the webhook scope off and on again. If it persists, your MiSP can review the subscription.

Webhook delivery refused by iPaaS.com

This is iPaaS.com's own answer to a WooCommerce webhook delivery (a code without the WOOC- prefix), not an error on the subscription's error page. A store administrator sees it in WooCommerce's webhook delivery log (WooCommerce > Status > Logs, source webhooks-delivery): AUTH-1001 - Bearer token is missing or invalid.

  • Description: The webhook's delivery address carries a webhook key that is not the subscription's current one, usually because the subscription's webhook key was regenerated or the address was edited in WooCommerce. The event is not received.

  • Resolution: Do not edit the delivery address in WooCommerce. The next poll (order/poll or customer/poll), or turning the webhook scope on again, moves this subscription's webhooks to the current key. Orders missed in the meantime arrive with the next order poll; for customers, see Webhook key changed in WooCommerce Connections and Settings.

iPaaS.com lookups

iPaaS.com lookup failed

WOOC-INTL-1001 - A lookup in iPaaS.com failed ({what the integration was looking up}). iPaaS.com tries the transfer again automatically.

  • Description: iPaaS.com did not answer a lookup the integration needs (an external id, a customer, a product or a location).

  • Resolution: No action is usually needed: the next retry normally succeeds. If it keeps failing, raise it with your MiSP first, then iPaaS.com Support, with the time of the error.

Any data type

Link not readable

WOOC-VALD-1014 - {id} is not a valid WooCommerce {record type} id. Remove the record's link in iPaaS.com and transfer it again.

  • Description: The stored link is not in the form this record type uses (for example, a product link that is not a number, or a variation link that is not {product id}|{variation id}).

  • Resolution: Remove the record's link in iPaaS.com and transfer it again.

Data type not handled

WOOC-BIZL-1013 - The WooCommerce integration does not handle {the mapping collection, for example "the Gift Card mapping collection"}. Remove or turn off that mapping collection; the supported data types are listed in the installation instructions.

  • Description: A mapping collection of a data type or direction this integration doesn't support was set up for it.

  • Resolution: Remove or turn off that mapping collection; the supported data types are listed in the installation instructions.

Reporting an issue

If you see an error not covered above, capture the iPaaS.com Subscription ID, the WooCommerce order, product or customer id (if any), and the iPaaS.com error log entry, including WooCommerce's own error code. Raise it with your MiSP first. For problems on the store side, your web host or WooCommerce developer can check WooCommerce > Status > Logs and the PHP error log (WooCommerce does not log refused REST API requests there by default).

Related Documents

Did this answer your question?