Reference · built on requestConnectorCommerce & orders

Linnworks

Open orders, processed orders, stock levels, and returns across channels from the Linnworks API.

Request accessPricing ↗

About

Linnworks is a multichannel order and inventory management system. Orders from marketplaces and web stores land in one open-orders book, are processed against stock held in one or more locations, and move to processed orders once dispatched. The Linnworks API, called API 1, is a set of granular POST and GET methods grouped by service: Orders, OpenOrders, ProcessedOrders, Stock, Inventory, ReturnsRefunds, and others.

Through Fibric, an operator polls open orders and stock levels on a schedule, spots an order that is parked, unpaid, or short on stock, and proposes a note, a tag, a stock correction, or a refund for approval. Each approved change is made once and kept with its reason.

This is a reference listing. It documents what Fibric would read from Linnworks and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Open orders, paged, from Orders/GetOpenOrders and their ids from Orders/GetAllOpenOrders, with status UNPAID, PAID, RETURN, PENDING, or RESEND
  • Full order records from Orders/GetOrdersById and OpenOrders/GetOpenOrdersDetails
  • Dispatched orders from ProcessedOrders/SearchProcessedOrders, with received date, processed date, and the days between them
  • Order audit trails from ProcessedOrders/GetProcessedAuditTrail
  • Stock levels by SKU and location from Stock/GetStockLevel_Batch, low-stock reports from Dashboards/GetLowStockLevel, and locations from Inventory/GetStockLocations
  • Booked refunds and returns from ReturnsRefunds/GetActionableRefundHeaders and GetActionableRMAHeaders
  • Stock consumption between two dates and per-item change history from Stock/GetStockConsumption and Stock/GetItemChangesHistory

Proposed actions

  • Target capability: propose a note on an order through ProcessedOrders/AddOrderNote
  • Target capability: propose tagging or parking an order through Orders/ChangeOrderTag, using tags 1 to 6 or tag 7 for parked
  • Target capability: propose setting a SKU's stock level through Stock/SetStockLevel or adjusting it through Stock/UpdateStockLevelsBySKU
  • Target capability: propose a refund for approval through ReturnsRefunds/CreateRefund, then ReturnsRefunds/ActionRefund to send it to the channel
  • Target capability: propose cancelling an open order through Orders/CancelOrder

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Flag open orders that will miss dispatch

    The operator polls GetOpenOrders, compares each order's received date and status with the picking queue, and proposes a tag and a note on any order that is stuck.

    With Order Risk, Stalled Shipment

  • Stop overselling across channels

    GetStockLevel_Batch and GetLowStockLevel show SKUs running down. The operator proposes a stock level correction or a channel allocation change before a marketplace order lands with no stock.

    With Oversell Watch, Stockout Forecast

  • Move refunds through approval

    Booked refunds from GetActionableRefundHeaders are checked against the order and the return. The operator proposes ActionRefund for the ones that pass and explains the ones it holds.

    With Returns Triage, Concession Review

  • Reorder from consumption history

    GetStockConsumption between two dates gives the run rate per SKU. The operator proposes reorder quantities for the items whose stock will not last the supplier lead time.

    With Reorder Point

Requirements

  • A Linnworks account and a developer portal login under the account holder's email, or a developer account requested from Linnworks support
  • An application of type System Integration, installed on the account through its Installation URL to obtain the Permanent Token
  • A session refresh routine: the session token expires after 20 minutes of inactivity and is re-issued from the same Permanent Token
  • Calls made to the regional server the session returns, such as eu-ext.linnworks.net, rather than a fixed host
  • The permissions each method names, such as GlobalPermissions.OrderBook.OpenOrdersNode or GlobalPermissions.Inventory.Stock.StockWrite.ChangeStockLevelsNode
Authentication
An application registered in the Linnworks developer portal with an Application ID and Application Secret; installing it on the account yields a Permanent Token, which Auth/AuthorizeByApplication exchanges for a session token sent in the Authorization header.

Limits

  • Rate limits are set per method, 150 or 250 calls per minute in the reference, so open-order sweeps are paced per endpoint.
  • The API 1 reference lists no webhook or event subscription; change detection is by polling open orders, processed orders, and stock levels.
  • Some methods are marked deprecated, including ProcessedOrders/SearchProcessedOrdersPaged, so the connector tracks the changelog.
  • Linnworks calling out to your endpoints is reserved for Channel and Shipping Integration app types, not for a System Integration.

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Linnworks ↗

Questions and answers

Which application type does a Fibric connector use?
System Integration. Linnworks describes it as the type where your system initiates requests on its own schedule, for example a 3PL pulling open orders or a warehouse system pushing stock updates. Channel and Shipping Integrations work the other way round.
How long does a session last?
A session token expires after 20 minutes of inactivity. The connector calls Auth/AuthorizeByApplication again with the Application ID, Application Secret, and the same Permanent Token to get a new one.
Where are the API definitions?
Linnworks publishes Swagger 2.0 definitions for API 1 in its GitHub, and each reference page carries an OpenAPI 3.0 block. The documentation index at apidocs.linnworks.net/llms.txt lists every page in Markdown.
Ask about Linnworks

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Linnworks through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy