Skip to content

FousHyphen SupplyPro

Turn your SupplyPro orders into an API

Read Received Orders, builder reschedules and cancellations, and order statuses from SupplyPro with one API call each. Or have a workflow pull every builder's newly received orders before your crews leave in the morning and email you the list by account.

Works with your own Hyphen SupplyPro account. Fous is an independent product.

What you can build on SupplyPro

  • Get received orders

    Build this

    Reads the Received Orders list on the Orders tab: orders BuildPro builders have sent you that nobody has accepted yet, sorted by request date.

    Takes
    Account (optional), subdivision (optional)
    Returns
    Builder order number, EPO flag, account, subdivision phase, lot and block, job address, task, total excl tax, requested start and end, late flag
  • Look up an order's status and dates

    Build this

    Finds orders with Order Search by order number, lot, account or subdivision and reads the SupplyPro and BuildPro status with the requested, acknowledged and actual dates.

    Takes
    Builder order number or lot number, account (optional)
    Returns
    Builder order number, account, job address, task, order status, builder status, requested, acknowledged and actual start and end, total excl tax
  • Get builder reschedules and cancellations

    Build this

    Reads the Alerted Orders pages for Order Reschedules and Order Cancellations: orders a builder has moved or cancelled in BuildPro that wait for your response.

    Takes
    Alert type (reschedules, cancellations or both)
    Returns
    Alert type, builder order number, account, subdivision phase, lot and block, task, requested start and end
  • Accept received orders

    Build this

    Ticks the orders you name on the Received Orders list and selects Accept Selected Orders, which changes their status and notifies the builder.

    Takes
    Builder order numbers
    Returns
    Builder order number, order status, account, task

Automate SupplyPro 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.

  • Newly received orders by account, before the crews leave

    Build this
    Starts
    Every weekday at 6:30
    Step 1
    Get the received orders on the Received Orders list.
    Step 2
    Keep the orders that were not there on the last run.
    Step 3
    Email you the list grouped by account, with late orders first.
  • Builder reschedules and cancellations to your scheduler

    Build this
    Starts
    Every hour
    Step 1
    Get the builder reschedules and cancellations from the Alerted Orders pages.
    Step 2
    Keep the orders that were not there on the last run.
    Step 3
    Post each one, with its new requested start and end, to your scheduling system's webhook.
  • Orders the builder has completed, handed to accounting

    Build this
    Starts
    Every weekday at 17:00
    Step 1
    For each builder order number on your list, look up the order's status and dates with Order Search.
    Step 2
    Keep the orders whose builder status changed to Complete since the last run.
    Step 3
    Post builder order number, account, task, actual end and total excl tax to your accounting webhook.

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 received orders” 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": "hyphensolutions.com/get_received_orders",
    "input": {
      "account": "Acme Homes - North Division"
    }
  }'
Example response
{
  "status": "completed",
  "data": {
    "orders": [
      {
        "builder_order_number": "4471208",
        "epo": false,
        "account": "Acme Homes - North Division",
        "subdivision_phase": "Northwind Ridge Phase 2",
        "lot_block": "Lot 37 / Block C",
        "job_address": "118 Juniper Bend, Round Rock, TX",
        "task": "Rough Plumbing",
        "total_excl_tax": 2865,
        "requested_start": "2026-11-16",
        "requested_end": "2026-11-17",
        "late": false
      }
    ],
    "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.

SupplyPro’s own options

Hyphen sells SupplyPro Connect to move orders, schedules and changes from BuildPro into your own accounting, ERP or scheduling software and to send acceptance, completion and notes back. It connects by REST API, SOAP API or CSV files over FTP and is set up with Hyphen's team. Hyphen publishes no price for it.

OptionWhat it coversWhat it takes
SupplyPro Connect, REST or SOAP APINew and future orders, schedules and changes into your system, and acceptance, completion and notes back to the builder.REST with JSON, or SOAP with XML on xCBL 4.0. Set up with Hyphen's SupplyPro Connect team; price on request.
SupplyPro Connect, CSV files over FTPOrder data delivered as CSV files over FTP for import into your accounting, ERP or scheduling software.Set up with Hyphen's SupplyPro Connect team; price on request.
SupplyPro by handThe Orders tab: Received Orders, To Do, Pending Approval, Completed Orders, Alerted Orders and Order Search, with printable POs and delivery tickets.A SupplyPro user ID with access to each builder account.

Read on November 12, 2026: SupplyPro Connect, SupplyPro Connect brochure, SupplyPro Help: Order Management.

Signing in to SupplyPro

SupplyPro signs you in with a username and password on its login page, with cookies enabled. One user ID reaches the builder accounts its security settings allow. With Fous you sign in once through SupplyPro's own login 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 has two statuses
O: shows the order's status in SupplyPro (Received, Accepted, Complete) and B: its status in the builder's BuildPro. B: Complete can release the PO for payment when the builder's back office is integrated.
Accepting several orders skips the email
Accept Selected Orders changes the status and notifies the builder, but sends no email acknowledgement. Receiving multiple orders this way is an optional module.
Reschedules wait for your answer
An accepted order the builder reschedules in BuildPro must be re-accepted or declined. The Orders tab keeps them in their own Pending Reschedules section.
Late means past the requested end date
An order is Late when its requested end date from BuildPro is before today. Received Orders highlights it with (Late).

More in Construction

Other industries: Ingram iPage, PayPal Business, FSA Partner Connect, National Grid US My Account, Deliveroo Partner Hub, Banorte en su Empresa.

Frequently asked questions

Yes, through SupplyPro Connect, which Hyphen's SupplyPro Connect team sets up with you. It offers a REST API with JSON, a SOAP API on xCBL 4.0 and CSV files over FTP for orders, schedules and changes, and sends acceptance and completion back. Hyphen publishes no price for it.

Pending Approval holds orders you have completed in SupplyPro that the builder has not yet completed in BuildPro. When the builder completes one, its builder status shows B: Complete, which can release the PO for payment if the builder's back office is integrated with BuildPro.

They are the requested (RS, RE), acknowledged (KS, KE) and actual (AS, AE) start and end dates. They share the Request / Acknowledged / Actual column of the order list.

Yes. The Orders tab lists orders from every builder account your user ID may view, and you can filter by account, subdivision, order status, order type, task filter and crew filter. Your security restrictions decide which builder accounts appear.

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

Put Hyphen SupplyPro 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 nextTrimble Unity ConstructGCPayOracle Textura Payment ManagementIngram iPageHow methods workHow workflows run

Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of Hyphen SupplyPro (Hyphen Solutions). 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.