What it does
parcelLab connects order data with branded delivery pages, notifications, returns and operational insights. Retailers need an account and an integration with their order information. Fees and scope are agreed in an order form, usually with annual advance billing.
Send order and parcel data through the API, file transfer or dispatch-email BCC. BCC takes less integration work, but each email must contain the required information and offers less flexibility. Order details can arrive first, with carrier and tracking numbers added later.
Create a landing page in your shop, add the Order Status Page snippet and insert your parcelLab account ID. Use the supplied sample tracking links to check the display, then adjust language, purchased-product lists and promotional banners. A split order can show its separate shipments.
For your own tracking subdomain, arrange page hosting, DNS and HTTPS, then set the branded tracking URL and test a real order link. Saving that URL does not create the website or certificate. A parcelLab-hosted arrangement has its own agreed setup.
The master agreement puts fees in the merchant's order form. Its default is annual advance payment and twelve-month renewals, with ninety days' written notice to stop renewal; the order form can set different terms. Customers registered in Germany use a separate agreement.
Strengths
- API, file transfer and email BCC provide different integration options
- One embedded page can display separate shipments from a split order
Watch out for
- Email BCC needs complete order and tracking information in each message
- A merchant-hosted tracking subdomain needs its own hosting, DNS and HTTPS
Best for
- Retailers embedding order tracking across split shipments
Sources
- parcelLab - Post-Purchase Experience Software (Oct 26, 2026)
- Enhance your delivery experience - parcelLab (Oct 26, 2026)
- Data Integration (Oct 27, 2026)
- Order Status Page (Oct 27, 2026)
- Master Software Services Agreement (Oct 27, 2026)
