WooCommerce as a Source

401 means invalid or expired credentials: regenerate the Consumer Key and Consumer Secret in WooCommerce admin, re-enter them, confirm the key user's WordPress role hasn't been restricted by a security plugin, and confirm a pretty permalink structure is set. 403 means the server accepts the connection but blocks access: a WAF, security plugin (Wordfence, Sucuri), or host firewall is blocking Flxpoint's outbound IPs. The vendor's host must whitelist Flxpoint's IPs; contact Flxpoint Support for the current list.

A 502 means the vendor's WooCommerce server returned a server error before completing the request (an nginx signature points to the vendor's web server, not Flxpoint). Common causes: the store is down or under heavy load, a hosting resource limit (memory/timeout) is hit during the catalog fetch, or a plugin conflict crashes the REST API. Ask the vendor to check their hosting error logs for PHP fatal errors or timeouts in the same window. If it persists, pause the schedule to avoid flooding the server and contact Flxpoint Support.

The Send Fulfillment Requests template references Source Shipping Method → Shipping Code, but no shipping method is configured on the WooCommerce source. Either add a shipping method (Sources → [Source] → Shipping Methods) so a code exists to map, or remove the Shipping Code mapping from the template: WooCommerce will apply its own default. Most WooCommerce vendor setups do not need a specific method passed from Flxpoint.

The most common cause is that the vendor's tracking plugin or format isn't one Flxpoint supports. Confirm which method they use; supported options are the paid WooCommerce Shipment Tracking plugin, the free Advanced Shipment Tracking plugin by Zorem, or private order notes in the exact TRACKING: [Carrier] - [Tracking Number] format. If they run a different plugin (e.g. Shipmate) alongside the paid one, disable one to resolve the conflict. Also confirm the Woo order ID was stored during Send Fulfillment Requests: if that failed, Get Shipments has nothing to look up.

Flxpoint is referencing a variation ID that no longer exists on the vendor's store, usually because a product was deleted and recreated (its variation IDs changed) while Flxpoint's External Listing IDs still point to the old ones. Re-run Get Inventory [Primary] to refresh the External Listing IDs to the current variation IDs, then confirm the listings re-linked. Stale IDs already on channel listings may need those listings re-built or re-linked after the refresh.

Check two things on the vendor's store: the product type must be Variable (not Simple): only variable products expose variants via the /variations endpoint, and each variation must be in Published status (draft variations aren't returned). Also confirm the variant-level fields (Variant SKU, Quantity, Price) are mapped in your Get Inventory template. If variants imported before and then vanished, the vendor may have switched the product from Variable to Simple, which removes all variation data.

This error occurs when Flxpoint attempts to sync price or quantity to a variation ID that does not exist on the WooCommerce store. A common cause is Flxpoint incorrectly storing the parent product ID as the variation ID (e.g., attempting to PUT to /variations/123 where 123 is the parent ID). To resolve this, unlink and then relink the affected listings in Flxpoint to refresh the correct variation mappings. Additionally, check for WooCommerce plugins (such as AI enhancement tools) that may be deleting and recreating variations, as this causes transient 404 errors during the sync window.

In WordPress, go to WooCommerce → Settings → Advanced → REST API and click Add Key. Enter a description, select the user the key should run as, and set Permissions to Read/Write, then click Generate API Key. The Consumer Key and Consumer Secret are shown only once: copy them immediately. Your Domain is the store URL shown in your browser, including https://. Enter all three into the Flxpoint connection form and click Test Connection.

Unlike the WooCommerce channel integration, the source integration has no separate draft/published filter. Get Inventory pulls whatever the REST API returns for your key's access scope; Draft products are typically not returned unless the key's user has draft-viewing permissions. If draft products do appear in your import, add a Post-Mapping Workflow rule with a Do Not Import action to filter them out by a status field value.

The full product catalog in batches: title, SKU, description and short description, regular and sale price, stock quantity, weight and dimensions (convert to lbs/in if the store uses different units), product categories (up to two levels), and images (parent gallery + featured image). For variable products, each variant is fetched with its own SKU, price, stock, dimensions, and a single variant image. The full feed is re-pulled every run: there is no delta or incremental mode.

Three sources. The default is the official WooCommerce Shipment Tracking plugin (paid). If the vendor doesn't have it, the recommended free alternative is the Advanced Shipment Tracking plugin by Zorem: once installed, Flxpoint reads from it automatically. The third needs no plugin: the vendor adds a private order note in the exact format TRACKING: [Carrier] - [Tracking Number] (e.g. TRACKING: UPS - 1Z999AA10123456784), one note per package for split shipments. Running multiple tracking plugins at once (e.g. Shipmate alongside the paid plugin) causes conflicts: choose one source per store.

It controls the maximum age of Fulfillment Requests that Get Shipments checks for tracking updates (default ~90 days). Flxpoint uses the WooCommerce order ID stored during Send Fulfillment Requests to query the store for shipment data. If older FRs never got tracking, temporarily increase the lookback and re-run. For most accounts 90 days is enough: extend it only when actively recovering old untracked orders.

Send Fulfillment Requests creates a new order in the vendor's store via the REST API using the same Consumer Key and Consumer Secret from your connection. Flxpoint sends the External Listing ID (saved during Get Inventory) as the item identifier, along with billing/shipping address, line-item quantity, shipping line, and totals from your mapping template. WooCommerce returns a Woo order ID as the acknowledgement, which Flxpoint stores and later uses in Get Shipments to fetch tracking. The Fulfillment Request Number is not passed: WooCommerce assigns its own order ID.