---
title: Product configuration
description: Descriptive packaging, native bundle flags, and verified component readback.
sidebar:
  order: 7
---

The [generated reference](/reference) and [MCP catalog](/warehouse-mcp-tools.json)
share the registered operation inputs. Use IDs returned for your current organization;
an external SKU is not a Vault product ID. [Authentication](/authentication) explains
connection scope. The [contract-checked examples](/examples#product-configuration)
show synthetic request shapes.

| Operation | Customer authority | Result |
| --- | --- | --- |
| `GET /v1/organizations/{orgId}/product-configuration`, MCP `products_configuration_get` | Member, Admin or Owner | Exact bound identities, local packaging, stock and native relationships |
| `PUT /v1/organizations/{orgId}/products/{productId}/packaging`, MCP `products_packaging_configure` | Admin or Owner | Revision-checked local packaging receipt; physical stock stays unchanged |
| `POST /v1/organizations/{orgId}/products/{productId}/bundle-import`, MCP `products_bundle_prepare` | Admin or Owner | CSV for one layer of standalone components; `verified: false` |
| `PUT /v1/organizations/{orgId}/products/{productId}/bundle`, MCP `products_bundle_set` | Admin or Owner | Exact provider readback of the flag, without confirming component assignment |

Staff access requires current customer-setup authority. Staff native-flag changes
also require a current provider-resource grant for that specific customer; global
staff authority alone does not permit that provider write.

Carton and case ratios describe the same physical unit. For example, 1,000 boxes
at 20 boxes per carton and 10 per case mean 50 carton equivalents and 100 case
equivalents. Those are not additional stock or instructions to unpack. Actual
loose packs, potential packs from sealed boxes, and native bundle capacity remain
separate quantities. An unavailable stock count is `null`.

Receiving box and pack products remain standalone, including identities protected
by historical receiving receipts. Condition variants represent a printing and
condition; they are not packaging. Nested native bundles are unsupported.

Component preparation sends no provider write. The guided import follows provider
documentation; account-specific component assignment has not yet been verified.
Availability depends on your ShipStation account. Import the prepared file with
ShipStation's **Import Product Bundles**, then call the configuration read again.
Only exact active customer-bound component identities and quantities establish
that one-layer relationship. An absent, foreign or nested relationship stays
unverified. Flag success alone never establishes component success.

Both packaging and flag mutations require a submission key and the reviewed
revision. A stale revision refuses the change. A flag write whose effect or
readback is unknown keeps its durable claim: read the outcome and exact product
state; do not create a new submission key to retry it. See [Reliability](/reliability).
