TourviaApp passed Salesforce Security Review. Tourvia is available through private AppExchange access.

The short version. The Salesforce managed package metadata now shows TourviaApp, version name ver 7.25.0, version number 7.25, published by SKZ Consulting. It passed Salesforce Security Review on May 22, 2026. Customers can install it today through private AppExchange access. Public discovery is held while the remaining listing copy and visuals are finalized for the Tourvia brand.

What actually happened

Salesforce runs a formal security review for every managed package that wants to be distributed through AppExchange. The reviewers test the package against the Lightning Platform security standards, including authentication, data access, sharing, CRUD and FLS enforcement, secret handling, third-party callouts, and how the package behaves inside customer orgs.

The current package metadata shows application name TourviaApp, publisher SKZ Consulting, version name ver 7.25.0, and version number 7.25. That package completed the review on May 22, 2026. Customers install it under the Tourvia product brand.

What Salesforce Security Review actually means for buyers

For Salesforce IT, security, and procurement teams, the relevant signal is not marketing. It is the answer to four practical questions:

• Has the package been reviewed against Salesforce's security standards before any customer org installs it?
• Does it enforce sharing, CRUD, and FLS rules instead of bypassing them?
• Does it manage secrets and external callouts the way AppExchange expects?
• Is the package distributed through the AppExchange pipeline rather than as an unmanaged metadata drop?

TourviaApp ver 7.25.0 cleared all of that. For an InfoSec or Salesforce architect doing vendor due diligence, this usually shortens the questionnaire and removes the most common blockers around installing a third-party managed package.

What "private AppExchange access" means in practice

The package is fully buildable, installable, and supported. What is not happening yet is public discovery: the listing is not searchable in AppExchange. Access is shared directly through an install link.

In other words:

• The install path is the same managed-package flow customers expect.
• Upgrades and patches go through the normal AppExchange pipeline.
• The Security Review status applies to the package, not to whether the listing is publicly searchable.
• The only difference from public listing is who can find the listing without a direct link.

Why public listing is waiting on rebrand, not on product

The original AppExchange work was built under the RouteForce name. The product is now called Tourvia on the customer-facing side, while the current application metadata shows TourviaApp. Before public discovery goes live, the listing copy, naming, and visuals need to fully line up with Tourvia so customers do not arrive on an inconsistent brand.

That work is mechanical. It is not waiting on product engineering or security readiness. It is waiting on the final rebrand and publication step. Until then, distribution stays private.

What buyers can actually use today

This is the same Salesforce-native field execution app we have been shipping. Nothing about the feature set is "preview" or "coming soon" in the install you get through private access.

Route optimization inside Salesforce

The route engine runs on Account, Contact, Lead, Opportunity, and custom objects with geolocation. Field reps and managers plan and re-optimize routes from the same Salesforce workspace, not from an external app that syncs back.

Campaign Member mapping

Salesforce Campaign Members (Lead and Contact members) appear on the map from a Campaign record page or from the global Tourvia workspace with a target campaign picker. Member status can drive marker color via Custom Metadata.

Visit planning

Visits are created as standard Salesforce events or as Tourvia visit records, linked back to the originating Account, Contact, Lead, Opportunity, or Campaign Member. Planning, route order, and visit creation stay on the same map.

Mobile field execution and GPS check-in

Reps run their day from the Salesforce mobile app. Tourvia handles GPS check-in at each stop, captures arrival and departure timestamps, and records the data against the visit so it appears in standard Salesforce reports.

Visit reports and dashboards

Visit data is regular Salesforce data. The package ships with prebuilt reports and dashboards for visit volume, coverage, plan vs actual, and field activity. Admins can clone and customize them like any Salesforce report.

Pricing during private access

While the listing is private, the commercial model is org-level: one flat price for the Salesforce org, not per user. This makes rollout decisions simpler. Adding more reps inside the same org does not change the price, so coverage decisions are not gated by per-seat math.

When the public Tourvia listing goes live, the pricing model will move toward a license-based structure published with the listing. Customers who sign during the private access window keep the org-level pricing for the agreed term.

If that org-level pricing matters for your buying decision, the practical answer is to lock it in before public listing. Once the listing is live, the published license-based pricing applies to new customers.

How to start an evaluation

Two paths, both straightforward:

• Request a private AppExchange install link. We share it directly with your Salesforce admin or IT contact.
• Or schedule a working session where we walk a Salesforce admin through install, permission sets, and the first end-to-end route, visit, GPS check-in, and report.

FAQ