Explore Shippo and check its current features and plans.
Visit Shippo- Who this is for
- Small product businesses and ecommerce operations teams with recurring order or stock reconciliation work.
- What you will leave with
- A reconciled order and inventory route with explicit quantities, statuses, owners and recovery evidence.
- Scope of this guide
- Documentation-based product information and an editorial evaluation plan. Verify the current plan, account configuration, and connection before implementation.
On this page · 10 sections
A store or product business with a shipping-label or carrier-workflow gap and a named fulfillment operator.
A need for manufacturing planning, a complete marketplace operating system or an assumption that label creation proves delivery.
Choose the shipping layer you need
Shippo offers a shipping application and an API route, with label, carrier, tracking and return-related capabilities. Select the route that matches the team's operating capacity. A store operator reviewing shipments in an application has different maintenance needs from a developer owning an integration. Compare the actual shipping job with the current platform before introducing another layer.
Define the parcel contract
Record the order and shipment identifiers, destination, package dimensions, weight, contents and service expectation. Include the units and where the values originate. A copied product weight is not necessarily the packed shipment weight. Use a controlled multi-item order and an unusual parcel to check that the operator can detect incomplete information before choosing a service or purchasing postage.
Verify the carrier and account scope
Check the carriers, services, origin and destination countries, billing arrangements and account access needed for the proposed route. Confirm eligibility directly for the business that will ship. Avoid assuming a general carrier list guarantees a particular service for every origin, parcel or destination. Keep an alternative operating procedure for a route that is not supported in the account.
Compare the complete shipment cost
Use the same parcel and destination when inspecting service options. Check quoted charges, adjustments, optional services and any platform or account fees under current terms. Record the delivery expectation separately from a guaranteed commitment. Compare the total job with the existing shipping method, including packaging preparation and operator review, rather than choosing a route from a remembered headline rate.
Separate a label from a dispatch
Write the milestones for label preparation, purchased postage, packed parcel, carrier acceptance and actual delivery. Decide which event changes the customer's order status. A label can exist before a parcel leaves the warehouse. Keep that distinction visible so a customer does not receive a shipped promise based only on a document being generated.
Use a controlled test route
Use the provider's documented test facilities or a no-purchase walkthrough for initial cases. Confirm which actions create real postage charges before performing a live test. Include an invalid address, missing parcel information and a repeated request. The purpose is to establish correct behavior and a dependable review point, not to create paid labels while the integration's state is still uncertain.
Inspect tracking and event order
For the selected application or API setup, document how a tracking update reaches the store and the support team. Prepare cases for a delayed, repeated or inconsistent event and check the actual account behavior. Preserve shipment identifiers when reconciling updates. An operator should be able to tell whether the parcel is merely waiting for new evidence or whether the handoff itself has failed.
Own returns and delivery exceptions
Define who handles an address issue, an unaccepted parcel, a delayed delivery and a requested return. Record the customer-facing explanation and the relevant carrier or merchant procedure. Check which actions the selected account can perform and which require a separate person or portal. Keep the customer's request and the physical shipment state together so a support response does not promise an action fulfillment cannot perform.
Prepare a careful retry and correction
When a label request or downstream update has an uncertain result, inspect the existing shipment before trying again. Identify who may correct an address, replace a label or request a refund under current rules. Retain a cross-reference between the original order and every related shipment record. A recovery procedure should prevent accidental duplicate purchases as well as duplicate dispatches.
Decide from accepted shipment evidence
Use representative parcels and exception cases with the same baseline process. Measure correct service selection, reconciled dispatch and tracking states, support visibility and active operator time. Compare the maintained application route with an API route only if the team can own that integration. Keep the existing shipping process available until the chosen configuration has a tested operator, cost model and recovery procedure.
A shipping workflow is complete when the correct parcel and service are reconciled with tracking and a responsible exception owner.
Independent editorial guide based on official documentation. We may earn a commission if you sign up or purchase through an affiliate link. Read our affiliate disclosure.
Visit ShippoOfficial sources
Shippo: shipping app and APIShippo: API documentationSource material supports product descriptions; workflow criteria and pilot suggestions are our editorial analysis. Check the current documentation and your account settings before implementation.