> ## Documentation Index > Fetch the complete documentation index at: https://docs.joinluminous.com/llms.txt > Use this file to discover all available pages before exploring further. # Update B2B product template > Rename a B2B Product Template, change its description, or add SKUs to it. Send at least one of `name`, `description`, `product_ids`, or `skus`; an empty body returns a 422. SKUs already on the template stay in place — `product_ids` and `skus` only add (SKUs already on the template are skipped). To remove SKUs, use `POST /b2b-product-templates/bulk-items`. The same eligibility rules as create apply: only active, non-discontinued standalone or master SKUs can be added, and any rejected SKU fails the whole request. Requires the permission to update B2B Product Templates. ## OpenAPI ````yaml /api-reference/build.yaml post /b2b-product-templates/{templateId} openapi: 3.0.0 info: title: Luminous API version: 1.0.0 description: API documentation for Luminous servers: - url: https://{companyName}.api.joinluminous.com/external/api/v1 variables: companyName: default: companyName description: Your company-specific subdomain security: [] tags: - name: Products description: Get and manage products - name: Pricing description: Manage price schedules, levels, and customizations - name: BOMs description: Manage Bills of Materials (BOMs) - name: Labels description: Label rendering via Labelary ZPL service - name: Companies description: Manage business accounts and their associated data - name: Contacts description: Manage contact information for individuals - name: Suppliers description: Manage suppliers (factories) — vendors used on purchase orders - name: Supplier SKUs description: Manage per-supplier SKU and unit-cost overrides for products - name: Locations description: Manage warehouses and locations - name: Inventory description: Get and adjust product stock levels - name: Lots description: Create, update, and delete product lots (batches) - name: Transfer Orders description: Manage transfer orders - name: Fulfillment Orders description: Manage fulfillment orders and picklists - name: Freight description: >- Freightview LTL freight — quotes, booking and documents for fulfillment orders - name: Fulfillment Priority Lists description: Configure fulfillment routing priority lists - name: Purchase Orders description: Get and modify purchase orders - name: Supplier Portal description: >- Read a supplier's response to a purchase order and control the one-click portal link - name: Receiving Reports description: Manage receiving reports - name: Payment Obligations description: Manage payment obligations for purchase orders - name: Sales Orders description: Manage sales orders and sales order shipments - name: Purgatory description: >- Inspect and resolve non-posted sales orders in the purgatory staging workflow - name: PickFlow Warehouse description: >- Warehouse-floor lookups for PickFlow — barcode resolution, bin and product stock, bin search, and receivables - name: PickFlow Shipping description: >- Provider-agnostic shipping rates, services, packages, and label purchase for PickFlow - name: Cycle Counts description: >- Create, drive, and post PickFlow cycle counts — batches, per-warehouse sessions, and CSV import/export - name: Print Stations description: List paired print stations and enqueue print jobs to them - name: Invoices description: Get and manage invoices - name: Work Orders description: >- Manage work orders — production lifecycle, steps, materials, links, shipments, and comments - name: Production Batches description: Group and manage work orders as production batches - name: Bills description: >- Accounts payable bill management, payments, attachments, allocations, and variance - name: Prepayments description: Manage vendor prepayments and applications - name: Vendor Credits description: Manage vendor credits and applications - name: Vendor Returns description: Manage vendor returns and credit generation - name: Customer Returns description: Manage customer returns (sales returns), receiving, and restock behavior - name: Stock Snapshot description: Point-in-time stock snapshots with export support - name: Consumption description: Consumption reports and exports - name: Inventory Aging description: Cost-layer-based inventory aging reports - name: Bills Reports description: Accounts payable bills aging reports - name: Forecast description: Materialized forecast data - name: Reports description: Close the books, inventory discrepancy, transaction COGS, and EDI reports - name: Tags description: Add/remove tags across various resources - name: Custom Fields description: Get and set custom fields across various resources - name: Currency description: Currency configuration, exchange rates, and conversion - name: Drive description: > Browse, upload, tag and manage files in your Luminous Drive. An API token sees the shared drive only, never My Files or restricted folders and files. Every write and download made through the API is recorded in the file's activity log (`GET /file-cabinet/files/{id}/activity`) with `actor_kind: api_token`. - name: Integration Mappings description: Manage integration mappings for external systems - name: Integration Field Mappings description: Manage field-level mappings between Luminous and external systems - name: Automations description: Create, test, and inspect automation rules and their runs paths: /b2b-product-templates/{templateId}: post: tags: - Products summary: Update B2B product template description: > Rename a B2B Product Template, change its description, or add SKUs to it. Send at least one of `name`, `description`, `product_ids`, or `skus`; an empty body returns a 422. SKUs already on the template stay in place — `product_ids` and `skus` only add (SKUs already on the template are skipped). To remove SKUs, use `POST /b2b-product-templates/bulk-items`. The same eligibility rules as create apply: only active, non-discontinued standalone or master SKUs can be added, and any rejected SKU fails the whole request. Requires the permission to update B2B Product Templates. operationId: updateB2bProductTemplate parameters: - name: templateId in: path required: true description: ID of the template schema: type: integer requestBody: required: true content: application/json: schema: type: object properties: name: type: string maxLength: 255 description: New template name. Cannot be blank when sent. description: type: string nullable: true description: New description. Pass `null` to clear. product_ids: type: array nullable: true description: Product IDs to add to the template. items: type: integer skus: type: array nullable: true description: SKU codes to add to the template. items: type: string responses: '200': description: The updated template content: application/json: schema: type: object properties: data: type: object properties: id: type: integer example: 12 name: type: string example: Private Label — West description: type: string nullable: true sku_count: type: integer description: Number of SKUs on the template example: 48 kit_count: type: integer description: Number of kits on the template example: 3 '401': description: Authentication credentials were missing or invalid content: application/json: schema: type: object properties: error: type: string example: Unauthorized message: type: string example: Authentication credentials are missing or invalid status_code: type: integer example: 401 '403': description: You do not have permission to perform this action content: application/json: schema: type: object properties: error: type: string example: Forbidden message: type: string example: You do not have permission to access this resource status_code: type: integer example: 403 '404': description: Template not found content: application/json: schema: type: object properties: message: type: string '422': description: >- Validation error (empty body, unknown SKU, or a product that cannot be added to a template) content: application/json: schema: type: object properties: message: type: string errors: type: object additionalProperties: type: array items: type: string security: - BearerAuth: [] components: securitySchemes: BearerAuth: type: http scheme: bearer description: >- Authenticate using a bearer token. To create a token, navigate to /settings/api-tokens and click Create API Token. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.