Partner Program FAQ

The F2 Core Partner Program is the public path for service vendors, equipment providers, installers, compliance partners, waste partners, and related organizations that want to use F2 Core-powered tools to run their own business, support customers, coordinate work, and participate in approved hardware opportunities where authorized.

No. Partners purchase F2 Core-powered tools for their own company. They do not resell F2 Core software, software licenses, or the platform itself.

Yes — when they are explicitly authorized for the relevant product categories. Approved hardware is a separate, governed motion and should never be confused with software resale.

Partners can sell their own products and services, approved F2 products available for partner sale, sourced products they buy from other partners or vendors, and approved F2 Core hardware products when authorized.

Yes. Partner commerce can support sourced products from other vendors or partners while keeping internal source visibility and customer-facing continuity intact.

When policy allows, purchased or approved products can move into the customer’s parts-master workflow with fields such as SKU, source, preferred supplier, substitutes, asset compatibility, warranty data, reorder rules, and service associations.

The customer portal can include service requests, assets, quotes, approvals, workflow milestones, service history, documents, approved parts visibility, and hardware or installation status where applicable.

Yes. If a dealership licenses the Vendor Communication Module, it can sponsor portal access for a partner relationship inside the dealership’s F2 environment under a vendor sub-domain for that dealership relationship.

A paid partner plan becomes necessary when the partner wants to support multiple dealerships, use F2 Core with its own customers, publish its own commerce experience, unlock advanced workflows, or manage broader cross-organization relationships.

Yes. Customer organizations and relationship-scoped access can be provisioned based on the portal model and approved setup.

Yes. F2 Core can support partner-to-partner sourcing, installations, service coordination, compliance collaboration, and other cross-organization workflows with scoped visibility and auditability.

Yes. A partner can use F2 Core to manage its own internal assets, requests, approvals, service vendors, and documentation while also supporting customer-facing relationships.

Enterprise Action Engine can route requests, draft follow-up, summarize status, flag missing information, recommend next actions, and escalate aging approvals while keeping governed approval controls in place.

High-risk actions such as money movement, vendor awards above threshold, hardware ownership changes, compliance sign-off, customer access changes, contract overrides, and destructive record changes still require explicit approval.

Customers can search the /partners directory by location, partner type, approved product, service capability, and other filters, then open decision-ready partner profiles.

Eligible partners can receive a public partner profile page, especially when they have an approved public program status and, where relevant, a paid F2 Core system and authorized hardware participation.

No public dollar figures should be shown on the /partners package page. Approved users can log in or register to view commercial details where applicable, and qualified prospects can talk to sales about scope and package fit.

F2 Core should keep organization relationships, roles, permissions, and visibility scoped so each party sees only the customers, sites, assets, workflows, and documents they are authorized to access.