A shipping label leaves the printer while the parcel remains on the packing bench. If the store immediately tells the customer “shipped,” it may have purchased a working technical connection and an operational experience that describes something which has not happened. Preventing that starts with the implementation proposal.
Ask the store integration provider to describe the complete parcel lifecycle: initial information, service selection, when the label becomes usable and what establishes transfer to the carrier. “Shipping and tracking integration” alone does not assign these responsibilities.
Store orders are not always identical parcels
Consider a fictional store selling lamps and installation parts. One order contains a large lamp and a small box, requiring two parcels. Does the customer receive two tracking references? Can support see that one arrived while the other did not? These questions expose boundaries without inventing a real customer's volume or results.
Start with product samples, known dimensions and destinations you actually intend to serve. Specify the source and units of packed weight and dimensions, and who reviews incomplete addresses. Avoid passing data correction to the driver after shipment creation or assuming every carrier and service supports your account and destination.
A scope sheet from rates to closure
| Stage | Proposal requirement | Suggested acceptance evidence |
|---|---|---|
| Parcel preparation | Order links to items and packed dimensions | One order displays separate parcels |
| Service selection | Rate source, available services and validity | Recorded choice and explanation of later differences |
| Label generation | Operation reference, state and responsible printer | Correct label retrieval without mixing parcels |
| Carrier handover | An event separate from label preparation | Ready parcels distinguished from carrier possession |
| Follow-up and exceptions | Each parcel's state and follow-up owner | A partially delivered order with understandable messaging |
| Reversal | Separate store cancellation and label refund request | Refund outcome tracked without assuming acceptance |
This proposed procurement sheet is not a particular carrier's specification. Shippo documentation illustrates separation between shipment preparation, rate selection and label purchase. That distinction helps buyers ask about the financial effect of each action without assuming every integration uses identical steps or names.
Do not group three problems under “failure”
An unavailable provider connection is a technical issue. A delivery problem may be an operational carrier event, while missing recent updates may require investigation before interpretation. Tracking documentation distinguishes different states, specifically separating the period before carrier possession from movement within the carrier's network.
In the illustration, the small parcel might arrive while the lamp needs another delivery attempt. Specify the customer message, who may contact the carrier and who records the outcome. Avoid closing the entire order when one parcel arrives or sending contradictory notifications because updates reach the store at different times.
Canceling a label does not complete its refund
A customer may change an order after printing. Ask how an unused label appears, who requests a refund when eligible and how the request is followed through. Shippo's page distinguishes requested, refunded and rejected outcomes; carrier and account conditions cannot become a universal promise across markets.
Add reprinting the same label, replacing a damaged parcel before handover and handling a late address correction. Request a distinction between editable details and changes requiring another operation, with a clear record. Real shipment purchases are unnecessary to demonstrate distinct interface states in a suitable test environment.
What should you send for a better proposal?
Provide possible parcels per order, sales channels, packing methods, required services, notification policy and the carrier-account owner. Separate implementation charges from external costs requiring independent verification and agreement. Request the completed state sheet as a deliverable, rather than merely a test account with unclear ownership.
Extend the store development scope with this sheet. The proof-of-delivery guide addresses evidence of field events; this article defines the integration lifecycle. Discuss it when requesting ecommerce development from Nextwave before comparing prices.
Review sources
Shippo documentation on label generation, tracking and label refunds was opened on 4 November 2026. The original example and sheet are illustrative, without label purchases or actual shipping. AI assisted preparation, with information and translation review.
