Skip to content
  • There are no suggestions because the search field is empty.

Resolving Stamps.com Rate Retrieval Issues in Webgility Desktop

This article helps Webgility Desktop users troubleshoot issues retrieving shipping rates from Stamps.com, even when credentials and settings appear correct. It provides a step-by-step process to isolate the problem and resolve it.

Overview

If you are unable to retrieve shipping rates from Stamps.com through Webgility Desktop—even with correct login credentials—systematic troubleshooting is required. The following steps will help you identify and resolve the most common causes of Stamps.com rate retrieval failures within Webgility Desktop.


Common Causes

  • Temporary Stamps.com service outages
  • Invalid or outdated Stamps.com credentials
  • Incorrect setup in Webgility or API configuration changes
  • Data inconsistency or corrupted shipping integration settings


Step-by-Step Investigation Guide

1. Verify Your Credentials and Settings

  • Open Webgility Desktop.
  • Go to Integrations > Shipping Providers.
  • Select Stamps.com from your list of providers.
  • Confirm that:
    • API Username and API Password are entered correctly (match your current Stamps.com login).
    • Account Status is active, and your subscription plan supports rate retrieval.
    • The API endpoints have not changed or been altered.
  • Optional: Try logging in directly at Stamps.com’s website to rule out account or subscription issues.

2. Review Shipping Logs

  • Navigate to C:\Webgility\UnifyEnterprise\SchedulerLog.
  • Look for:
    • Error messages or failed rate requests (such as authentication errors, timeouts, or “no rates” returned) in response logs.
    • API response codes that indicate the nature of the failure.
    • Exact timestamps and details for failed requests.

3. Attempt to Replicate the Issue

  • In your Webgility Desktop environment, manually request a shipping rate for a sample order using Stamps.com.
    • Use the same shipper, destination, and service options originally reported.
  • Observe if the issue occurs globally or only with specific parameters/accounts.