The shared layer
The platform organizes the information and repeatable paths that connect participants.
- Catalog and content connections
- Order intake and status pathways
- Published guidance and support routes

How the network moves
Frivi joins a digital storefront to practical work inside a neighborhood retail service station.
Shoppers get a legible route from browsing to handoff. Partners get a staged route from first conversation to daily operation. Each side can see what happens next and who owns it.
Choose your route
Switch perspectives to see the actions that matter to a shopper and to an independent retail partner.
Shopper route
The experience starts with clear catalog information and ends with a local service moment. Availability and exceptions stay visible instead of being hidden behind a generic confirmation.
Search the live assortment and see honest empty or unavailable states when the catalog has not published an item.
Review the useful details, select a quantity and confirm the contact information needed for the order.
The station receives the request and prepares the order against the current local workflow.
Complete the handoff at the counter with a direct route for questions or corrections.

The shopper map
This is the intended service path. Exact fulfillment options and timing depend on the published catalog and the participating station.
Search or browse a category using product information currently published to Frivi.
Check the available description, price and stock signals without substitute products filling a gap.
Order information moves to the service-station workflow so goods can be checked and prepared.
The shopper receives the order through the available handoff and can raise a clear exception if something changed.

Partner onboarding
There is no single checklist that can prove every store is a fit. The process creates decision points before time and operating commitments accumulate.
Review the existing business, service area, available space and the operator's priorities.
Working output: A documented fit briefSelect relevant service modules and name what remains outside the initial opening.
Working output: A scoped station planPrepare catalog, receiving, order handling, customer communication and exception routes.
Working output: A launch readiness reviewOpen the station, record recurring issues and agree on practical adjustments.
Working output: An operating review cadenceCommercial terms, timing and service availability are confirmed during the fit process, not promised by this overview.
Discuss your storeClick-to-counter swimlane
The shopper, platform and station each have distinct actions. Clear handoffs prevent a digital confirmation from getting ahead of physical reality.
Payment, collection and delivery methods may vary by station. Only options actually available should be shown to a shopper.
Who owns what
Frivi provides connective structure. The local operator provides place-based judgment. Several service moments need both.
The platform organizes the information and repeatable paths that connect participants.
The operator owns the work that depends on the physical store and the local customer relationship.
Both sides need a common record of recurring friction to improve the service without hiding it.
When the normal path breaks
The exact remedy depends on the order and applicable terms. The operating principle is consistent: name the change, identify its owner and keep the next action visible.
Pause the affected handoff, confirm the current shelf state and communicate the available next choice without silently substituting.
First owner: Service stationKeep the request in a reviewable state and ask only for the information needed to continue.
First owner: Frivi flowRoute the context to a person through the published contact channel and retain the request ID where available.
First owner: Shared supportWhen OneHub returns an error or rate limit, Frivi preserves the request identifier so support can discuss the actual event rather than guess.
Practical questions
These answers describe the intended operating model. A specific location or order can have additional terms.
The public catalog shows what the connected service currently publishes. Local availability and service scope can vary, so the interface should present only confirmed options.
The OneHub order contract supports guest ordering. A specific storefront may still ask for the contact and fulfillment details required to complete that order.
No. The model separates shared digital routines from decisions that belong with the local operator, including physical checks and customer-facing handoff.
This page does not promise a fixed timeline. Scope, readiness and location circumstances are reviewed before an opening plan is confirmed.
The interface should show an honest temporary state, respect the retry guidance from the service and preserve the request ID for support.
Choose the next useful step
Explore the partner path for a deeper view of store fit, or start a direct conversation about a location and its operating needs.