Skip to main content

WooCommerce Integration Known Limitations

Known limitations of the iPaaS.com WooCommerce integration: design decisions, WooCommerce constraints, the scope of version 2.0.0, and defaults to review before go-live.

New here? This page is a configuration reference for teams implementing the WooCommerce integration in iPaaS.com. It documents scope, design decisions, and settings to confirm before go-live. These are not product defects, and most items are handled during implementation by iPaaS.com or your Managed Integration Service Provider (MiSP). See Understanding Integration Scope & Known Limitations for how we document this for every integration.

This document lists the known limitations of the WooCommerce integration, as they stand at the time this documentation was written. They apply to all subscribers. None of these items are bugs. They come from design decisions, from how WooCommerce works, or from the scope of the 2.0.0 release.

For each limitation we explain what it is, why it exists, and what this means for you.

Platform Scope and Tested Versions

Item

Value

Integration name

WooCommerce

Integration version

2.0.0

Remote platform API

WooCommerce REST API v3 — [Store URL]/wp-json/wc/v3

Store requirements

WordPress with WooCommerce active, served over HTTPS, permalinks not set to Plain

Tested with

WooCommerce 11.0.1 on WordPress 7.1.3, high-performance order storage, block Cart and Checkout.

Last tested end to end

November 2026 (17 to 20 November), against the WooCommerce REST API v3.

Not built for

The older WooCommerce REST API versions (v1 and v2) and the legacy REST API; the WooCommerce Store API that themes use for the cart and checkout; WordPress sites without WooCommerce. If WooCommerce releases a new REST API version, this integration does not automatically support it.

Not covered in this version

Products TO iPaaS.com; orders FROM iPaaS.com (status or tracking write-back, orders placed elsewhere); coupons and product categories as records of their own

1. One stock number per product

What: Core WooCommerce keeps one stock number per product, or per variation. iPaaS.com keeps stock per location.

Why: This is how WooCommerce stores stock.

What this means for you:

  • The integration adds up the quantities of the iPaaS.com locations named in Stock Locations (blank counts every location) and writes the total.

  • Shoppers see the total, not the stock at each location.

  • A stock change at a location the setting leaves out does not change WooCommerce.

  • Every entry in Stock Locations must be an iPaaS.com location id or name. Each entry is checked against iPaaS.com's list of locations, and an entry iPaaS.com doesn't have stops the update with WOOC-NFND-1006.

  • Two cases can't be checked that way. If iPaaS.com returns no location list, the update stops with WOOC-NFND-1006 only when the record matches none of the listed locations. In a company with 100 or more locations, a name can't be proven missing, so a misspelt name is not caught: in a large company, use location ids.

  • When the setting is valid and a product has no stock at the listed locations, no stock is written for it. This is not an error.

  • Every stock update, with the product or stock-only, reads the quantity of every location in Stock Locations from iPaaS.com, measured by the Stock Quantity Field setting, and writes the total. A product transfer and a stock-only update therefore count the same quantity.

  • In the stock collections, map StockQuantity to the same quantity as the Stock Quantity Field setting (QtyAvailable or QtyOnHand), as a plain field. The total always uses the setting; the mapped quantity only confirms that iPaaS.com's read already shows the change, so a formula there (for example a safety buffer) never changes the total. When the mapped quantity matches neither of iPaaS.com's quantities, a product or variant transfer still writes the total read from iPaaS.com and logs a warning, and a stock-only update stops with WOOC-BIZL-1008. With a formula, every stock-only update stops.

  • The location mapping is optional: a stock record without a mapped location is found in iPaaS.com by its inventory record. The parent id must be mapped (WOOC-VALD-1010).

  • If iPaaS.com's inventory doesn't list the transferred location or inventory record for the product yet, the update stops with WOOC-INTL-1002 rather than writing a partial total, and iPaaS.com tries the transfer again automatically.

  • WooCommerce stores whole numbers. A total with a fraction stops the update with WOOC-VALD-1009.

  • Every stock update turns on Manage stock for the product or variation, because WooCommerce ignores a quantity otherwise.

2. Orders need the store's products in iPaaS.com

What: iPaaS.com accepts an order line only when its SKU is a product in iPaaS.com. A line with a blank SKU, or a SKU iPaaS.com doesn't know, is refused, and so is its order.

Why: iPaaS.com links every transaction line to a product, so the systems that receive the order can use it.

What this means for you:

  • The products usually come from the system that sends your catalogue to WooCommerce through iPaaS.com. Set up that system's product flow before orders arrive.

  • If your other systems only take orders (for example a CRM, a shipping system or a marketing system), you also need a system that sends products TO iPaaS.com. This version of the integration does not send WooCommerce products TO iPaaS.com.

  • The default template has a stand-in SKU for lines without one and one for fee lines, in each of the three order collections. Replace every placeholder (see Set the stand-in SKUs in the Installation Instructions).

3. Deletes in iPaaS.com are not sent to WooCommerce

What: Deleting a product, variant or customer in iPaaS.com does not delete it in WooCommerce. Removing a location's stock record does not change WooCommerce stock.

Why: A deleted WooCommerce product or customer loses its link to past orders.

What this means for you:

  • To take a product off sale, send its status as draft or private. For a variation, private.

  • To end a price promotion, empty the sale price in iPaaS.com: when a regular price is sent and the sale price is empty or not mapped, the sale ends in WooCommerce. If you run sales in WooCommerce instead, map KeepStoreSalePrice to a static true and WooCommerce's sale price is left alone.

  • To clear a location's stock, send a quantity of 0.

  • Delete records in WooCommerce yourself if you need them gone.

4. Trashed orders are not sent

What: An order moved to the trash or deleted in WooCommerce is not sent TO iPaaS.com. It stays in iPaaS.com as it was last sent.

Why: The integration does not register WooCommerce's order-deleted webhook in this version.

What this means for you:

  • Cancel an order, rather than trashing it, when the back office should know. A cancelled order arrives as a status change on its iPaaS.com transaction.

  • A refund whose order is not in iPaaS.com (for example because the order's own transfer failed, or the order was filtered out) is not sent. Only a line on the subscription's log page records it. Once the order reaches iPaaS.com, its refunds are sent after the order's transfer.

  • A refund deleted in WooCommerce after the order changed but before the refund's own transfer ran is not sent. No error is raised; a warning on the subscription's log page records it. No action is needed for that refund.

  • A refund deleted in WooCommerce after it reached iPaaS.com leaves its Return transaction in iPaaS.com as it was. No error or warning is raised. The order's next update shows it: the order carries the ids of its current refunds (in the default templates, the transaction custom field WooCommerce Refund Ids), and the deleted refund's id is no longer listed. Correct the Return by hand in iPaaS.com and in any system that received it.

5. Customer changes arrive by webhook only

What: customer/poll finds new customers only. Changes to existing customers reach iPaaS.com only through the customer.updated webhook.

Why: WooCommerce's customer list has no "changed since" filter, so a poll cannot tell which customers changed.

What this means for you:

  • Keep customer.updated turned on.

  • The poll lists WordPress users of every role. The default Customer TO iPaaS.com template sends shoppers only.

6. Variations should have options

What: Each variant should have its option names and values, such as Size = Large. A variant carries up to three options in Option1 to Option3 (name and value), and any further options in its Attributes list (a name and an option for each entry). A variant without options is written as it is sent.

Why: WooCommerce tells the variations of a product apart by their options. WooCommerce shows a variation without options as matching any option of the product.

What this means for you:

  • Give each variant its options. A variant sent without options is not refused, but WooCommerce treats it as matching any option, so shoppers can get it whatever options they choose.

  • The integration uses product-level (custom) attributes, which need no setup in the store. It does not use WooCommerce's global attributes (Products > Attributes).

  • Options already on a product in WooCommerce are kept; missing ones are added.

7. Product types

What: The integration creates simple, grouped, external (affiliate) and variable products. A grouped product lists the products it groups in GroupedProducts (their WooCommerce product ids); an external product uses ExternalUrl and ButtonText.

Why: These are the product types WooCommerce has.

What this means for you:

  • Leave Type empty to let the integration choose: a product with variants becomes variable, one without becomes simple.

  • Any other Type value stops with WOOC-BIZL-1002. Map Type to simple, grouped, external or variable, or leave it empty.

8. Order status follows WooCommerce; no status or tracking write-back

What: Orders move TO iPaaS.com only. A status change or tracking number in another system is not sent to WooCommerce, and orders placed in other systems are not created in WooCommerce. The Update WooCommerce Order TO iPaaS.com collection writes WooCommerce's order status on every order change, so a status another system sets on the iPaaS.com transaction is replaced at the order's next change in WooCommerce (for example a note, a payment or a refund).

Why: Order status and tracking write-back, and orders FROM iPaaS.com, are not part of this version, so WooCommerce owns the order's status. (Core WooCommerce also has no tracking number field of its own; shipment tracking comes from plugins.)

What this means for you:

  • Mark orders complete or cancelled in WooCommerce by hand. Tracking numbers stay in the shipping system, and iPaaS.com carries them to the other connected systems.

  • If your back office sets the order status in iPaaS.com and that status should stay, change the Status mapping in Update WooCommerce Order TO iPaaS.com to a keep-formula (a formula that keeps the transaction's current value). The other fields still update. Your MiSP can set it up.

  • The same applies to any field another system owns: to stop a TO iPaaS.com collection changing it, change its mapping to a keep-formula rather than deleting the mapping. The default update collections keep the fields WooCommerce doesn't own this way.

9. Images are sent again only when the list changes

What: The default templates don't map images; this applies when your MiSP maps them (for example from an iPaaS.com custom field). Product and variation images are sent as public image addresses. WooCommerce downloads each image when it is sent. The integration sends the images again only when the list of addresses changes.

Why: Sending unchanged images on every update would make WooCommerce download them again and fill its media library with copies.

What this means for you:

  • A new picture uploaded to the same address is not picked up. Give a changed image a new address.

  • Images must be reachable by your store over the internet.

10. Products are mastered in iPaaS.com

What: When a product or variation is updated FROM iPaaS.com, the fields the mapping fills are written, even if someone changed them in WooCommerce since the last sync. Fields the mapping does not fill are left as they are in WooCommerce, with one exception: when a regular price is sent without a sale price, a sale running in WooCommerce ends.

Why: The system that sends the catalogue through iPaaS.com is the source of product data.

What this means for you:

  • Make catalogue changes in the source system, or remove the field from the mapping if WooCommerce should own it.

  • Fields the mapping does not fill are never changed by the integration, except the sale price: removing the sale price from the mapping doesn't keep WooCommerce's sales. If you run sales in WooCommerce, add a static mapping KeepStoreSalePrice = true to the product and variant collections.

  • Customers follow a different rule: see Customer edits made in both systems below.

11. One billing and one shipping address per customer

What: WooCommerce keeps one billing address and one shipping address per customer.

Why: This is how WooCommerce stores customers.

What this means for you:

  • FROM iPaaS.com, the address marked billing (or primary billing) fills the billing address, and the one marked shipping (or primary shipping) fills the shipping address. With no marked billing address, the first address is used. With no shipping address, a new store account gets the billing address for both, and an update leaves the store's shipping address as it is.

  • Other addresses of the iPaaS.com customer are not sent.

  • A customer's username cannot be changed after the customer is created. An update that maps a different username saves the rest of the customer and then reports WOOC-BIZL-1016; a first transfer matched by email to a customer with another username is refused (WOOC-BIZL-1017, see 31).

12. Webhooks need the store to reach iPaaS.com

What: WooCommerce does not retry a failed webhook delivery, and turns a webhook off after more than five failures in a row. WooCommerce signs its webhooks with its own secret, which iPaaS.com cannot check, so the subscription's webhook key is part of the webhook's delivery address.

Why: This is how WooCommerce webhooks work.

What this means for you:

  • Schedule order/poll and customer/poll even with the webhooks on: they bring in missed orders and new customers. The customer poll finds new customers only, so it doesn't bring in a change to an existing customer made while customer.updated was off: Failed deliveries under WooCommerce Webhooks in WooCommerce Connections and Settings says how to bring one in.

  • The order poll does not resend an order whose transfer failed: each poll starts where the last one ended, whether or not that order's transfer succeeded. Fix the cause of the error (WooCommerce Error Messages).

  • If a webhook shows as disabled in WooCommerce > Settings > Advanced > Webhooks, it is turned back on at the next poll. To stop a webhook, turn its scope off in iPaaS.com rather than disabling it in WooCommerce (the poll would turn it back on).

  • Store administrators can see the webhook delivery address. Don't share it or change it.

13. HTTPS only

What: The integration refuses a store address that starts with http://.

Why: WooCommerce accepts the REST API key over HTTPS. Sending it over plain HTTP would expose it.

What this means for you: Serve the store over HTTPS before you install. Your web host can set up the certificate.

14. Checkout drafts and unpaid orders

What: Carts that WooCommerce's block checkout keeps while a shopper is still paying are never sent. By default, orders that never reached processing, completed, on-hold or refunded (pending payment, failed, cancelled) are not created in iPaaS.com.

Why: A cart or a failed payment is not an order the back office should act on.

What this means for you: A pending order is created when it later moves to one of those statuses. If your business ships before payment, add pending to the Add WooCommerce Order TO iPaaS.com filter.

15. Guest orders arrive without a customer

What: An order placed without a store account (a guest checkout) reaches iPaaS.com with the billing name and email address, but with no link to an iPaaS.com customer. An order from a registered customer is linked only when that customer is already in iPaaS.com.

Why: WooCommerce has no customer record for a guest, and the integration doesn't create customers from orders.

What this means for you:

  • Check whether the systems that receive your orders (for example an ERP or accounting system) need a customer on every order.

  • If they do, set them up to post guest orders to their own "cash sale" or "web guest" customer, or to match the order to a customer by its billing email. Your MiSP can help.

16. Every product sent FROM iPaaS.com reaches the store

What: The default Add/Update WooCommerce Product FROM iPaaS.com collection has no filter. Every product iPaaS.com sends is created or updated in WooCommerce, with the status the mapping sends. A new product with no status is published.

Why: Which products belong on the web differs for every business, so the template leaves the choice to you.

What this means for you:

  • If iPaaS.com holds items the web shouldn't sell (for example a full ERP item master with discontinued or trade-only items), add a filter to the collection before you turn on its events, for example only products in your web category or with a "publish to web" flag. Add the same condition to Add/Update WooCommerce Product Variant FROM iPaaS.com, Add/Update WooCommerce Product Inventory FROM iPaaS.com and Add/Update WooCommerce Product Variant Inventory FROM iPaaS.com. A filter on the Product collection alone doesn't stop the others: stock and variant changes for the excluded products then fail with WOOC-NFND-1004, WOOC-NFND-1005 or WOOC-NFND-1003.

  • To load a catalogue hidden, you can map Status to draft so new products arrive as drafts shoppers can't see. While the mapping says draft, every update writes draft: a product you publish by hand in WooCommerce goes back to draft at its next update. Changing the mapping back to the Status translation publishes each active product at its next update.

17. Existing products and customers are linked and updated

What: Before creating a product, the integration looks for a WooCommerce product with the same SKU; before creating a customer, one with the same email address. When it finds one, it links to it and writes the mapped fields over the values the store has. A customer is matched by email address only, so an iPaaS.com customer that carries a store shopper's email takes over that shopper's store account: its name and addresses are overwritten. A store administrator's or shop manager's account is never linked or overwritten (WOOC-BIZL-1015). A store customer whose username differs from the mapped Username is not linked or changed (WOOC-BIZL-1017), and a password is never sent to an existing account (see 31).

TO iPaaS.com, a store customer that isn't linked yet and whose email matches exactly one iPaaS.com customer is linked to that customer, and the transfer updates it instead of creating a second one. The link is made when the customer is read, before the collection's filter is applied: a store customer the filter leaves out is still linked, although none of its fields are written. Store administrators and shop managers are never linked this way either.

Why: WooCommerce has no other way to tell the integration a record already exists, and linking avoids duplicates.

What this means for you: Back up the store, or review products and customers whose SKU or email is also in iPaaS.com, before the first transfer. Start with one product. Make sure the source system's customer emails are each one person's own address: a shared or reused email links two people to one store account.

18. A firewall that allows only listed addresses needs iPaaS.com's addresses

What: WooCommerce itself has no address allowlist, but some hosts and security plugins accept requests only from listed IP addresses. Requests from iPaaS.com are then blocked, and the transfer shows a WooCommerce connection error (often WOOC-EXTN-1001).

Why: The integration's requests come from iPaaS.com's platform, which calls stores from 20.98.221.25 and 69.61.66.130. The current list is kept in Whitelisting iPaaS.com IP Addresses.

What this means for you: Ask your host to add 20.98.221.25 and 69.61.66.130 to the allowed addresses, or to exempt the /wp-json/wc/v3/ path (reading and changing data) from the address rule. Every request still carries your store's REST API key. The Installation Instructions have a paragraph you can forward to your host.

19. No first load of existing records

What: The integration has no initialization (bulk load) for any data type. The first customer/poll brings in only customers who registered in the last Customer Poll Initial Days, and the first order/poll only orders changed in the last Order Poll Initial Days.

Why: This version does not offer initialization. The first polls look back a limited number of days, so a new subscription doesn't send a store's whole history to every connected system.

What this means for you:

  • Existing customers who registered before the first poll's window reach iPaaS.com only when they change (through customer.updated) or place an order that links them.

  • Older orders reach iPaaS.com only when they change in WooCommerce.

  • To bring in more history on a new subscription, raise Order Poll Initial Days and Customer Poll Initial Days before the first polls run. Agree this first with whoever runs your other connected systems: older orders reach every one of them, where they may be picked, shipped or invoiced again. Values above ten years (3650 days) are treated as ten years, and a blank, 0 or invalid value uses 7.

20. Categories and tags are created by name

What: The default templates don't map categories or tags; this applies when your MiSP maps them. Product categories and tags are sent by name. A category or tag named on a product that doesn't exist in the store is created by name during the product transfer. A misspelt name creates a new category or tag. A bare category name (one without a Parent > Child path) that doesn't exist is created as a new top-level category.

Why: This version has no collection of its own for product categories.

What this means for you:

  • Use the store's exact category and tag names in the source system, and a Parent > Child path for a category that sits under another. Review new categories and tags in WooCommerce after the first transfers, and merge or delete any you didn't mean to create. A category or tag sent with its WooCommerce id is used as it is.

  • Brands work differently: a brand is sent by its WooCommerce brand id and is never created. A brand entry without an id is noted in the log and left out.

21. Customer edits made in both systems

What: Customers are edited in WooCommerce and in iPaaS.com. When a customer is updated FROM iPaaS.com, the integration compares each mapped field with the WooCommerce values iPaaS.com last received. A field is held back (WooCommerce's value kept) only when it changed in WooCommerce since then and iPaaS.com's value did not change. When both changed, iPaaS.com's value is written.

Why: The comparison uses the WooCommerce Sync Baseline customer custom field, which the Customer TO iPaaS.com collection fills and the Customer FROM iPaaS.com collection reads back.

What this means for you:

  • Keep both WooCommerce Sync Baseline mappings in place. Without them, every mapped field is written, and changes made in WooCommerce are overwritten.

  • A customer that has never come TO iPaaS.com from this store has no baseline yet, so every mapped field is written on its first update FROM iPaaS.com, including when an existing WooCommerce customer is linked by email.

  • In the rare case where iPaaS.com changes a field and then changes it back before WooCommerce reports the first change, the first change can come TO iPaaS.com again.

22. Two WooCommerce stores in one company

What: iPaaS.com keeps one WooCommerce Sync Baseline value per customer, tagged with the subscription that wrote it. When two WooCommerce subscriptions in the same company send the same customer, it holds the baseline of the store that last sent that customer TO iPaaS.com, and the other store ignores it.

Why: iPaaS.com keeps one value per customer custom field.

What this means for you: When the baseline was written by the other store, an update FROM iPaaS.com writes every mapped field to this store, so a change made in this store's WooCommerce that iPaaS.com has not received can be overwritten. An update that would change nothing is not written, so the two stores don't pass a customer back and forth. If customers are edited in both stores, decide which store's customer changes iPaaS.com should take, and keep the customer webhooks on in both.

One store per subscription. A subscription's links are WooCommerce record ids, which every store numbers from 1. The first store a subscription connects to is recorded (the persistent value Linked Store), and a Store URL changed to another store is refused with WOOC-BIZL-1014 before anything is written. A store that moved to a new address is recognised by this subscription's webhooks in it. A staging or test copy of the store carries those webhooks too, so it would be accepted as the same store: never point a live subscription's Store URL at a copy of the store; give a test copy its own subscription. Connect each store with its own subscription.

23. The order's phone number is not sent

What: An order's billing and shipping addresses reach iPaaS.com with name, company, street, city, region, postal code and country, and the order carries the billing email. The phone number on the order is not sent.

Why: An iPaaS.com transaction address has no phone field.

What this means for you:

  • If a system that receives your orders needs the shopper's phone number (for example a carrier), ask your MiSP to map it to a transaction custom field, and to read it from there in that system's integration.

  • A registered customer's phone number reaches iPaaS.com on the customer's addresses.

24. Webhooks are sent when the store has visitors

What: WooCommerce queues each webhook and sends it from its background scheduler, which WordPress runs when someone visits the site (or from a server task, if the store's host has set one up). On a store with few visitors, an order or customer can reach iPaaS.com minutes or hours after it was made.

Why: This is how WooCommerce and WordPress schedule background work: WooCommerce sends webhooks from its scheduled-actions queue, and WordPress's built-in scheduler runs only when a page of the site is loaded. The integration can't change this; it receives each webhook as soon as WooCommerce sends it.

What this means for you:

  • Keep the order/poll and customer/poll scopes on. The order poll brings in every order changed since the last poll; the customer poll brings in new customers only, so a change to an existing customer waits for its webhook (see 5).

  • Webhook deliveries that are still waiting are listed as pending actions in WooCommerce > Status > Scheduled Actions.

  • If your store is quiet but orders must arrive quickly, ask your web host to run the WordPress scheduler from a server task (often called a "real cron job") every few minutes.

25. A line removed from an order after it reached iPaaS.com stays on the transaction

What: When a line is removed from an order in WooCommerce after the order reached iPaaS.com, the order's update leaves that line on the iPaaS.com transaction. The order total follows WooCommerce, so the transaction can show a line that WooCommerce no longer has.

Why: An update to an iPaaS.com transaction keeps any line the update leaves out; iPaaS.com does not remove it.

What this means for you:

  • The transaction's other lines, its totals and its status still follow WooCommerce.

  • Remove the old line in iPaaS.com, or in the back office that receives your orders.

  • Better still, don't edit an order after it was sent: cancel or refund it through WooCommerce instead, so the change reaches iPaaS.com as a cancellation or a Return.

26. Removing a mapping that sends data TO iPaaS.com clears that field on the next update

What: In the collections that send orders, refunds and customers TO iPaaS.com, deleting a mapping does not leave the field alone in iPaaS.com: the next update of a record that is already in iPaaS.com clears that field (for example the company on an address, the phone, or the coupon code). Deleting a mapping marked "(Required.)" for an amount (payment, tax or discount amount) does not stop the transfer either: iPaaS.com saves the amount as 0.

Why: An update replaces the whole iPaaS.com record with what the collection sends, so a field the collection no longer sends becomes empty. iPaaS.com refuses some missing values (a line's SKU, an order's status, a payment's method) but not amounts. The default collections already keep the fields WooCommerce has no value for, so values your other systems set survive an update: for example an order line's shipped quantity, weight and position, a shipping address's ship date, a tax's original amount and a coupon's discount method and percent. What stays exposed is a mapping you delete or replace.

What this means for you:

  • To stop sending a field without clearing it, change its mapping to a keep-formula instead of deleting it, for example return DestinationValue != null ? DestinationValue.PhoneNumber : null; for the phone. Your MiSP can set it up.

  • Keep every mapping marked "(Required.)" in place.

  • Collections that send data FROM iPaaS.com to WooCommerce behave the other way round: a field you unmap is simply not sent, and WooCommerce keeps its value.

27. An order number another system already sent to iPaaS.com is refused

What: iPaaS.com refuses a new transaction whose number is already used in your company by another transaction, even one from a different system, with NFND-1029 "Duplicate transaction found! Transaction Number: …". WooCommerce numbers orders from 1 upward, so a second WooCommerce store, or another sales channel that also uses plain numbers, can send a number this store sends later.

Why: iPaaS.com keeps transaction numbers unique within a company.

What this means for you:

  • If another system in your company sends orders with plain numbers, change the TransactionNumber mapping in the three order collections (Add Order, Update Order and Add Refund) to add a prefix for this store, for example return "WEB-" + Number;. Change all three the same way before the first order arrives, so updates and refunds find their order.

  • An order refused this way is not written. It shows in Error Logs with NFND-1029 and the order's number, and iPaaS.com tries the transfer again later; each retry is refused the same way until the number is changed (for example with the prefix above).

  • After the change, resend the order from iPaaS.com.

28. Two collections of the same type TO iPaaS.com must not overlap

What: You can add a second collection of a type that already has one (for example a second customer collection for trade customers). A record whose filters match both collections goes through both, one after the other. When they send data TO iPaaS.com, the later collection replaces the whole iPaaS.com record with only the fields it maps: a field only the first collection maps is cleared, and an amount is saved as 0. If that leaves a value iPaaS.com requires empty (a customer with no first name, last name or company), iPaaS.com refuses the later collection's update with VALD-1039 and retries it. A keep-formula in the later collection does not help for orders: it keeps the value iPaaS.com had before the transfer, so it also undoes what the first collection just wrote. Child records (order lines, payments, addresses) that the later collection doesn't send are left as they are. For a store customer that isn't in iPaaS.com yet, both collections try to create it: the first one creates the customer, and iPaaS.com refuses the second with BIZL-1006 (the email is already in use), so the Error Logs show a failed transfer although the customer arrived.

Why: Each collection sends its own complete version of the record, and an update replaces the record (see 26).

What this means for you:

  • Give the collections filters that never match the same record, for example return Role == "wholesale_customer"; in the second customer collection and && Role != "wholesale_customer" added to the template one.

  • Collections that send data FROM iPaaS.com to WooCommerce may overlap: a record matching both is sent twice, each collection's mapped fields are written, fields a collection doesn't map are left as they are in WooCommerce, and the product is found by its SKU, not created twice.

29. Products need a SKU

What: A product sent FROM iPaaS.com needs a SKU. A product whose mapped SKU is empty is not created or updated, even though WooCommerce itself allows a product without one.

Why: The SKU is how the integration finds a product it already created, or one the store already has, so that it links to it instead of creating a duplicate (see 17).

What this means for you:

  • A product with an empty SKU stops with WOOC-VALD-1005. Give the product a SKU in its source system, or map one, and transfer it again.

  • Variants may have no SKU: a variant without one is matched to the store variation with the same options.

30. A sale price above the regular price shows no sale

What: A sale price above the regular price is sent to WooCommerce as it is given.

Why: WooCommerce shows a product as on sale only when its sale price is below its regular price.

What this means for you:

  • No sale shows in the store for that product or variant, and no error is raised. Correct the prices in the source record, or the price mappings.

  • When a regular price is sent without a sale price, a sale running in WooCommerce ends, unless the collection has a static mapping KeepStoreSalePrice = true (see 10).

31. Customer usernames and passwords

What: A customer's Username is sent when the customer is created. On an update it is sent only when it is the same as the username the customer already has in WooCommerce. A mapped Password is sent only when the integration creates a new store account: never on an update, and never when an existing store customer is linked by email. An email is needed only when the customer is created (WOOC-VALD-1012); an update without an email is written.

Why: WooCommerce does not let a username change after the customer is created. A password sent on an update would let iPaaS.com reset a shopper's store login, so it goes with a new account only.

What this means for you:

  • An update of a customer already linked that maps a different username leaves the username out, saves the rest of the customer, and then reports WOOC-BIZL-1016. The customer's other changes are already saved. Leave Username unmapped for customers that already exist, or map the store's username.

  • The first transfer of an iPaaS.com customer whose email belongs to a store customer with a different username writes nothing and links nothing (WOOC-BIZL-1017): the two may be different people. If they are the same person, leave Username unmapped or map the store's username; if not, give the iPaaS.com customer its own email address.

  • Map Password only to give new store accounts their first password. A shopper's password can't be changed from iPaaS.com; they change it in the store. A password is never written to the logs.

32. A customer written FROM iPaaS.com comes back once TO iPaaS.com

What: When the integration writes a customer to WooCommerce FROM iPaaS.com, WooCommerce reports the change through its customer.updated webhook, and the customer is sent back TO iPaaS.com once, as an ordinary update. It stops there: the update carries the values that were just written, and a customer update FROM iPaaS.com that would change nothing in WooCommerce is not written, so WooCommerce reports no further change.

Why: WooCommerce sends customer.updated for every change to a customer, whoever made it, so the integration's own write is reported like a change made in the store.

What this means for you:

  • After a customer update FROM iPaaS.com, expect one customer transfer TO iPaaS.com for the same customer shortly afterwards. This is expected and needs no action.

  • Keep customer.updated on. It is also how changes made in the store reach iPaaS.com (see 5).

  • The returning update is an ordinary TO iPaaS.com update, so 26 and 28 apply to it: keep every field the Customer TO iPaaS.com collection should not clear mapped, or mapped to a keep-formula.

Note: Products, variants and stock written FROM iPaaS.com do not come back: this version sends no products TO iPaaS.com.

33. Order statuses added by plugins need a translation row

What: The default WooCommerce Order Status TO iPaaS.com translation has a row for each of WooCommerce's own order statuses: pending, failed, on-hold, processing, completed, refunded, cancelled and checkout-draft. Plugins (for example for shipping, bookings or pre-orders) can add order statuses of their own, which have no row. iPaaS.com refuses an order whose status has no row, and nothing is written. The Add WooCommerce Order TO iPaaS.com filter also creates orders only in the processing, completed, on-hold and refunded statuses (see 14).

Why: Every store uses different plugins, so the template can only cover WooCommerce's own statuses.

What this means for you:

  • Before the first order arrives, list the order statuses your store's plugins add. For each one, add a row to the WooCommerce Order Status TO iPaaS.com translation, with the status as WooCommerce sends it as the source and the iPaaS.com transaction status it means as the target. Your MiSP can set it up.

  • If orders that are created in a plugin's status should reach iPaaS.com, add that status to the Add WooCommerce Order TO iPaaS.com filter as well, the same way as pending in 14.

  • Test each new status with one order in a staging subscription before relying on it in production.

  • If an order was refused this way, add the missing row, then resend the order from iPaaS.com or make a change to it in WooCommerce.

34. One payment per order, sent once the order is paid

What: An order reaches iPaaS.com with one payment: the order total, with the store's payment method and the payment gateway's transaction id, sent once WooCommerce records the order as paid. An order that arrives before it is paid (for example on hold, waiting for a bank transfer) has no payment; the payment is added by the order's next update after WooCommerce marks it paid. A refund arrives as its own Return transaction with a negative payment.

Why: WooCommerce keeps one payment method and one paid date for each order. It has no record of part payments or overpayments, and a payment that the gateway cancels or voids changes the order's status instead of adding a payment.

What this means for you:

  • Deposits or part payments taken through a payment plugin aren't sent as separate payments. iPaaS.com receives the full order total once the order is paid.

  • A cancelled or failed payment reaches iPaaS.com as the order's status through the WooCommerce Order Status TO iPaaS.com translation, not as a change to the payment. In the default translation, a cancelled order becomes Cancelled and a failed one Awaiting Payment.

  • If your back office needs to know whether an order is paid before its payment arrives, map the order's paid date or status in the order collections. Your MiSP can set it up.

Placeholder Values to Replace Before Go-Live

The default templates carry the values below as placeholders. Replace each one before the first order arrives; until you do, iPaaS.com refuses every order that uses it, and nothing is written. The Installation Instructions give the steps.

Where

Placeholder value

Replace with

Line SKU formula in the order line child collections of Add WooCommerce Order TO iPaaS.com, Update WooCommerce Order TO iPaaS.com and Add WooCommerce Refund TO iPaaS.com

REPLACE with your SKU for products without one

The SKU of an iPaaS.com product used for lines whose WooCommerce product has no SKU (for example MISC-ITEM)

The same three line SKU formulas

REPLACE with your fee item SKU

The SKU of an iPaaS.com product that stands for fees (for example FEE)

Every target in the WooCommerce Payment Method TO iPaaS.com translation

Text that starts with REPLACE with

The matching payment method of your iPaaS.com company; add a row for every payment method your store offers

Every target in the WooCommerce Shipping Method TO iPaaS.com translation

Text that starts with REPLACE with

The matching shipping method of your iPaaS.com company; add a row for every shipping method your store offers


This article documents 34 known limitations of the WooCommerce integration. For the detail of each collection, see the WooCommerce mapping collection descriptions and mapping documentation.

Related Documents

Did this answer your question?