many locations
One process logic for a client-defined location network.
A deployment may cover a plant, campus, museum, training facility, or technical site.
The client chooses the use and point order. Each location gets a QR/NFC marker,
and the app shows its technical read status.
A physical marker and optional geofence can technically validate a scan
in a specific place. The client defines the purpose and scope of that confirmation.
Location is used only during map use or scan time when the scenario requires it.
operations
Accurate locations and clear ownership are part of the project.
Routes with multiple points need a solid operational map. The client identifies the locations
and secures the permissions needed to place markers. Markerra adds the supplied locations to the
technical configuration, while the client team handles day-to-day site operations.
On the technology side, we prepare the app, QR/NFC identifiers, scan validation, and a diagnostic
report. On the client side remain the goal of the process, the content, the placement and upkeep
of the markers, and the process instructions.
service boundaries
Markerra builds the technology to a completed specification.
The client hands over the final map, order, texts, interface files, and rules.
Markerra verifies feasibility, implements, and tests the agreed features.
The client supplies the concept, map, order, content, branding, and reward and independently organizes
the project. Markerra produces the system and an aggregated report covering starts, scans, progress,
completions, and handled rewards, without targeting, retargeting, or advertising attribution.
With multi-location routes, consistent support at every point matters. The site contact
should know where the marker is, what a correct scan looks like, and what to do when a scan fails.
Before launch, the client prepares a simple site card: point name, marker location, QR/NFC type,
the participant-facing message, and a help instruction. Markerra supplies a technical marker test instruction.
