Foro Documentation

Replies: 0 Hi there, I found that WooCommerce Shipping turns off page caching on some of my regular front-end pages, pages that have nothing to do with shipping. What happens: my blog category pages (for example /category/reviews/) are never cached by WP Rocket. I traced it and the DONOTCACHEPAGE constant is being defined by WooCommerce Shipping. Why: Loader::rest_api_init() calls WCShippingRESTController::prevent_route_caching() every time rest_api_init runs, and that function defines DONOTCACHEPAGE straight away. rest_api_init doesn’t only run for real REST calls though. It also runs when any code on a normal page makes an internal request with rest_do_request(). On my site the Kadence Blocks Pro “Query Loop” filter buttons do exactly that while the page is being built, so the whole page gets marked “do not cache” even though no WooCommerce Shipping endpoint was ever called. Steps to reproduce: WooCommerce Shipping active, plus a page cache that respects DONOTCACHEPAGE (I use WP Rocket). A front-end page that calls rest_do_request() while rendering, for example a Kadence Blocks Pro Query Loop with the Filter Buttons block. Visit it logged out. It’s never cached. DONOTCACHEPAGE is defined during rest_api_init, from Loader::rest_api_init() -> WCShippingRESTController::prevent_route_caching() (src/WCShippingRESTController.php). Suggested fix: only define DONOTCACHEPAGE when the request is actually for one of your routes, for example inside your rest_post_dispatch callback (exc

Replies: 0 When you have really long address lines, like “123 AVE PONCE DE LEON APT 123”, the resulting shipping label, to Puerto Rico in our case, will have a cropped address that is limited to 28 characters, resulting in “123 AVE PONCE DE LEON APT 12”. There is no warning, no indication, and worst of all, the address becomes undeliverable, costing us money when it fails and is returned, and subsequently needs to be resent with the corrected address. Not to mention the upset it creates with the customer who did not receive his purchases on time. Please fix this, make sure addresses are properly wrapped—why not put the apartment etc on a separate line?—or, at the very least, generate an error message so that action can be taken BEFORE the damage is done.

Replies: 0 Rating: 1 star FedEx Extra Small Box is not available, although its a standard predefined packaging offered by Fedex Overall badly written plugin

Replies: 1 Fedex Extra Small Box is not included in predefined packages. only Small boxes. Please add Fedex Extra Small Box

Replies: 3 After updating to version 2.3.15 of WooCommerce Shipping we cannot ship product. The error message says, “…failed to match all required schemas…string…is too long.” It specifically mentions the address string is limited to 50 characters. Status WooCommerce WooCommerce 11.0.1 is configured correctly WordPress.com Connection WooCommerce Shipping is connected to WordPress.com, and working correctly WooCommerce Shipping Service data is up-to-date Last update on 9/2/2026, 10:57:17 AM Other Log: 2026-09-02T03:28:09+00:00 NOTICE Successfully loaded service schemas from server response. (Automattic\WCShipping\Connect\WC_Connect_Service_Schemas_Store::fetch_service_schemas_from_connect_server) CONTEXT: {“_legacy”:true}

Replies: 11 I have selected a shipping service and clicked the “Purchase Shipment” button, but the system didn’t purchase the label. The I am unable to use the “refresh purchase status” button. I have shipped other orders after this, so the system is working. But it’s been several hours and the order is still stuck. I haven’t been charged for the label, I have re-booted the website. I am stuck, please help.

Replies: 3 WooCommerce Shipping has recently become very slow when retrieving shipping label rates and purchasing labels. The WooCommerce Shipping log repeatedly shows: wcc_server_error Error: The WooCommerce Shipping server returned HTTP code: 0 (Automattic\WCShipping\LabelRate\LabelRateService) The problem is intermittent. Sometimes rates load normally, but other times there are long delays or failures. Environment: WordPress: 7.1 WooCommerce: 11.0.1 WooCommerce Shipping: 2.3.15 PHP: 8.3.33 PHP cURL: 8.21.0 OpenSSL: 3.5.5 Server: LiteSpeed I have done extensive connectivity testing from the hosting server: api.woocommerce.com resolves correctly to 192.0.96.246. Direct curl requests to: https://api.woocommerce.com/ return HTTP 200 normally. I ran 50 consecutive curl requests. All 50 returned HTTP 200 with total response times of approximately 0.03–0.10 seconds, with no timeouts. I tested the exact WooCommerce Shipping label-rate endpoint using PHP cURL: POST https://api.woocommerce.com/shipping/label/rates Result: HTTP: 401 Time: 0.0449 sec errno: 0 The 401 is expected because the diagnostic request did not include WooCommerce authentication. The connection itself succeeded normally. I tested the same endpoint through WordPress using wp_remote_post(). Result: HTTP: 401 Unauthorized So DNS, TLS, PHP cURL, and the WordPress HTTP API all appear to be working normally. I also confirmed that nothing on the site overrides the wcshipping_server_url filter. The errors only appear du

Replies: 6 We ship out the same items in the same packaging. In most cases, the shipping is calculated properly (It is almost identical to what USPS.com quotes) but often it appears this plugin is calculating based off the “cubic ground advantage” rate. I compare the rates calculated to what USPS.com quotes and the rate calculated from this plugin is almost identical to the “cubic” rate which is higher than the standard ground advantage rate show on USPS.com. I end up having to purchase the postage for these orders from USPS.com which is a hassle. Would there be a way to have both cubic and standard ground advantage as a selection after entering size/weight? I understand the plugin is supposed to return the cheapest rate, but it appears in some cases it isn’t doing that. Please advise because I can’t afford to lose $2 or more on these mis-quoted rates. It is adding a lot of time to our shipping process. Oh, and one more thing. Would it be possible to be able to get all the packages calculated/prepared then purchase shipping and print labels all at once rather than for each order? Thanks! This topic was modified 2 weeks ago by Pro Dev .

Replies: 4 Dear Support Team . Could you please consider changing the way you email the receipts for the Shipping Labels? Prior to WooCommerce shipping, I was using GoShippo to create shipping labels. Instead of emailing a receipt each & every time I purchased a shipping label, they would email a receipt for every $100 or so worth of shipping labels I purchased with a record of each one; basically a batch receipt. I find that GoShippo’s method of emailing receipts for the shipping labels is much more efficient as it saves time and paper. Support Team, if you see this, please consider giving users the option change the way they recieve shipping label receipts. It would be really nice to just have one big receipt containing a record of all the shipping labels I have purchased in a given month. This would save me so much time and paper!

Replies: 4 I am no longer able to print 3-page international USPS labels. The labels being generated are combining all three pages onto a single page and are completely unreadable. Switching to 8.5×11 also does not work. I’ve heard that this is a known issue, but I’d like to know the time frame for a fix. I have orders waiting to be shipped.

Replies: 1 WooCommerce: 11.0.1 WooCommerce Shipping: 2.3.14 Failed endpoint: upsdap?_locale=user HTTP response: 403 from WooCommerce Shipping server, surfaced locally as 500 Local error: missing_upsdap_terms_of_service_acceptance We are currently traveling, so our shipping origin address will change periodically while we are on the road. We are attempting to use the UPS label feature within WooCommerce Shipping, but we are now receiving the following server response: “Forbidden: You have reached the maximum number of origin addresses for this site. Please contact WooCommerce support if you need to create more origin addresses. (403)” Because of this limit, we are unable to accept the UPS Terms and Conditions for our current origin and therefore cannot purchase UPS labels through WooCommerce Shipping. Please clear/reset the accumulated origin addresses associated with our site so we can resume using the UPS shipping feature. We are not sure what the maximum number of origin addresses is, but we anticipate needing to use at least five additional temporary shipping origins before returning to our permanent origin: We are traveling to Wyoming tomorrow and will likely need to use a Wyoming shipping origin next. Because changing shipping origins is a legitimate and recurring requirement for our business while traveling, please also advise us on the following: Can the origin-address limit for our site be increased? Can old or unused origin addresses be permanently removed so they no

Replies: 3 I am getting the following error on an international shipment: /international-labels/v3/: code=400, message=OASValidation OpenAPI-Spec-Validation-International-Labels with resource oas://international-labels-v3.yaml: failed with reason: [ERROR – [Path ‘/customsForm’] Instance failed to match all required schemas (matched only 1 out of 2): [/properties/customsForm/allOf/1: Instance failed to match all required schemas (matched only 1 out of 2)]ERROR – [Path ‘/customsForm/contents/0’] Instance failed to match all required schemas (matched only 1 out of 2): [/properties/customsForm/allOf/1/properties/contents/items/allOf/0: String Titan Class Autobot Insignia (Toy or Cartoon Style) is too long (length: 51, maximum allowed: 30)]ERROR – [Path ‘/customsForm/contents/0/itemDescription’] String Titan Class Autobot Insignia (Toy or Cartoon Style) is too long (length: 51, maximum allowed: 30): []] I have shipped to this customer several times before and even tried to print a new label on an old order that was shipped before just to see if it would work and I am still getting an error no matter what I do. This topic was modified 3 weeks, 1 day ago by iaconjoni .