Bob Go Smart Shipping for WooCommerce

4.0.58

• Order updates no longer send the order’s item list to Bob Go when nothing about the items has changed. Bob Go treats the list it receives as the complete set, so an item it holds that the update leaves out is deleted — and when that item has already been shipped, Bob Go refuses the whole update, taking the address or status change sent with it. One store spent a day with an order failing to update every hour for this reason. The list is still sent in full when an order is created, and whenever the items genuinely change.
• An item change made to an order that was linked to Bob Go before this update now reaches Bob Go the first time. Whether an update needs to carry the item list is decided against a record of the list Bob Go last accepted, and an order linked by an earlier version, or by anything other than the normal create path (an incoming update from Bob Go, the check that repairs a wrong link, or being adopted because Bob Go already held the order under the same number), had no such record. The list was left out and the items as they stood at that moment were recorded as though Bob Go had them, so a first item edit was lost and only a second would have arrived. Every order already linked to Bob Go is now given that record in the background shortly after the plugin updates, and an order linked by one of those other paths records its list at the point of linking.
• An update Bob Go has already refused is no longer sent again unchanged. Every edit and every hourly check from Bob Go queued the same rejected request afresh, which filled the sync log without ever succeeding. The order is still marked as failed and still shown in the failed-sync notice, and the moment anything about it changes the update is sent again immediately. A request that failed to reach Bob Go, or that Bob Go answered with a server error, is still retried as before.
• Completing an order that already has a shipment now reaches Bob Go. The status update carried the order’s item list with it, so Bob Go refused the whole request once an item had shipped, and the status change was lost with it. Cancelling is sent the same way and is no longer held up for that reason — but Bob Go does not cancel an order whose items have already shipped, so such an order cancelled in WooCommerce stays open on Bob Go.
• An order taken back out of Cancelled in WooCommerce is no longer left cancelled on Bob Go. A merchant who cancelled an order, then received payment and set it back to Processing, saw the payment land on Bob Go while the order itself stayed cancelled there: the plugin sent the status only when an order was cancelled or completed, and Bob Go changes nothing it is not told about. Processing is now sent as well, so the order reopens. Because Bob Go keeps the status it is given, moving a completed order back to Processing in WooCommerce now reopens it on Bob Go too. Orders awaiting payment (Pending, On hold) and refunded orders are unchanged: those reach Bob Go as a payment status, which is how it records them.
• The suburb a buyer types at checkout now reaches Bob Go on the classic (shortcode) checkout. On a store set to “Default to customer shipping address” under WooCommerce → Settings → Shipping, a buyer who unticked “Ship to a different address” had their suburb dropped from the shipping quote: the plugin read the hidden shipping suburb field rather than the billing one they had actually filled in. Which address the buyer chooses now decides which field is used, instead of the store’s default setting.
• Orders now reach Bob Go with a suburb even where WooCommerce did not copy it onto the shipping address. WooCommerce normally mirrors the billing suburb onto the shipping address when “Ship to a different address” is off, but custom checkout templates, checkout field editors and replacement checkout plugins can interrupt that, leaving an order with a complete shipping address and no suburb. Where the order ships to the billing address, the billing suburb is now used. An order genuinely going to a different address is left alone, so a suburb from another city is never attached to it.
• The Bob Go shipping line on an order now reads in plain words. The service code — an identifier such as “bobgo_286837_15_0”, which tells Bob Go which service the buyer chose at checkout — is no longer shown on the order, and the rate detail below the shipping method is labelled “Description”, “Delivery from” and “Delivery by” rather than by its raw field names. This changes the display only: the service code is still recorded against the order and still sent to Bob Go exactly as before.
• Tested against WordPress 7.1 and WooCommerce 11.1.

4.0.50

• The Overview tab now reports what the plugin has observed rather than what it has been configured with. “Connected” previously meant only that an API key was stored, and the “Last Sync” tile showed when the hourly background check last ran under a label that reads like order sync — so a store whose orders were never reaching Bob Go could show nothing but green ticks. The tab now shows whether Bob Go has ever confirmed the API key and which account it belongs to, when the last order was actually sent and which one it was, the exact error Bob Go returned if the most recent attempt failed, and whether updates from Bob Go are arriving.
• Added a Background Jobs card. Every order sent to Bob Go, every status update and the hourly reconciliation are queued through WooCommerce’s Action Scheduler, so a queue that is not being processed stops orders reaching Bob Go while every setting on the page stays valid. The card shows how many orders are queued and waiting to be sent, whether WordPress is running its own scheduled events at all, whether the recurring check is scheduled, and when it last completed.
• When something is stopping orders from reaching Bob Go, the Overview now says so at the top of the page in one sentence, names the most likely cause, and lists the steps to clear it — including what to ask your host for, when the cause is a site or hosting setting rather than a Bob Go one. Each individual warning carries the same steps under a “How to fix this” link, so most of these situations can now be resolved without contacting support.
• The Overview no longer reports “none yet” for order activity it cannot actually see. Where the plugin’s own sync log could not be created — some hosts do not allow it — the affected tiles now read “Unknown” and explain why, instead of looking like a store that has never sent an order.
• The channel identifier sent with every request is now shown on the Overview, next to a link to your Bob Go sales channels. When it does not match a sales channel — for example www against non-www after a domain change — Bob Go answers with a 404 that previously left the connection looking healthy.
• A store left on the Sandbox or Development environment is now flagged on the Overview, since orders sync to that account and production API keys will not work against it.
• Test Connection is now available on the Overview tab, and the Overview separates configuration from health so a settings choice no longer reads as a fault.
• Test Connection now records what it proved: a test that Bob Go answers definitively marks the API key verified (or rejected) on the Overview, instead of leaving it “Not verified” after a successful test. When Rates at Checkout is disabled or no API key is stored yet, the button now says so — and where to go next — rather than doing nothing.
• Fulfillment webhooks now count as updates from Bob Go on the Overview. They were logged under the same name as the order panel’s own fulfillment fetch, so a store whose only inbound traffic was fulfillment events read “No webhook has reached this store” while webhooks were arriving and processing fine.
• An order held back because Bob Go could not confirm whether it already exists is now reported as held, rather than as a transport failure that “never got a response”. A failed status update is described as a failed update, not as orders failing to arrive.
• Times on the Order Sync card are now shown as relative times (“2 hours ago”) like the rest of the page, instead of raw UTC timestamps.
• Pressing Test Connection on the Overview now updates the status cards above it straight away. The test records what it proved, but the cards were rendered before it ran, so the page could report “Not verified” directly above a successful test result until it was reloaded.
• A rejected request is no longer reported as a bad API key. Bob Go answers with the same 401 when the channel identifier does not match a sales channel, and when rates at checkout is switched off for that channel — both on a perfectly valid key — so the Overview now names all the causes and puts the checks that cost nothing before generating a new key.
• Webhook registration failures are now explained in the plugin’s own words. A rejected key produced “Failed to register webhooks: You’re not logged in. Please log in and try again.”, which sent merchants looking for a login screen; it now names the API key and channel identifier, which is what the plugin can actually tell you about.
• Test Connection results now link to the tab you need, rather than naming it and leaving you to find it.
• Tested against WooCommerce 11.

4.0.43

• The connection check now verifies your API key against your Bob Go account. The Advanced tab shows your Bob Go account code.
• Re-syncing an order now sends the order to Bob Go rather than only fetching its shipment details back. Orders edited after their first sync are brought up to date, orders whose stored Bob Go reference no longer exists are re-resolved instead of failing against it forever, and the per-order “Re-sync” button reports a failure instead of reporting success without having sent anything.
• Fixed the “orders failed to sync” warning on the orders page reporting failures that “Re-sync all failed orders” then could not find. Both now work from the same list, and orders in a status that can never sync are no longer counted.
• Disconnecting now also removes the link between your WooCommerce orders and their Bob Go orders, so reconnecting to a different Bob Go account no longer leaves orders pointing at the old one. The links are removed in the background, the orders are not re-sent, and nothing is deleted on Bob Go itself.
• Every request to Bob Go now identifies the plugin version it came from, so support can diagnose a store without having to ask which version is installed.

4.0.36

• Fixed rates at checkout ignoring shipping-class, SKU and vendor based rate rules. The product SKU, shipping class and (on multi-vendor stores) vendor are sent with each cart item again, so rules configured on those in your Bob Go account are applied to the rates your buyers see.
• Fixed the milestone icons on the tracking page rendering unstyled — the wrong size, colour or spacing — because the widget’s HTML sanitiser discarded the styling Bob Go sends with each tracking step. Styling supplied by Bob Go is now applied as intended, while anything that would load an external resource is still removed.
• Fixed the tracking page showing nothing when a second order number was looked up without reloading the page. The same fault also left a second error message blank.
• Links out to the Bob Go workspace — from the Resources sidebar, the order panel and the rates at checkout connection notices — now follow the environment the plugin is connected to, instead of always opening the production workspace.
• Update the plugin directory listing

4.0.31

• Removed bundled translation files from the plugin package. Translations are delivered automatically through translate.wordpress.org.
• The legacy [uafrica] shortcode and uafrica/shipping block from the pre-rebrand plugin are no longer registered. Existing pages that still use them are rewritten automatically to the [bobgo] shortcode and bobgo/shipping block on upgrade, so tracking pages keep working unchanged.

4.0.22

• Fixed a critical order-matching bug on stores using WooCommerce’s classic (legacy) order storage: Bob Go notifications for orders with no WooCommerce counterpart — such as CSV imports or orders created manually on Bob Go — could attach themselves to an unrelated recent shop order. An affected order displayed a stranger’s tracking information, was treated as already synced (so it was never sent to Bob Go), could be marked completed by the stranger’s delivery, and could have its delivery address overwritten. Every lookup now either matches the exact order or matches nothing.
• Added a one-time, automatic link audit that verifies every stored Bob Go order link against the Bob Go API and silently repairs existing damage: wrongly-linked orders have the foreign link and tracking data removed, active orders are re-sent to Bob Go, and orders whose true Bob Go counterpart is found are relinked without creating duplicates. Completed orders are only unlinked and flagged internally, since merchants may have already shipped them manually.
• An order’s stored Bob Go link can no longer be overwritten by a notification claiming a different Bob Go order.
• Notifications whose order reference matches no shop order are now acknowledged instead of rejected, so stores receiving many of them (for example during a CSV import) can no longer have their Bob Go notifications disabled by the failed-delivery window.
• Fixed hourly reconciliation on stores using classic order storage: the batch could fill with orders that were never sent to Bob Go, starving the linked orders it was meant to refresh.