Customer Shipment Tracking Portal Development

What shippers expect from a tracking portal

Your customers have been trained by parcel tracking. They expect a link, a timeline and an arrival estimate for every shipment, whether it is a single carton or a full truckload of store fixtures. When a carrier or 3PL cannot provide that, customer service absorbs the gap one phone call and one email at a time. Tepia builds tracking portals that answer those questions before anyone has to ask.

The audience is usually broader than one person. A shipper’s logistics coordinator wants every open load for the week; a store manager wants only the deliveries coming to her location; an accounts team wants signed proof of delivery to close out the month. Tepia designs roles and views for each of them inside one customer account, with permissions managed by the customer’s own admin rather than your support desk.

The portal also has to tell the truth when things go wrong. A good one shows exceptions plainly: a missed pickup, a refused delivery, an appointment rescheduled by the receiver, a storm on the route. Customers forgive delays they hear about early. They rarely forgive a portal that shows on time until the load is a day late.

Portal features and who uses them

Tepia shapes the feature list around your modes and your largest accounts. A truckload carrier, an LTL network and an international forwarder need different detail, but most portals share this core:

Search by the customer’s own reference is the feature most often missing from carrier portals. Shippers think in purchase order numbers and store numbers, not your pro numbers. Tepia maps every reference that arrives in your EDI and API traffic onto the shipment record, so customers find a load the way they already track it internally.

Where tracking data comes from

The portal is only as good as the events behind it. Tepia connects the sources you already have and reconciles them into one timeline:

• EDI status messages (214) from partner carriers and load tenders (204) from shippers, through your VAN or an AS2 connection.
• Carrier APIs for parcel and LTL partners that publish tracking, plus webhooks where they exist.
• Your TMS, which stays the system of record for loads, stops and appointments.
• Driver apps and ELDs for GPS position, arrival and departure events and stop completion; see our proof of delivery app development page for the capture side.
• Reefer and trailer sensors when customers need temperature history on cold chain loads.

Each source has quirks: duplicate events, late messages, time zones reported inconsistently. Tepia writes rules for which source wins when two disagree, and the ETA logic uses the latest reliable position plus remaining stops and appointment windows instead of a straight line distance. When an ETA slips past the promised window, the exception alert fires once, to the right people, rather than every time the estimate wobbles.

How Tepia approaches shipment tracking portal development

Tepia runs its six phase process with a US based project manager, adapted to customer facing logistics software.

1. Discovery: a review of your TMS, EDI partners and carrier connections, a week of customer service call and email logs, and interviews with three or four key shippers. Deliverables are an Investigation Summary, an Interview Summary and User Stories such as a store manager checking tomorrow’s deliveries.
2. Design: design questionnaire, moodboards and a style guide matched to your brand, then wireframes and sample designs of the shipment list, timeline and document center.
3. Development and Testing: an Alpha with your own customer service team as users, then a Beta with a few friendly shippers, with tests for event ordering, ETA accuracy against actual arrivals and load testing at peak season volume.
4. Training: remote sessions for your customer service team and short guided walkthroughs for shipper admins.
5. Launch: backfill of recent shipments, invitation emails to customer admins, and support reps watching portal logins and questions during the first weeks.
6. Support: issue resolution, bug tracking, new carrier connections and feature requests like scheduled reports.

Discovery usually takes 1 to 3 months and development and QA 2 to 6 months, followed by a launch of about a month. Our process page has the details.

Notifications customers actually read

Most tracking portals send too many messages, and customers learn to ignore them. Tepia lets each user choose which events they hear about and through which channel, with sensible defaults by role. A coordinator might want every exception by email, a receiving manager only an SMS when a truck is an hour out, and a finance user only a daily digest of new proof of delivery files.

Shareable tracking links extend that reach without extra accounts. A distributor can forward a link to its own customer, who sees the timeline and ETA for that one shipment and nothing else. Messages go out through Twilio SMS and SendGrid email, with delivery logs so your team can confirm a customer was actually told about a delay.

Portal from your TMS vendor or a custom portal

Many TMS products include a basic customer portal, and if it shows your loads accurately and your shippers are satisfied, keep it. Tepia recommends a custom portal when:

• You run several carriers or modes and the TMS portal only shows your own trucks.
• Key accounts ask for features the vendor will not add, such as their own references or temperature logs.
• You want the portal to sell your service, with your brand and domain, not the vendor’s.
• You plan to expose the same data through an API to shippers’ own systems.

A tracking portal often grows into a broader customer portal with ordering and reporting. See related projects on our work page or contact Tepia to scope yours.

Frequently asked questions