Sellercloud
E-commerceManage omnichannel e-commerce operations in Sellercloud. Agents read and create catalog products, orders, and customers, check inventory levels by SKU, and reconcile purchase orders and vendors across all sales channels from a single connection.
What This Integration Enables
Sellercloud earns its keep as the operational spine for multichannel sellers: the place where Amazon, eBay, and webstore activity collapses into one catalog, one inventory position, and one order stream. That only works if the ERP actually stays current, and keeping it current is exactly the kind of repetitive, structured work FlowRunner agents are built for. Agents read the catalog, check stock by SKU, create orders from external channels, and reconcile purchase orders, while your team handles the calls that need judgment. - Pull catalog products and inventory levels into spreadsheets, databases, or downstream systems on a schedule - Create orders in Sellercloud from storefronts, marketplaces, or manual intake without retyping - Check available stock across warehouses before any order is committed - Reconcile inbound purchase orders against vendors before reorder decisions get made - Feed order detail into fulfillment and customer notification workflows The writes are where discipline matters. FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) orchestration means an agent can do all the lookups and validation at machine speed, then pause and hand the decision to a person when an order looks wrong. The bigger payoff shows up when Sellercloud stops being an island. The same agent that writes an order can check the storefront, the fulfillment provider, and the reporting sheet in one flow, because in FlowRunner each connector is a capability an agent composes with the others. The ERP stays authoritative, and the agent does the diplomacy between systems that used to happen over copy and paste.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The webstore order that becomes an ERP order
A new order fires from [Shopify](/integrations/shopify). The agent calls Get Inventory for each SKU to confirm the warehouse can cover it, matches the buyer with List Customers, then calls Create Order with the source channel set so channel-level reporting stays honest. If any SKU comes back short, the agent holds the order and asks the operations lead whether to split the shipment or backorder. The approved order lands in Sellercloud with its assigned order ID, and a summary posts to [Slack](/integrations/slack).
The daily availability snapshot nobody has to export
Every morning, the agent calls List Available Inventory and pages through the full catalog. Quantities land in [Google Sheets](/integrations/google-sheets) as a dated snapshot, and any SKU that crossed its reorder threshold gets called out in a digest to the purchasing channel. The team reads a live low-stock report instead of running the same export every day, and the thresholds live in the flow where anyone can adjust them.
Unshipped orders routed to fulfillment
On a recurring sweep, the agent calls List Orders filtered to unshipped status, then Get Order for full line items and shipping addresses. Each order is handed to [ShipBob](/integrations/shipbob) for fulfillment. Orders with incomplete addresses or mismatched line items do not go quietly into the queue: they surface to a person with the exact discrepancy named, because a bad handoff to the warehouse costs a day, not a click.
Human-in-Loop Highlight
Create Order is the write that moves real goods. Once an order enters Sellercloud it flows toward picking, packing, and carrier pickup, and unwinding a wrong order means clawing it back from a warehouse process built to move fast. So agents in FlowRunner treat Create Order as a gated step: the agent assembles the order, runs the stock check with Get Inventory, and when anything is off, quantity short, address suspect, customer unmatched, it posts the full order detail to the operations lead and waits. The person approves, edits, or rejects. Orders that pass every check flow straight through. The ones that would have become a warehouse problem become a thirty-second decision instead.
Agent Capabilities
10 actionsCatalog
2- List Products Lists catalog products with pagination and a keyword filter that matches SKU, product name, or manufacturer SKU. The discovery step before any per-product work.
- Get Product Retrieves full detail for a single SKU: name, manufacturer info, pricing, weights and dimensions, and available quantity. Used to enrich orders and sync catalog data downstream.
Orders
3- List Orders Lists orders with filters for status, source channel, and creation date range. The sweep behind fulfillment queues and channel reporting.
- Get Order Retrieves a single order in full: line items, quantities, pricing, status, customer, addresses, and shipping method. The context step before fulfillment handoffs and exception reviews.
- Create Order Creates a new order with a source channel, line items, and a shipping address, returning the assigned order ID. The write this page's human gate exists for.
Inventory
2- Get Inventory Retrieves available, physical, and reserved quantities for a single SKU across warehouses. The check that runs before any order is committed.
- List Available Inventory Lists available quantities across products with pagination. The bulk read behind daily snapshots and low-stock reporting.
Customers and Suppliers
3- List Customers Lists customers with pagination and a keyword search on name and email. Used to match buyers to existing records before creating orders.
- List Purchase Orders Lists purchase orders filtered by vendor and status. The read behind inbound stock reconciliation.
- List Vendors Lists vendors with pagination and a name search. Used to resolve a vendor ID before filtering purchase orders.
Frequently Asked Questions
What can FlowRunner do with Sellercloud?
FlowRunner agents can run List Products, Get Product, and List Orders in Sellercloud, plus 7 more actions.
Does connecting Sellercloud to FlowRunner require OAuth?
No. Sellercloud connects to FlowRunner with session-based authentication, no OAuth flow required.
Can Sellercloud trigger a FlowRunner workflow automatically?
Sellercloud doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Sellercloud
$100 in credits. No card required. Connect in minutes.