Skip to main content
HomeBlogGuidesHow Preorder and Crowdfunding Businesses Can Use Shipment Tracking to Manage Deliveries

How Preorder and Crowdfunding Businesses Can Use Shipment Tracking to Manage Deliveries

17TRACK

Preorder and crowdfunding businesses can use shipment tracking to connect each order or pledge to its fulfillment batch, monitor parcels after carrier handover, and send updates that reflect what has actually happened. The most effective approach separates production progress from shipping progress, tracks every package in a split delivery, and assigns someone to act when a shipment needs attention.

How Preorder and Crowdfunding Businesses Can Use Shipment Tracking to

Tracking cannot resolve a manufacturing delay or guarantee a delivery date. Its value is making the delivery stage visible and actionable, so your team can explain where an order stands without treating a printed shipping label as proof that it is on its way.

Separate the production promise from the delivery journey

Preorder customers and crowdfunding backers may wait through development, manufacturing, quality checks, and batch allocation before a parcel exists. A tracking link only describes part of that journey. If it becomes your only source of updates, people whose orders have not shipped are left without useful information.

Maintain two connected timelines:

  • Fulfillment timeline: the order or pledge is confirmed, required selections are complete, an address is ready, inventory is allocated, and the warehouse is preparing the shipment.
  • Shipment timeline: a label is created, the carrier records receipt or collection, the parcel moves through its network, and delivery is attempted or completed.

Describe each milestone precisely. “Assigned to the next fulfillment batch” does not mean “shipped.” “Label created” does not necessarily mean the carrier has the parcel. A carrier acceptance event is stronger evidence of handover, although scan timing and event wording vary by service.

Your customer-facing order page should make that distinction clear. Before dispatch, show the latest fulfillment update and the next planned communication. After dispatch, add package-level tracking without removing information about any items still waiting to ship.

Build an order-to-package record before releasing a batch

A spreadsheet can support a small campaign if it is maintained consistently. Larger operations may need connected order, warehouse, and tracking systems. Either way, the underlying records should answer the same question: which items are traveling in which parcel, for which customer?

Keep the following fields connected:

  • Order or pledge reference: a stable identifier that support can use across systems.
  • Fulfillment batch: the warehouse release or production allocation to which the order belongs.
  • Shipment contents: the items and quantities included in each package.
  • Carrier and tracking number: the information needed to identify the shipment correctly.
  • Label and handover records: separate dates or events for label creation, warehouse release, and carrier acceptance where available.
  • Latest tracking event: its description, event time, and the time your system last checked for updates.
  • Exception ownership: the person responsible, the next action, and the next review date.

Do not use a tracking number as your only permanent order identifier. Orders can have multiple parcels, replacement shipments, or canceled labels. Keep those records separately, and mark obsolete tracking numbers clearly so they do not generate misleading notifications.

Account for partial shipments explicitly

Suppose a backer receives the main product first and an accessory later. That is one pledge with two delivery journeys, not one shipment that remains vaguely “in progress.” Show which items belong to each parcel and which items have not yet been dispatched.

Calculate completion from the items promised, not from the first delivered tracking number. Otherwise, your system may mark a pledge complete while part of the reward is still in production.

Test the tracking workflow before a full batch leaves

Before enabling customer notifications for a large release, validate the workflow with a small operational test. This is especially useful when a fulfillment partner exports tracking numbers in bulk or when different destinations use different carriers.

  1. Reconcile shipment records. Confirm that each tracking number matches the correct order, recipient, and package contents.
  2. Check carrier identification. Resolve ambiguous or unrecognized numbers rather than assuming automatic detection is always correct.
  3. Inspect the customer view. Open the tracking link and confirm that it shows the intended shipment without exposing another customer's information.
  4. Test split orders. Verify that a delivered parcel does not hide an outstanding package.
  5. Review notification triggers. Confirm that a label event cannot accidentally send a message claiming carrier possession.
  6. Test exceptions and replacements. Check how the workflow handles an invalid number, a canceled label, and a new shipment replacing an earlier parcel.

Agree with your fulfillment partner on what its “shipped” field means. It may refer to packing completion, manifest creation, warehouse departure, or another operational step. Map that field to customer language only after its meaning is clear.

Choose tracking tools around the work your team must do

Start with the operational requirement rather than the longest feature list. A team checking occasional parcels needs a different setup from one connecting shipment events to a custom backer portal.

  • Manual tracking: useful when shipment volume is manageable and a person can review packages consistently.
  • Store-connected tracking: appropriate when orders live in an ecommerce platform and shipment information needs to remain associated with those orders.
  • API integration: worth considering when a custom portal, order management system, or support workflow needs tracking data programmatically.

For example, 17TRACK's tracking page provides a route for checking parcel tracking, while its Tracking API is relevant when evaluating a developer-led integration. Shopify merchants can also assess the 17TRACK Shopify app against their order-tracking requirements. These are different implementation paths, not interchangeable solutions.

Before selecting a service, verify support for your actual carriers and shipping products, the information returned for representative shipments, integration requirements, applicable pricing, and customer-facing behavior. Test domestic, cross-border, split, and replacement shipments if those are part of your fulfillment model. Do not assume that a tracking tool also manages pledge allocation, manufacturing schedules, or address changes.

Turn tracking events into an exception queue

A dashboard is useful only if someone responds to what it shows. Create a review queue with an owner and a next action for each unresolved shipment. Use carrier-specific guidance and your fulfillment agreement to set review thresholds rather than imposing one universal deadline.

SignalFirst checkOperational response
Label exists, but no acceptance eventWarehouse handover record and carrier collection informationInvestigate whether the parcel was handed over or is still awaiting dispatch.
No new movementLast event, route, service expectations, and known carrier noticesReview the shipment against the relevant service guidance; escalate when appropriate.
Delivery attempt or pickup instructionCarrier instructions and any stated deadlineTell the recipient what action is required and where to find official instructions.
Customs-related eventThe exact request and whether the sender or recipient must respondCoordinate the requested information without inventing a clearance date.
Delivered, but receipt disputedDelivery details and available carrier evidenceOpen a support investigation rather than treating the scan as automatic resolution.

An unchanged status does not, by itself, prove a parcel is lost. Likewise, an exception label may not explain the cause. Preserve the carrier's original event text alongside any simplified status so support can investigate without relying on a broad category alone.

Send updates that explain the next step

Customers need to know what changed, what it means for their order, and whether they must do anything. They rarely need a separate message for every routine scan.

Use individual shipment notifications for dispatch, meaningful delivery changes, recipient action, and delivery confirmation. Use campaign or batch updates for shared issues such as a manufacturing hold or a delayed warehouse release. Keep personal addresses and tracking numbers out of public campaign updates.

A useful delay message might read:

Your parcel's latest carrier update still shows it at the export facility. We have asked our fulfillment partner to check its progress. No action is needed from you at this stage. We will update you by [date], even if the carrier has not provided a new scan.

Use a message like this only when those statements are true and your team can meet the follow-up commitment. A promised communication date is something you control; a delivery date may not be.

If you display an estimated arrival window, identify whether it comes from the carrier or your own planning assumptions. Do not present either as a guarantee unless the applicable service and terms support that claim.

Review delivery performance by batch, not just in aggregate

Campaign-wide totals can hide a problem affecting one warehouse release, product configuration, or destination. Review results by fulfillment batch and shipping route so the team can identify where intervention is needed.

  • Awaiting handover: shipments with labels but no recorded carrier acceptance, reviewed against warehouse records.
  • Open exceptions: unresolved shipments grouped by issue, age, and owner.
  • Complete orders: orders for which all expected items have a resolved delivery outcome, with partial shipments kept separate.
  • Delivery-related contacts: support requests associated with each batch, distinguishing status questions from missing-item or damage reports.
  • Follow-up compliance: whether promised customer updates were sent when due.

Define denominators before reporting percentages. “Delivered packages” and “fully delivered pledges” measure different outcomes. Exclude canceled labels from active-shipment reporting, and keep replacement parcels linked to the original issue rather than counting them as unrelated success.

The practical goal is a repeatable handoff: fulfillment creates accurate package records, tracking surfaces delivery events, support owns exceptions, and customers receive an explanation that matches the evidence.

FAQ

When should we send a tracking number to a preorder customer?

Send it when it is assigned to the correct package and the accompanying message describes the actual stage. If the label exists but handover has not been confirmed, say that the shipment is being prepared rather than claiming the carrier already has it.

Can shipment tracking explain why a crowdfunding reward has not shipped?

Not on its own. Manufacturing, allocation, incomplete selections, and warehouse preparation require information from your campaign and fulfillment records. Tracking becomes useful once a shipment record exists, and carrier events provide visibility into the transport stage.

How long should we wait before investigating a parcel with no updates?

Set the threshold using the carrier's service guidance, the route, the last event, and your fulfillment agreement. There is no single waiting period suitable for every shipment. A recipient action deadline or a clear delivery exception may require attention sooner than an ordinary gap between transit scans.

What should we do if a customer changes their address after dispatch?

Check the actual shipment stage and the carrier's available options. Updating the address in your order system does not necessarily redirect a parcel already in transit. Confirm whether a change is possible before promising it, and explain any restrictions or costs that apply.

Should a delivered scan automatically close a support ticket?

Not if the customer has reported nonreceipt or another unresolved issue. Use the scan as evidence for the investigation, check available delivery details, and follow the applicable carrier process and your customer-service policy.

Sources