VTEX connector for Claude

Yes. Each store connects with its own account name, App Key and App Token, and bills as one data source account. Agencies add every client's store the same way and name the store when they ask.

Not in this version. Customers live in VTEX Master Data, which this connector does not read, and Porter leaves out the customer name, email and address that come with each order.

Your store's. VTEX keeps order dates in UTC, and Porter dates each order in the time zone its sales channel declares. If a channel declares a zone Porter does not map yet, Claude gets an error naming it instead of orders moved to the wrong day.

Yes. The same Porter account and connection work in any AI tool that supports MCP, with the same store and fields.

Usually for one of three reasons. VTEX counts cancelled orders in sales totals until you filter by order status, so ask for invoiced orders for net sales. Order Value includes shipping and tax, while Line Revenue does not. And a day in Porter is the store's local day, not the UTC day.

VTEX lists at most 30 pages of orders per request, so Porter splits a long date range into smaller ones and then reads each order. A month of a large store can take a while the first time. Catalog and inventory questions read every SKU, so they are slower than order questions.

VTEX ignores the date filter for periods before the oldest order it still keeps and answers with recent orders instead. Porter checks every order against the dates you asked for and returns an error rather than recent orders labelled with old dates.

VTEX rejected the App Key and App Token twice in a row, for example because the key was revoked. Generate a new key pair in the VTEX admin and reconnect it in Porter. If VTEX answers 403 instead, the key works but its role cannot read that data.