--- title: Quickbutik API Integration on Truto slug: quickbutik category: E-Commerce canonical: "https://truto.one/integrations/detail/quickbutik/" --- # Quickbutik API Integration on Truto **Category:** E-Commerce **Status:** Generally available ## MCP-ready AI tools Truto exposes 20 tools for Quickbutik that AI agents can call directly. - **list_all_quickbutik_settings_preorders** — List the preorder options configured for the quickbutik store. Options can be assigned to products and variants to signal pre-order availability and estimated delivery windows. Returns: id, attributes. - **list_all_quickbutik_scripts** — List Quickbutik storefront scripts, or pass the optional id filter to fetch a single one. Returns a single script record when id is given, otherwise an array of records, each including its string id; remaining fields are defined by the upstream Script schema the docs reference by $ref. Max 500 per page. - **create_a_quickbutik_script** — Create a new Quickbutik storefront script. Returns the created script record including its string id, with the remaining fields defined by the upstream Script schema the docs reference by $ref. Required: name, content. - **update_a_quickbutik_script_by_id** — Update an existing Quickbutik storefront script by id, or create one with a specific id. Returns the updated script record including its string id, with the remaining fields defined by the upstream Script schema the docs reference by $ref. Required: id. - **delete_a_quickbutik_script_by_id** — Delete a Quickbutik storefront script by id. Returns a generic success acknowledgement — the upstream SuccessResponse schema, whose fields the Quickbutik docs do not enumerate. Required: id. - **list_all_quickbutik_orders** — List Quickbutik orders with optional search by customer name, email or order ID, plus date/status filtering and sorting. Returns: name, in, schema. Max 1000 per page. - **create_a_quickbutik_order** — Create one or more Quickbutik orders with customer, payment, and product details; new orders are always set to status unpaid. Returns a per-order results object keyed dynamically (create_1, create_2, …). - **quickbutik_orders_bulk_update** — Update one or more existing Quickbutik orders — change status, products, customer, payment, shipping, discounts, or metadata. Returns a per-order results object. Status options: paid, done, cancelled, unpaid. - **list_all_quickbutik_products** — List Quickbutik products with optional filters for product IDs, SKUs, search text, categories, visibility, gift cards, and modification date, with sorting. Returns product records including id, sku, title, price, qty, and variants. Note: the response shape varies — a direct array when the search parameter is used, otherwise a product wrapper or a single object when fetching by product_id or sku. - **create_a_quickbutik_product** — Create and add a product to the Quickbutik store by sending a product payload as JSON. Returns the created product record including id, sku, title, price, qty, and variants. The request body follows the ProductCreate schema documented in the Quickbutik API reference. Required: title. - **quickbutik_products_bulk_update** — Update products in the Quickbutik store by sending an array of update objects as JSON; each product is identified by product_id or variant_id, or directly by SKU/article number when unique. Returns the updated product record including id, sku, title, price, qty, and variants. - **quickbutik_products_bulk_delete** — Permanently delete a product from the Quickbutik store. This operation is non-reversible. Returns a results confirmation object. Required: product_id. - **list_all_quickbutik_products_counts** — Count the total number of products in quickbutik. Returns the total product count as count. This endpoint takes no parameters. - **list_all_quickbutik_categories** — List Quickbutik store categories, or pass category_id to fetch a specific category. Returns category records identified by id; remaining record fields are defined upstream in Quickbutik. Max 500 per page. - **create_a_quickbutik_category** — Create a new product category in Quickbutik. Returns the created category record, including its id and the category attributes defined by the upstream category schema. Required: name. - **list_all_quickbutik_paymentmethods** — List the payment methods configured for the QuickButik store. Returns the store's payment method records with fields defined upstream. Max 500 per page. - **list_all_quickbutik_shippingmethods** — List shipping methods configured for a Quickbutik store. Returns: shipping_id, name, price. Optionally pass shipping_id to fetch a single specific method. Max 500 per page. - **get_single_quickbutik_metadatum_by_id** — Get the metadata stored for a selected scope and id in Quickbutik. Returns the metadata payload for that record; the upstream documentation does not enumerate the response fields. Required: id, scope. - **create_a_quickbutik_metadatum** — Create metadata for a selected scope and metadata id in Quickbutik by adding a metadata payload to that record. Returns a success confirmation only; the upstream documentation documents no response body fields. Required: scope, metadata_id. - **update_a_quickbutik_metadatum_by_id** — Update the metadata for a selected scope and id in Quickbutik; sending an empty value deletes the corresponding metadata entry. Returns a success confirmation only; the upstream documentation documents no response body fields. Required: id, scope. ## How it works 1. **Link your customer's Quickbutik 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 Quickbutik.** The Proxy API is a 1-to-1 mapping of the Quickbutik 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 - **Offer Nordic e-commerce connectivity to your merchant customers** — Quickbutik powers thousands of D2C brands across Sweden, Norway, and Denmark. Adding it as a native integration lets your SaaS expand into the Nordic SMB market without building and maintaining a bespoke connector. - **Sync orders and inventory for WMS, ERP, and 3PL platforms** — Pull new Quickbutik orders into your fulfillment workflow and push status changes, tracking, and stock decrements back in bulk. This lets operational SaaS tools serve Quickbutik merchants without hitting per-record rate limits. - **Auto-install storefront widgets for MarTech and Reviews SaaS** — Instead of asking merchants to paste script tags, programmatically inject your pixel, popup, or review badge the moment they authenticate. This removes the biggest onboarding friction point for MarTech and CRO tools. - **Power PIM and catalog automation for scaling brands** — Let merchants manage products, variants, and categories in your PIM and push them into Quickbutik as the source of truth. Bulk product updates and deletes make it viable even for merchants with thousands of SKUs. - **Enable analytics, accounting, and BI syncs** — Regularly pull order and product data to hydrate dashboards, financial ledgers, or forecasting models. Preorder settings give inventory planning tools visibility into pre-sale windows alongside standard stock. ## What you can build - **Bulk order fulfillment sync** — Poll new orders, then use bulk order updates to write back tracking numbers and mark orders as done in batches — ideal for WMS and 3PL workflows. - **One-click storefront script injection** — Use the Quickbutik Scripts API to create, update, and remove your JavaScript widget on the merchant's storefront automatically when they connect or disconnect the integration. - **Two-way product catalog sync** — Create products and categories from your app, then keep stock levels, prices, and variants in sync using bulk product update and delete operations. - **Cross-system ID mapping via metadata** — Attach your internal IDs (ERP SKUs, warehouse bin codes, CRM contact IDs) directly onto Quickbutik products and orders using the metadata endpoints, eliminating fragile mapping tables on your side. - **Preorder-aware inventory forecasting** — Read preorder settings alongside product counts to distinguish sellable stock from pre-sale demand in your planning or replenishment dashboards. - **Payment and shipping method-aware checkout analytics** — Pull configured payment and shipping methods to enrich order data with context for reporting, reconciliation, or checkout optimization tooling. ## FAQs ### How does authentication work for Quickbutik through Truto? Truto handles the Quickbutik credential exchange and token storage for you. Your end users connect their Quickbutik store through Truto's connect flow, and your app calls the unified endpoints without managing API keys directly. ### Which Quickbutik resources are currently supported? The available tools cover Orders (list, create, bulk update), Products (list, create, bulk update, bulk delete, counts), Categories (list, create), Scripts (full CRUD), Metadata (get, create, update), Preorder settings, Payment methods, and Shipping methods. ### Can I update thousands of products or orders without hitting rate limits? Yes. Quickbutik exposes native bulk endpoints for product updates, product deletes, and order updates, which Truto surfaces directly. This lets you batch high-volume writes instead of firing one request per record. ### How do I store my own internal IDs against Quickbutik records? Use the Quickbutik metadata endpoints through Truto to attach custom key-value data (like your ERP item ID or CRM contact ID) to products or orders. This avoids maintaining a separate ID mapping table in your backend. ### Can my SaaS install its storefront widget automatically? Yes. The Scripts endpoints let you programmatically create, update, and delete script tags on the merchant's Quickbutik storefront, so merchants never have to paste code manually during onboarding. ### Is there a Unified API for Quickbutik, or is this a direct integration? Quickbutik is currently exposed as a direct integration through Truto's tool interface, not yet mapped to a Unified API. You get normalized auth, pagination, and error handling, while the resource shapes stay close to Quickbutik's native model. ## Related reading - [Connect Quickbutik to ChatGPT: Manage Catalog, Orders & Metadata](https://truto.one/blog/connect-quickbutik-to-chatgpt-manage-catalog-orders-metadata/) — Learn how to connect Quickbutik to chatgpt using Truto. Step-by-step guide to tool calling, API quirks, and autonomous workflows. - [Connect Quickbutik to Claude: Sync Inventory, Shipping & Payments](https://truto.one/blog/connect-quickbutik-to-claude-sync-inventory-shipping-payments/) — Learn how to generate a secure Truto MCP server for Quickbutik and connect it natively to Claude Desktop. Automate inventory, shipping, and bulk orders via LLM. - [Connect Quickbutik to AI Agents: Automate Orders & Store Scripts](https://truto.one/blog/connect-quickbutik-to-ai-agents-automate-orders-store-scripts/) — Learn how to connect Quickbutik to AI agents using Truto's /tools endpoint. Build autonomous e-commerce workflows for orders, products, and scripts.