Do you replace Sendcloud, MyParcel or ParcelPro?
For smaller webshops working with one or two carriers, those tools are usually sufficient. We don't build an alternative for them, and we will honestly point you back to the standard packages. We do build custom track & trace software when you combine multiple carriers with your own drivers, want a fully white-label tracking experience, have specific compliance requirements (pharma, food, medical devices), need batch and lot traceability that parcel shippers don't cover, or want to integrate your own GPS or RFID hardware for which standard SaaS offers no room.
Which carriers and APIs do you support?
We have built production integrations for PostNL, DHL, DPD, UPS, GLS, Bpost and various parcel aggregators such as Sendcloud (as an event source for shipments you book there) or ShipStation. For lesser-known carriers, we build the integration based on their documentation, via webhook bridges or via EDI where that is the only option. We connect your own drivers via a mobile scanning app, via your existing planning or TMS system, or via a combination of both.
What is the difference between GPS tracking and scan-based tracking?
GPS provides continuous real-time location, which is ideal for vehicles, asset pools and equipment where you need to know at all times where something is. Scan-based tracking provides event data at handover points (collection, hub, delivery) and is cheaper for parcel flows because you don't need hardware for each item. For most clients we combine both: GPS on the driver or lorry, scans on the consignment itself, and BLE beacons or RFID where they fit (for example in a warehouse or for returnable packaging).
Can an in-house tracking system be fully white-label?
Yes, that is exactly why many clients opt for custom development. A tracking page on your own domain in your house style, SMS and email templates in your branding, with no external logos or brand names. We configure notification senders with your own sender ID and set up DKIM/SPF properly, so messages arrive in the inbox as coming from you and not in spam. Push notifications also come through your own app, with your own sound and icon.
What determines the cost of a track & trace project?
The main factors are: the number of carriers and internal systems we integrate with, whether you need tracking at asset or batch level (with or without hardware), the volume of notifications and events per day, and how many branded customer flows (portal, push, SMS, email) are required. Compliance requirements for pharma or food make the data model and audit layer more complex. After the first conversation, we give you a direction; a scope with assumptions and risks follows only after the architecture phase.
How long before a first version can go live?
That depends on the scope. A first working tracking page for one carrier and one notification flow can be live within a few sprints, giving you something to test straight away. A multi-carrier platform with a customer portal, ERP integration and your own drivers is a multi-sprint project and typically goes live in phases: first a pilot segment or pilot carrier, then a broad rollout across the rest of your operation. We work in two-week sprints with a working build at the end of each, so you are never left in the dark for long.
Do you work with our IT department and existing systems?
Almost always. We connect to your WMS, TMS, ERP (Exact, AFAS, SAP, NetSuite or custom), and to your identity provider for SSO. During rollout we transfer knowledge to your IT team with a runbook, architecture overview and clear responsibilities, even if you later want to take over maintenance yourself or have another party handle it. We do not build lock-in at the codebase level.
How do you handle data volume and performance?
Tracking platforms grow quickly: a driver sending a GPS ping every 30 seconds already generates thousands of events a day. We model events with PostgreSQL plus PostGIS for geo queries, use Redis for live state, and Kafka or another event broker when volume requires it. History is archived to cheaper storage tiers, with the option to look back for an audit without slowing down operational queries.