How the network moves

From click to counter, one clear path.

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.

01Discover02Confirm03Prepare04Handoff

Choose your route

The same network feels different on each side of the counter.

Switch perspectives to see the actions that matter to a shopper and to an independent retail partner.

Shopper route

Useful products, a visible handoff and a nearby place to ask.

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.

  1. 01

    Browse what is published

    Search the live assortment and see honest empty or unavailable states when the catalog has not published an item.

  2. 02

    Choose what fits today

    Review the useful details, select a quantity and confirm the contact information needed for the order.

  3. 03

    Follow the local handoff

    The station receives the request and prepares the order against the current local workflow.

  4. 04

    Collect with context

    Complete the handoff at the counter with a direct route for questions or corrections.

Browse the live catalog
A shopper selecting products in a neighborhood grocery aisle
Digital discovery stays connected to a real local handoff.

The shopper map

Four moments connect an online choice to a local counter.

This is the intended service path. Exact fulfillment options and timing depend on the published catalog and the participating station.

  1. Discover

    Find the useful shelf

    Search or browse a category using product information currently published to Frivi.

  2. Decide

    Review before committing

    Check the available description, price and stock signals without substitute products filling a gap.

  3. Prepare

    Route the request locally

    Order information moves to the service-station workflow so goods can be checked and prepared.

  4. Handoff

    Close the loop at the counter

    The shopper receives the order through the available handoff and can raise a clear exception if something changed.

A customer completing a contactless payment at a grocery counter
Visible by design. Catalog outages, empty shelves and validation errors remain real interface states. Frivi does not replace them with invented success data.

Partner onboarding

A staged opening, with a useful output at every step.

There is no single checklist that can prove every store is a fit. The process creates decision points before time and operating commitments accumulate.

  1. 01
    Fit conversation

    Understand the store and street

    Review the existing business, service area, available space and the operator's priorities.

    Working output: A documented fit brief
  2. 02
    Station design

    Define the operating scope

    Select relevant service modules and name what remains outside the initial opening.

    Working output: A scoped station plan
  3. 03
    Readiness

    Rehearse repeatable work

    Prepare catalog, receiving, order handling, customer communication and exception routes.

    Working output: A launch readiness review
  4. 04
    Opening rhythm

    Begin, observe and tune

    Open the station, record recurring issues and agree on practical adjustments.

    Working output: An operating review cadence

Commercial terms, timing and service availability are confirmed during the fit process, not promised by this overview.

Discuss your store

Click-to-counter swimlane

One order, three coordinated views.

The shopper, platform and station each have distinct actions. Clear handoffs prevent a digital confirmation from getting ahead of physical reality.

ParticipantDiscoverConfirmPrepareHandoff
ShopperSearches the published assortmentSubmits chosen items and contact detailsWatches for the current order stateChecks and receives the order
FriviPresents live catalog informationValidates the request and records itConnects status and exception informationKeeps the service record legible
Service stationMaintains local shelf contextReceives the order requestChecks goods and prepares the handoffCompletes service and raises issues

Payment, collection and delivery methods may vary by station. Only options actually available should be shown to a shopper.

Who owns what

Shared standards work only when ownership is specific.

Frivi provides connective structure. The local operator provides place-based judgment. Several service moments need both.

01Frivi

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
02Local partner

The station layer

The operator owns the work that depends on the physical store and the local customer relationship.

  • Local receiving and shelf checks
  • Order preparation and counter handoff
  • Local service judgment and escalation
03Shared

The improvement loop

Both sides need a common record of recurring friction to improve the service without hiding it.

  • Readiness and routine reviews
  • Exception categorization
  • Clear changes to operating scope

When the normal path breaks

An exception needs a route, not a vague apology.

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.

Availability changed

An item cannot be prepared as shown

Pause the affected handoff, confirm the current shelf state and communicate the available next choice without silently substituting.

First owner: Service station
Order needs correction

Contact or item details are incomplete

Keep the request in a reviewable state and ask only for the information needed to continue.

First owner: Frivi flow
Service question

The issue does not fit a standard state

Route the context to a person through the published contact channel and retain the request ID where available.

First owner: Shared support

A traceable next step

When OneHub returns an error or rate limit, Frivi preserves the request identifier so support can discuss the actual event rather than guess.

Practical questions

What the process does and does not assume.

These answers describe the intended operating model. A specific location or order can have additional terms.

01

Does every Frivi station offer the same assortment?

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.

02

Can a shopper use Frivi without opening an account?

The OneHub order contract supports guest ordering. A specific storefront may still ask for the contact and fulfillment details required to complete that order.

03

Does Frivi replace the store operator's judgment?

No. The model separates shared digital routines from decisions that belong with the local operator, including physical checks and customer-facing handoff.

04

How long does partner onboarding take?

This page does not promise a fixed timeline. Scope, readiness and location circumstances are reviewed before an opening plan is confirmed.

05

What happens when a request is rate limited?

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

See the model in the context that matters to you.

Explore the partner path for a deeper view of store fit, or start a direct conversation about a location and its operating needs.