--- title: "Picqer Integration" description: "Connect AI agents to Picqer, a warehouse management system for e-commerce fulfillment. Agents create and process orders, manage products, customers, and picklists, and read warehouse and supplier data so order fulfillment keeps moving without manual data entry." url: https://flowrunner.ai/integrations/picqer-debesis date_modified: 2026-08-12T15:40:33-07:00 --- # Picqer [Logistics](https://flowrunner.ai/integrations/category/logistics-fulfillment) Connect AI agents to Picqer, a warehouse management system for e-commerce fulfillment. Agents create and process orders, manage products, customers, and picklists, and read warehouse and supplier data so order fulfillment keeps moving without manual data entry. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 19 actions · Basic auth · available [Picqer website](https://picqer.com/) · [Platform Documentation](https://picqer.com/en/api) · Capability data verified 2026-08-12 1. A webshop order clears payment and is ready for fulfillment 2. Agent creates the order in Picqer and processes it into picklists 3. Agent watches picklist status through the shift 4. Agent reads picked against ordered quantities on picklists reported finished 5. Agent separates genuine shorts from lines that were simply not scanned yet 6. Agent posts the short lines with product, quantity, and warehouse to the floor lead 7. Floor lead chooses to close short and ship partial, hold for restock, or split the order ## What This Integration Enables Picqer is the floor. The distinction matters because the moment an order is processed it stops being a record and becomes a person walking a warehouse with a cart. Everything upstream of that is reversible with a database write. Everything downstream costs labor, stock allocation, and packaging. So the useful automation here is not "create orders faster", it is putting the right work on the floor and getting an accurate answer back about what happened. FlowRunner agents sync orders in from a webshop or ERP, process them into picklists, cancel orders that should not be picked, keep the product catalog current, create and update customers, list picklists by status and warehouse, close finished picklists, and pull a printable picklist PDF for an operator. Warehouses and suppliers are readable so a workflow can route work to the right site and reference the right vendor. The API is scoped per account under your own subdomain and authenticates over HTTP Basic with the API key as the username, so credentials are per environment rather than shared across tenants. List endpoints return up to 100 results per page, which means any workflow that reports on the whole warehouse needs to page rather than assume the first response is the full picture. ### Without FlowRunner **Orders retyped into the WMS**: Someone copies webshop orders into Picqer, and the copy is where mistakes enter **Picking progress checked by walking**: Knowing how the shift is going means asking the floor or refreshing a screen **Short picks discovered at packing**: A missing item is found when the box is being sealed, after the label is bought ### With FlowRunner **Orders arrive already processed**: Paid orders become picklists without anyone rekeying an address or a line item **Progress visible where the team works**: Outstanding picks are posted into the channel the warehouse already watches **Shorts decided deliberately**: An incomplete pick becomes a choice between partial, hold, and split, made by the person who can see the shelf ## Use Case Scenarios ### Paid order to picklist without a keystroke An order is paid in [Shopify](https://flowrunner.ai/integrations/shopify) or [WooCommerce](https://flowrunner.ai/integrations/woocommerce). The agent maps the customer, creating them with Create Customer if they are new, calls Create Order with the lines and address, then calls Process Order to turn it into picklists. The warehouse sees work appear. Nobody retypes an address, which removes the single most common source of a misdelivered parcel in a small fulfillment operation. ### Outstanding picks surfaced where the team already looks On a schedule the agent calls List Picklists filtered to new and open statuses per warehouse and posts a short summary into [Slack](https://flowrunner.ai/integrations/slack): how many picks are outstanding, how old the oldest is, and which are for orders with a promised same-day dispatch. Where a paper pick is wanted, it calls Get Picklist PDF and files the document. The supervisor stops walking the floor to find out how the shift is going. ### Catalog and stock kept honest across systems Product data drifts when it lives in two places. The agent watches the master catalog and applies changes with Create Product and Update Product, then reads stock per warehouse back with Get Product to feed availability into the storefront and into reporting in [Google Sheets](https://flowrunner.ai/integrations/google-sheets). Where a product exists in one system and not the other, the agent raises it rather than inventing a record, because a silently created product is a product nobody owns. ## Human-in-Loop Highlight The gate sits on Close Picklist. Closing a picklist is the system declaring that the pick is complete, and that declaration flows straight into what ships and what the stock count says. The problem is that the picker knows something the API does not. When a line comes up short, the shelf is empty but the record says there were four, and the reason could be a miscount at receiving, a breakage, an item in the wrong bin, or stock already committed to another order. An agent watching for finished picklists cannot see any of that. If it closes on a rule, the order ships short, the customer gets a partial delivery they were not warned about, and the stock figure now disagrees with the shelf in a way nobody notices until the next count. So the agent stops on the shorts and asks: "Picklist 2214, warehouse Rotterdam, 11 of 12 lines picked. SKU BR-4408 short by 2 of 3. Order has a same-day promise. Close short and ship partial, hold the order for restock, or split into two shipments?" The floor lead answers from in front of the bin. This is [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) where the source of truth is physical and the system is only a description of it. 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 19 actions ### Products 4 - **List Products** Returns catalog products, up to 100 per page. Used to reconcile a master catalog against what the warehouse holds. - **Get Product** Returns a single product with stock per warehouse. Used to check availability before promising a dispatch date. - **Create Product** Adds a product to the catalog. Used to keep a new SKU available for picking as soon as it exists upstream. - **Update Product** Updates an existing product. Used to push description, barcode, and packaging changes without duplicate data entry. ### Orders 5 - **List Orders** Returns orders, filterable and paged. Used for reconciliation between the storefront and the warehouse. - **Get Order** Returns a single order with its lines and status. Used when a workflow needs the full detail on one order. - **Create Order** Creates an order in the warehouse system. Used to move paid webshop or ERP orders into fulfillment automatically. - **Process Order** Turns an order into picklists and puts the work on the warehouse floor. Used as the deliberate boundary between data and physical labor. - **Cancel Order** Cancels an order so it will not be picked. Used when a payment reverses or a customer withdraws before the work starts. ### Customers 4 - **List Customers** Returns customers in the account. Used to find an existing record before creating a duplicate. - **Get Customer** Returns a single customer. Used to confirm addresses and contact details before an order is created. - **Create Customer** Creates a customer record. Used during onboarding from a CRM or storefront. - **Update Customer** Updates an existing customer. Used to keep delivery addresses current from the system where they are maintained. ### Picklists 4 - **List Picklists** Returns picklists filtered by status and warehouse. Used to report on outstanding picking work through the shift. - **Get Picklist** Returns a single picklist with its lines and picked quantities. Used to compare what was picked against what was ordered. - **Close Picklist** Marks a picklist finished. Used only after short lines have been resolved by a person, because it determines what ships and what the stock count claims. - **Get Picklist PDF** Returns the picklist as a base64 encoded PDF. Used to print a paper pick sheet or archive the document against the order. ### Warehouses 1 - **List Warehouses** Returns the warehouses in the account. Used to route orders and reporting to the right site. ### Suppliers 1 - **List Suppliers** Returns the suppliers in the account. Used to reference the right vendor in restock and purchasing workflows. ## Frequently Asked Questions ### What can FlowRunner do with Picqer? FlowRunner agents can run List Products, Get Product, and Create Product in Picqer, plus 16 more actions. ### Does connecting Picqer to FlowRunner require OAuth? No. Picqer connects to FlowRunner with basic authentication (a username and password), no OAuth flow required. ### Can Picqer trigger a FlowRunner workflow automatically? Picqer doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Picqer?** This integration exposes Picqer to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/picqer-debesis. Site index: https://flowrunner.ai/llms.txt