Biyo POS

Connect AI agents to Biyo POS, a cloud point of sale platform for retail and restaurants. Agents sync the catalog and modifiers across stores, update order status and customer, raise purchase orders to suppliers, complete stock movements, and pull inventory and sales reports.

80 actions API key available

Biyo POS website ↗ Platform Documentation ↗

A scheduled stock transfer run starts, or a count from the warehouse system lands

Get Stock History and List Stock Movements show what has already been applied

Create Stock Movement opens a draft of the right type against the source store

Add Stock Movement Item adds each product line with its quantity

The draft is read back with Get Stock Movement and reconciled against the source count

The inventory manager receives the draft, its line count and the net change per product

A person releases Complete Stock Movement, which applies the change and cannot be undone

What This Integration Enables

Biyo POS is a point of sale system, and a point of sale system has an unusual property for something you automate: the terminal is the authority on what happened, and the API owns everything around it. That boundary is drawn deliberately in this connector, and it is worth knowing before you design a flow. The catalog is yours: products, categories, modifiers, modifier groups, discounts and tax rates are readable and writable, so a menu or a price list maintained in another system can be pushed into Biyo rather than retyped. Customers and customer groups are yours. Stores, terminals and printers are yours, which means a new site can be provisioned from a flow rather than configured by hand. Suppliers, purchase orders and stock movements are yours, and that is where the operational value concentrates. Reports are read only and comprehensive, covering sales summary, item sales, modifier sales, taxes, discounts, voids, shifts and an hourly sales heatmap.

Orders are the exception, and the catalog description of this connector overstates them. This integration does not create orders. Order line items and totals are produced by the POS terminal, not by the API, so what you get here is List Orders, Get Order and an Update Order that changes high level fields such as status and the associated customer. That is a genuinely useful surface for routing and reconciliation, and it is not an ordering API. Two smaller boundaries are worth stating alongside it: modifier group creation is not exposed, because both documented create endpoints build a modifier rather than a group, so groups are created in the Biyo back office and only read and updated here; and orders expose summarised payment information, meaning payment type names, totals, tips and refunded totals, with no action anywhere in the connector that reads or writes cardholder data. Configuration is two fields, a Store URL and an API Key, because Biyo is multi tenant and every store is served from its own subdomain with the REST API under /api/v1 on that host. The key travels as a Token authorization header and Verify Connection exists so a flow can confirm both before it depends on either. There are no triggers, and the reason is that Biyo publishes no webhook subscription surface, so change detection is polling: List Orders filtered by an open date range, List Stock Movements, or the report actions compared between runs. List responses arrive in the standard paged envelope with a next that is null on the last page. Agents keep the catalog, the purchasing and the reporting in step across stores. The write that changes what the shelf says is where human-in-the-loop oversight belongs.

Without FlowRunner

Counts reconciled in a spreadsheet Store counts are exported, compared by hand, and adjusted at the terminal days after the discrepancy appeared

Catalog changes made store by store A new item, its modifiers and its tax rate are entered separately in each location, and the third store's price does not match the first

Reporting pulled when somebody asks Sales, tax and shift figures are exported manually at month end, so a bad day is discovered several weeks later

With FlowRunner

Adjustments built as reviewable drafts A movement is created, populated line by line and read back before anything touches inventory

One catalog definition, applied everywhere Products, categories, modifiers, discounts and tax rates are written from a single source through the API

Reports on a schedule, not on request Sales, item, modifier, tax, discount, void, shift and hourly reports run daily and land where the team already looks

Use Case Scenarios

A catalog change that lands the same way in every store

A retailer maintains its product master somewhere other than the till, in a merchandising system or a shared base. When a new line is approved, the agent reads it, calls List Categories and List Tax Rates to resolve the category IDs and the tax rate the product should carry, and calls Create Product with the correct Tax Status and rate rather than letting a default decide how the item is taxed. Modifiers follow the same path: Create Modifier assigns an add on to one or more modifier groups, and because group creation is not available through the API the flow validates against List Modifier Groups first and stops with a clear message if the group a product needs does not exist yet. Price changes run through Update Product, which changes only the fields supplied, so a repricing flow does not accidentally clear a description. The whole run finishes with a read back through List Products so the diff that gets posted to the merchandising channel in Slack reflects what Biyo now holds rather than what the flow intended to write.

Purchasing that closes the loop between a supplier and the shelf

Stock runs low on a supplier's lines. The agent calls List Supplier Products for the supplier's catalog with its supplier specific pricing, builds the order with Create Purchase Order against the right supplier and store, and adds each line with Create Purchase Order Item, adjusting quantities with Update Purchase Order Item and dropping lines with Remove Purchase Order Item as the buyer refines it. Advance Purchase Order Status then moves the order through the configured workflow, from draft to shipped to accepted, on the evidence the flow can see: a supplier confirmation email, a delivery note, a scan at goods in. Because the status workflow is a sequence rather than a free assignment, each advance is an assertion that a real world step happened, so the flow only advances on evidence it can point at and asks a person when it cannot. When goods arrive, the inventory side takes over and the movement that records them is built as a draft rather than applied directly.

Yesterday, reported before the store opens

Every morning the agent runs Sales Summary Report and Item Sales Report for the previous day, adds Taxes Summary Report and Discount Summary Report for the finance view, and Void Report and Shifts Report for the operational one. The results are written to a tracking sheet in Google Sheets so the same figures feed the daily standup and the month end reconciliation without being pulled twice. Hourly Sales Heatmap Report supplies the staffing view, showing sales by hour and weekday and optionally scoped to one store, which is the report a rota is actually built from. The value here is not the export, it is the exception handling on top: a void count above the trailing average, a discount total that jumped, or a shift with no sales against it goes to the area manager as a question rather than as a row in a file, while the ordinary days simply land in the sheet.

Human-in-Loop Highlight

Complete Stock Movement is the operation to gate, and the vendor is explicit about why: completing a movement applies its quantity changes to inventory and cannot be undone. Everything before it is safe. Create Stock Movement opens a draft, choosing Stock In to add, Stock Out to remove, Stock Adjustment to set corrected counts or Stock Movement to transfer between stores with a destination store supplied. Add Stock Movement Item populates it a product line at a time. Cancel Stock Movement discards the whole thing. All of that is reversible right up to the moment it is not. Complete Stock Movement is the one call in this connector that changes what the shelf is believed to hold, and there is no compensating operation: an over applied adjustment is corrected by building a second movement in the opposite direction, which leaves both in the history and neither in agreement with the count. The errors that reach it are the boring kind. A count file with a units column and a cases column, and the wrong one is read. A transfer built against the source store when the destination was intended, so stock moves the wrong way between two sites that both then reorder. An adjustment type chosen as Stock Out when the source data expressed a corrected total, so a count of forty removes forty rather than setting forty. Each of those produces a valid movement that Biyo will complete without complaint, and the first evidence is a till that refuses a sale or a purchase order raised for stock already sitting in the back. So the agent builds the movement and then stops. It reads Get Stock Movement for the assembled draft and Get Stock History for what has already been applied to the same products, and posts to the inventory manager in Slack: "Stock Adjustment draft ready for Northgate, 34 lines, built from this morning's count file. Net change is negative 212 units. 3 lines move by more than 50 percent of current stock: Oat Milk 1L, 96 to 41; House Blend 1kg, 60 to 22; Paper Cups 12oz, 400 to 180. 1 product on the count file is not in the Biyo catalog and was skipped. Complete Stock Movement applies these quantities to inventory and cannot be undone. Complete all 34, complete the 31 routine lines and hold the 3 large ones, or cancel the draft?" A person answers once and the agent completes only what was released, cancelling the rest with Cancel Stock Movement so no half applied draft is left waiting. Advance Purchase Order Status sits behind a lighter version of the same gate, because advancing a purchase order to accepted asserts that goods arrived, and Create Store, Create Terminal and Create Printer join it during a site opening, since a terminal registered against the wrong store takes its sales with it. This is the digital andon cord placed on the one irreversible write in a point of sale connector.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via Slack

Human decides

Agent resumes with decision

Agent Capabilities

80 actions

Account

Verify Connection Returns the authenticated employee for the configured store API key. Use it to confirm that the store address and the key are both valid before a flow depends on either, since a wrong subdomain and a wrong key fail differently.

Catalog

List Products Returns a paged list of the store's catalog products, with a free text search across product fields.
Get Product Returns the full record for one catalog product, including pricing, categories, tax configuration and per store stock information.
Create Product Creates a catalog product. Supply one or more category IDs the product belongs to, and set tax behaviour with Tax Status and an optional tax rate ID rather than leaving it to a default.
Update Product Updates selected fields on an existing product. Only the fields you provide are changed, so a repricing flow leaves descriptions and categories alone.
List Categories Returns a paged list of the store's product categories.
Get Category Returns a single product category by ID.
Create Category Creates a product category. The colour labels the category tile in the POS interface, which is a staff facing detail worth setting deliberately.
Update Category Updates selected fields on an existing product category.
List Discounts Returns a paged list of the discounts configured for the store.
Get Discount Returns a single discount by ID.
Create Discount Creates a discount. A Percentage Off discount treats the value as a percent, while an Amount discount treats it as a fixed currency amount, and choosing the wrong one is the classic pricing bug here.
Update Discount Updates selected fields on an existing discount.
List Tax Rates Returns a paged list of the tax rates configured for the store.
Get Tax Rate Returns a single tax rate by ID.
Create Tax Rate Creates a tax rate, expressed as a percentage.
Update Tax Rate Updates selected fields on an existing tax rate.

Modifiers

List Modifiers Returns a paged list of modifiers, the add on options such as an extra shot or no ice that belong to one or more modifier groups.
Get Modifier Returns a single modifier by ID.
Create Modifier Creates a modifier and assigns it to one or more modifier groups. The groups must already exist, because group creation is not exposed through this API.
Update Modifier Updates selected fields on an existing modifier.
List Modifier Groups Returns a paged list of modifier groups, each bundling related modifiers that can be attached to products.
Get Modifier Group Returns a single modifier group by ID.
Update Modifier Group Updates the name of an existing modifier group. Creating a group is done in the Biyo back office rather than here.

Customers

List Customers Returns a paged list of customers in the store's customer database.
Get Customer Returns a single customer by ID, including the default address.
Create Customer Creates a customer record in the store's customer database, which is how a web form or a CRM feeds loyalty and receipts.
Update Customer Updates selected fields on an existing customer.
List Customer Groups Returns a paged list of the customer groups used to segment the database.
Get Customer Group Returns a single customer group by ID.
Create Customer Group Creates a customer group.
Update Customer Group Updates the name of an existing customer group.

Stores and hardware

List Stores Returns a paged list of the store locations on the account.
Get Store Returns a single store location by ID.
Create Store Creates a store location. Country is an ISO 3166-1 alpha-2 code such as US, GB or CA.
Update Store Updates selected fields on an existing store location.
List Terminals Returns a paged list of the POS terminals, meaning registers, across the account.
Get Terminal Returns a single POS terminal by ID.
Create Terminal Creates a register at a store, with Mode selecting the ordering interface the terminal runs. A terminal registered against the wrong store takes its sales with it, so this belongs in a reviewed provisioning flow.
Update Terminal Updates selected fields on an existing terminal.
List Printers Returns a paged list of the printers configured across the account.
Get Printer Returns a single printer by ID.
Create Printer Creates a printer. A kitchen display printer shows orders on a screen instead of printing paper tickets.
Update Printer Updates selected fields on an existing printer.

Orders

List Orders Returns a paged list of orders, filterable by an open date range, each with its line items, totals and any associated customer. With no trigger available, this filtered list is the polling read that detects new sales.
Get Order Returns a single order by ID with its line items, tax and discount totals, grand total and customer. Payment information appears as summarised payment types and tips, never as card data.
Update Order Updates high level fields on an existing order, such as its status or associated customer. Line items and totals are produced by the POS terminal and cannot be set through this action, which is also why this connector does not create orders.

Suppliers

List Suppliers Returns a paged list of the suppliers used for purchasing and inventory.
Search Suppliers Returns a paged list of suppliers filtered by a search term.
Get Supplier Returns a single supplier by ID.
Create Supplier Creates a supplier. Country is an ISO 3166-1 alpha-2 code.
Update Supplier Updates selected fields on an existing supplier.
List Supplier Products Returns a paged list of the products associated with a supplier, including supplier specific pricing, which is what a reorder decision should be priced from.
Associate Product With Supplier Associates a product with a supplier, recording supplier specific pricing and ordering details.
Disassociate Product From Supplier Removes the association between a product and a supplier.

Purchase orders

List Purchase Orders Returns a paged list of the purchase orders used to restock inventory from suppliers.
Search Purchase Orders Returns a paged list of purchase orders filtered by a search term.
Get Purchase Order Returns a single purchase order by ID.
Create Purchase Order Creates a purchase order for a supplier and a store. Add products to it with Create Purchase Order Item.
Update Purchase Order Updates selected fields on an existing purchase order.
Advance Purchase Order Status Advances a purchase order to the next status in the configured workflow, for example from draft to shipped to accepted. Each advance asserts that a real world step happened, so it belongs on evidence rather than on a timer.
List Purchase Order Items Returns the line items on a purchase order.
Create Purchase Order Item Adds a product line item to a purchase order.
Update Purchase Order Item Updates a line item on a purchase order.
Remove Purchase Order Item Removes a line item from a purchase order.

Inventory

List Stock Movements Returns a paged list of stock movements, meaning inventory transfers and adjustments, filterable by type, status, store and date range.
Get Stock Movement Returns a single stock movement by ID with its items. This is the read that lets a person review a draft before it is applied.
Create Stock Movement Creates a stock movement. Stock In adds inventory, Stock Out removes it, Stock Adjustment sets corrected counts, and Stock Movement transfers between stores with a destination store supplied. The type decides whether a quantity is a delta or a total.
Add Stock Movement Item Adds a product line to a stock movement while it is still a draft.
Complete Stock Movement Completes a stock movement and applies its quantity changes to inventory. This cannot be undone, which is why it belongs behind a person rather than behind a rule.
Cancel Stock Movement Cancels a stock movement before it is completed, discarding the draft rather than reversing an applied change.
Get Stock History Returns the historical record of stock changes across the store, which is the context a proposed adjustment should be read against.

Reports

Sales Summary Report Returns a sales summary for a date range, including totals and net payments.
Item Sales Report Returns sales totals per product for a date range.
Modifier Sales Report Returns sales totals per modifier for a date range, which is how add on attachment rates become visible.
Taxes Summary Report Returns collected tax totals grouped by tax rate for a date range.
Discount Summary Report Returns discount totals for a date range.
Void Report Returns a paged list of voided orders and items, the report most worth watching for exceptions rather than trends.
Shifts Report Returns a paged list of employee shifts for a date range.
Hourly Sales Heatmap Report Returns a heatmap of sales by hour and weekday for a date range, optionally scoped to one store. This is the report a staffing rota is actually built from.

Frequently Asked Questions

What can FlowRunner do with Biyo POS?

FlowRunner agents can run Verify Connection, List Products, and Get Product in Biyo POS, plus 77 more actions.

Does connecting Biyo POS to FlowRunner require OAuth?

No. Biyo POS connects to FlowRunner with an API key, no OAuth flow required.

Can Biyo POS trigger a FlowRunner workflow automatically?

Biyo POS doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Biyo POS

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us