Questions, answered plainly.

Waytrail is the operational platform between your tracking technology and your teams. It takes detections from readers, filters and interprets them, maps them to recognisable zones on your floor plans, and keeps a searchable current location and a time-stamped history for every tracked item. Teams use dashboards, search and reports, while other systems can use the same record through the API and webhooks.

Waytrail addresses three recurring visibility problems: valuable assets moving when or where they should not, inventory records drifting away from what is actually on the floor, and people losing productive time searching for equipment, stock or containers. The same platform can support more than one use case, but a deployment should begin with a specific operational problem and a clear outcome worth measuring.

Waytrail is best suited to warehousing, distribution, manufacturing and other physical operations where assets move frequently, are shared between teams, are expensive to lose, or take meaningful time to find and count. It earns its place wherever finding, counting or securing things costs real time. Where items are few and low in value, movement is rare, or an existing process already gives reliable visibility without much manual effort, a simpler approach will do.

Waytrail can track equipment, tools, containers, totes, pallets, work in progress, stock units and other physical items that can carry a suitable tag. The right level of tagging depends on the use case: sometimes every asset needs its own identity; sometimes tracking the pallet, tote or container provides the value. Materials, environment, movement patterns and the economics of the item all affect the choice.

No. Waytrail separates the operational platform from the tracking technology beneath it. RFID, BLE, UWB and other detection sources can feed the same asset records, floor plans, search, history, reports and integrations. The technology, or combination of technologies, should be chosen around the problem rather than treated as a fixed part of the product.

That depends on the range and precision you need, how and where items move, the materials involved, the volume of assets and the economics of the deployment. RFID is often effective for identifying tagged items at controlled movement points; BLE can provide broader proximity or presence information; UWB can support more precise positioning but usually requires greater infrastructure investment. We define the operational question first, then select and test the technology that can answer it reliably at a sensible cost.

Accuracy depends on the tracking technology, tags and readers, their placement, the physical layout, nearby materials, interference and what counts as a useful location for the operation. We start by defining whether you need building, room, zone, doorway or more precise positioning, then design and pilot the deployment against that requirement.

An item needs its own tag if you want Waytrail to identify and trace it individually. If the commercial question can be answered by tracking a pallet, tote, cage or other handling unit, the contents may not need individual tags. Choosing the right tagging level is important because it affects hardware, process design and the economics of the deployment.

Potentially. Waytrail is not tied to one hardware vendor, but compatibility depends on the tracking technology, reader interfaces, event format and the quality of the detections produced. We assess existing hardware before committing to reuse it; vendor independence does not mean that every device will work without configuration or integration.

Waytrail keeps showing the position it last confirmed, together with when and how it was determined, rather than presenting an old sighting as if it were new. It filters duplicate and low-confidence detections, preserves the underlying sighting history and can surface assets that have not been seen within the expected period. Reader placement and pilot testing are used to reduce missed detections where they would undermine the use case.

Start with the operational problem, not a shopping list of tags and readers. We need to understand what you want to track, how it moves today, where visibility breaks down, what level of location accuracy would change a decision, and how success should be measured. Floor plans, representative assets and access to the relevant site and process help turn that into a practical deployment design.

No. A focused first deployment is usually more useful than trying to instrument an entire operation at once. One area, asset group or movement route can test the technology, data quality and operational value before coverage is extended. The platform is designed so additional sites, areas, zones and read points can be added as the case is proven.

Yes. A pilot should test a defined operational question in a representative area, not simply prove that a reader can detect a tag. We agree the assets, locations, read points, workflows and success measures in advance, then review detection quality, user experience and commercial value before deciding whether and how to expand.

It depends on the size of the area, the tracking technology, hardware availability, installation requirements, integrations and the amount of operational testing required. After reviewing the use case and site, we provide a phased plan with a clear first deployment rather than offering a generic timetable that may not survive contact with the environment.

Yes. Waytrail provides a REST API covering the same operational record used by the application, including assets, tags, locations, sightings and current positions. Webhooks push events as they happen, deliveries are signed, and the delivery history can be inspected so integrations can verify what was sent and when.

Yes. The API and webhooks allow other systems to consume positions, sightings and movement events, and integration can also connect Waytrail records to the asset or stock identifiers you already use. The exact design depends on which system should remain the system of record, which events need to move between systems and what decisions the integration is intended to support.

Usually not. A WMS or ERP records what should have happened through booked transactions; Waytrail adds evidence of what was physically detected on the floor. The value often comes from comparing or sharing those two views, while leaving the existing business system responsible for orders, stock accounting and core operational processes.

Waytrail records movement events as they occur and can send them to connected systems through signed webhooks. Those events can feed the alerting, messaging or workflow tools your teams already use, for example when an item leaves a zone or moves outside an expected period. The relevant rules, destinations and response process are defined as part of the deployment rather than assuming every movement should produce an alert.

You own the operational data Waytrail holds about your assets, tags, locations, sightings and movement history. The API allows that record to be read and exported, so the value you build in the data is not trapped inside the user interface. Any required export, retention or handover arrangements can be documented as part of the deployment.

Each customer has a dedicated Waytrail deployment, so your operational data is held in its own instance rather than in a shared multi-tenant database. We can operate that deployment for you or work with your technical team to agree where it should run, how it connects to your environment and what operational responsibilities sit with each party.

Pricing follows the shape of the deployment rather than a single per-user licence. The main drivers are the number and complexity of sites, the tracking technology and read points required, the scale of what is tracked, integrations, implementation work and the ongoing operating and support model. We normally scope a focused first deployment so the cost can be considered against a specific operational and commercial outcome.

Waytrail is designed, built and supported by The Curve. Support can cover the application, integrations and operation of the deployment, with responsibilities and service expectations agreed around the way you choose to host and run it. Responsibility for hardware support is agreed according to who supplies and manages the devices.

Waytrail is designed, built and supported by The Curve, an independent UK technology consultancy based in Sheffield. The team combines software engineering, data, product and operational expertise, allowing us to shape the tracking technology, platform and integrations around the problem rather than selling a fixed hardware package.