Skip to content

E-Commerce · Beta

QLS
API integration

Ship E-Commerce features without building the integration. Full QLS API access via Proxy and 60+ MCP-ready tools for AI agents — extend models and mappings to fit your product.

Built for specific customer use cases. Issues are resolved quickly.

Talk to us
QLS

Use Cases

Why integrate with QLS

Common scenarios for SaaS companies building QLS integrations for their customers.

01

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.

02

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.

03

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.

04

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.

05

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

Ship these features with Truto + QLS

Concrete product features your team can ship faster by leveraging Truto’s QLS integration instead of building from scratch.

01

Order-to-fulfillment pipeline

Create QLS fulfillment orders directly from your platform and sync status, tracking, and cancellations back to your UI via webhooks.

02

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.

03

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.

04

Service point selector for checkout

Fetch nearby QLS service points by postal code and render pickup locations inside your checkout or shipping-rules product.

05

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.

06

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.

SuperAI

QLS AI agent tools

Comprehensive AI agent toolset with fine-grained control. Integrates with MCP clients like Cursor and Claude, or frameworks like LangChain.

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.

Why Truto

Why use Truto’s MCP server for QLS

Other MCP servers give you a static tool list for one app. Truto gives you a managed, multi-tenant MCP infrastructure across 1050+ integrations.

01

Auto-generated, always up to date

Tools are dynamically generated from curated documentation — not hand-coded. As integrations evolve, tools stay current without manual maintenance.

02

Fine-grained access control

Scope each MCP server to read-only, write-only, specific methods, or tagged tool groups. Expose only what your AI agent needs — nothing more.

03

Multi-tenant by design

Each MCP server is scoped to a single connected account with its own credentials. The URL itself is the auth token — no shared secrets, no credential leaking across tenants.

04

Works with every MCP client

Standard JSON-RPC 2.0 protocol. Paste the URL into Claude, ChatGPT, Cursor, or any MCP-compatible agent framework — tools are discovered automatically.

05

Built-in auth, rate limits, and error handling

Tool calls execute through Truto’s proxy layer with automatic OAuth refresh, rate-limit handling, and normalized error responses. No raw API plumbing in your agent.

06

Expiring and auditable servers

Create time-limited MCP servers for contractors or automated workflows. Optional dual-auth requires both the URL and a Truto API token for high-security environments.

How It Works

From zero to integrated

Start with QLS in a free sandbox, usually ready within one business day. No boilerplate, no maintenance burden.

01

Link your customer’s QLS account

Use Truto’s frontend SDK to connect your customer’s QLS account. We handle all OAuth and API key flows — you don’t need to create the OAuth app.

02

We handle authentication

Don’t spend time refreshing access tokens or figuring out secure storage. We handle it and inject credentials into every API request.

03

Call our API, we call QLS

Truto’s Proxy API is a 1-to-1 mapping of the QLS API. You call us, we call QLS, and pass the response back in the same cycle.

04

Unified response format

Every response follows a single format across all integrations. We translate QLS’s pagination into unified cursor-based pagination. Data is always in the result attribute.

FAQs

Common questions about QLS on Truto

Authentication, rate limits, data freshness, and everything else you need to know before you integrate.

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.

QLS

Get QLS integrated into your app

Our team understands what it takes to make a QLS integration successful. A short, crisp 30 minute call with folks who understand the problem.