Skip to content

FousLOOP

Get your LOOP orders and approvals through an API

Read your LOOP Order History, the orders waiting in Order Approvals and the stock of your usual items at a store or Licensee Service Center with one API call each. Or have a workflow email you each weekday morning the orders still Pending Approval per LID.

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

What you can build on LOOP

  • Get order history

    Build this

    Opens Order History from the licensee dropdown and reads each placed order and its details for one LID.

    Takes
    LID, placed since (optional)
    Returns
    Order number, placed date, status, fulfillment type, store or LSC, pickup or delivery date, items, quantities
  • List orders waiting for approval

    Build this

    Reads Order Approvals: stock orders your buyers placed and Special Orders your authorized vendors entered, both waiting for an Approver.

    Takes
    LID, date range (optional)
    Returns
    Order number, submitted by, vendor, submitted date, fulfillment, items, quantities, payment method
  • Check stock for a list of items

    Build this

    Searches each PLCB item number for the store or Licensee Service Center set as your fulfillment location and reads whether it can be ordered.

    Takes
    LID, fulfillment type, store or LSC, PLCB item numbers
    Returns
    PLCB item number, product name, in stock or out of stock
  • Place an order from item numbers

    Build this

    Adds items with Enter SKUs manually, checks out with the pickup or delivery date you give and places the order, which then waits in Pending Approval.

    Takes
    LID, fulfillment type, store or LSC, PLCB item numbers and quantities, date, time or payment method
    Returns
    Order number, status, items added, items not available, pickup or delivery date

Automate LOOP 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 still Pending Approval, every LID

    Build this
    Starts
    Every weekday at 8:00 Eastern Time
    Step 1
    For each LID you name, list the orders waiting in Order Approvals.
    Step 2
    Stop when no LID has an order waiting.
    Step 3
    Email you the list, one section per LID, with each order's items and fulfillment.
  • Last week's LOOP orders, handed to accounting

    Build this
    Starts
    Every Monday at 7:00 Eastern Time
    Step 1
    For each LID, get the order history for the last 7 days.
    Step 2
    Keep the orders that were not there on the last run.
    Step 3
    Post each order, with its items and quantities, to your accounting system's webhook.
  • Out-of-stock items on your usual order

    Build this
    Starts
    Every weekday at 6:30 Eastern Time
    Step 1
    Check stock for your list of PLCB item numbers at your store or Licensee Service Center.
    Step 2
    Keep the items shown as out of stock.
    Step 3
    Email you those items before anyone builds the day's order.

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": "lcbloop.com/get_order_history",
    "input": {
      "lid": "LID-48213",
      "placed_since": "2026-11-02"
    }
  }'
Example response
{
  "status": "completed",
  "data": {
    "lid": "LID-48213",
    "orders": [
      {
        "order_number": "LP-2093381",
        "placed_date": "2026-11-09",
        "status": "Pending Approval",
        "fulfillment_type": "LDP",
        "location": null,
        "delivery_date": "2026-11-13",
        "items": [
          {
            "plcb_item_number": "000004521",
            "name": "Acme Reserve Bourbon 750ML",
            "quantity": 24
          }
        ]
      }
    ],
    "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.

LOOP’s own options

The PLCB does not document an API for LOOP. Licensees place and approve orders in the website, where a large order can be uploaded as a two-column CSV or Excel file. The board publishes its wholesale catalogs as Excel downloads, and order, invoice and return history stays in LOOP for up to two years.

OptionWhat it coversWhat it takes
CSV or Excel order uploadAdds many items to an order at once: column A the PLCB parent item code or the SCC/GTIN for cases, column B the quantity.A LOOP account. The order is still checked out and placed in LOOP, and LOOP offers a CSV template to download.
Wholesale catalogsFull RTDC, Wine, Spirits, Special Order and Accessories catalogs as .xlsx, and the item changes of the past 12 weeks.Nothing: public downloads on the PLCB's LOOP page, with instructions and a field descriptions file.
Email notificationsEmail updates on order fulfillment.A LOOP user account.
LOOP by handOrder entry, Order History, Order Approvals, invoice and return history and Special Order approvals, one LID at a time.Enrollment in LOOP and a registered user. Available 24 hours a day, 7 days a week.

Read on November 12, 2026: Order wine and spirits online: LOOP portal, Licensee FAQs about LOOP, LOOP Order Entry Quick Reference Guide.

Signing in to LOOP

LOOP signs you in with your email address and password, and passwords expire. If you registered several LIDs with the same email address, one sign-in shows them all. With Fous you sign in once through LOOP'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

Every order waits for an Approver
A placed order goes to Pending Approval until a Licensee Approver or Admin approves it. Special Orders entered by an authorized vendor also wait for you to approve them and choose the payment method.
No changes after submitting
LOOP allows no edits to a submitted order: you cancel it and submit again. Pickup orders can be canceled until picking has begun, and LDP orders until 1:00 PM ET two business days before delivery.
Item codes depend on how you order
You order units by the PLCB item number and cases by the manufacturer's SCC/GTIN. Search uses the SKU/PLCB item number for store and LSC pickup and the SCC for LDP.
Store pickups are paid at the store
Online payment in LOOP covers only LDP, Licensee Service Center pickup and Special Orders. An order picked up at a Fine Wine & Good Spirits store is paid there at pickup.

More in Government: US courts, records, permits and licensing

Other industries: Halifax Intermediaries Online, FBI NICS E-Check, PASSPort, My DOR, NYS DOL Unemployment Services for employers, thermofisher.com.

Frequently asked questions

No. The PLCB documents no API for LOOP. You place orders in the website, by hand, by barcode scan or by uploading a two-column CSV or Excel file, and the wholesale catalogs are published as Excel downloads. With Fous you can build methods that read your orders and approvals and call them from code.

Upload a .csv or .xlsx file while entering the order. The file has two columns: column A the PLCB parent item code for units or the SCC/GTIN for cases, column B the quantity. You then check the items, add them to the cart, check out and place the order.

No. LOOP allows no edits to a submitted order, only a cancellation, after which you submit it again. Store and LSC pickup orders can be canceled until picking has begun; LDP orders until 1:00 PM ET two business days before the delivery date.

Up to two years. Returns, orders and invoice history placed through the current LOOP stay available for that long, so a workflow that copies your orders to your own system each week keeps a record beyond it.

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

Put LOOP 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.

Read nextSunshine 811Texas811 PortalUSA North 811Halifax Intermediaries OnlineHow methods workHow workflows run

Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of LOOP (Pennsylvania Liquor Control Board). 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.