Intake

Product description

The Intake product converts unstructured input, such as an email, a purchase order, or a spreadsheet, into a structured Cart, Quote Request, or Shopping List in commercetools. It reduces manual data entry for customer service, sales, and operations teams that receive requests as free text or files.

Intake accepts a natural-language prompt, file uploads, or both. It extracts line items, matches them to your commercetools Product catalog, and resolves the Customer, Business Unit, and Store from the input. The result is a standard commercetools resource that can be reviewed, edited, and processed with the regular APIs or in the Merchant Center.

Intake is available in two ways:

In the Merchant Center, users open it from the Carts, Shopping Lists or Quotes page, review the parsed Cart, and choose a next action such as freezing the Cart, creating a draft Quote, or a Shopping List.
Through the API platform, developers call a single stateless endpoint from their own systems, for example, from an email or ticketing integration.

Intake uses AI to interpret the data you provide, so its output must be reviewed before it is used. Products that cannot be matched and files that cannot be parsed are reported as warnings instead of failing the request. Your data is not used to train models.

Only Administrators of the relevant project organization in the Merchant Center can enable Intake. To enable Intake for a Project, submit a support request that includes the Project key.

Defined scope

Intake includes Intake in the Merchant Center and the Intake API endpoint for each Project where the feature is enabled.

Merchant Center users need the View and edit all: Agent Intake permission, and API clients need the manage_intake_agent:{projectKey} scope.

The following list links to the documentation pages representing the functionality made available by Intake.

API
- Cart and Order management
  - Intake
Merchant Center
- AI agents
  - Agent Registry
    - Intake

Notes to Defined scope

The following pages also provide relevant information for understanding the scope and usage of Intake: Merchant Center Permissions for Agents, Intake API scope, Intake API errors.

Model and data processing

Intake uses a large language model to interpret the input you provide. The model works with what is provided in your prompt: messages, any files you upload, and its own previous replies in that conversation. It does not have access to other files, accounts, or data unless you choose to add them. It accesses the Project data you choose to add in the large language models through a fixed set of tools, Customer search and product search, which we call the commercetools APIs. Everything Intake creates is a standard commercetools resource in your Project.

To deliver these capabilities, we may process personal data, such as contact details, usage statistics, user behavior, and any additional information submitted or created during feature usage.

Data may be processed by third-party providers per our List of Sub-Processors. Due to global AI architecture, data may be processed outside your hosting region and deployment regions may update over time.

Please note that your data is not used to train models. However, AI-generated content can be inaccurate, incomplete, or biased, so you should always check it before relying on or publishing it. AI also carries operational and security risks that can't be fully ruled out. If requested, your data will be deleted where technically feasible.

You can find more information on our privacy and security practices here or contact our Support Team.

Compliance

Intake processes personal data, such as the Customer email address and any personal data contained in uploaded files. The commercetools GDPR compliance guidance applies to the Carts, Quote Requests, and Shopping Lists that Intake creates, because they are standard commercetools resources.

Intake is covered by the Standard SLA for AI Agents, which commits to a minimum Availability of 99.0% and exclusions as described here. Intake output is generated by AI and provided as a draft; commercetools does not warrant or guarantee that extracted line items, Product matches, or resolved Customer, Business Unit, and Store assignments are correct or complete. The Customer is responsible for reviewing every Cart, Quote Request, or Shopping List created by Intake, including any warnings, before using it in a business process.

Compatibility

Intake is built on commercetools Platform and inherits its compatibility model.

commercetools APIs

commercetools uses continuous delivery to deploy updates multiple times a day. This means there are no fixed release cycles; features are released as soon as they are ready, and issues are corrected promptly.

The Cart, Quote Request, and Shopping List returned by Intake are standard commercetools resources, and the commercetools APIs used to work with them are versionless, removing the need for version upgrades. Individual fields or actions may change as part of API evolution. These changes will not break existing solutions but might require adjustments.

If additional undocumented fields are sent in API requests, these can conflict with future new field names and cause runtime errors. Avoiding this is the responsibility of the Customer.

SSL/TLS lifetime

To keep connections to the API secure at all times, SSL/TLS certificates are periodically renewed and replaced when adapting to newer security policies. A maximum of one certificate renewal per year is targeted. If security issues are found within encryption algorithms in use, certificates may be replaced more frequently.

Limits

Intake is subject to contractual limits in addition to the standard commercetools API limits. The specific allowances and overage rates are defined in your contract. Contact your commercetools representative for details.

The following limits apply to every Intake request.

Limit	Value
Files per request	Up to 3
Size per file	Up to 20 MB
Supported file formats	PDF, TXT, CSV, DOCX, XLSX, EML, Markdown, HTML
Entities created per request	Cart or Shopping List
API conversation model	Stateless; each call starts a new workflow run, and multi-turn conversation is not supported

Product description.css-c0cbbx{display:inline-block;}.css-c0cbbx >:disabled{pointer-events:none;}

Defined scope.css-c0cbbx{display:inline-block;}.css-c0cbbx >:disabled{pointer-events:none;}

Notes to Defined scope.css-c0cbbx{display:inline-block;}.css-c0cbbx >:disabled{pointer-events:none;}

Model and data processing.css-c0cbbx{display:inline-block;}.css-c0cbbx >:disabled{pointer-events:none;}

Compliance.css-c0cbbx{display:inline-block;}.css-c0cbbx >:disabled{pointer-events:none;}

Compatibility.css-c0cbbx{display:inline-block;}.css-c0cbbx >:disabled{pointer-events:none;}

commercetools APIs.css-c0cbbx{display:inline-block;}.css-c0cbbx >:disabled{pointer-events:none;}

SSL/TLS lifetime.css-c0cbbx{display:inline-block;}.css-c0cbbx >:disabled{pointer-events:none;}

Limits.css-c0cbbx{display:inline-block;}.css-c0cbbx >:disabled{pointer-events:none;}