Skip to main content
HomeBlogGuidesWhy Secondhand Marketplaces Need a Shipment Tracking API?

Why Secondhand Marketplaces Need a Shipment Tracking API?

17TRACK

Secondhand marketplaces need a shipment tracking API when delivery updates must support more than a tracking link. By bringing shipment events into the marketplace’s own systems, an API can help buyers follow purchases, sellers demonstrate shipping progress, and support teams investigate delivery problems. Its greatest value is connecting shipment visibility to marketplace operations without treating tracking data as proof of an item’s identity, condition, or authenticity.

Why Secondhand Marketplaces Need a Shipment Tracking API

For product managers, engineering teams, and marketplace operators, the decision is not simply whether to display parcel locations. It is whether a shared shipment record would improve the way the platform handles seller dispatch, buyer communication, delivery exceptions, and disputes.

Why secondhand shipping creates a different visibility problem

A secondhand marketplace may coordinate transactions between many individual sellers rather than dispatching everything from a controlled warehouse. Sellers can use different carriers, buy labels through different channels, and hand parcels over at different times. The marketplace therefore needs to distinguish what a seller reports from what a carrier has recorded.

Resale also changes what happens when delivery goes wrong. A particular used jacket, collectible, or refurbished item may not have an identical replacement available. Support teams need a clear account of the shipment before deciding what to investigate or how to explain the next step to a buyer.

Consider an illustrative transaction: a seller marks a used camera as shipped and enters a tracking number. The carrier initially shows only electronic shipment information. Later, an acceptance scan appears, followed by a delivery attempt. Those events represent different operational states. Collapsing all of them into “shipped” leaves the buyer poorly informed and gives support little basis for action.

A tracking API can make these distinctions available inside the marketplace. The platform must still decide what each event means under its own rules.

What a shipment tracking API does—and does not do

A shipment tracking API provides a programmatic way to submit shipment identifiers and retrieve tracking information. Depending on the service and integration, updates may be obtained through API requests, webhook notifications, or a combination of both. A webhook is a message sent to your application when an update becomes available.

The useful output is not just a carrier’s latest status text. It is a shipment history that the marketplace can associate with an order, seller, buyer, and support case.

  • Buyer experience: Display progress within the order page instead of requiring buyers to interpret separate carrier websites.
  • Seller operations: Distinguish a submitted tracking number from a shipment with recorded carrier activity.
  • Support workflows: Present shipment events alongside transaction details and previous communications.
  • Exception handling: Route selected delivery problems to a queue for investigation.
  • Operational reporting: Examine dispatch and delivery patterns using clearly defined milestones.

These are potential applications, not automatic results. A tracking integration does not itself create a dispute policy, guarantee delivery, verify parcel contents, or provide shipment insurance. Likewise, buying a label, arranging collection, calculating postage, and tracking a parcel are separate capabilities. Do not assume one API includes all of them.

Five marketplace workflows that benefit from shared tracking data

1. Separating seller declarations from carrier activity

“The seller says it shipped” and “the carrier recorded acceptance” should be separate facts in the order record. A label-created event generally should not be presented as confirmation that the carrier physically holds the parcel.

Preserve the seller’s dispatch declaration, the time tracking was submitted, and any relevant carrier events separately. This lets support explain a missing acceptance scan without immediately accusing the seller of failing to ship. Missing or delayed scans require investigation, not an automatic conclusion.

2. Giving buyers useful updates without creating false certainty

Buyers need to know what changed and whether they should act. An acceptance scan may require only a quiet order-page update. A collection-ready event may justify a notification, while an unsuccessful delivery attempt may need a clearer explanation of the next step.

Notifications should reflect the information actually received. Do not invent a delivery date when none is supplied. If an estimated date is available, label it as an estimate and preserve its source. Avoid describing tracking as continuously live: updates depend on carrier events, data availability, and the integration’s processing behavior.

3. Organizing delivery exceptions

A parcel awaiting pickup needs a different response from one returning to its sender. Instead of putting every non-delivered shipment into a single problem queue, define queues around actionable conditions.

  • No recorded acceptance: Check the seller’s handover information and the carrier’s guidance.
  • Unsuccessful delivery attempt: Show any available redelivery or collection instructions.
  • Awaiting collection: Notify the buyer when reliable collection information is available.
  • Return movement: Route the order into the relevant return or support process.
  • Delivered but disputed: Preserve the delivery event and open a separate investigation.

Set inactivity thresholds by shipping service and route where practical. A single universal delay rule can create unnecessary alerts for slower services while overlooking problems on faster ones.

4. Supporting disputes and payout decisions

Shipment events can contribute to a transaction timeline, but they should not become the sole authority for a financial decision. A delivered scan does not establish that the correct item was inside the package or that it matched the listing.

If delivery events feed a payout workflow, use a separate policy layer. That layer should account for the marketplace’s published terms, applicable requirements, open disputes, and review procedures. A sensible design allows an exception to pause an automated action rather than forcing support to reverse it afterward.

5. Making return journeys visible

A return shipment is a new logistics journey. Associate it with the original transaction, but give it a separate shipment record and direction. Otherwise, a return’s delivered event could be mistaken for delivery to the buyer.

Return tracking can establish transport milestones. It cannot establish whether the returned item is the original item or whether its condition has changed. Those questions require a separate inspection or evidence process.

A practical integration design

Build the integration around shipments rather than a single tracking field on an order. One order may contain multiple parcels, and a transaction may later acquire a return shipment.

  1. Create a shipment record. Associate it with the order and seller. Store the tracking number, carrier when known, journey direction, and relevant timestamps.
  2. Check the submitted details. Catch empty values, obvious formatting problems, and unintended duplicates. Do not treat a plausible number as proof of a genuine shipment.
  3. Register or retrieve tracking. Follow the selected provider’s documented process. Keep unsupported, ambiguous, and temporarily unavailable results distinct.
  4. Receive updates reliably. For webhooks, use the provider’s supported authentication or verification mechanism. Process accepted messages through a durable queue where appropriate.
  5. Preserve source events. Store the original status text alongside your normalized status, with access and retention controls.
  6. Apply marketplace rules. Generate buyer updates, support tasks, and review requests from your own policy layer.
  7. Reconcile missing updates. Use permitted retrieval methods and operational alerts to investigate gaps rather than assuming every notification will arrive successfully.

Design for duplicate messages and events that arrive out of sequence. Reprocessing the same event should not send another buyer notification or trigger a second financial action. Keep the event’s timestamp separate from the time your system received it; these answer different questions.

Tracking numbers should not serve as public authorization credentials. Restrict shipment records to authorized users, protect API credentials on the server, and avoid exposing unnecessary recipient details in notifications or application logs.

How to evaluate an API for a secondhand marketplace

Start with shipments representative of your actual seller base. A broad carrier list is less informative than successful handling of the services, routes, and event types your marketplace uses.

  • Carrier and service fit: Test the actual services sellers use, including relevant international handoffs and return journeys.
  • Status interpretation: Check whether your application can distinguish electronic shipment information, acceptance, transit, delivery attempts, collection, delivery, and returns when those events are available.
  • Event detail: Examine timestamps, source descriptions, and how corrections or delayed events are represented.
  • Webhook operations: Verify authentication options, delivery behavior, retry handling, and recovery procedures in the documentation.
  • Integration constraints: Confirm request limits, registration requirements, error responses, and testing options.
  • Data governance: Review access controls, retention terms, contractual responsibilities, and the information your integration actually needs.
  • Commercial model: Confirm what is billable, how repeat requests are treated, and what happens when usage exceeds the agreed allowance.

17TRACK’s Tracking API page and official API documentation are relevant starting points for evaluating its API offering. Use those resources to check the integration against your shipment sample and technical requirements. Confirm service coverage, commercial terms, and operational limits before committing; this guide does not establish those details for a particular account or implementation.

For a custom marketplace, assess the API integration itself rather than assuming a consumer tracking page or a storefront app will meet backend requirements. The important question is how shipment data will enter your order model and drive controlled actions.

When an API is worth implementing

A tracking API becomes a stronger investment when support repeatedly checks carrier websites, buyers lack a consistent order view, or shipment events need to trigger internal workflows. It is especially relevant when manual tracking checks are becoming an operational dependency.

A small marketplace with limited shipping activity may reasonably begin with validated tracking links and a documented manual process. An API is not a substitute for clear seller dispatch expectations or a workable dispute policy. Automating an unclear process can simply make inconsistent decisions happen faster.

Run a controlled pilot before expanding. Include normal delivery, no acceptance scan, unsuccessful delivery, return movement, duplicate updates, and a delivered-but-disputed case. Check whether each produces the intended buyer message and support action.

Measure business outcomes as well as technical delivery. Useful measures include shipment-status contacts per shipped order, investigation handling time, duplicate notification frequency, and the share of shipments with usable milestone data. Define each measure before launch and compare similar shipment groups. A successful API response alone does not demonstrate a better marketplace experience.

FAQ

Can a tracking API prove that a seller shipped the right item?

No. Tracking describes the parcel’s reported journey, not its contents. An acceptance or delivery event may support a shipping timeline, but item identity and condition require other evidence.

Should delivery automatically release the seller’s payout?

Only if that action is consistent with the marketplace’s policies and applicable requirements. Keep payout logic separate from tracking ingestion, and provide a way for disputes or review conditions to pause an otherwise automatic action.

What should happen when a tracking number has no updates?

Show that no carrier update is available rather than inventing progress. Check the number and carrier, distinguish electronic label information from acceptance, and follow the relevant service’s guidance before classifying the shipment as lost.

Are webhooks enough on their own?

Webhooks can support event-driven updates, but the application still needs duplicate handling, monitoring, and recovery procedures. Where the provider permits it, reconciliation requests can help investigate missing or inconsistent updates.

Can the same integration track buyer returns?

Potentially, if the return carrier and service are supported. Create a separate return shipment linked to the original order, and distinguish delivery to the seller from delivery to the buyer.

Sources

The official resources below provide the product and implementation reference points for the 17TRACK evaluation discussed above. The workflow recommendations in this guide are editorial guidance, not statements of a particular marketplace’s policies or guaranteed product outcomes.