Tracktainer Blog
Gate out

Logistics tech

Putting a tracking box on your own website

Your customers should not have to leave your site to find their container. This takes an afternoon.

Quick take

  • An embedded tracking box keeps customers on your domain.
  • Implementation is a container div and a script tag.
  • Style it to match your site, or it looks like an advert.

Most forwarder websites send customers to a carrier site to track. That is a customer leaving your brand to get information you could have given them.

Why it belongs on your site

Three reasons. Your customer stays with you rather than learning the carrier's brand. You see which shipments generate anxiety, which is genuinely useful demand signal. And you stop answering the same status question by email fifteen times a week.

How it works

Structurally it is a container element plus a script that renders into it:

<div id="tracking-root" data-config='{"lang":"en"}'></div>
<script src="https://your-provider/widget.js" async></script>

The script injects the search box and the results view. Nothing else on your page needs to change. If you are migrating from another provider, the swap is usually two lines and a configuration value.

See it on your own shipment

Paste a container number, bill of lading or booking reference. We detect the carrier across 170+ shipping lines, and when the data does not line up, a person checks it.

Making it yours

The default styling of any widget looks like someone else's product sitting inside your page. Spend an hour matching the typeface, the border radius and the button colour to your site. Customers trust a search box that looks like it belongs there, and they hesitate over one that does not.

Put it on the page people already visit when they want status, usually the contact page or the customer area. Do not bury it in a menu.

Questions people ask

Does it slow my site down?

A well built widget loads asynchronously and should not affect your page render.

Can I use my own design instead?

Yes, if you build against the API directly. More work, complete control.

Read next