SOS Inventory

SOS Inventory is inventory, order and manufacturing management built on QuickBooks Online. Agents manage items, sales orders, purchase orders and builds, read bills of materials, and keep stock, lots and serials in step with the books.

Verified 121 actions OAuth available

SOS Inventory website Platform Documentation Capability data verified 2026-08-26

A paid order arrives from the storefront or the marketplace channel

Agent reads the customer, the lines, the quantities and the promised ship date

Query Items confirms every line is stocked at the location the order will ship from

Create Sales Order records the commitment, then Create Pick Ticket sends the work to the floor

Create Shipment relieves the stock and Create Invoice raises the bill that reaches the accounting system

The shipment reference and the invoice number post back onto the storefront order

A person decides what happens to a line the location cannot fill by the date that was promised

What This Integration Enables

SOS Inventory is the physical goods layer that sits on top of QuickBooks. The accounting system knows what things cost. SOS knows where they are, how many, in which lot or against which serial number, what they were assembled from, and which document moved them. That division is the reason a flow touching SOS is usually a flow that spans two or three systems. It is also why this connector covers the whole surface rather than a convenient slice of it: twenty four record types with full create, read, update, delete and query on each, plus the bill of materials behind an assembly.

Two properties of this API shape every flow built on it. The vendor's update is a PUT that replaces the entire record and clears every field the request leaves out, silently and with a success response. This connector reads the current record first and merges your changes over it, so a partial update stays partial, and blanking a field on purpose has to be asked for by name. Its throttle is the same shape of hazard, since a breached rate limit answers with a success status rather than an error, and the connector inspects the body and raises instead. SOS publishes no webhooks, so flows here are driven by a schedule or by an event in another system rather than by the inventory system announcing itself. Where a write consumes material or ends a document, human-in-the-loop is the default.

Without FlowRunner

Two systems and one typist Orders are keyed into the inventory system by hand, and the gap between it and the storefront turns up at month end

A partial update that erases An update sent with only the changed field clears everything left out, and the response reports success

Production recorded after the fact Components come off the shelf on the floor, and the system hears about it whenever somebody gets round to entering it

With FlowRunner

Orders arrive as documents A paid order becomes a sales order, a pick ticket, a shipment and an invoice without anyone retyping a line

A partial update stays partial Every change reads the current record first and merges over it, so a field nobody named keeps the value it had

Production recorded as it happens The build is written when the work is finished, with its components and lot assignments named at the time

Use Case Scenarios

Order to cash without a second person typing it

A paid order from Shopify reaches the flow. The agent resolves the buyer with Query Customers, creating one with Create Customer only when no match exists, then writes Create Sales Order with the lines mapped to SOS item ids. Create Pick Ticket sends the work to the floor. When the pick is confirmed, Create Shipment relieves the stock and Create Invoice raises the bill that flows through to the accounting system. The shipment and invoice references post back onto the storefront order, and a row lands in Google Sheets for the daily check. The lines the flow could not resolve to an item are the only thing a person sees.
Purchasing that closes its own loop

A reorder point is breached, or a demand report says it will be. The agent runs Query Vendors for the preferred supplier, calls Create Purchase Order with the quantities, and posts the order to the buyer for approval before it is sent. When the delivery arrives, Create Item Receipt records what actually turned up against the purchase order, which is what puts the stock into SOS. A short delivery is not silently accepted: the agent compares the receipt against the order lines and raises the difference with the buyer, who decides whether to chase, part receive, or close the order short. Goods going back to the supplier are recorded with Create Return To Vendor so the ledger and the shelf keep agreeing.
A work order that becomes a build with the right lots on it

Production finishes a run. The agent reads the work order with Get Work Order and the recipe with Get Item Bill Of Materials, works out which components and quantities the build should consume, and checks Query Lots and Query Serial Numbers for what is actually available to assign. It assembles the whole build, with the finished item, the component lines, the location and the lot assignments, and presents it. It does not write it. The person who ran the job confirms what came off the shelf, and the agent calls Create Build with exactly what was confirmed.

Human-in-Loop Highlight

Create Build is the operation on this connector with the least forgiving arithmetic. It consumes the component quantities named on it and produces the finished item, which means stock moves in two directions at once and lot and serial assignments are bound to a unit that will ship to a customer. The natural instinct is to say the undo exists, because Delete Build is right there in the action list. It is not that simple. SOS answers a refused delete with an HTTP 200 carrying a status object rather than an error, so a delete that will not be allowed does not look like a failure at the protocol level. This connector reads that status and raises rather than reporting a success that did not happen, which is exactly how an agent finds out that its undo was declined: after the build, not before. So the agent does the reading, the arithmetic and the lot matching, and then stops. It posts what it intends to consume, from which lots and at which location, and waits for the person who watched the work happen to confirm it. Assembling the build is machine work. Consuming the material is not.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

121 actions

Items and Inventory

Query Items Lists items across the account. The catalog record every stock movement points back at, whether it is stocked, non stocked, a service, an assembly or a kit. Paging here is a row offset into the whole result set rather than a page number, which every list operation in this connector shares.
Create Item Creates an item. Referenced customers, vendors and items are named by id and are never created inline.
Get Item Supplying a location changes the quantity figures to that location rather than to the whole company, and the response carries the syncToken an update needs.
Update Item Changes an item. Price, reorder point, item type and the accounts it posts to all live on this record.
Delete Item Removes an item from the catalog. Anything that still refers to it is why the call may be refused.
Get Item Bill Of Materials Reads the bill of materials behind an assembly or kit item, one line per component with its quantity and cost. The vendor marks this route beta, and an item that is not an assembly or a kit has no bill of materials to return.
Query Adjustments Lists inventory adjustments across the account. The correction that reconciles counted stock against recorded stock, and where a breakage or a found box gets written down.
Create Adjustment Creates an inventory adjustment. The quantities on it move stock as soon as it is written.
Get Adjustment Reads one inventory adjustment by id, with every attribute the record carries.
Update Adjustment Changes an inventory adjustment. Changing a line changes the stock the adjustment moved, so read the current lines before sending new ones.
Delete Adjustment Removes an inventory adjustment, which puts back the quantities it moved.
Query Lots Lists lots across the account. The batch a tracked item was received or built in, which is what a recall or an expiry check follows.
Create Lot Creates a lot. Used when a receipt or a build needs a batch that does not exist yet.
Get Lot Reads one lot by id, with every attribute the record carries.
Update Lot Changes a lot. Expiry dates and batch references are the fields that usually move here.
Delete Lot Removes a lot. Movements already recorded against it are why the call may be refused.
Query Serial Numbers Lists serial numbers across the account. The individual unit record behind a serialized item, which is how one physical thing is followed from receipt to customer.
Create Serial Number Creates a serial number. Used when units arrive with numbers the system has not seen before.
Get Serial Number Reads one serial number by id, with every attribute the record carries.
Update Serial Number Changes a serial number. Status and the notes carried against one unit are what this changes.
Delete Serial Number Removes a serial number record.

Sales

Query Sales Orders Lists sales orders across the account. The commitment to a customer that picking, shipping and invoicing all descend from.
Create Sales Order Creates a sales order. This is where an order taken on a storefront or a marketplace becomes a document the warehouse can work.
Get Sales Order Reads one sales order by id, with every attribute the record carries.
Update Sales Order Changes a sales order. A changed quantity, address or ship date belongs here, before picking starts rather than after.
Delete Sales Order Removes a sales order. Documents already raised against it are why the call may be refused.
Query Estimates Lists estimates across the account. The quote that becomes a sales order once the customer accepts it.
Create Estimate Creates an estimate. Used to turn a priced proposal into a record the rest of the flow can act on.
Get Estimate Reads one estimate by id, with every attribute the record carries.
Update Estimate Changes an estimate. Revised pricing and validity dates are the usual reason to touch one.
Delete Estimate Removes an estimate.
Query Invoices Lists invoices across the account. The billing document that carries through to the accounting system, which is why an invoice is rarely the right thing to edit quietly.
Create Invoice Creates an invoice. The bill it raises reaches accounting, so this is a write to be deliberate about.
Get Invoice Reads one invoice by id, with every attribute the record carries.
Update Invoice Changes an invoice. Editing a raised invoice changes what the customer was told they owe, so pair it with a note explaining why.
Delete Invoice Removes an invoice. This is a finance record, so treat a deletion as a correction that needs a reason behind it.
Query Sales Receipts Lists sales receipts across the account. The paid at the counter sale that skips the invoice step entirely.
Create Sales Receipt Creates a sales receipt. Used where payment and fulfillment happen at the same moment.
Get Sales Receipt Reads one sales receipt by id, with every attribute the record carries.
Update Sales Receipt Changes a sales receipt. Payment details and lines are what change here.
Delete Sales Receipt Removes a sales receipt.
Query Shipments Lists shipments across the account. The record of goods leaving, which is what actually relieves stock against a sales order.
Create Shipment Creates a shipment. Writing it relieves the stock on the lines it names.
Get Shipment Reads one shipment by id, with every attribute the record carries.
Update Shipment Changes a shipment. Tracking numbers and carrier details are the fields a fulfillment flow writes back.
Delete Shipment Removes a shipment, which returns the stock it relieved.
Query Pick Tickets Lists pick tickets across the account. The instruction the warehouse floor works from, and the document that turns an order into somebody walking with a cart.
Create Pick Ticket Creates a pick ticket. Used to release an order to the floor once stock has been confirmed.
Get Pick Ticket Reads one pick ticket by id, with every attribute the record carries.
Update Pick Ticket Changes a pick ticket. Changing a picked quantity here is how a short pick is recorded before it becomes a shipment.
Delete Pick Ticket Removes a pick ticket, which withdraws work the floor may already have started.
Query RMAs Lists RMAs across the account. The authorization a customer needs before goods can come back, raised before anything is shipped to you.
Create RMA Creates an RMA. Used the moment a return is agreed, so the goods arrive against a document rather than a surprise.
Get RMA Reads one RMA by id, with every attribute the record carries.
Update RMA Changes an RMA. Approved lines, quantities and the reason for the return are what move here.
Delete RMA Removes an RMA.
Query Customer Returns Lists customer returns across the account. The goods actually arriving back and the stock they put onto the shelf.
Create Customer Return Creates a customer return. The quantities should reflect what was inspected rather than what was expected.
Get Customer Return Reads one customer return by id, with every attribute the record carries.
Update Customer Return Changes a customer return. Adjusting a line changes how much stock came back, so treat it as a stock correction.
Delete Customer Return Removes a customer return, which reverses the stock it put back.
Query Customers Lists customers across the account. The account sales orders, invoices and returns are all placed against.
Create Customer Creates a customer. Query first and create only on a genuine miss, because a duplicate splits a history reporting depends on.
Get Customer Reads one customer by id, with every attribute the record carries.
Update Customer Changes a customer. Addresses, terms and contact details are the fields a CRM sync writes.
Delete Customer Removes a customer. Documents raised against them are why the call may be refused.

Purchasing

Query Purchase Orders Lists purchase orders across the account. The commitment to a vendor, and the document a receipt is later matched against.
Create Purchase Order Creates a purchase order. Raised from a reorder point or a demand plan, usually before a person has approved it.
Get Purchase Order Reads one purchase order by id, with every attribute the record carries.
Update Purchase Order Changes a purchase order. Quantities and expected dates change here while the order is still open.
Delete Purchase Order Removes a purchase order. A receipt already booked against it is why the call may be refused.
Query Item Receipts Lists item receipts across the account. The goods actually turning up against a purchase order, which is what puts purchased stock into the system.
Create Item Receipt Creates an item receipt. It should record what was counted on the dock rather than what the paperwork promised.
Get Item Receipt Reads one item receipt by id, with every attribute the record carries.
Update Item Receipt Changes an item receipt. Correcting a received quantity here corrects the stock the receipt added.
Delete Item Receipt Removes an item receipt, which takes the stock it added back out.
Query Returns To Vendor Lists returns to vendor across the account. The goods going back to a supplier, and the stock that leaves with them.
Create Return To Vendor Creates a return to vendor. Used for a faulty delivery or an over shipment, so the ledger and the shelf keep agreeing.
Get Return To Vendor Reads one return to vendor by id, with every attribute the record carries.
Update Return To Vendor Changes a return to vendor. Quantities and the reason given to the supplier are what change here.
Delete Return To Vendor Removes a return to vendor.
Query Vendors Lists vendors across the account. The supplier record purchase orders and returns to vendor are raised against.
Create Vendor Creates a vendor. Used when onboarding a supplier from a procurement system rather than by hand.
Get Vendor Reads one vendor by id, with every attribute the record carries.
Update Vendor Changes a vendor. Terms, lead times and contact details are the fields worth keeping in step with procurement.
Delete Vendor Removes a vendor. Open purchasing documents are why the call may be refused.

Production and Operations

Query Builds Lists builds across the account. The assembly that consumes components and produces a finished item, which is where a bill of materials becomes real stock.
Create Build Creates a build. It consumes the components it names and produces the finished item, which is the operation this page gates.
Get Build Reads one build by id, with every attribute the record carries.
Update Build Changes a build. Changing components or quantities after the fact changes what the build consumed.
Delete Build Removes a build. SOS can refuse this, and a refusal arrives carrying a success status rather than an error.
Query Work Orders Lists work orders across the account. The planned production job that a build is later executed against.
Create Work Order Creates a work order. Used to schedule production from demand rather than from a whiteboard.
Get Work Order Reads one work order by id, with every attribute the record carries.
Update Work Order Changes a work order. Dates, quantities and status are what a production schedule writes here.
Delete Work Order Removes a work order.
Query Processes Lists process transactions across the account. The conversion step that turns one set of items into another without a full assembly.
Create Process Creates a process transaction. Used for cutting, blending, repacking and the other steps that change what an item is.
Get Process Reads one process transaction by id, with every attribute the record carries.
Update Process Changes a process transaction. Inputs and outputs are the arrays that move, and sending one replaces it.
Delete Process Removes a process transaction.
Query Jobs Lists jobs across the account. The container that groups costs and activity under one piece of work.
Create Job Creates a job. Used where profitability is measured per project rather than per order.
Get Job Reads one job by id, with every attribute the record carries.
Update Job Changes a job. Status, dates and the customer a job belongs to are what change here.
Delete Job Removes a job.
Query Transfers Lists transfers across the account. The movement of stock between locations, which changes where something is without changing how much of it there is.
Create Transfer Creates a transfer. Used to rebalance stock between a warehouse and a shop, or between two warehouses.
Get Transfer Reads one transfer by id, with every attribute the record carries.
Update Transfer Changes a transfer. Quantities and the destination location are the fields that move.
Delete Transfer Removes a transfer, which puts the stock back where it started.

Rentals

Query Rentals Lists rentals across the account. The item that is out with a customer rather than sold to them.
Create Rental Creates a rental. Used where stock leaves the building on a clock instead of on an invoice.
Get Rental Reads one rental by id, with every attribute the record carries.
Update Rental Changes a rental. Due dates and rates are what a rental desk changes.
Delete Rental Removes a rental.
Query Rental Returns Lists rental returns across the account. The rented item coming back and rejoining available stock.
Create Rental Return Creates a rental return. Written when the item is checked back in, which is what makes it available again.
Get Rental Return Reads one rental return by id, with every attribute the record carries.
Update Rental Return Changes a rental return. Condition notes and the returned quantity are what change here.
Delete Rental Return Removes a rental return.

Frequently Asked Questions

What can FlowRunner do with SOS Inventory?

FlowRunner agents can run Query Items, Create Item, and Get Item in SOS Inventory, plus 118 more actions.

Does connecting SOS Inventory to FlowRunner require OAuth?

Yes. SOS Inventory connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.

Can SOS Inventory trigger a FlowRunner workflow automatically?

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

Start building with SOS Inventory

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us