InvuPOS

InvuPOS is the point-of-sale and back office used by establishments to run their menu, orders, inventory and stores. This connector links Claude to one InvuPOS branch so owners and managers can ask about their business in plain language and act on it, without opening the portal or using the API.

What you can do

Menu: list, search and update items, prices, taxes, categories, subcategories and modifiers; update many records at once.

Sales: sales and payment totals by date, items sold, invoices and the journal entry.

Inventory and recipes: ingredients, recipes, stock movements, the Kardex report, counts, adjustments, warehouses and transfers.

Purchasing: providers, requisitions and purchase orders, from draft to receiving.

Customers: list and add customers.

How it works You sign in with your InvuPOS login and choose which areas Claude may use and at what level. Read never changes data. Write and Destructive are granted explicitly and capped by your own API role. Each connection belongs to one branch, and you can lower its access or disconnect it at any time from Connected apps in the InvuPOS Developer Portal.

InvuPOS is moving its API to version 2. Areas already on v2 use it; the rest are served by the original InvuPOS API as "Legacy operations", which only an API Admin can turn on for a connection. As each area moves to v2, the connector switches to it with no change on your side.

Requirements An InvuPOS branch and a login with the Administrador or Franquiciado role, or with API access its branch's API Admin gave it.

Limitations Claude can use only the operations the InvuPOS API offers and you approve. It never moves money: payments and deposits can be read but not recorded. Lists are paginated, and very long answers are shortened and say how to get the rest.