Skip to content

FousProvi

Pull your Provi orders and invoices into your systems

Build methods that return your Provi Order History, the status your rep gave each order and your ProviPay invoices from one API call each. A workflow can then check each morning which orders are still Sent or Seen and hand new invoices to your accounting.

Start building freeBook a demo

Works with your own Provi account. Fous is an independent product.

What you can build on Provi

  • Get order history

    Build this

    Reads Order History and each order's details for the dates you choose: order date, distributor, status, PO number, items and estimated total.

    Takes
    From date, to date, status (optional)
    Returns
    Order date, distributor, status, PO number, number of items, estimated total

  • Read an order's details and rep messages

    Build this

    Opens one order from Order History and reads the order details page: the items ordered, the status at the top and the messages with your rep.

    Takes
    Order date, distributor
    Returns
    Status, items with quantity and price, PO number, order notes, rep messages

  • Check ProviPay invoices

    Build this

    Reads your ProviPay invoices in Payments: each invoice from a partnered distributor with its due date, status, total and who paid it.

    Takes
    Status (optional), distributor (optional)
    Returns
    Invoice, distributor, due date, status, total, paid by

  • Send an order to one distributor

    Build this

    Adds the products you list to the cart, adds a PO number and order notes, and sends that distributor's order with Send Order.

    Takes
    Distributor, products with quantities, PO number (optional), order notes (optional)
    Returns
    Distributor, sales rep, status, items, estimated total

Automate Provi with a workflow

A workflow runs your methods as one process, with nobody at the screen. A schedule or a call from your own system starts it, the steps run in order, and the result arrives in your inbox or in the systems you already use.

  • Orders your reps have not confirmed yet

    Build this
    Starts
    Every weekday at 9:00
    Step 1
    Get the order history for the last two days.
    Step 2
    Keep the orders still in Sent or Seen, and any marked Rejected.
    Step 3
    Email you the list with order date, distributor, status, PO number and estimated total.

  • New ProviPay invoices, handed to your accounting

    Build this
    Starts
    Every weekday at 10:00
    Step 1
    Check the ProviPay invoices on the Invoices page.
    Step 2
    Keep the invoices that were not there on the last run.
    Step 3
    Post the invoice, distributor, due date, status and total to your accounting system's webhook.

  • Overdue and failed invoice payments

    Build this
    Starts
    Every weekday at 8:00
    Step 1
    Check the ProviPay invoices with the status Overdue or Failed.
    Step 2
    Stop when there are none.
    Step 3
    Email you each one with distributor, due date and total.

You can run a workflow by hand on every plan, Free included. Schedules and webhook triggers come with the paid plans, from $29 a month.

Once built, one call from your code

Once you have built a method, it is one POST to /v1/runs from your backend, or a tool an AI agent calls over MCP. This is what “Get order history” would look like.

Example request
curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "app.provi.com/get_order_history",
    "input": {
      "from_date": "2026-11-09",
      "to_date": "2026-11-11"
    }
  }'
Example response
{
  "status": "completed",
  "data": {
    "orders": [
      {
        "order_date": "2026-11-11",
        "distributor": "Northwind Wine & Spirits",
        "status": "Seen",
        "po_number": "ACME-2291",
        "items": 14,
        "estimated_total": 1186.4,
        "currency": "USD"
      }
    ],
    "count": 1
  }
}

An example with invented data, not a ready-made endpoint. The method exists in your organization once you build it, and its name, inputs and fields follow your request.

Provi’s own options

Provi's help centre for buyers covers ordering, Order History, a Reports Dashboard and ProviPay in the web app, and documents no API for buyers. Its integrations connect Provi to the handhelds of partnered distributors' reps and to OHLQ's Wholesale Cloud system in Ohio.

OptionWhat it coversWhat it takes
Partnered distributorsYour order reaches the rep on the distributor's integrated handheld, and the distributor can mark it Rejected. Their invoices appear in ProviPay.A distributor that is partnered with Provi. With others, orders go to the sales rep you add, by text and email.
OHLQ integrationOHLQ's catalog with live stock and pricing; high-proof spirits orders go to OHLQ's wholesale portal next to your beer and wine orders.A permitted Ohio on-premise establishment signed up for Provi.
ProviPay autopayPays a partnered distributor's invoices on the invoice due date, before the delivery window begins.A linked bank account and a user with the Admin or Finance role, enrolled per distributor in Payment Settings.
Provi by handOrder History, order details with rep messages, the Reports Dashboard, the Invoices page, and an Order Summary PDF from the cart.A Provi buyer account. Pricing shows only with a valid liquor license on the account.

Read on November 12, 2026: What do the different order statuses mean?, FAQs: ProviPay Payments, OHLQ expands digital initiatives with Provi integration.

Signing in to Provi

Provi signs you in with your email address and a password, or with single sign-on through a Google, LinkedIn or Microsoft account. A new account confirms its email with a verification code. With Fous you sign in once through Provi's own sign-in with your own account: the login is sealed with AES-256, code and AI agents never see it, and an expired session is signed back in.

Worth knowing

Statuses come from your rep
An order moves from Sent to Seen when the rep opens it, then Confirmed. A confirmed order can still change, for example when out-of-stock items are removed. Rejected appears only with partnered distributors.
Invoices arrive after delivery
An invoice appears once the order is delivered and finalized, typically one business day after the delivery date. Its total can differ from the order's estimated total after the rep's discounts, custom pricing or swaps.
Minimums and cut-off times per distributor
Some distributors require the first order of their business day to meet the order minimum, and some need your account number or a sales rep on file. The cart shows each distributor's cut-off time and minimum.
Only Admin or Finance can pay
Only users with the Admin or Finance role can pay invoices. ProviPay shows invoices only from distributors partnered with Provi, whatever way the order was placed.

More in Food service, restaurants and alcohol

Other industries: Q2 business online banking, CareCredit Provider Center, Cổng thông tin hóa đơn điện tử, Income Tax e-Filing Portal, My ARC, Facturación Electrónica DIAN.

Frequently asked questions

Not for buyers, in what Provi documents. Its help centre for buyers covers the web app: ordering, Order History, the Reports Dashboard and ProviPay. Provi's integrations connect it to partnered distributors and to OHLQ in Ohio.

Open Order History from the main menu: each order shows its status, and the order details page shows it at the top. The statuses are Sent, Seen, Confirmed and, with partnered distributors, Rejected. A workflow you build can read this page every morning and email you the orders not yet confirmed.

Because the order total is an estimate. The finalized invoice includes your rep's discounts, custom pricing and swaps for out-of-stock items. With methods that read both, you can compare the estimated total with the invoice total.

Provi names three reasons: a missing account number, a missing sales rep, or an order below the distributor's minimum. The cart shows each distributor's cut-off time and order minimum. A newly added account can take 3 to 5 business days to update in Provi.

No. Fous is an independent product. You use it with your own Provi account, and a method reads and does only what that account can.

Put Provi behind an API call

Describe one job in Studio and see the method it builds, with 100 credits a month and no credit card, or book a demo and bring the sites your team signs in to.

Start building freeBook a demo

Read nextmyCokeBEESMETRO Online-KundenkontoQ2 business online bankingHow methods workHow workflows run

Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of Provi (Provi). The name is used only to say which system this page is about. Something here wrong or out of date? Write to legal@fous.com.