Using a different carrier? See Package Tracking.
Introduction
Zembula reads InPost parcel tracking for Poland through InPost's ShipX tracking API. InPost's tracking doesn't need an API key, so there's nothing to create at InPost and nothing to paste in Zembula.
Zembula only reads tracking. It never creates or changes your shipments.
This guide covers connecting InPost in the Zembula platform and using it in your content.
Who can do this
You don't need an InPost developer account or an API key. InPost's tracking can be read without one.
In Zembula, only account Admins can connect InPost. Other users can open the Package Tracking page, but they can't change it.
Before you go live
This connection covers InPost parcels in Poland. InPost runs separate systems for the UK, for Italy and for Mondial Relay, so those parcels aren't covered.
InPost returns tracking for 45 days from the day the shipment was created. After that, the parcel reads as not found, so your content can show a fallback.
Each time an image with InPost tracking loads, Zembula can ask InPost for the parcel's latest scans. So each email open can use one InPost call. InPost tracks one parcel per call, and its tracking guide doesn't state a usage limit.
Connect InPost in Zembula
In the Zembula platform, open Data Sync → Integrations and select the Data integrations tab.
Click Set up on the Package Tracking tile. If Package Tracking is already set up, the button reads Open instead.
If Package Tracking is off, click Turn on. The page shows Setting up the builder source… and then Use INTERFACES › Package Tracking in the builder.
Under Carriers, click Add on the InPost row.
The row reads InPost needs no account details — connect it to add it to your tracking. Click Connect.
There's nothing to paste. The InPost row then reads Connected — starts answering within the hour.
If order data is live for Package Tracking, the InPost row reads Connected — waiting: carriers and order data can't run together until the next release. To switch, click Use InPost instead. This turns order data off and InPost on. Content that sends only an order ID then shows your fallback.
Try it
Add INTERFACES › Package Tracking to a draft image in the builder, turn on Simulate, and preview it with an InPost tracking number from the last 45 days. If a number you know is real shows no tracking, check that it's a parcel sent with InPost in Poland.
The Status section at the bottom of the Package Tracking page also lists anything that needs attention.
Using InPost in your content
Send each parcel's tracking number in tracking_number and the carrier in carrier. Zembula doesn't work out the carrier from the tracking number, so always send the carrier.
A carrier value that contains InPost as a word goes to InPost, in any case. In-Post and IN_POST work too, and so does any value that contains Paczkomat, such as Paczkomaty InPost. In Post, with a space, doesn't go to InPost.
If the number contains spaces, dashes or other separators, Zembula removes them before it asks InPost.
What shoppers see
Status: the latest scan InPost reports when the image loads, such as In Transit, Out for Delivery, Ready for Pickup or Delivered. Most scans show InPost's own English description. A scan Zembula can't classify reads In Transit.
No delivery estimate: InPost's tracking doesn't include one. After delivery it reads Delivered, with the delivery time.
Ready for Pickup: when the parcel is waiting in its parcel locker, the image can also show the locker's name, address and opening hours.
Tracking link: the parcel's page on inpost.pl.
No manage delivery link: InPost's tracking doesn't give one.
If InPost sends a parcel back to the sender, the return gets its own tracking number. Zembula doesn't follow it.
What Zembula sends to InPost
Zembula sends InPost only the tracking number, to InPost's tracking API (api-shipx-pl.easypack24.net). There are no InPost credentials to store.
To stop using InPost, open the Package Tracking page and click Disconnect on the InPost row.
Additional resources