---
title: QLS API Integration on Truto
slug: qls
category: E-Commerce
canonical: "https://truto.one/integrations/detail/qls/"
---

# QLS API Integration on Truto



**Category:** E-Commerce  
**Status:** Beta

## MCP-ready AI tools

Truto exposes 64 tools for QLS that AI agents can call directly.

- **list_all_qls_brands** — Get a list of brands.
- **get_single_qls_brand_by_id** — Get a brand. Required: id.
- **list_all_qls_companies** — Get a list of companies. The connector pages through all results.
- **get_single_qls_company_by_id** — Get a company. Required: id.
- **update_a_qls_contact_by_id** — Update a contact. Required: id.
- **list_all_qls_fulfillment_order_backorders** — List fulfilment orders in backorder. The connector pages through all results.
- **create_a_qls_fulfillment_order_product** — Create an order product. Required: order_id.
- **get_single_qls_fulfillment_order_product_by_id** — Get an order product. Required: id, order_id.
- **update_a_qls_fulfillment_order_product_by_id** — Update an order product. Required: id, order_id.
- **list_all_qls_fulfillment_orders** — List fulfilment orders, filterable by created time, shop integration and brand. The connector pages through all results.
- **get_single_qls_fulfillment_order_by_id** — Get a fulfilment order. Required: id.
- **create_a_qls_fulfillment_order** — Create an order. Required: brand_id.
- **update_a_qls_fulfillment_order_by_id** — Update an order. Required: id.
- **qls_fulfillment_orders_cancel** — Cancel an order. Required: order_id.
- **update_a_qls_fulfillment_product_barcode_by_id** — Update an extra barcode. Required: id, product_id.
- **delete_a_qls_fulfillment_product_barcode_by_id** — Delete an extra barcode. Required: id, product_id.
- **list_all_qls_fulfillment_product_barcodes** — Get a list of extra barcodes. Required: product_id.
- **create_a_qls_fulfillment_product_barcode** — Create an extra barcode. Required: product_id.
- **list_all_qls_fulfillment_product_master_cartons** — Get a master carton. Required: product_id.
- **create_a_qls_fulfillment_product_master_carton** — Create a master carton. Required: product_id.
- **update_a_qls_fulfillment_product_master_carton_by_id** — Update a master carton. Required: id, product_id.
- **delete_a_qls_fulfillment_product_master_carton_by_id** — Delete a master carton. Required: id, product_id.
- **list_all_qls_fulfillment_product_stock** — Get the stock of one fulfilment product. Required: fulfillment_product_id.
- **list_all_qls_fulfillment_product_stocks** — List the stock of all fulfilment products, filterable by created/modified time. The connector pages through all results.
- **list_all_qls_fulfillment_product_suppliers** — Get a list of suppliers for a product. Required: product_id.
- **create_a_qls_fulfillment_product_supplier** — Connect a supplier to a product. Connect a supplier to a product. Creates supplier if supplier does not exist. Required: product_id, supplierName.
- **delete_a_qls_fulfillment_product_supplier_by_id** — Disconnect a supplier from a product. Required: id, product_id.
- **list_all_qls_fulfillment_products** — List fulfilment products (SKUs stored at QLS), with stock, filterable by EAN, SKU and stock amounts. The connector pages through all results.
- **get_single_qls_fulfillment_product_by_id** — Get a fulfilment product. Required: id.
- **create_a_qls_fulfillment_product** — Create a product. Required: name.
- **update_a_qls_fulfillment_product_by_id** — Update a product. Required: id.
- **delete_a_qls_fulfillment_product_by_id** — Delete a product. Required: id.
- **qls_fulfillment_products_merge** — Merge other products into this product. Required: product_id.
- **list_all_qls_in_transit_purchase_orders** — List purchase orders in transit to the warehouse. The connector pages through all results.
- **create_a_qls_order_return** — Create a return for a fulfilment order. Required: order_id.
- **list_all_qls_parcel_products** — List the parcel service products (carrier products) of the company.
- **list_all_qls_product_backorders** — Get a list of products in backorder.
- **list_all_qls_product_service_points** — Get a list of service points for a product. Required: product_id, country, postal_code.
- **list_all_qls_purchase_orders** — List purchase orders (inbound deliveries), filterable by status and created/modified time. The connector pages through all results.
- **get_single_qls_purchase_order_by_id** — Get a purchase order. Required: id.
- **qls_purchase_orders_cancel** — Cancel a purchase order. Required: purchase_order_id.
- **create_a_qls_purchase_order** — Create a purchase order (announce an inbound delivery).
- **update_a_qls_purchase_order_by_id** — Update a purchase order. Required: id.
- **list_all_qls_returns** — List returns, filterable by status and created/processed time. The connector pages through all results.
- **create_a_qls_return** — Create a return. Required: brand_id.
- **get_single_qls_return_by_id** — Get a return. Required: id.
- **qls_returns_archive** — Archive a return. Required: return_id.
- **list_all_qls_service_points** — Get a list of service points. Required: country, postal_code.
- **list_all_qls_shipment_returns** — Get a return shipment for shipment. Required: shipment_id.
- **create_a_qls_shipment** — Create a parcel shipment (and its label). Required: brand_id, product_combination_id, receiver_contact.
- **qls_shipments_cancel** — Cancel a parcel shipment. Required: shipment_id.
- **list_all_qls_shipments** — Get a list of shipments.
- **get_single_qls_shipment_by_id** — Get a shipment. Required: id.
- **list_all_qls_shipping_methods** — List the shipping methods available for a sender, recipient and parcel measurements.
- **list_all_qls_suppliers** — Get a list of suppliers.
- **create_a_qls_supplier** — Create a supplier. Required: name.
- **get_single_qls_supplier_by_id** — Get a supplier. Required: id.
- **delete_a_qls_supplier_by_id** — Delete a supplier. Required: id.
- **update_a_qls_supplier_by_id** — Update a supplier. Required: id, name.
- **list_all_qls_webhook_types** — List the webhook event types.
- **list_all_qls_webhooks** — List webhooks. The connector pages through all results.
- **create_a_qls_webhook** — Create a webhook.
- **get_single_qls_webhook_by_id** — Get a webhook. Required: id.
- **delete_a_qls_webhook_by_id** — Delete a webhook. Required: id.

## How it works

1. **Link your customer's QLS account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app.
2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request.
3. **Call Truto's API to reach QLS.** The Proxy API is a 1-to-1 mapping of the QLS API.
4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field.

## Use cases

- **Embed 3PL fulfillment for e-commerce platforms** — Let your merchant users connect their QLS account and push orders directly from your storefront or OMS to QLS warehouses. Truto handles the auth and API quirks so you can ship a native fulfillment integration in days, not quarters.
- **Power returns management workflows** — If you build a returns portal or post-purchase platform, use the QLS returns API to create return shipments and detect warehouse arrivals so you can automate refunds and store credit for your merchant customers.
- **Enable real-time inventory sync for multichannel sellers** — Multichannel listing tools and PIMs can pull live stock from QLS and broadcast availability across marketplaces to prevent overselling, using Truto's unified webhooks and polling patterns.
- **Deflect WISMO tickets in support helpdesks** — Customer support and AI helpdesk vendors can query QLS shipment, backorder, and purchase order status to answer 'where is my order' questions automatically, with accurate ETAs sourced from the warehouse.
- **Automate inbound supply chain for ERP and procurement tools** — ERPs and procurement SaaS can create QLS purchase orders, manage suppliers, and track in-transit inbound shipments on behalf of merchant users without writing QLS-specific logic.

## What you can build

- **Order-to-fulfillment pipeline** — Create QLS fulfillment orders directly from your platform and sync status, tracking, and cancellations back to your UI via webhooks.
- **Live stock dashboard** — Surface real-time product stock levels from QLS warehouses with per-SKU breakdowns, backorder flags, and master carton details inside your app.
- **Returns automation workflow** — Trigger QLS return creation when shoppers submit a return request, then listen for warehouse receipt events to auto-refund or archive the return.
- **Service point selector for checkout** — Fetch nearby QLS service points by postal code and render pickup locations inside your checkout or shipping-rules product.
- **Purchase order and supplier manager** — Let merchants create purchase orders, manage suppliers, and track in-transit inbound shipments to QLS warehouses from inside your ERP or OMS.
- **Shipping label generator** — Generate QLS parcel labels on demand for merchants who self-fulfill but want QLS carrier rates across DPD, DHL, PostNL, and GOFO.

## FAQs

### How does authentication to QLS work through Truto?

QLS uses API key based authentication. Your end users provide their QLS API credentials once in Truto's connect flow, and Truto securely stores and injects them on every request — you never handle the keys directly.

### Which QLS objects can I read and write?

Truto exposes brands, companies, contacts, fulfillment orders and backorders, fulfillment products (with barcodes, master cartons, suppliers, stock), purchase orders, shipments, returns, service points, shipping methods, suppliers, and webhooks. Full CRUD is available where QLS supports it.

### Does the integration support real-time events?

Yes. You can call list_all_qls_webhook_types and create_a_qls_webhook through Truto to subscribe to QLS events like shipment updates, stock changes, and return arrivals, and receive them via Truto's normalized webhook delivery.

### Can I cancel orders, shipments, or purchase orders?

Yes. Dedicated endpoints exist for cancelling fulfillment orders, shipments, and purchase orders, as well as archiving returns, so you can expose full lifecycle control in your product.

### How fresh is inventory and shipment data?

You can either poll list_all_qls_fulfillment_product_stocks and shipment endpoints on your own cadence or subscribe to QLS webhooks for push-based updates. For most use cases, webhooks give near real-time freshness without rate-limit pressure.

### Can merchants use QLS only for shipping labels without warehousing?

Yes. The create_a_qls_shipment endpoint lets merchants who pack their own orders generate QLS parcel labels across its multi-carrier network, independent of QLS fulfillment orders.
