Auto-Generating Tracking URLs in Pipe17

How It Works

When Pipe17 ingests fulfillment data from a connected fulfillment channel, it processes tracking information based on the following rules:

• Tracking Numbers are Required for URL Generation Tracking numbers are not required to create a fulfillment record. However, if a tracking number is not present, Pipe17 has no data to pattern-match against and will not generate a tracking URL. The fulfillment will be created, but no tracking URL will be available to pass to the selling channel.
• Tracking URLs are Optional If the fulfillment channel includes a tracking URL, Pipe17 will:
  • Accept the URL as provided.
  • Pass it through to the associated selling channel without modification.
• If the fulfillment includes multiple tracking numbers, Pipe17 uses the first tracking URL in the list. Each tracking number may have its own URL; all are stored on the fulfillment record and passed to the selling channel.
• Auto-Generation via Pattern Matching If a tracking URL is not supplied, Pipe17 attempts to identify the carrier based on the tracking number format. When a match is successful, Pipe17 auto-generates a public-facing tracking URL based on known carrier URL formats.

Example: A tracking number that starts with 1Z and is 18 characters long (the 1Z prefix followed by 16 alphanumeric characters) will be recognized as a UPS shipment. Pipe17 will generate a URL such as: https://wwwapps.ups.com/WebTracking/track?track=yes&trackNums=${trackingNumber}

Supported Carriers for Pattern Matching

Pipe17 currently supports tracking number pattern recognition for the following carriers:

• Amazon
• Canada Post
• Deliverr (was Flexport)
• DHL
• FedEx
• Lasership
• OnTrac
• Purolator
• Royal Mail
• UPS
• USPS

Pipe17 may not cover all possible tracking number formats for each carrier. If a valid tracking number fails to match a known pattern, the carrier will remain unidentified and no URL will be generated.

Bypassing Auto-Generated Tracking URLs

If your workflow requires disabling the automatic generation of tracking URLs, you can implement a custom field mapping in the fulfillment inbound configuration of your integration.

Steps to Override:

1. Add a custom mapping for the trackingURLs field.
2. Set the source to a dummy value, such as ["dummyurl"].

Example Mapping Configuration:

{
  "enabled": true,
  "name": "trackingURLs",
  "source": "[\\"dummyurl\\"]",
  "target": "trackingURLs"
}

This will prevent Pipe17 from applying its auto-generation logic for tracking URLs.

Troubleshooting

• Issue: No fulfillment record is created. Cause: Tracking number is missing in the fulfillment data. Solution: Ensure that all fulfillment data includes valid tracking numbers.
• Issue: Tracking URL is not passed to the selling channel. Cause: Tracking number did not match any known patterns and no URL was provided. Solution: Update the fulfillment channel to include URLs, or adjust custom mapping rules.
• Issue: Incorrect or missing carrier identification. Cause: Tracking number format not recognized. Solution: Contact support with an example tracking number for review.

Need Help?

If you need additional assistance:

• Use Ask Pippen, our AI agent, located at the top of the app page.
• Submit a support request with as much relevant detail as possible. Learn how to submit a request.
• For urgent issues, email us directly at support@pipe17.com.

We're here to help you succeed with your operations.