Isolate Shipping Label Errors to Webgility Desktop or Your Carrier

 You are in the right place if

You clicked Ship Order or Process Shipping in Webgility Desktop and got an error such as Unable to process request, an exception code like 0X005F0313, or a generic "system error" while the label was being generated. The order looks ready to ship — customer, address, weight, and service are all filled in — but no label prints and no tracking number is created.

Why this happens

Webgility Desktop does not print labels on its own. It hands the shipment details to your carrier's service (Stamps.com, UPS, FedEx, or USPS) over their API, waits for the carrier's response, and displays whatever comes back — including any error the carrier returns. A label error can come from either side. Webgility might be sending a field the carrier does not accept, or the carrier's own service might be rejecting the shipment (a rate change, an account restriction, a maintenance window). The five-minute check below sorts one from the other.

What to do

Step 1: Update Webgility Desktop first. Click the Help menu, choose Check for Updates, and install the update if one is offered. After Webgility restarts, try shipping the same order again. If it prints cleanly, the earlier failure was a bug the update already fixed and you are done.

Step 2: Copy the exact error text and any code (such as 0X005F0313) into a note on your desk. You will match this against what the carrier's own portal shows in Step 3, so precise wording matters.

Step 3: Sign in to your carrier's own web portal in a browser — stamps.com, ups.com, fedex.com, or usps.com — using the same account you connected to Webgility. Open the carrier's own label-creation screen (usually called "Ship" or "Create a Label" on that site). Fill it in with the same shipment details as the failing Webgility order: recipient address, package weight, dimensions, and the service the order was set to (for example, UPS Ground). Click the carrier's own Print Label or Create Shipment button. The carrier's portal then either prints the label or shows an error.

Step 4: Compare what you see with what you noted in Step 2. Two things can happen:

a. The carrier's own portal returns the same error (or a closely related one) with the same shipment details. The issue is on the carrier's side and not something Webgility can fix. Contact your carrier's support team directly — Stamps.com Support, UPS Support, FedEx Support, or USPS Support — and share the shipment details, the recipient address, and the error text. If your account has multiple carrier configurations, walking through How to Add Multiple FedEx Accounts in Webgility Desktop is a good sanity check that Webgility is pointed at the right carrier account.

b. The carrier's own portal prints the label cleanly for the same shipment. The carrier is happy — the issue is on the Webgility side. Contact Webgility Support with the order number, the exact error text and code you noted in Step 2, and a short confirmation that the same shipment succeeded on the carrier's portal. That last confirmation is the fastest way to skip diagnostic back-and-forth, because Support can go straight to reviewing what Webgility sent to the carrier.

Step 5: If you want to keep the customer's shipment moving while the root cause is being sorted out, print that one label directly from the carrier's own portal (the same Step 3 flow). Then paste the tracking number back into the order in Webgility. The order posts to your accounting the same way any other order does.

Good to know. Two adjustments sometimes turn a "Webgility side" failure into a clean print without any support ticket at all. On the failing order, try switching the shipping service to a closely related one (for example, UPS Ground to UPS Ground Saver, or USPS Priority to USPS Ground Advantage) and try again. If it prints on the alternate service, the original service was the sticking point. Also try turning off any Signature Required or Adult Signature delivery-confirmation option that is not strictly needed for the shipment — some carrier accounts reject those add-ons for accounts that are not enrolled for them, and the label prints as soon as the option is off.

Still need help?

If the same shipment fails on both Webgility Desktop and the carrier's own portal, and the carrier's own support cannot see why, share the order number, the recipient address, the exact error text, and screenshots of both portals with Webgility Support. Support then has everything needed to work with the carrier on your behalf.