Skip to main content
To support your Shippo integration, we recommend developing a test plan. A test plan is a roadmap for testing how different parts of your application works with an integration. Use the test scenarios below as a framework to build your test plan.

Testing setup

Different integration types will be best structured as follows:
  • White Label
    • Two accounts should be established, one for production and one for testing. These are both best setup as accounts where many users can access the email such as an alias. This prevents problems with staff transitions and password resets. Individuals or teams can also use their own accounts as needed.
  • White Label Platform
    • A top level account will be set up and established as the parent account. This account is not generally used for rating and label generation but is the structure for tenant accounts. Tennant accounts should be used for testing and development purposes as this level is where production labels will be managed.
  • Gray Label
    • Because gray label integrations rely on Oauth for tracking and attribution there is no need for a strict account structure. Every account will be stand alone and linked to an integration by the Oauth registration process. It is best that testing for production purposes is performed by registering through Ouath just as a customer would. Please Note: Testing through Oauth will require a valid credit card for registration.

Testing scenarios

Below are examples of scenarios to consider when establishing a testing plan. Use this guide to test a new carrier integration. Based on Shippo’s experience with API integrations, these are the minimum tests your integration must pass before deploying for production. Not all tests will apply to the carrier or integration you are testing, review the test scripts and determine which ones apply to your business. If you are preparing to release into production with this carrier, run these test scripts using a production account. Remember to void any labels created during testing to avoid being billed for them. For pre-production testing it is best to use the test mode API token to avoid being charged for shipments. You will need the following:
  • Carrier Account Information or an activated Shippo carrier account
  • A list of all service levels you are supporting for the carrier.
  • Required shipping fields: a valid from address, a valid to address, parcel dimensions.
    • You will need to account for domestic and international addresses when applicable
  • An understanding of the capabilities integrated for the carrier. For example, not all carriers support manifests or custom’s functionality.

Suggested Tests

Validate an Address

NoteAddress validation will not work with your test API token. You must use your live API token.

Add A Carrier

Get A List of Carriers

Get A Rate

Purchase Label from Existing Rate

Purchase a Label in One Step

Refund a Label

Track a Label

NoteTracking will not work with your test API token. You must use your live API token.

Schedule a Pickup

Manage Batch Shipping

Test Carrier Service Levels

Create a Manifest

Create a Webhook

NoteIf you are testing in production, remember to cancel any labels that were purchased to avoid being charged.
Last modified on July 16, 2026