Troubleshooting WooCommerce

When you save, Qoblex checks that it has received the connection credentials from WooCommerce. If they have not arrived yet, the save is blocked with: “We have not received your integration credentials from WooCommerce yet. Please try saving again or reach out to support for help”. This check runs on every Save, and also when you use Finish Setting Up Your store, because that button saves your settings before it opens the import prompt. Wait a moment and select Save again. Confirm the WooCommerce authorization step was completed and that you connected the store you intended. If the message persists after authorization, contact support before starting a product import.

Every WooCommerce store must have at least one Qoblex location to fulfill its orders from. If you leave the order-locations field empty, the save is rejected with: “Please select at least one location to sync orders to”. In the Sale Order Synchronization section, under “Which locations to fulfill WooCommerce sale orders from?”, select one or more Qoblex locations, then save again. If you select more than one, use the up and down arrows to set fulfillment priority: orders are filled from the first location that has available stock.

If you set inventory levels to Sync from Qoblex to WooCommerce, Qoblex needs to know which warehouse levels to publish to the store. If no inventory location is selected, the save is rejected with: “Please select at least one location to sync inventory levels to WooCommerce”. In the Inventory levels Synchronization section, under “Which warehouse inventory levels are reflected in your WooCommerce store?”, select one or more locations, then save again. Select multiple locations to aggregate their stock into the single WooCommerce quantity. This location requirement only applies when inventory sync is set to Sync from Qoblex to WooCommerce. When it is set to Do not sync, no inventory location is required.

The Pricing Synchronization section checks your price lists before it will save. You may see any of these messages: – “Price and Compare At price lists must be different” – choose a different list for the Compare At price than for the Price. – “Price and Compare At price lists must have the same currency” – pick two lists that share a currency. – “Price price list must have the same currency as your store (<currency>)” and “Compare At price list must have the same currency as your store (<currency>)”, where <currency> is your WooCommerce store currency – choose custom lists whose currency matches your store. Fix whichever lists are flagged under “Which price list would you like to assign to your product prices on your store?” and its Compare At counterpart, then save again. Because all WooCommerce settings save together, a pricing error blocks the whole page even when the other sections look complete.

If you try to navigate away while you have pending settings changes, Qoblex asks: “You have pending changes, if you leave this page you will lose those changes. Do you want to continue?”. Choose Cancel to stay on the page and save your work with Save. Choose OK only when you genuinely want to discard the changes.

Qoblex imports WooCommerce orders on a schedule rather than the instant they are placed, so a short delay is normal. New and changed orders are picked up automatically every few minutes, so wait a little and re-check. If an order still does not appear, open Activity and look for a WooCommerce message. When an order cannot be processed, Qoblex records a warning there that begins “Unable to process WooCommerce order.” followed by the reason. Successful imports are logged too, as “Order [number] successfully processed from WooCommerce”. If you see neither, confirm the store is still connected. See Sales Order Sync Settings for how orders map in. WooCommerce order statuses map to Qoblex order states: “completed”, “shipped”, and “delivered” arrive Closed; “cancelled” arrives Cancelled; “refunded”, “trash”, and “checkout-draft” arrive as a Quote; everything else arrives Open.

If Activity shows “Unable to process WooCommerce order. No valid location found for the Integration …”, Qoblex could not decide which location to place the order at. Qoblex uses your Sale Order Synchronization order locations first, falls back to your inventory locations, and finally to the store’s default location mapping. Open the settings page and make sure at least one order location is selected under “Which locations to fulfill WooCommerce sale orders from?”, then save. Once a valid location is set, the order is retried automatically on the next import cycle.

If Activity shows “Unable to process WooCommerce order.” followed by an allocation error, Qoblex created the order but could not reserve stock for it from your selected locations. The message lists the reason returned by Qoblex (for example, not enough available stock at the chosen locations). Provision the missing stock, or adjust your order locations and priority so a location with stock is tried first, then wait for the next import cycle. Orders that fail this way are logged as a warning and left for retry, not silently dropped.

Qoblex matches each WooCommerce order line to a Qoblex variant by its SKU, or by the WooCommerce variant/product reference recorded when the product was imported. If a line item has a SKU that does not exist in Qoblex and was never imported, Qoblex cannot line it up with one of your products. Import the product first (or create it in Qoblex with the matching SKU), then let the order re-import. See Finish Setup and Import Products for importing your catalog and Product Sync Settings for how matching is chosen.

Whether Qoblex applies product and price changes coming from WooCommerce depends on your sync directions. Product information changes are only brought in when “How would you like us to sync your products information?” is set to Sync from WooCommerce to Qoblex or Sync both ways. Price changes are only brought in when “How would you like us to sync your product prices?” is set to Sync from WooCommerce to Qoblex. Open the settings page, set the relevant direction to a WooCommerce-source option, then save. If a setting is left on Do not sync or on Sync from Qoblex to WooCommerce, WooCommerce changes for that data are ignored on purpose. See Product Sync Settings and Pricing Sync Settings for what each direction does. Inventory levels for WooCommerce sync outbound only. The inventory dropdown offers Do not sync or Sync from Qoblex to WooCommerce, so a stock change made in WooCommerce is never pulled back into Qoblex. See Inventory Sync Settings.

When product matching is set to Match products by SKU, Qoblex needs at least one SKU on the incoming product to line it up with an existing Qoblex product. If none of its variants have a SKU, Activity shows: “Could not sync [product] … The product SKUs are not set.” The same happens with Match products by barcode when no barcode is set, shown as “The product barcode(s) are not set.” Add SKUs (or barcodes) to the product in WooCommerce, or switch “How would you like Qoblex to identify and match similar products across different stores?” to Match products by name, then let the product re-sync.

If the incoming product is not yet mapped but one of its SKUs (or barcodes) already belongs to a different, already-mapped Qoblex product, Qoblex will not sync it, to avoid attaching the store to the wrong product. Activity shows “Could not sync [product] … [existing product] has one or more similar SKU.” (or “similar barcode”). Correct the duplicate identifier in WooCommerce or in Qoblex so each product has its own SKU/barcode, then let the product re-sync. This guard only fires for products that are not already mapped to the store.

Qoblex can import WooCommerce simple and variable products only. If a product is another WooCommerce type (for example grouped or external/affiliate), Activity shows “Unsupported product type … Only simple and variable product types are supported” and the product is skipped. Change the product to a simple or variable type in WooCommerce if you want Qoblex to manage it, or leave it as-is and manage that item directly in WooCommerce.

This is expected. When a product is deleted in WooCommerce, Qoblex removes the link between that product and the store, it does not delete your Qoblex product. Your Qoblex product and its stock history stay intact and simply stop being tied to the deleted WooCommerce product. If you also want it gone from Qoblex, remove it in Qoblex yourself.

Qoblex can only process a WooCommerce refund against an order it already has. If the original order was never imported into Qoblex, the refund is skipped. First confirm the order exists in Qoblex (see the order-not-appearing rows above); once it does, the refund is picked up on the next import cycle. If a refund cannot be processed, Activity shows a warning beginning “Unable to process WooCommerce Refund/Return.” with the reason. A common reason is that a refunded line cannot be matched back to an order item, or the refund is for more than the amount or quantity Qoblex has invoiced. Re-check the refund in WooCommerce and confirm it applies to items and amounts that exist on the imported order. If you also use the Shipping DZA add-on, Qoblex intentionally skips WooCommerce refund and return processing to avoid conflicts, and logs “ShippingDZA integration is enabled. Refund/Return processing is skipped to avoid conflicts” on Activity. Handle those refunds through your Shipping DZA workflow instead.

Disconnecting removes the connection and the store’s WooCommerce webhooks, so no further data moves between the two systems. If the store still appears afterward, refresh the Integrations page. If it remains, open it again and retry the disconnect. See Disconnect WooCommerce for the full steps.

If a problem persists, collecting a few details first makes it much faster to resolve: your WooCommerce store URL, the exact message shown (on the settings page or on Activity), which settings section it came from, your selected order and inventory locations, your sync directions, your chosen price lists, and whether the store was still in setup or you had unsaved changes.